Meeting follow-up email examples
Short emails for discovery calls, demos, team decisions, and a quiet inbox. Each gives the recipient a clear next step without inventing a promise.
Jump to an example: Discovery call · Demo · Decision · Reminder
Send the smallest useful recap.
A good follow-up helps the recipient remember the context and know what to do next. Two accurate sentences beat a long summary that turns a tentative idea into a promise.
Replace every bracketed field. Remove conditional lines that do not apply. Check names, dates, recipients, and commitments before sending.
After a customer discovery call
Use the customer's own description. Ask for a correction before treating your interpretation as a finding.
Subject: What I heard about [workflow]
Hi [name],
Thanks for walking me through [specific situation]. My understanding is that [problem] happens when [trigger], and the current workaround is [what they actually do].
Did I get that right?
[If agreed: I'll send you [specific item] by [date].]
Thanks,
[your name]
After a demo or proposal discussion
A proposed next step is a question. An agreed next step has an owner. Do not write 'as agreed' if it wasn't.
Subject: Next step on [project]
Hi [name],
We covered [use case] today. The main requirement you raised was [requirement], and [question] is still open.
[Owner] agreed to [action] by [date]. I'll [your agreed action].
[If no next step was agreed: Would a short conversation about [specific unresolved point] be useful?]
Best,
[your name]
After an internal decision meeting
Separate decisions, commitments, and open questions. Someone reading this later should know which is which.
Subject: Decision and next steps: [topic]
Team,
We decided to [settled decision] because [brief reason].
Next steps:
- [Owner]: [committed action], [agreed date]
- [Owner]: [committed action], [agreed date]
Still open: [unresolved question]. We haven't decided [pending choice] yet.
Notes: [meeting link]
Reply if I've missed or misrepresented anything.
When the first follow-up gets no reply
Keep the original thread. Offer an easy way to say no. Avoid manufactured urgency and repeated 'just bumping this' messages.
Subject: Re: [original subject]
Hi [name],
Checking whether [specific next step] is still useful. If priorities have changed, no problem.
Would you prefer to [small option A], [small option B], or leave this for now?
Thanks,
[your name]
Before you hit send
Does the email distinguish what was decided from what is still being considered?
Did the person actually agree to the action and date you wrote?
Can the recipient answer the request without reading a transcript?
Does the meeting link have the right sharing permissions?
Use it with Runa
Ask Runa to draft a follow-up from the meeting context. Choose one of these structures, then review the draft against the notes and transcript. Keep unresolved questions open and edit the language so it sounds like you.