AI meeting notes to a follow-up email, sent while the meeting is still fresh

Who it’s for

UK consultants, freelancers and solo founders who have several client meetings a week and too many follow-ups that go out late or not at all

Time to set up

10 minutes (Meet or ChatGPT), 45 minutes (optional Make flow)

Difficulty

Beginner

Monthly cost

£0 on top of what you already pay

Here are my notes or a transcript from a client meeting. Write:
1) A follow-up email from me to [client first name], under 180 words, British English, plain and warm. Thank them, list the actions we AGREED (who, what, by when), then anything still to confirm, phrased as a question or a next step. No sign-off clichés.
2) ACTIONS: a table of action | owner | due date.
3) NOT AGREED / UNCLEAR: anything that sounded tentative, a guess or a 'probably'.
Use only what's in the notes. Never turn a maybe into a promise. Never invent dates, prices or names; where something is missing, add a short note in brackets saying in plain words what's missing, for example (no date agreed yet).
Notes: [paste]

The follow-up email is the cheapest thing a consultant can do to look organised, and the thing most often written at 7pm, or never. Meanwhile the client remembers “probably” as “yes”. This guide gets the email out while the meeting is still fresh, with the maybes kept out of the promises.

What does this automation do?

After a client meeting you get:

• a short follow-up email, as a draft, listing who agreed to do what and by when
• a separate list of things that were only floated, phrased as questions
• an action list you can paste into your task app (or that Google Tasks gets automatically)

Pick the route that fits your setup:

What do you need before you start?

• A sentence you’ll say at the start of meetings (Step 1).
• For Option A: a Google Workspace edition that includes “Take notes for me”. Google’s help page says the feature “requires an eligible Google Workspace edition or Google AI plan”, and next steps are listed for Business Standard and Plus, Enterprise Standard and Plus, and Google AI Pro for Education (Google).
• For Option B: a paid ChatGPT plan. OpenAI says audio uploads “are available with paid ChatGPT subscriptions and workspaces” (OpenAI, 6 October 2026).

How do I set it up?

Step 1: Tell people you’re taking notes

UK GDPR’s right to be informed means telling people, at the time you collect their information, what you’re collecting, why, how long you’ll keep it and who it’s shared with (ICO). For a client meeting, one sentence at the start does most of the work:

“I’m using AI notes so I can send you the actions straight after. They stay in our Google account and I delete them after 90 days. Happy to switch them off if you’d rather.”

Use whatever retention period you actually set. Put the same details in your privacy notice. If someone says no, switch it off and use the free prompt with your own notes instead.

Your Workspace administrator (probably you) can also make Meet ask every participant for explicit consent before notes, recording or transcription start. It’s off by default (Google Meet Help).

Step 2: Option A: switch on next steps in Google Meet

1. In the meeting, turn on “Take notes for me”. Next steps only appear if it was on during the meeting.
2. When the meeting ends, look on the post-meeting screen for “Routines for this meeting”.
3. Enable draft a follow-up email and, if you like, add action items to Google Tasks. You can switch a next step on for all your meetings, so it runs every time notes are on.

Google says these are the first two routines, with more on the way, and that the rollout started on 5 October 2026 and may take more than 15 days to reach everyone (Google Workspace Updates). If you don’t see it yet, use Option B or the prompt in the meantime.

The notes themselves go to a doc attached to the calendar event, and the notes email includes a meeting summary and suggested next steps (Google Meet Help). Meet’s draft is a good start; if you want the agreed/unclear split, paste the notes doc into the prompt in Step 4.

Step 3: Option B: upload the recording to ChatGPT

Record the meeting with whatever you already use (your phone’s voice recorder works for in-person meetings, once you’ve told people). In ChatGPT, attach the audio file to a new chat and ask for a transcript. OpenAI says you can turn “a meeting, interview, or lecture into structured notes or a follow-up email draft” (OpenAI). It also warns that “transcripts may contain errors”, which is why Step 5 exists.

Delete the recording when you no longer need it, in line with what you told the client.

Step 4: Run the follow-up prompt

Paste the transcript, Meet’s notes or your own scribbles into the copy-paste prompt. The important bit is section 3, NOT AGREED / UNCLEAR. Meetings are full of “probably”, “let’s aim for” and “I’ll check with my MD”. An AI summary tends to tidy those into decisions. The prompt keeps them out of the promises and turns them into questions.

