Write a CRM call summary the next person can actually use

Example result.

Must be true to move: the partners' meeting (date unknown) puts supply on the agenda.
I committed to: indicative pricing "in the next few days". No calendar date promised.
I don't yet believe: that the contract ends in March. Notice period unconfirmed.
Do not repeat: don't lead on delivery problems. They came from the practice manager.

1. Open the call and see what the summary covers

In HubSpot, go to CRM › Calls (under More if you don’t see CRM) and click the call title. Read the AI summary for its shape before its content. You can switch its template by clicking Auto and choosing Support Rep (built around case resolution) or Sales Rep (built around deal and prospect insight). Pick the one that matches what the next person needs, not your job title.

The generated summary can’t be edited. HubSpot sends you to the Notes box below it, which keeps the machine’s account and your judgement visibly separate. In another CRM, find the equivalent call record and a notes field that doesn’t overwrite the source.

Why this works: every summary field records what happened in the call. None records what you suspect or what the next person should be careful about, so you know what you’ll need to add.

What you should see: the call date, speakers and account confirmed, and a clear sense of what the summary does and doesn’t try to say.

2. Pull out every commitment, with the sentence behind it

Paste the transcript into Claude, ChatGPT, Gemini or Copilot in your work account, or use your CRM’s assistant if it can read the call. HubSpot has an Ask a question field on the call record for narrower questions such as “Did the customer mention a budget?”.

Prepare a factual handover from this call record for [colleague or role].
Use only the material below. Do not update the CRM or send anything.

Return:
1. Customer statements relevant to the next conversation, attributed to the speaker, not treated as verified facts.
2. Explicit commitments: who, what, exact timing and any condition.
3. Dependencies and unresolved questions.
4. Any gaps or uncertain speaker attribution.

Give a short exact quote and timestamp for each item. If no date was given, write "no date given". Do not infer budget approval, deal stage, sentiment or a deadline. Distinguish a firm promise from an offer, estimate or suggestion.

CALL DATE AND ACCOUNT: [details]
SOURCE: [transcript or notes]

[colleague or role] is who will pick this up. [details] is the call date and account name. [transcript or notes] is the pasted material, plus any dated correction.

Why this works: a model asked to list commitments will produce a list whether or not they exist. One asked to quote the sentence has to find it, and when it can’t, the gap shows.

What you should see: a short list where every item carries a quote and a timestamp. A row with a paraphrase instead of a quote is unconfirmed until you look.

3. Check the date, number and name against the transcript

In HubSpot, use the Transcript tab on the call record and its search bar. Check every item that matters, starting with three kinds:

• Dates. “Early next month” becoming “3 November” is the most common quiet promotion, and the next person will read it as a promise.
• Numbers. Prices, volumes, sites, discounts. Summaries round. Contracts don’t.
• Names. Multi-speaker calls are where attribution slips. “Their finance director raised the renewal clause” is a different account from “someone mentioned renewals”.

Why this works: these are what a covering colleague will act on. One error tells you to check the rest more carefully, not less.

What you should see: each consequential item marked supported, attributed or unconfirmed. Where your source is human notes, don’t invent a verbatim quote from a shorthand line.

4. Write the four-line handover

Add this in the notes field, in your own words:

HANDOVER — [your name], [date]
Must be true to move: [the single condition this deal depends on]
I committed to: [what you said you'd do, and by when]
I don't yet believe: [the claim you're not taking at face value, and why]
Do not repeat: [what landed badly, or the question already asked]

• Must be true to move names the dependency, not the activity. “Positive call, good engagement” is a mood.
• I committed to is what a colleague must read before contacting the customer. A next-steps list doesn’t reliably tell your firm promise from a passing “we could probably look at that”.
• I don’t yet believe is about claims, not people. “The March end date is unconfirmed” is useful. A judgement about the person who said it isn’t, and it may be read by people you didn’t expect, including the customer.
• Do not repeat saves the next conversation from a question already asked.

Why this works: the summary answers “what was said”. These four lines answer “what does the next person need to know”, which no summary can know.

What you should see: four lines someone who wasn’t on the call could act on. Reopen the record and check the note landed on the right account. Saving a useful handover to the wrong account is an unusually efficient way to create two problems.

Check the result

• Every date in the handover matches the transcript’s wording, including vague ones.
• Every customer claim is attributed to the person who made it.
• Your commitments match what you actually said, with the timing you gave.
• Nothing in the note judges a person’s character or mentions their personal circumstances.

The usual failure: the summary turns a vague ending into a schedule. “Let’s speak again after the partners’ meeting” becomes “follow up in two weeks”, and “the next few days” becomes “by Friday”. Spot it by searching the transcript for each date the summary gives.

Correct the handover item [item]. The source says [exact wording and timestamp]. Keep that level of certainty, timing and condition, and attribute the statement to its speaker. If the source doesn't settle the timing, mark it unconfirmed. Do not add a new deadline or next step.

[item] is the line that strengthened the source. [exact wording and timestamp] is what the transcript really says.

Fictional example. Nina at Meridian Supplies has a discovery call with Harlow Dental Group, a six-practice group, before she goes on leave. Dev is the partner on the call.

CALL: Harlow Dental Group, 6 October 2026
04:20 Dev: We have six practices. Consolidated invoicing would help.
05:40 Dev: Our practice manager says two sites have had late deliveries. I'm not sure it's that bad.
07:10 Dev: I think the current agreement runs to about March, but I need to check the notice period.
09:30 Nina: I'll send indicative consolidated pricing in the next few days.
12:00 Dev: Let's speak again after the partners' meeting. I don't have its date yet.

The generated summary:

Six-practice customer; delivery reliability issues at two sites; contract ends 31 March. Sentiment: positive. Next steps: send pricing by Friday; follow up in two weeks.

• The failure. Only the six practices are supported as Dev’s statement. “31 March”, “by Friday” and “two weeks” are all invented precision, and the delivery complaint is presented as Dev’s view when he played it down.
• The repair. Nina ran the correction prompt on the three dates, then wrote the handover shown in the example result. “In the next few days” is still a timing commitment, so the handover keeps it rather than saying no timing was given.
• Why the last line matters. The cover now won’t open with a complaint the partner didn’t make. The summary wasn’t wrong. It just answered a different question.

Task kit for this job: Download (ZIP) · Reusable instructions

Go deeper

Reconcile these dated account notes. For each commitment or dependency, show the latest supported position and the evidence for any change. Keep earlier uncertainty visible as history. Do not treat the newest mention as agreed without evidence.

CORRECTION — [author], [date]
Earlier item:
Supported wording:
Evidence:
Field needing the account owner's review:

Sources

• HubSpot: Review call recordings and transcripts
• Salesforce Help: Call summaries and generative conversation insights