Follow-up email after a consultation call (templates)
Send the follow-up within 24 hours of the call: thanks plus one specific reference, a three-bullet recap, decisions made, the next step with a date, and one question that takes a line to answer. Three copy-paste templates are below - the same-day recap, the paid-engagement close, and a polite nudge for a quiet client. Under 150 words each; the recap email is where a good call either becomes a project or quietly dissolves.
Why the 24-hour window matters
The call creates momentum; the email decides whether it survives the week. Send inside 24 hours and three things happen:
- You're the one who wrote history. Whoever summarizes the meeting controls what "was agreed". If it's you, the recap in the client's inbox becomes the shared truth; if you wait, the client's own (fuzzier) version takes that place.
- The next step stays hot. A decision made on Tuesday gets acted on if it's confirmed by Wednesday - and gets renegotiated if nobody writes it down.
- Professionalism is timestamped. Clients compare consultants to every other vendor they talk to. A same-day recap with their own words quoted is the cheapest differentiation there is.
- After ~48 hours the same email reads as housekeeping; after a week it reads as an apology. Timing is most of the craft.
The recap email is also the natural end of the same-day routine: the client call summary you wrote for your files and this email share most of their content - decisions, action items, next step. Write the summary first, and the email is a two-minute edit.
Template 1: the same-day recap
Hi [Name],
Thanks for the call today. You mentioned [specific phrase the client used] - that context helps a lot.
Quick recap of where we landed:
- [What the client needs / the situation, one line]
- [Decision made, one line]
- [Next step + date, one line]
One thing to confirm: [single question with an easy answer - e.g., "does [date] still work for the review?"]
[Your name]
Note the shape: five sentences plus three bullets. The quoted phrase in line two is doing the heavy lifting - it proves the email was written by a person who listened, not generated after "meeting recap" became a chore.
Template 2: closing a paid engagement
Hi [Name],
Closing the loop on today's session. What you now have:
- [Deliverable 1]
- [Deliverable 2]
What we agreed on next: [next step, owner, date]. I'll send [the proposal / the scope / the invoice] by [day].
If anything in the summary doesn't match your notes, reply and I'll correct it - better to fix the record now.
[Your name]
The last paragraph is the quiet contract: you've invited a correction within a defined window, after which the written record stands. Disputes about "what we agreed" die when this line is in the thread.
Template 3: when the client goes quiet
Hi [Name],
Floating this back up - you mentioned [their stated constraint, e.g., "the review was planned for Friday"], so I wanted to check whether [the pending decision, e.g., "Monday still works for the sprint start"].
If priorities moved, no problem - just say the word and I'll re-plan around you.
[Your name]
Cadence: first nudge after 3-4 business days, one more after a week, then a graceful close ("I'll assume priorities changed - door's open when timing improves") and a calendar reminder to check back in a month. Two nudges maximum; the follow-up works because it's rare.
What makes follow-ups get answered
- One question, one line to answer. "Does Tuesday work?" gets a reply from a phone. "Let me know your thoughts" gets silence.
- Their words, not yours. Quote the client's own phrasing of the problem once. Generic recaps read as automation even when they're not.
- Under 150 words. The recap is read between meetings, on a phone. Everything that doesn't fit goes in your internal notes system, not in the email.
- Dates, not "soon". Every next step carries a calendar date. "By Friday" creates accountability; "shortly" creates nothing.
- Nothing new in the nudge. If the client went quiet, repeating the same ask with fresh context beats adding new asks - new questions restart the clock.
The honest limit: a follow-up can't rescue a call that ended without a clear next step. If nobody said what happens next, the email's job is to propose one - "Based on today, I suggest [X] by [date] - does that work?" - which is a legitimate and often welcome move.
Never reconstruct a call from memory again
Nerpa records the consultation with no bot joining, transcribes it with speaker labels, and drafts the summary, decisions, and action items - so the follow-up email becomes a two-minute edit instead of an archaeology project. Notes are filed per client, so the next email starts with history.
Latest stable release. Requires macOS 12+
Frequently asked questions
How soon should I send a follow-up after a consultation call?
Within 24 hours, the same day if possible. The recap is most valuable while the conversation is fresh for both sides, and a same-day reply signals professionalism. If the call ended with a decision needed from you (a proposal, a scope document), sending it inside 24 hours is part of the deliverable.
What do you write in a follow-up email after a consultation?
Five short parts: thanks and one specific reference to what the client said, a three-bullet summary of the situation, the decisions made, the next step with a date, and one clear question that takes a line to answer. Keep the whole email under 150 words - the client should be able to read it on a phone between meetings.
How do I follow up without being pushy?
Follow up on the thing they asked for, not on the thing you want. "You mentioned the review was planned for Friday - should I hold the sprint start for Monday?" adds value and reminds at the same time. Send at most two nudges (3-4 business days apart, then a week), keep each under three sentences, and make the last one an easy out.
What if the client doesn't reply to my follow-up?
After two unanswered emails, stop chasing and close the loop politely: send a final note saying you'll assume priorities changed, leave the door open, and set a reminder to check back in a month. Silence usually means timing, not rejection - and a graceful close keeps the relationship alive for the next budget cycle.