Step 5: Check promises, dates and names before you send

Read the draft against your own memory of the meeting, in about a minute:

• Every “I’ll” in the email. Did you actually agree to it, by that date?
• Dates. Does “Friday” mean the right Friday? AI is bad at days of the week.
• Names and numbers. Transcripts mishear both. A budget that’s off by a zero is not a typo the client will forgive.
• Anything confidential said in the meeting that shouldn’t be in an email that may be forwarded.

Then send it from your normal email.

Step 6: Option C (optional): automate the draft with Make

Before you paste your key into Make

Give this scenario its own expiring OpenAI API key. In Project settings › Limits, set a monthly spend limit and turn on Enforce a hard limit, because “Spend alerts alone don’t stop API traffic.” (You need to be the project owner to set it.) Once the cap is hit, OpenAI stops the calls (spend can go slightly over), which beats a surprise bill. Key leaked? Replace it at once on the API keys page (OpenAI: Best practices for API key safety).

If you’re on Option A and want the draft in your own words every time, with an action log:

1. Meet’s notes arrive by email. In Gmail, give those emails a label, for example Meeting notes.
2. In Make, start with a Gmail trigger that watches emails with that label.
3. OpenAI › Generate a response, with our prompt and the email body mapped into “Notes”.
4. Gmail › Create a draft with the response. Leave the recipient for you to fill in.
5. Google Sheets › Add a Row to an “Actions” sheet: date, client, and the ACTIONS table.

This uses an OpenAI API key (billed separately from ChatGPT) and Make Free. We haven’t run this flow end to end yet, so test it on an internal meeting first.

The copy-paste prompt

Here are my notes or a transcript from a client meeting. Write:
1) A follow-up email from me to [client first name], under 180 words, British
English, plain and warm. Thank them, list the actions we AGREED (who, what, by
when), then anything still to confirm, phrased as a question or a next step.
No sign-off clichés.
2) ACTIONS: a table of action | owner | due date.
3) NOT AGREED / UNCLEAR: anything that sounded tentative, a guess or a
'probably'.
Use only what's in the notes. Never turn a maybe into a promise. Never invent
dates, prices or names; where something is missing, add a short note in
brackets saying in plain words what's missing, for example (no date agreed
yet).
Notes: [paste]

What UK rules apply?

• Transparency. Tell people you’re taking AI notes, why, how long you keep them and who sees them, at the time you collect the information (ICO: right to be informed).
• A lawful basis. You need one of the six lawful bases under UK GDPR to process personal information, and you should record which one you rely on. Consent is only one of them, and the ICO warns you can’t usually swap from consent to another basis later, so choose deliberately (ICO: lawful basis).
• Confidentiality. Your client contract or NDA may limit which tools can hold their information. If it does, use Option A inside your own Workspace, or anonymise notes before using the prompt.

What can go wrong?

• A maybe becomes a promise. The classic AI summary failure. The NOT AGREED section is there to catch it; don’t delete it from the prompt.
• Wrong recipient. Meet’s notes can be shared with everyone on the calendar invite, depending on your sharing settings. Check who gets the notes before you turn them on for client meetings.
• The rollout hasn’t reached you. Next steps were still rolling out on 20 October 2026. Use the prompt until it appears.
• The recording is the risk. Keep it only as long as you said you would, and keep it out of shared folders.
• Sending too fast. A follow-up in 5 minutes is great. A wrong follow-up in 5 minutes is worse than a right one tomorrow.

If the meeting was a sales call, our guide to turning a call into a proposal draft takes it from there. And when the work’s done, chase the invoice automatically. One automation like this lands in your inbox every Friday if you join our free email.

Frequently asked questions

Sources

1. Google Workspace Updates: Find your routine next steps on the post-meeting screen in Google Meet
2. Google Workspace Updates, October 2026
3. Google Meet Help: "Take notes for me" in Google Meet
4. OpenAI Help: ChatGPT release notes (6 October 2026, audio uploads)
5. ICO: Right to be informed
6. ICO: A guide to lawful basis

This guide is general information, not legal, tax or financial advice. Tool prices and screens change; we re-check every guide regularly. Spotted something out of date? Tell us and we’ll fix it.