Sales Call Notes Template
Why sales calls get misremembered
Memory is a bad CRM. By the time you write up a discovery call, your brain has already edited it: the firm objection ("we tried this before and it failed") softens into "some concerns about adoption," the champion's offhand remark about who really signs off disappears entirely, and the next step you thought was agreed turns out to have never been said out loud. Then the deal stalls, and nobody can reconstruct why — because the record of the call is a summary of your hopes, not of their words.
Sales call notes exist to prevent exactly that. This template separates what discovery actually has to capture into six parts: the pain in the prospect's own words, their current situation, budget and authority as actually stated, the decision process, objections recorded verbatim with timestamps, and next steps that were confirmed on the call rather than assumed after it. Copy it and fill it in within thirty minutes of hanging up.
The sales call notes template (copy and paste)
Blank template
# Sales Call Notes — [Company / account] · [Call type & stage] **Date:** **Rep:** **Call type:** discovery / demo / follow-up / negotiation **Deal stage before call:** → **after call:** **Recording consent:** given · how (verbal on recording / other) ## Attendees & their roles in the decision - [Name] — [title] — role in decision: champion / economic buyer / end user / blocker / unknown ## Snapshot (2–3 lines, written first) - ## The pain — in their words - Pain: … | How they described it: "…" [00:00:00] | Cost of leaving it unsolved: … ## Current situation / status quo - What they use today, what is broken about it, who feels it most: … ## Budget & authority - Budget: stated amount / range / unknown | Whose budget: … - Approval threshold (what needs a higher signature): … ## Decision process - Who else must agree: … | Evaluation criteria named: … - Timeline / compelling event: … | What happens if they do nothing: … ## Objections & concerns (verbatim, with timestamps) - [00:00:00] "…" | Type: price / timing / trust / incumbent / internal priority | Resolved on the call? What would resolve it: … ## Questions they asked us - ## Commitments & next steps | Next step | Owner (us / them) | Date | Said & confirmed on the call? | |-----------|--------------------|------|-------------------------------| | | | | | ## My read (kept separate from the record) - What I think is really going on — labeled as my interpretation: …
Two sections do the heavy lifting. The verbatim objections section exists because an objection in the prospect's exact words ("we bought a system in 2023 and the team abandoned it") tells you what you actually have to overcome, while your paraphrase ("adoption concerns") tells you almost nothing. And the confirmed column in next steps is the difference between a pipeline and a wish list: if it wasn't said and answered on the call, it isn't a next step yet.
Example: filled in for a B2B discovery call
Filled example
# Sales Call Notes — Northgate Logistics · Discovery #1 **Date:** Thursday, Oct 16 **Rep:** Jordan (AE) **Call type:** discovery **Deal stage before call:** first conversation → **after call:** discovery complete, pilot scoping agreed **Recording consent:** given, verbal on recording ## Attendees & their roles in the decision - Rachel Nguyen — Director of Operations — champion; owns the problem and the ops budget - Tom Becker — VP Operations (joined for the last 15 minutes) — approves any pilot; likely economic buyer above Rachel's threshold ## Snapshot (2–3 lines, written first) Peak-season scheduling runs on spreadsheets two supervisors understand. Rachel has budget authority up to a threshold and wants a 2-site pilot in January. The real obstacle is not price — it is a failed 2023 rollout that burned the supervisors. ## The pain — in their words - Pain: peak-season overtime blows the labor budget every year | How they described it: "Last November we spent about $410K on unplanned overtime because the schedule lives in a spreadsheet only two supervisors actually understand." [00:07:38] | Cost of leaving it unsolved: another peak season on agency staffing at premium rates ## Current situation / status quo - Scheduling: shared spreadsheets + a whiteboard per site, 14 warehouses. Two supervisors are single points of failure; when one was out sick in August, a site ran a shift short for three days. ## Budget & authority - Budget: not a line item yet, but "anything under sixty doesn't need a CFO signature — it comes out of my ops budget" [00:26:14] | Budget owner: Rachel up to ~$60K; above that, CFO + procurement - Approval threshold: security review by IT required for any vendor touching workforce data, est. 2–3 weeks ## Decision process - Who else must agree: Tom approves the pilot; IT security reviews; supervisors at pilot sites must be involved from day one (Rachel insisted — see objection below) - Evaluation criteria named: supervisor adoption, no IT babysitting, works across all 14 sites if the pilot succeeds - Timeline / compelling event: peak-season post-mortem in January; budget locks in March — decision needed before then - What happens if they do nothing: "We survive it. We just pay for it." [00:29:47] ## Objections & concerns (verbatim, with timestamps) - [00:31:52] "We bought a system in 2023. Six weeks in, the supervisors were back on the whiteboard. I am not living through that again." | Type: trust / adoption | Resolved? No — what would resolve it: pilot scoped *with* supervisors, not rolled out at them - [00:38:20] "If this needs IT to babysit it, it's dead on arrival — they have no bandwidth this year." | Type: internal priority | Resolved on call? Partly — confirmed the pilot needs no integration; IT only does the security review ## Questions they asked us - Where is workforce data stored, and who can see individual-level schedules? (security review will ask again — send documentation) - How long until supervisors are trained? Her bar: "an afternoon, not a certification course." ## Commitments & next steps | Next step | Owner | Date | Confirmed on the call? | |-----------|-------|------|------------------------| | Send security questionnaire answers + pilot one-pager | Us (Jordan) | Fri Oct 24 | Yes | | Introduce IT security contact by email | Them (Rachel) | Wed Oct 22 | Yes | | Pilot scoping call with Tom + 2 site supervisors | Both | Tue Oct 28, 10:00 | Yes, invite sent | ## My read (kept separate from the record) - Rachel is a genuine champion but she is spending credibility earned before the 2023 failure. Tom is the real gate: if the scoping call doesn't win him, Rachel can't carry it alone. Win theme is supervisor adoption, not features — lead every next conversation there.
Notice the discipline in the example: the budget figure is a quote, not a guess; the biggest objection is the prospect's sentence, not a category; and every next step has a name, a date, and a "yes" in the confirmed column because it was actually agreed before the call ended.
How to use this template well
- Fill it in within thirty minutes. The snapshot and the verbatim sections decay fastest. If you only have five minutes, do those two plus next steps — the rest can be completed from the recording or transcript.
- Never paraphrase an objection. The moment you translate "I'm not living through that again" into "change-management concerns," you've thrown away the information. Objections are data in the prospect's language; keep them that way, with the timestamp so you can re-hear the tone.
- Label everyone's decision role — especially "unknown." Single-threaded deals die silently. If you don't know who the economic buyer is, writing "unknown" in the template is what forces the question on the next call.
- Review the notes, not your summary of them, before the next call. Read the objections and their exact words again in the ten minutes before you dial. The follow-up call should open where their words left off, not where your pitch deck starts. (We keep a short technique for exactly this: the 10 minutes after a sales call.)
- Field and in-person selling counts double here. Site visits, walk-throughs, trade-show conversations, and working lunches produce the richest discovery — and the least written record, because there is no call to "check later." Capture those in this template the same day, or they effectively didn't happen.
Reviewing the call, not your memory of it
Everything above gets easier if the call itself is recorded — not your impression of it. With CoHear, the conversation records on your iPhone: no bot joins your prospect's call, which matters when a customer won't accept one, and it works identically for the meetings that never touch a calendar invite — site walk-throughs, plant tours, coffee with a champion. You get the transcript with each quote tied to its timestamp and an organized summary in about 65 seconds for a one-hour call, so the verbatim objections section fills with checkable evidence instead of reconstruction. Sessions run 4+ hours, which covers a full day of on-site visits in one recording.
One honest note about scope: CoHear does not push fields into your CRM. This template is the bridge — two minutes to copy the snapshot, next steps, and objection quotes across, in the format above. What you gain for those two minutes is that what reaches the CRM was verified against what the prospect actually said.
If in-person conversations are most of your pipeline, see CoHear for sales. For internal team sessions rather than customer calls, the meeting notes template uses the same decisions-and-evidence structure.
FAQ
What should sales call notes include?
Six things: who was on the call and their role in the decision; the pain described in the prospect's own words; budget and approval authority as actually stated; the decision process and timeline; objections recorded verbatim; and next steps with an owner, a date, and confirmation they were agreed on the call. Notes missing the last two will produce a pipeline you can't trust.
How soon after a call should I write up my notes?
Within thirty minutes for the snapshot, verbatim quotes, and next steps — those are what memory rewrites first. The fuller sections (status quo, decision process) can be completed later the same day from the recording or transcript. Notes written the next morning are a reconstruction, and everyone who's done it knows it.
Should I tell the prospect I'm recording the call?
Yes — and get the consent noted, which is why the template header has a line for it. Recording laws vary (one-party vs. all-party consent), and enterprise prospects may have their own policies. In practice, a plain "I'm recording this so I capture your requirements accurately — is that okay?" is rarely refused, and the recording protects both sides when requirements are disputed later. This is not legal advice; follow your company's policy.
What's the difference between call notes and a CRM update?
Call notes are the full record: the quotes, the context, the read on the room. A CRM update is the distilled subset your company forecasts from — stage, amount, close date, next step. Write the notes first, from the call; then distill. Reps who write the CRM fields directly end up with neither: no record worth re-reading, and forecast data built on compressed memory.
