A sales call notes template that captures the buyer's own words

The sales call notes template

Copy everything in this section. Square brackets mark the bits you replace. Keep the field names and keep the order. That is what lets you read forty notes quickly, and what lets a manager scan one in ten seconds without asking you three questions.

This is the discovery shape, the longest version. The demo, renewal and loss variants further down are the same skeleton with fields added or dropped.

Account and contact block. One field per line, at the top.

1. 1The problem, in their words. [Two or three sentences the buyer actually said, in quotation marks, about what is going wrong. Not your tidy summary of it. This is the single most valuable field on the page.]
2. 2What it is costing them. [The number, or the nearest thing to one: hours a week, credits issued, deals lost, overtime, fines, staff turnover. If they gave no number, write what they said instead and mark it as unquantified. Never invent the figure.]
3. 3What they have tried already. [Tools, a spreadsheet, an extra hire, a process change. And why it did not stick. This tells you what your proposal must not sound like.]
4. 4Who decides. [Three names, if you can get them: who signs, who can say no, and who has to use the thing every day. Mark which of them was on this call and which you have never met.]
5. 5How they buy. [The steps between "yes" and "signed": security review, legal, procurement, a pilot, a board date, a purchase order. Ask for them in order and write them in order, with rough durations.]
6. 6Timeline, and the event behind it. [A date, plus the thing that happens on that date: a contract ending, a busy season, an audit, a new site opening, a report someone has to present. A timeline with no event behind it is a wish, and it will slip.]
7. 7Budget. [What they pay today for this problem, which line the money comes from, whether it is already approved, and who approves it if not.]
8. 8Competitors mentioned. [Every name they said out loud, including the incumbent, "we would build it ourselves" and "we could do nothing". Note what they liked about each, in their words. What they liked is the bar you have to clear.]
9. 9Objections raised, and how you answered. [One line for the objection, one for your answer, one for whether they accepted it. Mark the ones you fumbled, honestly. Those are your next call's homework.]
10. 10Risks. [What could kill this. The champion is junior. The budget belongs to next year. The IT lead went quiet after minute twenty. Write the uncomfortable one down.]
11. 11Next step. [One action, one owner, one date and time, already in both calendars before you hang up. "Follow up next week" is not a next step.]
12. 12My read. [Two sentences. How likely you think this is, and what you are least sure about. This is the field your manager will actually read.]

• Account: [Company name, plus size in whatever unit matters to your product: staff, sites, engineers, seats, monthly volume]
• Date and time: [Tuesday 3 March 2026, 14:00 to 14:35 GMT]
• Call type: [Discovery / demo / pricing / security / renewal / loss debrief]
• Their side: [Name, job title, and what they actually control. One line each. Add "joined late" or "camera off, said nothing" if that is true]
• Our side: [Everyone from your team who was on the call]
• Source: [Inbound form / outbound sequence, which one / referral from NAME / event]
• Stage before: [Your CRM stage] Stage after: [Your CRM stage]
• Deal size, rough: [Amount, and the maths behind it: seats times price, sites, volume]
• Recording: [File name or link, if you recorded and told them you were recording]

A call note, a transcript and a CRM record are three different things

One call produces three documents, and mixing them up is why most sales notes are useless a month later. The transcript is every word. The call note is the short read. The CRM record is the handful of fields your pipeline report runs on.

Write the note for a stranger. Here is the test: if you left tomorrow, could the rep who inherits this account run the next call from your note alone, without listening to anything? If not, something is missing, and it is almost always the buyer's own words or a date on the next step.

Every field, and the shortcut that costs you the deal

Most bad notes fail in the same handful of places. Each bullet below is the field, then the mistake.

• The problem. People write their own paraphrase. "Wants better reporting" is a paraphrase of six different problems, and it is worth nothing in three weeks. Keep the quote.
• The cost. People round up, or write a number the buyer never said. If the buyer said "a lot", write "a lot" and put a question mark next to it. A made-up figure in a proposal is the fastest way to lose a champion's trust.
• What they tried. People skip this because it feels like history. It is the opposite: it tells you the exact story your solution has to beat, and it usually names the person who has already been burned once.
• Who decides. People write one name, the person they like. Write the signer, the blocker and the daily user separately. If two of the three are still strangers to you, that is the note's real headline.
• How they buy. People write "procurement" and stop. Ask how long each step took the last time they bought something, then write those durations down. That is how a close date stops being fiction.
• Timeline. People write the date the buyer wants and treat it as pressure on themselves. Write the event behind the date. No event, no deadline.
• Budget. People ask "do you have budget?" and get a yes. Ask what they pay now, and for which line it comes out of. A yes with no line behind it is not budget.
• Competitors. People write only the rival they fear. Write "do nothing" too, because that is the option that wins most deals. Note the incumbent's renewal date if there is one.
• Objections. People record the objection and not their own answer, so nobody can coach them and they answer it differently next time. Two lines, every time.
• Next step. People write an action with no date, or a date with no owner. Both fail the same way: nothing happens and neither side feels responsible. If the calendar invite went out during the call, say so in the note. Your follow-up email after the meeting should repeat that step back to the buyer word for word.

Write down what the buyer actually said, word for word

This is the habit that separates a note that helps from a note that gets filed and forgotten. Buyers describe their problem in language nobody in your company would ever choose. That language is worth more than your version of it, for three reasons.

It goes into the proposal. When your first page opens with the sentence the buyer said out loud, they read it as "they listened" rather than "here is our pitch". It goes into the internal case they build for you, because your champion has to sell this to a finance director you never meet, and their own words travel better than your marketing. And it goes into the objection you will get in six weeks, because most late objections are early sentences you paraphrased away.

A worked example. The buyer says: "We are flying blind between eight in the morning and six at night." The rep writes: "Wants better visibility." Two weeks later the proposal says "improved operational visibility", the finance director reads it as a nice-to-have, and the deal stalls on price. The original sentence had a shape, a time of day and a feeling in it. The paraphrase had none.

So keep quotation marks in your notes, and keep them accurate. If you cannot type fast enough while also running the call, record it. Recording the call, with the room told plainly at the start, is the only way to get verbatim quotes without splitting your attention. Apps like Noter AI do this from your phone even when the call is a face-to-face meeting in the buyer's office, and give you timestamps so you can jump back to the exact sentence later.

1. 1Say you are recording in the first thirty seconds, plainly, and carry on. In some places consent is a legal requirement, not a courtesy.
2. 2Type only quotes during the call. Nothing else. Quotes and the odd number. Everything else can wait.
3. 3Leave the last five minutes for the next step, agreed out loud and put in both calendars before anyone hangs up.
4. 4Fill in the rest of the fields within the hour, while you still remember the tone of the room. Later than that and you are writing fiction.
5. 5Copy four fields into the CRM: stage, amount, close date, next step. Leave the note where the note lives, and stop duplicating the whole thing.

A filled-in example from a real discovery call

This deal is invented, and so is every company, product and person named in it. It is written at the level of detail a real first call produces. Notice how much of it is in the buyer's voice, and how specific the risks are.

Account: Ellinby Facilities Group, 640 staff, 140 field engineers, UK. Date and time: Tuesday 3 March 2026, 14:00 to 14:35 GMT, Zoom. Call type: Discovery, first call. Their side: Marcus Deane, Head of Field Operations, owns the engineer rota and a budget line up to 30,000 pounds; Priya Nair, IT Manager, joined at minute 25, asked two questions about where data is held. Our side: Leila Osman, account executive, no engineer on the call. Source: Inbound demo request from the pricing page, 26 February. Stage before: New. Stage after: Discovery complete. Deal size, rough: 140 engineers at 14 pounds per engineer per month, about 23,500 a year. Recording: ellinby-disco-03mar.m4a, told them at 14:00.

• The problem, in their words: "We are flying blind between eight in the morning and six at night. The dispatcher rings an engineer, the engineer says he is on site, and we find out on Friday that he never went." Also: "Every reschedule is three phone calls and a WhatsApp voice note that nobody can find afterwards."
• What it is costing them: Six to nine missed appointment slots a week. Each missed slot triggers a 180 pound credit note under their contract with Brantwood Retail, their largest client. Marcus put the total at "somewhere north of forty grand a year, and that is before the shouting." Two dispatchers spend roughly half their day chasing status by phone.
• What they have tried already: A shared Google Sheet rota, which fell apart because engineers stopped updating it on the road. A second dispatcher hired in 2024, which Marcus described as "two people making the same phone calls".
• Who decides: Marcus signs up to 30,000 pounds. Above that, Fiona Bell, Operations Director, approves, and Marcus has not offered to introduce her. Priya Nair can block on data and security. The 140 engineers have to actually use it: "if they hate it on day two, it is dead."
• How they buy: Security questionnaire from Priya, about a week. Then a 30-day pilot on one region, the South East, 22 engineers. Then Fiona signs. Purchase order through finance takes about two weeks.
• Timeline, and the event behind it: Brantwood Retail contract review meeting on 15 July. Marcus wants improvement numbers to take into it, so he needs the South East live by 1 June. That means the pilot has to start by 1 May.
• Budget: Currently paying 9,600 pounds a year for the scheduling module of Renfield Works, which renews 30 June. Separately, 24,000 pounds sits unspent in the 2026 operations line for "field productivity", approved by Fiona in January.
• Competitors mentioned: Kelmscote Dispatch, seen last year: "too big for us, the demo alone was a week of setup." Renfield Works, the incumbent, which they will keep for invoicing whatever happens. And building on top of the existing sheet, an idea of Priya's that went nowhere.
• Objections raised, and how I answered: (1) "Our engineers are not app people, half of them are over fifty." I described the job list that works with no signal and the two-tap check-in. Half accepted, he wants to see it on a real phone, not a slide. (2) Priya: "Where does the data live, we hold client site addresses." I answered on region and encryption, but fumbled the retention question and promised to send it in writing.
• Risks: Fiona holds the pen above 30,000 pounds and I have not met her. Priya said nothing after the data answer, which I am reading as unconvinced rather than satisfied. The 1 June date only works if the pilot starts by 1 May, which leaves eight weeks for a security review that has not started.
• My read: Real problem, real money, wrong signature. I would call it 60/40 to close by the end of June. The thing I am least sure about is whether Fiona has already promised that 24,000 to something else.

Variant 1: the demo call

A demo note has a different job. Discovery is about learning; a demo is about watching. Keep the account block, drop the fields you already filled in on the first call, and add four that only a demo can give you.

• Who came, and who they brought. New faces are the story. A daily user turning up unasked is a good sign. The signer not turning up after being invited twice is a bad one.
• What they reacted to. The two or three moments someone leaned in, or said "can it do that". Quote the reaction. These are the features that go on page one of the proposal, and they are rarely the ones you thought.
• What they ignored. The parts you were proud of that got nothing. Cut them from the next demo.
• Questions asked, and by whom. A question from IT is a different signal from the same question asked by the budget holder. Note who asked, not just what.
• What you promised live. Every "I will check that" or "we can probably do that". Write each one down as it happens, because these are the promises that quietly become deal terms.
• Gaps found. Things your product genuinely does not do that they asked for. Write them plainly. A gap you hid in the note becomes a cancelled contract later.
• Objections and answers. Same two-line format as discovery.
• Next step. Usually a pilot, a security review or a pricing conversation. Date and owner, agreed before you close the call.

Variant 2: the renewal call

A renewal note is the one people write worst, because everything feels fine until it is not. Keep the account block, then replace the discovery fields with these.

• Renewal date and notice period. The two dates that actually matter, at the top, every time.
• Who is in the seat now. Champions leave. Write down whether the person who bought this is still there, and who replaced them. A new manager is a re-sell, not a renewal.
• What they use, and what they stopped using. Ask them, in their words. "We only really use the reports" is a warning shaped like a compliment.
• Value in their numbers. What has changed since they bought, in figures they own, not yours. If neither side can name one, that is the finding.
• Open problems. Support tickets they still remember, promises from last year that never landed. List them even when they are yours to fix.
• What has changed on their side. Headcount, a merger, a new tool, a budget freeze, a new boss with opinions.
• Anyone else talking to them. Ask directly. Note the name and what they were told.
• Expansion or contraction signals. Seats they are not using, sites they are opening, a team that wants in.
• Next step. For a renewal this is nearly always a date to agree terms, set well before the notice deadline, not after it.

Variant 3: the debrief on a deal you lost

Write this one within a day, while it still stings, and write it honestly. The loss note is the cheapest research your company will ever get, and it is worthless if it says "lost on price" when the truth was that you never met the signer.

Ask the buyer for fifteen minutes. Many say yes, because the pressure is off. Then fill in this shape.

• Who won, including "nobody, they did nothing" and "they built it internally". Both count as losses and both teach you something different.
• Their stated reason, quoted. The sentence they actually said when you asked why.
• Your read on the real reason. Written separately from theirs, because the two often differ. Be specific: no access to the signer, wrong champion, a gap in the product, a security answer that never landed, or genuinely price.
• The moment it turned. Name the call or the week. Almost every lost deal has one, and it is usually earlier than the rep thinks.
• What the winner did differently, in the buyer's words. "They just showed it working on my own data on the second call" is worth more than any competitor battlecard.
• What you would do again from the start. One or two concrete things, not "qualify harder".
• What would bring them back, and when. A renewal date to diary, a project that failed, a person who moves on.
• Diary date. Set a real one for six or twelve months out. A surprising number of lost deals come back when the thing they bought instead does not work.

Taking the note while you are also running the call

The template only works if it survives contact with a live conversation. You cannot type twelve fields and listen properly at the same time, so do not try. Split it into three passes.

1. 1Before the call, pre-fill the account block from the CRM and the calendar invite. Two minutes, and it removes half the typing from the live call.
2. 2During the call, capture two things only: quotes and numbers. Quotation marks and figures. Everything else is reconstructable, and those two are not.
3. 3In the last five minutes, agree the next step out loud and send the invite before anyone leaves the call. Write it into the note as agreed or not agreed.
4. 4Within the hour, fill in the remaining fields in order. It takes six or seven minutes when the quotes are already there, and half an hour the next morning when they are not.
5. 5Copy the four CRM fields across, then stop. Do not paste the whole note into a CRM comment box that nobody reads.
6. 6Before the next call with the same account, reread the note once. That is the entire point of writing it in a fixed order.

Getting the note written from the recording

If you would rather not fill this in by hand after every call, Noter AI has a Custom output style that you can point at this exact field list. You describe the format once, in plain words, listing the fields above in the order you want them, and every call afterwards comes back in that shape. Because the shape never changes, forty notes stay comparable, and so do the notes from the other reps on your team. There are also ready-made styles for key bullet points, a to-do list, an email or a formal report if you want the same call in a second shape without recording it again.

It covers both kinds of sales call. A bot joins Zoom, Google Meet, Microsoft Teams or Webex from your synced Google or Outlook calendar. For a meeting in the buyer's office, you record from the phone on the table, and the recording keeps running with the screen locked, so nothing stops when you put the phone away. More on that on the page about recording in-person meetings and on the sales calls page.

The verbatim part is where it earns its place. You get speaker labels, so you know whether the objection came from the IT manager or the budget holder, timestamps on every segment, and playback that jumps to that exact second when you tap a line in the transcript. That is how you paste the buyer's real sentence into a proposal instead of your memory of it. Company names and product terms sometimes come back spelled wrong, so the transcript is editable, and after you fix a name you can re-run the summary so the note picks up the correction. Action items are pulled out on their own, which covers the next-step field, and you can ask questions across every note at once, so "which accounts mentioned Kelmscote Dispatch this quarter" is a search rather than an afternoon.

Two things matter more for sales teams than they first sound. The first is language. Transcription covers 60+ languages with detection always on, and language is tagged word by word, so a call that runs half in Arabic and half in English, or Spanish and English, is written down the way it was said. Single-language tools make you pick before you press record, then write the other language out phonetically, which is exactly the sentence you needed to quote. Finished notes translate into 18 languages, so a call held in one language can go to a head office that reads another. See transcribing multilingual meetings for the detail.

The second is price. Noter AI charges $9.99 a month, or $49.99 for the year, per person rather than per seat. Sales is the department where per-seat billing costs the most, because you never buy one seat for sales, and you buy again every time you hire. Fathom Team is $19 per user a month, tl;dv Pro $18, Otter.ai Pro $16.99, Granola $14, Fireflies $10 to $19 per seat. The per-person rate never steps up as the team grows: five reps is five subscriptions, about $50 a month, or about $4.17 each per month on the annual plan, with no seat minimum and no admin seat to buy. It is not a team plan, though — five separate subscriptions, no shared workspace, no single invoice. What it does not give you is a manager's view of the team's calls, so if call coaching from a shared library is the reason you are buying, buy a platform instead.

Worth knowing before you try it: transcription happens in the cloud, not on the phone, there are no CRM integrations, so the note leaves as PDF, Word, plain text or a rich-text copy you paste in yourself, and there are no live captions during the call. Download it for iOS or Android. There is a free trial. Test it on one real discovery call and compare the output against the note you would have written yourself.