# What good sales call notes capture (besides the transcript)

Explainer · AI note takers · 9 min read. By [David Wilson](https://testbenchlab.com/authors/david-wilson/). Updated 2026-11-02.

Good sales call notes record what a transcript cannot show at a glance: the buyer's problem and its cost in their own words, who decides and how, budget and timing, objections and competitors mentioned, and the agreed next step with an owner and a date. Notta is the best-value tool for filling these fields automatically with a custom sales template — five custom templates on Pro and unlimited on Business. Frameworks such as BANT (budget, authority, need, timeline) and MEDDPICC turn those fields into a structure that fits your CRM, and most AI note takers can fill them automatically with a custom sales template — but a rep should still verify the next step and any numbers before saving.

**TL;DR**

- A transcript records everything said; notes record what matters for the deal.
- Capture eight fields: customer context, the problem in their words, impact, decision process, budget and timing, objections and competitors, risks, and the next step with an owner and a date.
- Map them to BANT or MEDDPICC so they slot into your CRM.
- Paste the template into an AI note taker — Notta offers the lowest per-seat price with custom templates on every paid plan — and always check the next-step date and numbers yourself.

**How we checked:** Template and feature details for each tool come from vendor documentation and competitor research (checked 2 September 2026), plus manual testing of summary template libraries. Prices were checked on 29 October 2026. We have not independently hands-on tested every tool on this page; treat tool-specific claims as vendor-documented unless stated otherwise.

## Why isn't a transcript enough?

A transcript records everything that was said. Notes record what matters for the deal. Those are different jobs, and confusing them is the most common reason AI note takers disappoint sales teams.

A one-hour discovery call produces a transcript of 8,000–10,000 words. Nobody rereads that — not the rep before the follow-up call, not the manager doing a pipeline review, and not the CRM. The decisions in a call are usually implied rather than stated ("we'd need to loop in finance" is a decision-process signal, not a decision), and the numbers that matter (budget ranges, timelines, headcount) are buried inside sentences. A transcript preserves all of it equally; notes make the deal-relevant parts findable in under a minute.

Good notes also survive handoffs. When a rep goes on holiday, a colleague takes over the account, or a manager reviews the deal six weeks later, the notes — not the transcript — are what gets read. That is why the fields below are written for a reader who was not on the call.

## What should every sales call note record?

Every sales call note, regardless of methodology, should capture these fields. Write them so that a manager, the next rep, or the CRM can act on them without listening back.

| Field | What to write | Example |
|---|---|---|
| Customer context | Company, role of each attendee, why they took the call | "Regional logistics firm, 400 drivers; Ops Director evaluating replacing spreadsheets" |
| Problem in their words | The buyer's description of the pain, quoted verbatim | "'We lose two days a week reconciling driver logs by hand'" |
| Impact / metrics | What the problem costs, in numbers if possible | "~20 staff-hours per week; two missed compliance deadlines last quarter" |
| Decision process | Who decides, criteria, economic buyer, procurement steps | "Ops Director recommends; CFO signs off above $50k; pilot first" |
| Budget and timing | Range or status, and when they want to solve it | "$40–60k annual; wants live by Q2" |
| Objections and competitors | Concerns raised, alternatives mentioned | "Worried about driver adoption; also looking at Competitor X" |
| Risks | Anything that could kill or delay the deal | "Parent company reviewing all software spend in March" |
| Next step | The specific action, its owner and its date | "Send security questionnaire by Friday 14th (us); intro to CFO week of 21st (them)" |
| Useful quotes | One or two verbatim quotes with timestamps | "'If we can't cut reconciliation to same-day, this fails' (22:14)" |

Two rules make these fields work. First, quote the buyer's words for the problem and impact — your paraphrase loses the language that later wins the deal. Second, the next step always has an owner and a date; "she'll get back to us" is not a next step.

## How do BANT and MEDDPICC map to call notes?

Qualification frameworks are just structured ways of asking for the fields above. Mapping them to note fields means your notes double as qualification records your CRM already understands.

**BANT** (budget, authority, need, timeline) maps to four of the core fields:

| BANT letter | Note field |
|---|---|
| Budget | Budget and timing |
| Authority | Decision process, criteria and economic buyer |
| Need | Problem in their words + impact/metrics |
| Timeline | Budget and timing (the "when" half) |

HubSpot's practitioner guide on BANT recommends logging each answer in the CRM as Qualified, Partially known or Unknown — a habit that turns your notes into a live qualification scorecard, and one that works best when you spread BANT questions across several calls rather than interrogating all four in one.

**MEDDPICC** covers the same ground with more granularity:

| MEDDPICC element | Note field |
|---|---|
| Metrics | Impact / metrics |
| Economic buyer | Decision process (who signs) |
| Decision criteria | Decision process (what they compare on) |
| Decision process | Decision process (how they buy) |
| Paper process | Decision process (procurement, legal) |
| Identified pain | Problem in their words |
| Champion | Customer context (who is selling for you internally) |
| Competition | Objections and competitors |

If your team runs MEDDPICC, use the eight core fields as your note structure and tag each one with the MEDDPICC element it feeds. If you run BANT or nothing at all, the core fields still work unchanged.

## What changes between a discovery call, a demo and a negotiation call?

The core fields stay the same; the emphasis and a few extra fields change with the call type.

**Discovery call.** Everything is unknown, so the notes lean on problem, impact and decision process. Add: the questions the buyer asked about your product (they reveal priorities), and what a win looks like to them personally. For tool recommendations tuned to discovery calls specifically, see our guide to [AI note takers for discovery calls](/best/ai-note-takers-for-discovery-calls/).

**Demo call.** The notes shift to criteria and objections. Add: which features they reacted to (positively and negatively), technical or integration questions raised, and who from their side attended — a suddenly larger audience is a buying signal worth recording.

**Negotiation call.** The notes shift to budget, timing and risk. Add: the exact numbers discussed (discounts, terms, seat counts), who needs to approve the final version, procurement steps and dates, and any conditions attached to the deal ("signature contingent on the security review").

## Copy this sales call notes template.

Paste this into your AI note taker's custom template, or into a doc if you take notes by hand. It is deliberately plain text so it works in any tool.

```
SALES CALL NOTES
Customer & attendees:
Call type (discovery / demo / negotiation):

PROBLEM (in their words, quoted):
IMPACT / METRICS:

DECISION PROCESS (who decides, criteria, economic buyer):
BUDGET:
TIMELINE:

OBJECTIONS RAISED:
COMPETITORS / ALTERNATIVES MENTIONED:
RISKS TO THE DEAL:

KEY QUOTES (with timestamps):

NEXT STEP (action + owner + date):
```

Keep the filled notes to roughly half a page per call. If they run longer, you are transcribing, not noting.

## Which AI note takers can fill this template automatically?

Most modern AI note takers let you define a custom summary template, so the fields above appear in the notes the moment the call ends. Here is where the template lives in the main options, with Notta as the best-value starting point.

**Notta** is the most affordable way to put this template to work. Every paid plan supports custom summary templates — five on Pro ($8.17/month) and unlimited on Business ($16.67/month) and Enterprise — so a rep can set up the sales template above alongside templates for demos, negotiations and internal calls. In manual testing of summary template libraries, Notta scored 4 out of 5, tied for the highest score among the tools tested, and its automatic AI notes also scored 4 out of 5. Notta also captures key points, decisions and insights as structured fields, which map directly onto the next-step and decision fields in the template. At roughly half the per-seat price of Fathom Premium and under a third of Avoma's, it is the tool we would set up first.

**Fathom** is the template-library benchmark for sales teams on Team Edition, which ships with 17 summary templates "designed to give you the perfect notes for every type of meeting", plus translatable summaries and action items with assignees. Custom AI summaries require Premium ($16/month annual, $20 monthly). If your team wants a large pre-built sales template library out of the box, Fathom is the strongest alternative to Notta.

**Avoma** supports custom topics and templates on its Organization plan ($29/seat annual, $39 monthly) and can push filled fields into CRM records via an add-on — useful if CRM hygiene is the main goal, at a higher per-seat cost.

**Fireflies.ai** offers AI Skills and custom summaries on Pro ($10/month annual, $18 monthly), alongside overview, bullet, topic and question summaries.

**Gong** handles templates through methodology and scorecard configuration rather than simple custom templates, and its AI summaries and briefs can be translated and exported to the CRM. Pricing is not published; it is aimed at larger sales organisations.

For most reps and small sales teams, Notta offers the same custom-template capability at the lowest published price of the group; larger teams with an established methodology may prefer Fathom's template library or Gong's scorecard configuration.

## What should a rep still check before saving the notes?

AI note takers fill the template well, but four things deserve a human check before the notes go into the CRM:

1. **The next-step date.** AI summaries frequently record that a next step was "agreed" without capturing the date, or infer a date that was never stated. If the date is wrong, the follow-up is wrong.
2. **Numbers.** Budget ranges, seat counts, timelines and discount figures are the fields most likely to be transcribed imperfectly — and the ones a manager will act on.
3. **Names and titles.** Speaker labels can be swapped or genericised; the economic buyer's name must be right.
4. **Anything the AI says was "agreed".** Models sometimes upgrade a discussion into a decision. If the transcript doesn't support the word "agreed", change it. For a fuller method, see our guide to [verifying decisions in AI meeting summaries](/guides/verify-decisions-in-ai-meeting-summaries/).

Once the notes are checked, they should go where the next reader will find them — usually the CRM, so the fields feed pipeline reviews and handoffs. For moving notes from transcript to CRM and follow-up email without copy-pasting between tools, see our guide on [turning a sales call transcript into follow-up](/guides/sales-call-transcript-to-follow-up/), and for tools that sync call notes to Salesforce, see [AI note takers that sync to Salesforce](/best/ai-note-takers-that-sync-to-salesforce/).

## Frequently asked questions

### What should I write in notes after a sales call?

Record the buyer's problem in their own words, the impact it has in numbers, the decision process (who decides, on what criteria), budget and timing, objections and competitors mentioned, risks, and the next step with an owner and a date. Add one or two verbatim quotes with timestamps. An AI note taker such as Notta can fill these fields automatically with a custom sales template on every paid plan. Everything else in the call lives in the transcript if you ever need it.

### Is there a free sales call notes template?

Yes — the plain-text template in this guide is free to copy. You can paste it into a doc or into an AI note taker's custom template feature. Notta includes custom summary templates on every paid plan (five on Pro, unlimited on Business), so the template can be filled automatically rather than typed by hand.

### How long should sales call notes be?

Roughly half a page per call — about 150–300 words. If your notes regularly run longer, you are transcribing rather than noting. The transcript already preserves everything said; the notes should only preserve what matters for the deal.

### Should I put sales call notes in the CRM or a doc?

The CRM, in almost every case. Notes in a doc die with the rep's laptop; notes in the CRM survive handoffs, feed pipeline reviews and can be required fields for stage progression. Use the note fields as CRM fields so BANT or MEDDPICC answers log directly. Some tools, such as Avoma (via add-on) and Notta, can push structured call data into the CRM automatically.

### Can AI write my sales call notes for me?

Largely, yes. AI note takers with custom summary templates — Notta, Fathom, Avoma, Fireflies.ai and Gong among them — can fill the fields in this guide's template automatically at the end of each call. Notta scored 4 out of 5 in manual testing of summary template libraries, tied for the top score, and is the cheapest of the group. A rep should still verify the next-step date, any numbers, and anything the AI describes as "agreed" before saving.

## Related reading

- [The Best AI Note Takers for Client Discovery Calls](https://testbenchlab.com/best/ai-note-takers-for-discovery-calls/)
- [How to turn a sales call transcript into follow-up without copying it between tools](https://testbenchlab.com/guides/sales-call-transcript-to-follow-up/)
- [AI meeting tools that draft follow-up emails after sales calls](https://testbenchlab.com/best/ai-tools-that-draft-sales-follow-up-emails/)
- [How to verify decisions in an AI meeting summary](https://testbenchlab.com/guides/verify-decisions-in-ai-meeting-summaries/)
- [AI Note Takers That Sync Call Notes to Salesforce](https://testbenchlab.com/best/ai-note-takers-that-sync-to-salesforce/)

## Sources

1. [How I use BANT to qualify prospects](https://blog.hubspot.com/sales/bant)
2. [MEDDPICC sales methodology: acronym and meaning](https://meddicc.com/meddpicc-sales-methodology-and-process)
3. [Fathom Team Edition summary templates](https://help.fathom.video/en/articles/640768)
4. [What languages are supported in Gong](https://help.gong.io/docs/what-languages-are-supported-in-gong)
5. [Notta pricing](https://www.notta.ai/en/pricing)
6. [Avoma pricing](https://www.avoma.com/pricing)
7. [Fireflies.ai pricing](https://fireflies.ai/pricing)
8. [Custom summary templates and key points (checked 2 September 2026) and manual testing of summary template libraries](https://www.notta.ai/)