# How to write a follow-up email after a client meeting, with templates

> For freelancers and consultants who send a recap after client calls on Google Meet or Microsoft Teams: when to send the follow-up email, what goes in it and in what order, subject lines that keep the thread findable, three copy-paste templates for a kickoff, a weekly status call and a difficult call, and who to copy. Ends with how TrackHeros puts the minutes on your clipboard.

Canonical: https://trackheros.com/blog/follow-up-email-after-client-meeting/  
Author: Sami Kanafani  
Updated: 2026-10-22

**In short:** Send a follow-up email after a client meeting the same day, ideally within the hour. Put the decisions first, then the action items split into yours and the client's, each with a date, then open questions, the next meeting and an invitation to correct anything. TrackHeros puts the minutes of a Google Meet or Microsoft Teams call on your clipboard with Copy for email.

A follow-up email after a client meeting turns what was said into what was agreed. This guide is for freelancers and consultants who run client calls on Google Meet or Microsoft Teams and want the recap to be quick to write and hard to misread. It covers when to send it, what goes in and in what order, subject lines, who to copy, and three templates to copy: after a kickoff, after a weekly status call, and after a call that went badly.

## When should you send a follow-up email after a client meeting?

The same day, within the hour if you can. People start acting on their own version of the meeting the moment it ends, and a recap that arrives the next afternoon has to compete with that version.

- Block fifteen minutes after every client call in your calendar, as part of the meeting.
- If the client's working day has already ended, send it anyway. It should be the first thing they read in the morning.
- After a hard call, give yourself an hour to write it plainly. Not a day.

## What goes in a meeting follow-up email?

Decisions, then actions, then open questions, then the next meeting, then a line inviting corrections. That order puts what matters most where someone reading on a phone will see it.

1. One line saying what the meeting was. Thanks are optional, and one word of it is enough.
2. Decisions, one sentence each.
3. Action items in two groups, "From me" and "From you", each with a date.
4. Dates that moved, and dates that did not.
5. Open questions, each with a name next to it.
6. The next meeting: day, time, timezone.
7. A correction line with a deadline.

The split in point 3 is the one most recaps miss. In a single mixed list a client sees your tasks; split into two, they see theirs. [How to write action items](/blog/how-to-write-action-items/) covers the items themselves.

What stays out: who argued for what, your opinion of a decision, estimates you are not ready to commit to, and anything at all about another client.

## What subject line should a follow-up email have?

The same pattern every time: what kind of meeting, which project, which date. A predictable subject keeps the thread findable on both sides months later.

| Meeting        | Subject line                                       |
| -------------- | -------------------------------------------------- |
| Kickoff        | Kickoff recap: [Project], [date]                   |
| Weekly call    | [Project] weekly: decisions and actions, [date]    |
| Scope change   | [Project]: change agreed on [date], please confirm |
| Difficult call | [Project]: what we agreed today, [date]            |
| Sign-off       | [Project] [milestone]: sign-off confirmed, [date]  |

Avoid "Follow-up", "Quick recap" and "Great call today". They say nothing in an inbox search, and the last one ages badly if the call was not.

## What should a follow-up email after a kickoff say?

Everything the project now rests on: scope, dates, who signs off what, and what each side owes the other in the first week. A kickoff recap is the email both sides will search for when there is a disagreement in month three, so it is the one to write most carefully. Agenda and questions for the call itself are in the [kickoff meeting guide](/blog/client-kickoff-meeting-agenda/).

```text
Subject: Kickoff recap: Payments integration, 6 October 2026

Hi Priya, Tom,

Thanks for today. Here is what we agreed, so we are working from the same page.

What we decided
- Phase one covers card payments and full refunds. Partial refunds move to phase two.
- Go-live is Tuesday 3 November 2026.
- Priya signs off designs; Tom signs off changes to the payments service.

From me
- The project plan with milestones, by Wednesday 7 October.
- The staging environment checklist, by Thursday 8 October.

From you
- Staging credentials, by Friday 9 October (Tom). The first deploy waits on these.
- Final copy for the checkout pages, by Friday 16 October (Priya).

Still open
- Is a load test needed before go-live? I will bring a proposal on Monday.

Next call: Monday 12 October, 10:00 London time, same link.

The full minutes are attached. If I have missed or misstated anything,
reply by Thursday and I will correct it.

Sam
```

