Sales Call Notes Template for Every Call Type

Quick summary

What to include: a ten-field sales call notes template covers every call type: call type, date and attendees, stage, pain in their words, budget signals, timeline, decision process, competition, next steps, and a one-line summary.

How to adjust by call type: discovery needs pain and timeline, demo needs competition and reactions, and closing needs real budget numbers and final stakeholders.

Where to build it: as a Notion database default page, so every new call note inherits the structure with one click instead of a blank page. A general meeting notes template for internal meetings is further down.

Here is a copyable sales call notes template you can paste into Notion or HubSpot today. One core template works for every call type; the adjustments for discovery, demo, follow-up, and closing calls come after it.

The core sales call notes template

Drop this ten-field template into a Notion page, a HubSpot note, or a Google doc and you have a working structure. Every field has a one-line prompt to make it obvious what goes in it.

The template below is the one I use and the one most NoteLinker customers settle on after a few weeks of iteration. It is short on purpose. A template no one fills out is worse than no template at all, so every field has to earn its place.

• Call type

  Discovery, demo, follow-up, closing, or customer success check-in. One word.

• Date and attendees

  Date, your team's attendees, and the prospect's attendees with titles. Titles matter for decision-process tracking later.

• Stage

  Where the deal is in your pipeline at the start of the call. Captures any movement during the call automatically.

• Pain in their words

  Direct quotes when you can get them. "We are drowning in spreadsheets" is more useful than "needs better data tooling." Their language ends up in your follow-up email.

• Budget signals

  Allocated budget, current spend on the problem, how they evaluate new tools. You almost never get a number on a first call, but you can capture signals.

• Timeline and trigger event

  What is driving the date. "Q3 planning kicks off in June" is actionable. "Soon" is not.

• Decision process

  Who else needs to sign off, whether procurement is involved, and who the internal champion is.

• Competition

  Other tools they are evaluating or have used before, plus what they liked and disliked about each.

• Next steps

  Action, owner, date. One line per step. If a next step has no owner and no date, it is not a next step.

• One-line summary

  The single sentence a teammate would read if they only had five seconds. Write this last.

Why a template beats free-form notes

Free-form call notes feel faster in the moment and cost more later. A rep types a paragraph, moves to the next call, and a week later cannot tell whether the prospect had budget approved or was just curious. The notes look complete and contain almost nothing actionable.

A template solves three problems at once:

• It captures the fields the team needs to act on

  Even when the call ran long, the structure forces the rep to record what matters instead of a vague paragraph.

• It makes notes searchable

  Every account has the same properties in the same place, so anyone can scan across deals without reading prose.

• It lets a teammate pick up an account cold

  The real test of CRM hygiene is whether someone else can reconstruct the deal from the notes. A template makes that possible.

The point is not to write more, it is to write the same things every time. Mueller and Oppenheimer's 2014 study in Psychological Science on note-taking found that note-takers who summarized and reframed information in their own words retained and applied it significantly better than those who transcribed verbatim. A template that forces structured summary, not transcript, is the same idea applied to sales.

Consistency is what makes a sales note useful three months later. The template is the consistency.

Variants by call type

The same ten fields work for every call type, but the emphasis shifts. Treat these as the fields that should not be empty for each call type.

Discovery call

Mandatory: pain in their words, budget signals, timeline, decision process, next steps. The whole point of a discovery call is to fill these in. If you walk out without them, the call did not do its job. For a deeper take on what to capture in conversation, see how to take discovery call notes that close deals.

Demo call

Mandatory: pain in their words (revisited and confirmed), competition, next steps. Optional but valuable: a "demo reactions" line under each major feature you showed. The most useful note from a demo is which feature got the prospect to lean in.

Follow-up call

Mandatory: stage change (if any), next steps, one-line summary. A follow-up call where the next step is "follow up again" is a flag that the deal is stalling. The template surfaces that pattern faster than free-form notes do.

Closing or negotiation call

Mandatory: budget signals (now with real numbers), decision process (final stakeholders), competition (final shortlist), next steps. This is where vague notes from earlier calls cost you, because you are negotiating against information you should have captured weeks ago.

Customer success handoff

Mandatory: pain in their words, the deal's promised outcomes, decision-process champions (so CS knows who their internal sponsor is). The template doubles as a handoff doc. A clean handoff is the difference between a renewal and a churn six months later. See the sales-to-customer-success handoff for the full handoff playbook.

Building the template in Notion

A few minutes of setup makes this template work as a real workflow rather than a doc you copy each time.

1. 1

   Create the database

   Make a Notion database called something like "Sales Calls." This is where every call becomes a row in a consistent shape.

2. 2

   Add the ten fields as properties

   Call type as a select, stage as a select, date as a date, attendees as multi-select or text, and the rest as text or rich text. Add an Email property with the main contact's email (the same one HubSpot has) and, for deal calls, a Deal Name property. Those two are the join keys that tie each call to the right HubSpot record.

3. 3

   Build the default page template

   Open the database's default page template (the "+ New" arrow, then "+ New template") and drop the headings for the fields directly onto the page so every new row inherits them.

4. 4

   Create a new call note in one click

   Now creating a new note is a single click, and you start typing into a structured page instead of a blank one.

