Client call summary template (copy-paste)
A client call summary needs nine fields: client and project, date, attendees, purpose, what the client said, decisions made, action items (with owners and dates), open questions, and the next step. The copy-paste template is below, with a filled example. Write it within 24 hours, keep it under 250 words, and the recap itself becomes a trust-builder: the client sees you listened and knows exactly what happens next.
Why a written summary matters
An hour-long call produces more than any memory holds. Three weeks later nobody remembers exactly what was agreed about the handoff date or who owns the copy review - and "I thought you said" is how client relationships start souring. A summary solves three problems at once:
- Shared truth. The client and your team point at the same half page when a detail is disputed.
- Momentum. Action items with dates get done; verbal agreements drift.
- History that compounds. Twelve summaries into an engagement, you have the full story of the project - and the basis for a client call log that makes every future call start smarter.
The cost side is real too: a summary written from scratch takes twenty minutes and often never gets written at all. The template below cuts it to five.
The template (copy-paste)
| Field | What to write |
|---|---|
| Client / project | Name and engagement, so it files correctly ("Harbor & Co - rebrand, phase 2") |
| Date · duration | When the call happened and how long it ran |
| Attendees | Everyone on the call, roles if they are new |
| Purpose | One line: why this call was scheduled ("kickoff for phase 2 scope") |
| What the client said | 3-5 bullets: needs, concerns, constraints - in the client's own words where possible |
| Decisions made | Every "so we agreed on..." - each decision one line |
| Action items | Who does what by when. No owner or no date = not an action item |
| Open questions | What couldn't be resolved on the call and who unblocks it |
| Next step | One sentence: what happens next and when you'll talk again |
Keep two versions of the same summary: the client-facing recap (everything above) and your internal notes - budget hints, frustrations, mentions of competitors - which never leave your side. The shared version builds trust; the private one is where honesty about the project lives.
A filled example
Here is the template filled in for a typical consulting call, so you can calibrate length and tone:
Purpose: align phase 2 scope before the sprint starts.
What the client said: launch window is fixed to May 1 (investor event); Josh wants bolder visuals but Elena worries about brand recognition; internal team can only review on Fridays.
Decisions: phase 2 ships in two milestones (Apr 10 concepts, Apr 24 final); the logo stays, the palette changes.
Action items: Morgan - moodboard by Mar 8; Elena - Friday review slot booked; Josh - confirm investor date to Morgan by Mar 6.
Open questions: who signs off if Elena and Josh disagree (raised, unresolved).
Next step: moodboard review Friday Mar 8, 15:00.
Under 200 words, and every dispute about "what we agreed" ends by pointing at a line in it. That's the standard to hit.
How to write it in five minutes
- Minute 0-1, right after hanging up: fill the header facts - client, date, attendees, purpose. Memory loss starts immediately; the facts you can still type in sixty seconds.
- Minute 1-3: write what the client said from memory while it's warm - three to five bullets, their words not yours.
- Minute 3-5: decisions and action items with owners and dates, one next-step sentence. Stop. Don't polish - a sent, imperfect summary beats an unsent perfect one.
- Within 24 hours: send the client-facing version by email - the follow-up email templates turn this step into a two-minute edit. If something was sensitive, that stays in your internal notes only.
The routine matters more than the tool: same template, same place, every call - that's also what a consulting notes system is built on, and this template is the per-call unit of it.
Let the transcript write the draft
The middle sections - what the client said, decisions, action items - are the slowest to write from memory and the fastest to generate from a recording. That's the honest pitch for recording your calls:
- Nerpa records the call from your Mac with no bot joining, transcribes it with speaker labels, and drafts the summary, decisions, and action items automatically - so the template fills itself and you edit for tone. Notes are organized by person, so each client's history accumulates in one place.
- Already have a recording? The free audio to text tool on this site transcribes a file in your browser - up to 35 minutes, no signup - and you can lift quotes from the transcript into the summary.
- Privacy note: raw audio stays in a local folder on your Mac, and transcription runs on your computer - worth knowing before recording client conversations; the rules for private meeting recordings still apply.
Summaries that write themselves
Nerpa records the call without a bot, drafts the summary with decisions and action items, and files it under the client - you send the recap and move on.
Latest stable release. Requires macOS 12+
Frequently asked questions
What should a client call summary include?
Nine fields: client and project, date, attendees, purpose of the call, what the client said (needs, concerns, constraints), decisions made, action items with owners and dates, open questions, and the agreed next step. Together they fit in half a page - longer summaries stop being read.
How long should a call summary be?
About 150 to 250 words, half a page. The client should be able to skim it in under a minute. If it runs longer, move detail into an appendix or keep it in your internal notes instead - the summary is for decisions and next steps, not a transcript.
Should I send the call summary to the client?
Yes - a summary sent within 24 hours builds trust and prevents disputes about what was agreed. Keep two versions: the client-facing recap (decisions, action items, next step) and your internal notes (frustrations, budget hints, competitive mentions) which stay with you.
How do I write a call summary faster?
Two habits: fill the header facts within a minute of hanging up, and record the call so the middle sections write themselves - a recorder like Nerpa generates the transcript with speaker labels plus draft summary, decisions, and action items, so you edit instead of remembering. A file can also be transcribed free in the browser on this site.