A sales call lasts ten minutes. What you record afterwards can matter for months. It’s the difference between a colleague picking up a lead with confidence and ringing the customer to ask what’s already been said.
Most reps know they should log their calls. Plenty do it badly, either writing nothing or writing so much it takes longer than the call. Here’s a short checklist and a way to get it done in a minute. It sits within our wider look at keeping track of customer relationships.
Why bother
For continuity first: whoever speaks to the customer next, including you in three weeks, can carry on from where you stopped. For follow-up, because the call usually ends with a promise, and recorded with a date it becomes a task that gets done, while unrecorded it depends on memory. And for learning, since across many calls patterns appear, such as the objections you hear most and which questions lead to a proposal.
Six things, in about a minute
Record the outcome, in a line. Did you speak to someone, leave a message, reach the wrong number? Even a failed attempt belongs in the log, because it tells the next person not to ring at the same time tomorrow.
Record who you spoke to, with their name and role, especially if it wasn’t your usual contact. “Finance manager, not Mike” changes how the next call should go.
Record what was said that matters, in two to four short points: what they need, what they raised and who they’re comparing you with. Don’t transcribe. Capture what would change how someone approaches the next call.
Record any objection and how you answered it. “Worried about switching during the busy season. Said we could start in January.” Objections that are written down can be prepared for.
Record anything promised by either side. “I’ll send a price by Friday.” “She’ll check with her partner and come back next week.” Promises are the most commonly forgotten part of a call and the most damaging to forget.
And record the next step with a date: who does what, and when. If you write nothing else, write this. Without it the lead has no future.
If it helps, copy this shape: Spoke to (name, role). Outcome (one line). Key points. Objection, if any. Promised. Next step (action, owner, date). Everyone ends up with notes in the same form, which makes them quick to read.
Good notes and poor ones
“Called. Went ok. Will call back.” tells the next person nothing: not who, not what, not when. Try instead: “Spoke to Aoife (office manager). Currently uses three suppliers and wants one. Worried about the cost of moving. I explained we handle the set-up and offered a call with her director. She’ll ask him and I’ll ring Thursday.” It’s a few lines, and anyone could take it from there.
The same goes for failed attempts. “Left voicemail” is weak. “Left voicemail at 10:15 asking for a call back about the quote. Third attempt. Try the mobile after 4, per reception” gives the next person something to act on.
Do it straight away
The most useful rule is the simplest: log the call before the next one. Within a few minutes you remember everything. By the end of the day you remember the headline. By tomorrow, you remember that it happened. If you’re making calls back to back, block a minute between each. It feels slow, but it saves far more time than it costs, because nobody has to reconstruct things later.
Let the system do part of the work. If your phone system is connected, calls are matched to leads by number and appear on the timeline automatically. In Henkan CRM, phone system integration works with Wildix and Aircall, and you can still log your own outcome and next callback date whenever you want to add notes. That leaves you the part only you can do: what was said and what happens next.
In the lead profile you log the call, record the outcome, add notes and set the next callback date before you move on, and you can open a sales script or your objection responses in floating panels beside the lead, so they’re in front of you during the call.
Better still, agree the next step during the call. “Shall I ring you next Thursday?” gives you a date the customer has agreed to, which makes the follow-up more welcome and more likely to happen. Then set it as a task or callback, as described in tasks and callbacks, and it’ll be on your list on the day.
What to leave out
Opinions about the person. “Difficult” tells a colleague nothing and looks bad if the customer ever sees it. Sensitive personal details that aren’t relevant to the sale. Anything you wouldn’t say to the customer’s face, because you should assume they could one day read it. And anything that wouldn’t change how someone handles the next call.
Whether to record the call itself is a separate matter, with consent and legal points that depend on where you and the customer are, so take advice first. Written notes cover what most teams need.
What managers can do
Agree a standard and show a good example. Read a few notes each week and say what’s good about them. When a lead changes hands, check the new person has what they need. And don’t use notes to catch people out, because if they’re used punitively they get shorter and vaguer. For more on getting a team to do this consistently, see getting your whole team to use the CRM, and for the system you’re recording into, what to look for in a relationship-based sales CRM.
The awkward calls
Some calls don’t fit the neat template, and they’re often the ones that matter most. After an unhappy call, record what the customer said in their words, what you offered and what you agreed to do, and be factual. After a no-show, note it and the time, and set the follow-up straight away, because it’s easy to read a no-show as lack of interest when it’s often just a diary clash. When you get past a gatekeeper, note their name and what worked: “Reception suggested ringing after 2.” The next person will be grateful. And if a customer tells you something personal, record only what’s useful and appropriate, such as “prefers email, travelling until the 14th”, rather than the detail.
To see how a call gets logged in Henkan CRM, book a demo.