## What should a follow-up email after a weekly status call say?

Only what changed: decisions, actions and the next call, short enough to read without scrolling on a phone. If the weekly recap keeps growing past that, the call is covering too much; the [weekly status meeting guide](/blog/weekly-client-status-meeting/) has a format that stays short.

```text
Subject: Payments weekly: decisions and actions, 12 October 2026

Hi Priya,

Short one this week.

Decided
- Partial refunds stay in phase two.
- Go-live stays on 3 November.

From me
- Estimate for partial refunds, by Monday 19 October.

From you
- Staging credentials (Tom), now due Friday 16 October.
  Each day they slip moves the first deploy by a day.
- Who signs off the design? (Priya), by Friday 16 October.

Next call: Monday 19 October, 10:00 London time.

Corrections by Wednesday, please.

Sam
```

## What should you send after a difficult client call?

Facts, agreements and next steps, in the plainest words you have. The email is not where you win the argument. It is where you fix what was agreed, so the argument does not have to happen twice.

- No adjectives about the meeting or about anyone in it.
- Acknowledge the problem in one sentence, without apologising for what was not yours.
- State what happened with dates, and what was agreed with dates.
- Include something you will do differently, if you agreed to.
- If nothing was agreed, say what happens next and when.

```text
Subject: Payments integration: what we agreed today, 19 October 2026

Hi Priya,

Thanks for raising the delay directly today. To make sure we have the same record:

What happened
- Today's planned release moved because staging access arrived on
  Friday 16 October rather than Friday 9 October, and the deploy needs
  five working days from access.

What we agreed
- The release is now Monday 26 October.
- From now on I will flag any blocker in the project channel on the day
  it appears, not at the weekly call.
- Tom will confirm by Wednesday whether production access can be set up
  this week, so go-live is not held up the same way.

Still open
- Whether the 3 November go-live holds. I will confirm by Friday 23 October.

If any of this does not match your notes, reply and I will correct it.

Sam
```

Write it, wait twenty minutes, then read it as if the client's manager will see it. They may.

## Who should be on the follow-up email?

Everyone who attended, plus anyone named in an action item who was not there. Copy nobody else without saying so: if you add someone senior, name them in the first line and say why. Reply on the same thread each week rather than starting a new one, so the history stays in one place.

Never send one recap to two clients, even when two meetings covered the same topic. Each client gets their own email, from the account you use for that client. [Keeping client notes separate](/blog/keep-client-meeting-notes-separate/) explains why the slip is so easy to make.

## How does TrackHeros help with the follow-up email?

TrackHeros does not send email for you. After a Google Meet or Microsoft Teams call, Export minutes on the meeting page offers Copy for email on every plan, which puts the minutes on your clipboard as HTML and plain text: paste into a mail client and the formatting comes with it, paste into a plain text field and you get clean text. Formal PDF minutes in the client's colour theme, for the kickoff attachment, are on paid plans ([pricing](/pricing/)).

Sections with nothing in them are left out, and headings follow that meeting's notes language. You still write the opening line, split the actions into yours and theirs, read it, and send it from your own account. More in [sending meeting notes to a client](/answers/send-meeting-notes-to-a-client/) and on the [minutes feature page](/features/meeting-minutes/).

## Frequently asked

**How soon should I send a follow-up email after a client meeting?**

The same day, and within the hour if you can. After a difficult call, wait until you can write it calmly, but still send it that day. A recap that arrives two days later competes with everyone's memory of the meeting, and usually loses.

**Should the follow-up email include the full minutes?**

For a routine call, the decisions, the action items and the next meeting in the body are enough. For a kickoff, a scope change or a sign-off, attach the full minutes as a document and still put the decisions and actions in the body, because the body is what gets read.

**Who should receive the follow-up email?**

Everyone who attended, plus anyone named in an action item who was not there. Do not add new people silently; if you copy in someone's manager, say so in the first line. Never send one recap to two clients.

**What if the client disagrees with the recap?**

That is what the recap is for. Correct it in a reply on the same thread, so the record and the correction sit together. A disagreement found the same day is a two-line email; found a month later, it is a dispute.

---

TrackHeros is in early access: https://trackheros.com/#early-access