How to write a follow up email after a client call

The 4 line structure that works

A follow up email is not a transcript. Clients skim. Use four parts and stop.

• Thanks plus one specific reference to the call (proves you listened)
• Decisions: one or two lines on what was agreed
• Action items: who does what, by when, as a short list
• Next step: the single thing that moves the project forward

When to send it

Same day beats perfect. A good enough recap sent within 4 hours outperforms a polished one sent on Friday. The call is still fresh for the client, so corrections come back fast and cheap.

If the call ends late, schedule the email for 9:00 AM the next morning. Early morning sends get read; late night sends get buried.

Template: project call recap

Subject: Re: [Project], next steps

Hi [Name], great speaking today. Quick recap so we stay aligned: you want [deliverable] by [date] with [key constraint]. On my side: I will send [item] by [day]. On your side: [their item] by [day]. Next step: I send [first deliverable] and we review on our next call. Anything I missed, reply here.

Mistakes that cost renewals

Writing the recap from memory hours later is where promises get lost. If you said Thursday on the call and write Friday in the email, the client notices.

• Recapping from memory instead of the recording
• Burying action items inside paragraphs
• No owner or date on tasks (so nobody does them)
• Skipping the recap on short calls (short calls create promises too)

Automating this without losing your voice

Tools can draft the recap from the actual recording so dates and names come from what was said, not memory. Inbeo does this: upload the call, get the recap email prefilled with the client's address and a suggested send time, edit the tone, tap Schedule. Nothing sends without your approval.