Generate next-best-action prompts for sellers
Sellers lose deals to things the buyer already told them — a need raised on call two that no one answered by call four. NEXT reads across every conversation on the account and works out what the rep should do next. It writes a short note into the deal record: the unaddressed need, the risk, and the recommended follow-up.
The detail isn't missing. It's logged in calls no one rereads. NEXT brings the relevant parts back to the surface, attached to the deal, the moment a new call is logged.
What the next-best-action note looks like
The output is a few lines written onto the deal record — not a report, not a dashboard tile. A rep reads it before the next touch.
Example next-best-action note
Example based on what a rep would see after a new call is logged on an active deal. Numbers are representative, not from a real account.
Account
Mid-market deal, about $84K ARR, in evaluation for six weeks.
Unaddressed need
The buyer asked about SSO and SCIM provisioning on two calls. Neither was answered.
Risk
The security reviewer joined call three and has not been followed up with. Deals that stall the security contact at this stage tend to slip a quarter.
Recommended follow-up
Send the SOC 2 report and the SSO setup doc to the security reviewer. Book a short provisioning walkthrough before the next pricing conversation.
What the buyer said
"We can't move forward until our security team signs off on SSO." — VP Engineering, call 2
"The last vendor took three weeks on provisioning and it killed our timeline." — IT lead, call 3
Signal strength
Strong. The security requirement appears in two calls and a follow-up email.
Caveat
Budget authority is still unconfirmed. The note marks this as an open gap, not a recommended action.
The rep didn't re-listen to three calls to find this.
How NEXT does this
NEXT reads the account's conversations — calls, the notes and emails attached to the deal, and prior touchpoints. It keeps a running record of what each buyer has said across the deal, so the requirement from call two is still available at call four. When a new call is logged, NEXT compares what was just discussed against that record, identifies what's unaddressed or newly risky, and writes a short next-best-action note onto the deal in the CRM. It can notify the rep where they already work. The note names the need, the risk, the suggested follow-up, and how well the signal is supported. The rep decides whether to act on it.
Why next-best-action runs on memory and luck today
Most CRMs already store every call. The problem is what happens to the detail between calls. A buyer raises a security requirement on call two; the rep notes it, moves on, and by call four it's a half-remembered line in a status meeting.
Pipeline dashboards report stage and close date. Open one and it shows what already happened, not what to do next on this deal. Ask a sales AI assistant and you get the loudest recent thread, not the requirement buried two calls back. Neither comes looking for the rep — the rep has to go looking, and on a full pipeline they don't.
So the guidance that exists in enablement's playbooks never meets the moment it applies to. The play is written for a stage; the buyer's actual objection sits in a transcript no one reopens.
A dashboard reports the number; it doesn't tell the rep what to do next on the deal in front of them. NEXT pushes the next move into the deal record, grounded in what the buyer actually said.
How this compares to the tools you already know
Approach | Where the guidance lives | What the rep does at decision time |
|---|---|---|
CRM activity fields and tasks | Scattered across notes and logged calls | Reads back through the history to reconstruct what's open |
Sales AI assistant | Behind a prompt; surfaces the most recent thread | Has to know what to ask, and ask it |
Static playbooks and battlecards | In a doc, organized by stage | Maps a generic play onto a specific deal manually |
NEXT | Written onto the deal record as the call is logged | Reads the next move, then decides whether to act |
What changes for you and your reps
If you own enablement, you stop shipping plays that reps never apply at the right moment. The play used to live in a doc and depend on the rep remembering it mid-deal. Now the relevant move arrives attached to the specific deal, with the buyer's own words behind it.
For the rep, the workday change is small and concrete. They open a deal before a call and the open need is already named — the SSO question that went unanswered, the security contact who went quiet. The deal looked routine until the unaddressed security requirement was attached to it. They don't reopen three transcripts to prep; they read three lines and act.
For a new rep covering a transferred account, this is the difference between an hour of archaeology and a usable starting point. The note carries the prior reps' context forward.
NEXT supplies the next move and the demand context behind it. Whether to run the play, and how to sequence it against everything else on the deal, stays with the rep.
Downstream effects
Coaching gets specific. Managers review the notes reps acted on and the ones they skipped, and coach on real decisions instead of generic stage advice.
Forecasting inputs improve. Unaddressed needs and stalled contacts are visible on the deal, so risk shows up in the record rather than in a manager's gut feel.
Enablement content gets a feedback loop. When the same unaddressed need recurs across deals, it tells you which play or asset is missing — not from a survey, but from what buyers keep asking.
Where the human stays in control
NEXT writes the note; the rep runs the deal. You set the bar for what gets written — how strong the signal must be before a follow-up is recommended, and whether weak or contradicted patterns are held back rather than surfaced. You can require a human to review notes before they're written to the record while you tune that bar. This is configuration work: deciding the threshold and the sources, not approving each note one by one.
What to get right before you turn it on
The note is only as good as the conversations NEXT can read. Confirm that calls are being logged and transcribed for the segments you care about — coverage that's strong for enterprise and thin for SMB will produce uneven notes, and reps will notice fast.
Set the threshold deliberately. Too low and routine chatter becomes a recommendation; too high and real risks stay quiet. Start stricter and loosen it.
Decide where the note lands and when. Writing it as the call is logged means the rep sees it during prep, not after the next call. And agree on what an unconfirmed gap looks like — a missing budget owner should read as an open question, not a confident instruction.
Where this breaks down
Thin or missing call data
If calls aren't recorded or transcripts are sparse, NEXT has little to reason over. The note will be vague, and a vague note erodes rep trust quickly. Fix coverage before scaling.
Contradicted signal
A buyer who says one thing on a sales call and another to a champion produces mixed signal. NEXT can mark this as contradicted rather than recommend a move — but only if you've set it to hold uncertain patterns instead of forcing a recommendation.
Notes that read as orders
If the wording sounds like a directive, experienced reps push back. The note works best framed as the unaddressed need plus a suggested move, leaving the judgment with the rep.
Stale accounts
On a deal that's gone quiet for months, the most recent call may not reflect the current state. Treat notes on dormant deals as lower-confidence until a fresh conversation is logged.
FAQ
How is this different from the AI summary my CRM already generates?
A call summary recaps the call that just happened. The next-best-action note reasons across the whole account history and tells the rep what to do next — the need raised two calls ago that's still open, the contact who went quiet, the follow-up that moves the deal. It's a decision aid attached to the deal, not a transcript recap.
Does NEXT decide the rep's next move?
No. NEXT surfaces the unaddressed need, the risk, and a recommended follow-up, with the buyer's own words behind it. The rep decides whether to act, how to sequence it, and how to read the relationship. NEXT brings the move to the decision; the call stays with the seller.
What does it need to produce a useful note?
Logged, transcribed conversations for the deal and consistent coverage across the segments you sell to. With sparse call data the note will be thin. The quality of the note tracks the quality of the conversations NEXT can read, so confirm coverage before rolling it out widely.
What happens when the signal is thin or contradicted?
You set the bar. NEXT can mark a pattern as weak or contradicted and hold it back rather than recommend a follow-up. The point is to keep low-confidence chatter from cluttering the deal record — reps stop trusting the note the first time it tells them to chase a non-issue.
Does this replace manager call reviews?
No. It makes them sharper. Managers can see which notes reps acted on and which they skipped, and coach on actual deal decisions instead of generic stage advice. The note is the rep's working guidance; the review is the coaching layer on top of it.
How does this help conversion specifically?
Deals slip when a real buyer need goes unanswered or a key contact goes cold. The note catches those before the next touch, so the follow-up that matters actually happens. It doesn't promise more closed deals — it reduces the number lost to detail that was already sitting in the call history.