The meeting went well. Everyone nodded, decisions felt made — and then nothing happened. No owners, no dates, and by Thursday half the room remembers the agreement differently. A good follow up email after a meeting is what turns a conversation into commitments, and it takes five minutes once you know the shape. Below: the five rules that matter, subject lines that get opened, six copy-paste templates for the most common situations, and a separate meeting recap template for when you need a record rather than a reply.
The five rules
- Send it within 24 hours. Memory decays fast and momentum decays faster. Same day is best; the next morning is the deadline.
- One clear goal. Book the demo, confirm the date, get the approval. An email that asks for three things usually gets zero answers.
- Recap decisions and action items — with owners and dates. “We’ll move forward” is not a decision. “Anna sends the contract by Friday” is.
- Keep it short. Under 150 words for a follow-up. If it scrolls, cut.
- Write a specific subject line.“Following up” gets archived. “[Project] — recap + next steps” gets opened now and found again in search later.
Subject lines that get opened
The subject line does two jobs: it earns the open today and it makes the thread findable in three months. Name the topic, then signal the next step.
After a sales call or demo:
- Acme × [Product]: recap + next steps
- Pricing you asked for + proposed timeline
- Next step from today’s demo
After an internal meeting:
- [Project] — decisions & owners from today
- Recap: sprint planning, action items inside
- What we agreed this morning (30-second read)
Networking and interviews:
- Great meeting you at [event]
- That [topic] article I mentioned at [event]
- Thank you — [role] interview
Six copy-paste templates
Replace the brackets, delete what doesn’t apply, and keep each one under 150 words. The structure — recap, action items, one ask — matters more than the exact wording.
— We agreed [Product] covers it, pending [open question].
— Me: pricing for [tier] to you by [day].
— You: confirm [stakeholder] can join a 20-minute demo next week.
[You]
— We ship v2 on [date]; scope is frozen.
— [Feature] moves to the next cycle.
— [Name]: draft the release notes — by [date]
— [Name]: fix [bug] — by [date]
— [Milestone] approved as presented.
— Timeline shifts one week to [date] to absorb [change].
From your side: we need [asset or approval] by [date] to hold the timeline.
[You]
[You]
Meeting recap email: not quite the same thing
A follow-up and a meeting recap get conflated, but they do different jobs. A follow-up advances something: one goal, one ask, usually aimed at one person. A recap is the record: what was decided, who owns what, sent to everyone who attended, with no ask beyond “correct me if I got this wrong.” For small meetings, one email can do both. For high-stakes meetings, send a recap to the whole group and a separate follow-up to the person whose answer you actually need.
— [decision one]
— [decision two]
— [Name] — [task] — due [date]
— [Name] — [task] — due [date]
— [question] — [who owns the answer]
Stop reconstructing meetings from memory
The hard part of every template above isn’t the writing — it’s the brackets. What exactly was decided? Who took which item? Which date did they say? Reconstructing that from memory an hour later is where follow-ups get vague, and vague follow-ups are why the 24-hour rule slips.
Full disclosure: we build Eidetic, and this is precisely the problem it exists for. It’s a native macOS menu-bar app that records both sides of any call — Zoom, Meet, Teams, or an in-person conversation — directly on your Mac, with no bot joining the meeting. Transcription and summaries run on-device, so nothing is uploaded anywhere. When the call ends, you can ask its built-in local chat to draft the follow-up email from the transcript: it pulls the decisions, action items, and dates for you, and you review the draft, copy it into your mail app, and send. The five-minute follow-up becomes a one-minute one, and the brackets fill themselves from what was actually said.
One honest note on recording: consent laws vary by country and by US state, so tell participants you’re recording, whatever tool you use.
Eidetic is a €49 one-time purchase after 6 free meetings — no subscription, unlike every cloud meeting service. The honest limits: it’s macOS-only (Apple silicon), and it’s single-user — built for your meetings, not a shared team workspace.
FAQ
How do you write a follow-up email after a meeting?
Use a fixed structure: a specific subject line (topic + next step), a one-line opener, the decisions that were made, the action items with an owner and a date on each, and exactly one ask. Keep it under 150 words and send it within 24 hours. Templates 1–3 above cover the most common cases.
How soon should you send a follow-up email after a meeting?
Within 24 hours — same day if you can. The email exists to capture agreements while everyone still remembers them the same way; every day of delay makes the recap less accurate and the reply less likely. If you take notes or record the meeting, the follow-up takes minutes instead of memory work.
How do you write a meeting recap email?
Put the meeting name and date in the subject, then list decisions, action items (owner + task + due date), and open questions — in that order. Send it to everyone who attended, and give a deadline for corrections (“flag anything wrong by Friday”) so silence counts as agreement. Skip the play-by-play; a recap records outcomes, not conversation.
Should the follow-up and the recap be the same email?
For a small meeting, yes — one email that recaps and makes a single ask. For anything high-stakes or with many attendees, split them: send the recap to the whole group as the shared record, then a short personal follow-up to the one person whose decision or reply you need. Mixing an ask into a group recap is how asks get ignored.