Follow-up emails after a meeting: recap and thank-you templates

This page is for salespeople, account managers, founders and anyone else who has just come out of a meeting with a prospect, client or new contact and needs to write the email that follows. It covers thank-you notes, recaps for meetings with several people, site visits, events, senior executives and meetings that raised concerns. For calls (discovery, demo, pricing, no-shows), the sales call follow-up emails go into each outcome.

What a follow-up email after a meeting has to do

1. Thank them for something specific. "Thanks for walking me through the warehouse" says you were paying attention. "Thanks for your time" says nothing.
2. Recap what matters, not everything. Two or three decisions, numbers or concerns, in their words where you can. The attendees were there; they need the record, not the minutes.
3. Turn agreement into actions. Each action has one owner and one date. "We'll look into it" is not an action.
4. Confirm what happens next. The next meeting with a date, or the decision with a deadline. Send the calendar invite before the email so the email can say it's done.
5. End with one question. Usually "Did I miss anything?" It invites corrections while they're cheap and gives the reader an easy reason to reply.

Send it the same day. If the meeting ends late, send it first thing the next morning. Every day you wait, the attendees remember less and your recap matters more, because it becomes the only record.

Recap or minutes? What goes in the email

If you need full minutes for a formal meeting, attach them or link to them, and keep the email to the summary.

Follow-up email after meeting templates

Fill each bracket from your notes. If you can't fill one honestly, cut the line.

Subject: [Topic]: notes from [day]'s meeting

Hi [first name],

Thanks for [specific: walking me through how your team handles X]. The point about [something they said] was useful, and I've already [small action you took].

