Sales Call Notes: What to Record After Every Client Conversation
Good sales call notes record who you spoke to, what the client needs, what both sides agreed, the next step with a date, and anything a colleague would need to pick up the account tomorrow.
That’s it. If your CRM is full of entries like “called, interested”, nobody can piece the relationship back together when the rep is off sick or walks out the door. Below: a checklist of what to write down, a short template you can steal, and a habit that costs you a few minutes per call.
Table of Contents
Why do “called, interested” notes fail?
Vague notes make sense to exactly one person. The one who wrote them. And only for a few days. Now picture a colleague covering a sick day. They open the contact, see “called, interested” and have no clue what was promised, to whom, or by when. So what do they do? They ring the client and ask the same questions all over again, a follow-up slips through the cracks, and from the client’s side your company looks like it can’t get its act together. A simple test tells a useful note from a useless one: could someone who wasn’t on the call pick up the conversation tomorrow?
What to record in sales call notes after every conversation
Write down the facts a stranger would need to move the deal forward. Not your vibe from the call. If you’re staring at a blank field wondering what to write after a sales call, just go down this list:
- date and type of contact (phone, video, visit);
- who took part and their role: decision maker, user or gatekeeper;
- the client’s problem in their own words;
- their current solution or supplier;
- budget and timing signals;
- objections and open questions;
- what you promised to send;
- the agreed next step with a date and an owner.
Keep facts and interpretation apart. “Said the price is above budget” is a fact. “Seems unsure” is your read on it, so flag it as your read. And write down what didn’t land, too: offers the client turned down, topics they don’t want brought up again (the kind of thing you really don’t want a colleague stumbling into).
A short call notes template you can copy
With a fixed template, notes look the same across the team and get written faster, because nobody has to decide from scratch what matters. Paste this into your CRM or a text snippet tool:
Contact: date, channel Who: name, role, decision maker? Situation / Need: problem in their words, current supplier Objections: what worries them, open questions Promised by us / by client: documents, answers, data Next step: what, who, when Anything unusual: rejected offers, sensitive topics
Keep it to five to eight lines. A note nobody reads is about as useful as no note at all. Same structure works fine for meeting notes for sales, by the way: add who attended and one line on what got decided.
Next steps after a sales call: make them specific
A next step only counts if it has an action, an owner and a date. “Follow up soon” is a wish. “Send pricing for ten users to Anna by Thursday, call her Monday morning” is a plan anyone on the team can run with. Turn that step into a task with a due date and a reminder. Don’t leave it buried in the note text, because on the day it matters nobody’s going to see it there. Then send the client a short email confirming what you agreed. Both sides get the same record, and any misunderstanding shows up early instead of three weeks later.
Logging calls in a CRM so the whole team can use them
Notes go on the contact or deal record. Not in a notebook, not in someone’s private inbox. Log them right after the call while it’s all still fresh; saving everything up for the end of the day is how you lose exactly the details that make a note worth reading. The goal is to keep the history of every relationship in one timeline: calls, emails, tasks and deal stage changes.
In EpicCRM, notes and comments sit on the contact next to its relationship history, tasks have assignees and reminders, and an @mention pulls a colleague into the thread. Think hard about which fields to make required, like next step date or deal stage, so logging doesn’t turn into paperwork. And no, recording calls isn’t a shortcut here. You need the other party’s consent for that. Written notes stay the default.
How to get the team to write useful notes
People keep writing notes when they see someone actually using them. So managers need to read them and bring them up. Agree on the template together, then pull a few real notes into the weekly meeting and ask one question: could a stranger act on this? Show the payoff, too. Covering for a sick colleague without calling the client twice. Or handing clients to a colleague when someone leaves. It’s all part of the wider job of getting salespeople to log activity consistently (which, let’s be honest, is a whole topic of its own).
A CRM for small sales teams helps when notes, tasks and deals live in one place instead of three. But whatever tool you use, treat sales call notes as a handover document written for someone else. If a colleague can pick up the account tomorrow without calling you, the note did its job.
FAQ
How long should sales call notes be?
A few lines following a fixed template. That’s enough. All you need is for a colleague to be able to continue the conversation, nothing more. Long notes tend to go unread anyway.
Should I write notes during or after the call?
Jot down keywords during the call so your attention stays on the client. Then write the full note straight after, while it’s fresh and before you dial the next number.
Can I record sales calls instead of taking notes?
Only with the other party’s consent and within local law. And even then, what the team actually uses is a written summary with the agreed next step. Nobody’s going to replay a recording just to find a date.
