Explain a meeting notetaker before a client call
The client should hear about the notetaker before it starts listening. Prepare the invitation, the opening and a real alternative, so nobody has to negotiate settings in the middle of the call.
What you'll make
a short notice for the client invitation, a spoken opening, a reply for when someone prefers no AI notes, and the notes’ sharing set to the right people.
What you'll need
approval to use this notetaker for this meeting, confirmed facts about what it captures, where the output goes, who can see it and how long it’s kept, and a host who can work the controls. Claude, ChatGPT, Gemini or Copilot in your work account turns the facts into wording. About 30 minutes. This helps you communicate an arrangement that’s already approved. Unresolved legal or privacy questions go to your privacy lead.
Example result.
We propose using Tool A to process the meeting audio and draft notes for our delivery team. It won’t save an audio recording. The notes will be held in our project workspace under the retention arrangements in the attached privacy notice. Please contact the organiser before the call if you have questions or would prefer manual notes.
1. Get the facts behind the notice
Write down the tool name attendees will recognise and exactly what it processes. A feature can process audio to make notes without keeping a recording, and screen content may end up in the notes too. “It only takes notes” is too vague. “It’s all secure” is not an answer and sounds like one, which is worse.
Confirm with your administrator:
- what is processed and what is saved
- where each saved output lives, and who can open it, including automatic recipients
- how long each output is kept, and any exceptions
- how someone raises an objection, and what the fallback is
Where outputs go depends on the tool. In Google Meet, notes are a Google Doc emailed to whoever the host’s sharing setting names. For Zoom and Teams, ask where transcripts and summaries are stored and for how long. Choose a meeting notetaker that fits your consent and retention rules has the full fact sheet.
Why this works: every sentence in the notice will be a promise. Checking the facts first means you only promise what’s true.
What you should see: a short fact sheet with each item confirmed or marked unknown.
2. Draft the invitation from those facts
Draft a short plain-English notice for a client meeting invitation, using only the facts below. Include the tool, its purpose, what is processed and saved, who can access it, retention and how to raise an objection. Point to the privacy notice for fuller detail.
Do not invent security, accuracy, location or deletion guarantees. Do not say that silence, attendance or clicking a product notice is legal consent. If a required fact is missing, list the question instead of writing a confident statement. Don't force it into two sentences if that removes something important.
FACTS: [fact sheet]
PRIVACY NOTICE: [link, or "not supplied"]
OBJECTION AND FALLBACK: [contact, process and alternative][fact sheet] is your list from step 1. [link, or "not supplied"] is the full privacy notice. [contact, process and alternative] is who to contact and what you’ll do instead.
Why this works: the invitation does most of the work, because people can read it and raise a concern privately, without an audience.
What you should see: a short notice in which every factual phrase matches your fact sheet.
3. Prepare the opening and a real fallback
Keep capture off until the notice and any consent steps are done. Don’t say “I’m turning it on now” while asking whether anyone objects.
Using the facts above, draft: 1. a brief opening before AI capture starts, asking whether attendees have questions or would prefer the alternative; 2. a brief reply when someone objects, using that alternative. Don't promise a control we haven't confirmed, ask anyone to explain an objection publicly, or treat no reply as consent.Rehearse the controls with the host. Know that a product notice can restrict people: Zoom lets admins require explicit consent, and non-host attendees then join with camera and microphone off until they accept. Don’t assume someone can decline and carry on normally.
Why this works: a fallback the host can actually run is what makes “prefer manual notes?” a genuine question.
What you should see: two short scripts, and a host who has practised switching capture on and off.
4. Set who receives the notes before the call
Decide the recipients before the meeting, not after. In Google Meet, the host chooses under Send notes to: all invited guests (including people outside your organisation), only invited guests inside your organisation, or hosts and co-hosts only. “Invited guests” means everyone on the Calendar invite, not everyone who actually attended, so a forwarded invitation can widen it. Set it in Google Calendar when you schedule.
During the call, check the indicators match what the host did. If someone joins late, give them the same notice.
Why this works: the notice describes who gets the notes. The sharing setting decides it.
What you should see: the sharing setting matching the access described in your notice.
Check the result
- Every claim in the notice matches a confirmed fact, and unknowns are questions, not reassurances.
- The objection route and the fallback appear in both the invitation and the opening.
- Capture stays off until the opening is done.
- Notes go only to the recipients the notice describes.
The usual failure: the assistant adds reassurance the facts don’t support. “Stored in our project workspace” becomes “your data never leaves our organisation”, or “kept for 60 days, with exceptions” becomes “all copies disappear after 60 days”. Spot it by underlining every promise and finding it on the fact sheet.
Remove [unsupported sentence]. Replace it only with this confirmed fact: [fact]. Restore the objection route and fallback. Keep any unknown information as a question for the organiser.[unsupported sentence] is the reassurance. [fact] is the matching line from your fact sheet.
Worked example: the client chooses manual notes
Fictional example. A consultancy’s privacy lead has approved Tool A for an ordinary project review. It processes meeting audio to draft notes and keeps no audio recording. Notes are stored in the project workspace, open to the named delivery team, and kept for 60 days subject to the firm’s preservation exceptions. Manual notes are the approved alternative.
The first draft invitation said: “Tool A only takes notes, and all copies disappear after 60 days, so your data never leaves our organisation.”
- The failure. “Only takes notes” hides the audio processing. “All copies disappear” ignores the exceptions. “Never leaves our organisation” isn’t on the fact sheet at all.
- The repair. Two passes of the repair prompt gave the notice in the example result. The 60 days stays in the full privacy notice, where its exceptions can be explained.
- On the call. The host opened: “Before we start, we proposed Tool A in the invitation. Capture is still off. Does anyone have a question or prefer manual notes? You can also message me privately.” The client asked whether the notes would reach the wider account team. The host checked the access list, answered, and the client preferred manual notes. “That’s fine. We’ll use manual notes today, and I’ll confirm the actions with everyone at the end.” Capture stayed off.
Task kit for this job: Download (ZIP) · Reusable instructions
Go deeper
Optional training: keep a recurring invitation accurate
Review the notice whenever the attendees, purpose, tool or settings change, and check for a new external guest before each meeting.
Meeting series:
Approved purpose and tool:
Notice version and link:
Capture and recipient settings, checked by and when:
Fallback and who can run it:
Change that needs a fresh review:Optional training: when the client brings its own notetaker
If an unfamiliar participant appears, ask before you carry on: “Before we go further, can I ask what that is in the participant list?” Ask what it captures, who sees the output and how objections are handled, and check your own organisation’s rules about externally captured meetings. A client’s preference and your organisation’s approval are separate facts.
Optional training: what you send afterwards is part of the promise
Review any generated notes before they go anywhere. Check actions, owners and conditions against what was said, remove personal material that isn’t needed, and send only to the recipients the notice described. Use ChatGPT to extract actions from meeting notes covers checking the actions. If capture started when it shouldn’t have, Review which meetings should use AI notes covers what to do next.