What I took away:
- [Their goal or problem, in their words]
- [The number or constraint that matters, e.g. "has to be live before the March intake"]
- [How they'll decide, and by when]

Next steps:
- Me: [action] by [date]
- You: [action] by [date]
- Both: [next meeting, date and time], invite sent

Did I miss anything?

[Your name]

Subject: Thank you, [first name]

Hi [first name],

Thank you for today. I especially appreciated [specific point or introduction].

As promised, I'll send [the thing] by [date]. Until then, if anything comes up, I'm on [phone].

[Your name]

Subject: [Company] and [your company]: decisions and actions from [date]

Hi all,

Thanks for making time today, and to [name] for [specific contribution]. A summary, so everyone has the same record:

Decided:
1. [Decision, e.g. pilot with the Denver team first]
2. [Decision]

Open questions:
- [Question] (who's finding out: [name], by [date])

Actions:
- [Name]: [action] by [date]
- [Name]: [action] by [date]
- [Your name]: [action] by [date]

Next meeting: [date, time, who should attend]. Invite sent.

Please reply if I've got anything wrong, or forward this to anyone who should have been there.

[Your name]

Subject: What I saw at [site]: notes and next steps

Hi [first name],

Thanks for the tour of [site] on [day]. Seeing [specific thing, e.g. how garments are sorted on the dock] made [their problem] much clearer than a call would have.

Three things I noted:
- [Observation 1, with a number if you have one]
- [Observation 2]
- [Observation 3]

I'll send [proposal, quote or plan] based on these by [date]. If I've misread anything, tell me before I build it in.

[Your name]

Subject: Good to meet you at [event]

Hi [first name],

Good to meet you at [event] on [day]. You mentioned [specific thing they said, e.g. that hiring for the new clinic starts in January].

[One useful thing tied to it: a resource, an introduction or a short answer to their question.]

If it's worth a proper conversation, would [day] or [day] next week suit for 20 minutes?

[Your name]

Subject: [Their priority]: next step from today

Hi [first name],

Thank you for the time today. You said [their priority, in their words]. We'll [what you'll do] and have it with [their delegate] by [date].

[Your name]

Subject: Your questions about [topic]

Hi [first name],

Thanks for being direct today. I heard two concerns: [concern 1] and [concern 2].

On [concern 1]: [answer, with evidence or a reference you have permission to share].
On [concern 2]: I don't have a good answer yet. I'll come back by [date] with [what you'll check].

Does that cover it, or is there something behind these I should know?

[Your name]

Subject: Thanks for the coffee, [first name]

Hi [first name],

Thanks for meeting on [day]. Your advice on [topic] was useful, and I'm going to [what you'll do with it].

As promised, here's [the introduction, article or contact you offered]. If I can return the favor with [something you can offer], just ask.

[Your name]

Subject: [Meeting name] recap: [date]

Hi all,

Thanks for joining. Here's what we agreed.

Purpose: [one line]
Decisions: [numbered list]
Actions: [name, action, date for each]
Not decided yet: [items, and when we'll decide]
Next meeting: [date and time]

Reply with corrections by [day], after which I'll treat this as the record.

[Your name]

Subject lines for follow-up emails after a meeting

Name the topic or the meeting. "Following up" and "Checking in" describe what you're doing, not what's in the email.

Sending it to everyone who was there

You don't need to retype the invite list.

• Outlook (new): open the meeting in your calendar, open the Tracking pane, select More options and choose Copy attendee names, then paste them into a new email.
• Outlook (classic): open the meeting, select Tracking, then Copy Status to Clipboard, and paste into the To line, keeping only the addresses.
• Google Calendar: open the event and select Email guests, next to the number of guests. A new email opens with every invited guest included.

Check the list before you send. Invites often include people who declined, a colleague's assistant or someone from your own side who shouldn't see what you say to the client.

Worked example: a recap after a buying-group meeting

Illustrative example. The companies, people and figures are fictional, to show the method.

The seller: Nadia, an account executive at Talentloop (talentloop.example), recruiting software. The prospect: Brightwater Health (brightwaterhealth.example), a group of outpatient clinics with six recruiters. In the meeting: Owen, VP of talent acquisition; Priya, HR systems manager; and Marcus from finance, who joined for the last 15 minutes.

What Owen said: each recruiter spends about 6 hours a week scheduling interviews by email, and Brightwater opens a new clinic in March that needs 40 hires. Nadia's estimate, which Owen agreed was fair to test, was that self-scheduling halves that time.

Subject: Brightwater and Talentloop: decisions and actions from 21 October

Hi Owen, Priya and Marcus,

Thanks for today, and to Priya for showing us the current interview calendar. A summary, so we're working from the same record:

Decided: we'll test self-scheduling with two recruiters for three weeks, starting 3 November.

The numbers we agreed to test: your recruiters spend about 6 hours a week scheduling. If the pilot halves that, the six of you get back 828 hours a year, worth about $37,260 at Marcus's $45 an hour, against an $18,000 subscription. The pilot will tell us whether 50% is right.

Open question: whether the integration needs IT approval (Priya to check by 28 October).

Actions:

• Nadia: pilot accounts and setup guide by 30 October
• Priya: names of the two pilot recruiters by 28 October
• Owen: confirm the March clinic hiring plan by 31 October

Next meeting: 24 November, pilot results, with Marcus. Invite sent.

Did I miss anything?

Nadia

Why it works: every number has a name next to it, so Marcus can check the arithmetic without having been in the room. The 50% is labeled as something the pilot will test, not a promise. Each action has one owner and a date, and the next meeting is already booked.

Before a meeting like this, it helps to know who else is involved and what's changing at the company. Bebop researches each account and writes a playbook with the people, recent news and the angle to open with, so you walk in knowing more than the agenda.

Mistakes to avoid

• "Per our meeting, please find attached our deck." It shows you weren't listening and gives them homework.
• Recapping your pitch. The recap is about their situation and decisions.
• Actions owned by "us" or "the team". Give each one a name.
• Waiting a week. By then, someone else's version of the meeting is the one people remember.
• Getting a name or number wrong. One error makes readers doubt the rest.
• Sending it to everyone on the invite without checking. Remove declines and anyone who shouldn't see it.

Checklist before you send

• It's going out the same day, or first thing the next morning.
• The thank-you names something specific.
• The recap has two or three points, in their words where possible.
• Every action has one owner and one date.
• The next meeting invite is already sent.
• Someone who missed the meeting could forward it and understand it.
• The subject line names the topic, not "Following up".
• There's one question at the end.

Next step: when a deal has several people and dates to keep track of, turn the recap into a shared plan with the mutual action plan template.