CRM notes after a call: what to record and how to write it
Write a useful CRM note from a call recording: client request, confirmed conditions, constraints and next step. Includes an example and a short template.
Write the note for the next person handling the case
“Had a call, all good” does not help anyone continue the deal. A colleague cannot tell what interested the client, what constraints came up or what action was promised. Pasting the entire transcript makes it harder to find the details amid greetings and repetitions.
Decide which facts will affect the next contact: the use case, confirmed scope, decision-makers, when to expect materials or an open question. Fields and statuses vary by CRM. The format below is intended to work across systems.
Write a short note from verifiable facts
State the context of the call
Record the date, participants and purpose in your team's usual format. If the CRM already stores some of that information, avoid duplicating it unnecessarily. A reader should be able to distinguish this conversation from older conditions and know whose request is described.
Identify confirmed conditions
Find the need, constraints and selection criterion in the recording. Check numbers, dates and negatives against the audio. “We’ll reply by Friday” and “We won’t reply by Friday” can lead to opposite actions if you copy an unchecked transcript.
Distinguish agreements from expectations
“We’ll think about a pilot” does not authorize a launch. Label the status: confirmed by the client, proposed by the account manager or awaiting clarification. Describe specific working circumstances instead of personal judgments such as “difficult client.”
Assign the next step
State the action, owner, date and expected result. If a reminder is needed, use the CRM's normal task feature. A note preserves context, but it may not show up in the scheduled work list.
Call about a trial rollout
This is a fictional training example. The names, circumstances and outcomes are included solely to explain the method.
We need to test how one team handles requests. I’ll send the channel list tomorrow. We’ll decide whether to expand after the test. I can’t commit to a larger scope yet.
The client confirmed interest in a limited test and promised to send a channel list. An expansion is still open. Preserve that distinction so the next account manager does not open with an assumption that a larger rollout was agreed.
Replace “tomorrow” with a date based on the date of the call. The account manager's next step is to check for the list and prepare a test proposal around it. A rollout start date has yet to be agreed.
| Excerpt | Accurate note | What remains unconfirmed |
|---|---|---|
| Test with one team | Interest in a limited test | Full rollout agreed |
| I’ll send the list tomorrow | List expected by a specific date | Data already received |
| We’ll decide after the test | Expansion still unconfirmed | Larger scope promised |
Short CRM note template
Adapt the fields to the team’s process. If an important condition is disputed, include an authorized internal link to the excerpt.
Purpose of the call: Need and use case: Confirmed facts: Constraints and selection criteria: What was agreed: What was only proposed: Open question: Next step / owner / date: Expected outcome of the step: Source or timecode if needed:
Read the note as if you were the new account manager
- The purpose of the contact is clear.
- Assumptions are distinguishable from the client’s words.
- Numbers and dates have been checked against the recording.
- The next step is a specific action.
A closer look
Should I paste the whole transcript?
A short note is usually easier to use in a working record. Store the source separately with suitable access if the company’s process permits.
What if the client has not made a decision?
Record that the decision is pending. State what information is missing, who will provide it and when the parties will discuss it again.