This is also the point where the template becomes useful at the team level. Anyone on the revenue team can filter the database by account, by stage, or by date range and see every call that touched a given deal in a consistent shape.

A general meeting notes template for every other meeting

Not every meeting is a sales call. Internal standups, one-on-ones, client status calls, and project kickoffs need a lighter structure with the same backbone: what was decided and who does what next. Copy this into Notion, a doc, or a markdown editor.

# [Meeting type] - [Date]

**Attendees**: [Names, with roles for external attendees]
**Meeting type**: [Standup / 1-on-1 / Client status / Kickoff / Retro]

## Agenda
- [Topic 1]
- [Topic 2]

## Discussion
- [Brief bullet on what was discussed, and why it matters]

## Decisions
- [Explicit decision, in the language used]

## Next steps
- [ ] [Owner] to [verb] [object] by [date]

## Internal notes (client meetings only)
- [Stakeholder dynamics and context that is not shared with the client]

Three rules keep it useful:

• Pull the decisions out of the discussion

  Most meeting notes bury the decision in a paragraph that ends with "so we agreed to do X." A separate decisions section lets anyone scanning the note a week later see what happened in thirty seconds.

• Write every action item as owner, verb, object, date

  Not "follow up on pricing" but "Sarah to send revised pricing to Acme by Thursday." Items with all four parts mostly get done; items without them mostly do not.

• Keep the header, even for quick meetings

  A note titled "Sync" with no date, type, or attendees is a note nobody finds again. For one-on-ones, keep one running page with the weeks stacked, so you can scroll back to what was promised.

Common mistakes to avoid

Three failure modes kill the habit faster than anything else.

• Writing transcripts instead of summaries

  A wall of paraphrased dialogue is harder to act on than five well-chosen lines. The template forces the summary. Do not work around it.

• Skipping the next-step field

  A call note without a concrete next step (action, owner, date) is the single biggest predictor of a deal stalling. If the prospect did not give you one, that is itself the data point.

• Leaving notes only in Notion

  The most carefully structured template does nothing for the deal if the AE who picks up the account tomorrow works in HubSpot.

The third mistake is the one teams underestimate. Notion is the better environment for writing structured notes; HubSpot is where the rest of the revenue org actually works. If your template lives only in Notion, the CRM stays empty and your reporting, sequences, and handoffs all run on partial information. The cost of that gap is covered in detail in the hidden cost of copy-pasting notes between Notion and HubSpot.

Getting the template into HubSpot

There are three practical ways to get a Notion-based template in front of whoever opens the HubSpot contact or deal, and the right one depends on volume and team size.

• Manual copy-paste

  Works for the first week. Dies on a busy week. Formatting drops, reps skip the step under time pressure, and the habit collapses inside a month, usually right when you would have most wanted the notes for a forecasting review.

• A generic automation tool (Zapier or Make)

  These shine on structured properties but choke on rich text. The template arrives in HubSpot as one stripped paragraph with no headings, and reps stop trusting the sync within a few cycles. HubSpot's own activity logging documentation is a useful reference for what the destination side expects.

• A live view on the record (NoteLinker)

  Nothing gets copied. Every call row whose Email matches the contact, or whose Deal Name matches the deal, shows on the HubSpot record's NoteLinker card, with the properties you chose as columns (call type, stage, one-line summary, next steps) and a link to the full page in Notion. Edit the note and the record shows the change on its next load. For the full mechanics, see how to view Notion inside a HubSpot record.

Adapting the template to your sales motion

The ten template fields are framework-agnostic on purpose, but most teams want the template to enforce a specific qualification framework. Two small swaps cover the common cases.

For BANT (Budget, Authority, Need, Timeline), the fields already line up: budget signals to budget, decision process to authority, pain in their words to need, timeline and trigger event to timeline. BANT is lighter and works well for transactional sales motions where the cycle is short and the buyer is the user.

For MEDDIC or MEDDPICC, swap pain in their words for "metrics + identified pain," add a "decision criteria" field, and rename competition to "implications of inaction or competitive alternatives." This adds two fields but enforces the heavier qualification a complex enterprise deal needs. The full walkthrough, including how to run the MEDDPICC version end to end, is in how to run MEDDPICC deal qualification in Notion and sync it to HubSpot.

The template is the place to encode the framework, not the rep's memory. If you want every discovery call to capture economic buyer and decision criteria, those have to be fields that stare the rep in the face during the call, not principles in a sales-enablement deck.

The simple test for whether the template is working

A year from now, open any account in your CRM cold. If you can read the call notes and reconstruct the deal (what they wanted, why, who was involved, what stalled it, what closed it) the template is doing its job. If you cannot, the issue is almost never the framework. It is either that the template is too long and reps stopped filling it in, or that the notes never made it out of Notion in the first place.

Start with the ten template fields, run them for two weeks, and trim anything that has stayed empty across every call. The template that survives is the one that fits your team.

Frequently Asked Questions

What should a sales call notes template include?

What is the best format for sales call notes?

How do I share sales call notes with my team?

What should a general meeting notes template include?

Should sales call notes follow BANT or MEDDIC?