The job
The rep steps off a call. A transcript waits. The station reads it and returns: structured summary, action items, next-step email. All in the rep’s voice. All grounded in what was actually said.
A call transcript is unstructured time. Forty-five minutes of actual speech. The station shapes it into decision-making material. What did the prospect say they need? What did they ask? What did the rep commit to? When should the next touch be? The rep has this in their head. The station forces it into prose the CRM can hold.
Plated well: the rep gets off a call. Clicks recap. Two minutes later the station returns a summary that reads like the rep wrote it. The rep reads it, makes one edit, and posts it to the CRM. The deal history is complete.
The recipe
All seven ingredients still apply. The leverage on this dish is Examples (Ingredient #4). Recap quality depends entirely on examples: three recaps you wrote in your house voice.
Training sets the recap format and tone (formal? casual? decision-focused?). Examples are the load-bearing ingredient because the station copies the structure and voice of the recaps you show it. Three good recaps beat one hundred generic instructions. Output Over Process is critical: tell the station what the recap should include (summary, action items, next-step email) and let it find the words. Guardrails protect against overstatement. Measurement is simple: does the rep edit the recap or post it as-is? If the rep is rewriting it, examples need sharpening.
How to build it
-
Collect three recaps you love. Recaps you wrote from past calls. In your voice. With structure you want to replicate (summary, key decisions, action items, next steps).
-
Annotate the structure. Mark where the summary ends and action items begin. Show the station the pattern.
-
Set the guardrails. The station never commits to a timeline without saying “pending approval.” The station never attributes claims without a quote from the call. The station never invents an action item that wasn’t discussed.
-
Set the output shape. “Three-paragraph summary, five bullet action items, one-paragraph next-step email.” Be specific.
-
Add the house style. What tone do your recaps carry? Formal? Casual? Decision-focused? Collaborative? Show it through examples.
-
Transcribe five recent calls. Have the station recap each. Have the rep review them. Edit one. Compare the original to your edited version. Does the station understand your voice? If not, sharpen the examples.
What breaks it
-
Generic examples. You show the station a template recap instead of three recaps you actually wrote. The station learns the template, not your voice. The output reads like a CRM vendor’s guidance, not your work.
-
Over-refinement in the guardrails. You try to cover every edge case. The station becomes rigid. Real calls have ambiguity. Let the guardrails cover only the things that must never happen (committing to timelines, inventing commitments). Let the station figure out the rest.
-
No voice examples. The station has three recaps but no sense of tone. Should this recap be collaborative or forensic? Cautious or confident? Examples carry tone. Show it, don’t describe it.
-
Absent review. The station creates recaps. Nobody reads them for two weeks. By week three, the station is generating recaps nobody is checking. The rep is rewriting them silently. Update the recipe. Bring the rep back to the pass.
When it’s working
The rep gets off a call. Reviews the station’s recap. Makes zero edits or one-line fixes. Posts it. By week three, the rep is barely reading them anymore because the station reads the call the way the rep does.
The side effect: deal history is now complete. Every call is documented in the CRM in your style.
Monday Move
Record your next call. Have the station transcribe and recap it. Read the recap. How close is it to what you would have written? One edit? Five? If it’s five, send the recap plus three recaps you’re proud of back to the station and retrain it on your examples.
Dish 3 of 10 on the Sales Station. Build-note leverage: Examples (Ingredient #4).