AI Meeting Notes: The Complete Workflow, the Right Tools and Recording Consent Rules in the US (2027)
From scheduling to the follow-up email: how to run meetings with AI, which note takers fit Zoom, Teams and Google Meet, 7 copy-paste prompts, and the recording consent rules every US team should know before a bot joins the call.

The average knowledge worker spends a big part of the week in meetings, then more time scheduling them, writing up notes and chasing whoever promised to do something. The good news: almost every step, from the invite to the follow-up, can now be done faster with AI. The less good news: done badly, you get long AI summaries nobody reads, tasks without owners, and, in a dozen US states, a real legal risk if you record without everyone's consent.
This guide follows the life of a meeting: scheduling, preparation, recording and transcription, the summary, the follow-up email, task tracking and recurring meetings. Each step has the right tools, a copy-paste prompt, and what you need to know when you work inside a company.
- The rule that matters: a recap with decisions, owners and dates, sent within ten minutes of the meeting ending.
- The method that works: a transcription tool your company approved, plus an AI assistant such as Claude or ChatGPT that turns the transcript into a summary, an email and tasks in a fixed format.
- Before you record: tell everyone and get their consent. In all-party consent states such as California, Florida and Pennsylvania, recording without it can be a crime.
Step 1: Schedule without an email chain
Scheduling a meeting with five people can take longer than the meeting itself. Three ways to cut it short:
- The calendar you already have: Outlook and Google Calendar now include AI assistants that suggest times based on attendees' availability.
- A booking link: tools such as Calendly let the other side pick a free slot. Best for meetings with people outside your company.
- An AI assistant: Claude and ChatGPT can connect to Google and Microsoft 365 calendars, propose slots and draft the invite. Even without a connection, paste the availability and ask.
Prompt: schedule a multi-person meeting
I need to schedule a [length] meeting about [topic] with: [names].
Here is my availability and theirs this week: [paste free slots or calendar screenshots].
1. Suggest 3 times that work for everyone, prioritizing [key attendee].
2. If no time works for everyone, suggest the one that works for most and say who it does not work for.
3. Write a short invite: title, the meeting goal in one sentence, and 3 agenda points.
4. Write a short, polite note to anyone the time does not suit, asking for an alternative.
Tip: every invite needs one sentence that says what decision must be made by the end. If you cannot write that sentence, it is probably an email, not a meeting.
Step 2: Prep and agenda
Meetings without an agenda run long and end without decisions. AI builds an agenda in a minute from the last meeting's notes, and gets you to a client meeting already knowing the full history.
Prompt: agenda from the previous meeting
Here are the notes from our last meeting about [topic]: [paste].
Build an agenda for the next meeting, [length] long:
1. Start with open items and tasks that were not completed.
2. For each item, write the decision that must be made (not just "discuss").
3. Split the time between items and leave 5 minutes to wrap up.
4. Flag any item that should be an email instead of meeting time.
Prompt: client meeting prep sheet
I have a meeting with [client] about [topic].
Here is what I have: [email history, past proposals, notes from the last meeting].
Prepare a one-page brief:
1. Where things stand: what the client needs and what was already agreed.
2. Open commitments, ours and theirs.
3. Three points I want to get across.
4. Three tough questions they may ask, with a suggested answer for each.
Make it a habit: keep a project (in Claude) or a custom GPT per client or team with past meeting notes. Then "prep me for the next meeting" already has all the context.
Step 3: Recording and transcription
This is the big leap: instead of typing during the meeting, an AI tool records, transcribes and identifies speakers, and you are free to listen and take part. Before choosing a tool, answer three questions: does it fit your meeting platform, did your company approve it, and how does it handle consent.
| Option | How it works | Worth knowing |
|---|---|---|
| Google Meet, "Take notes for me" (Gemini) | Built in. Captures notes into a Google Doc and emails the organizer a recap | Needs an eligible Workspace edition or Google AI plan. Google lists English, French, German, Italian, Japanese, Korean, Portuguese and Spanish, one language per meeting |
| Microsoft Teams intelligent recap | Built in. AI notes, tasks and recap after the meeting | Requires Teams Premium or a Microsoft 365 Copilot license (Microsoft Q&A) |
| Zoom AI Companion | Built in. Meeting summaries and in-meeting questions | Availability depends on your Zoom plan and admin settings |
| Bot notetakers (Otter, Fireflies, Fathom, tl;dv, Read.ai) | A bot joins the call as a participant and records | Work across Zoom, Meet and Teams. Everyone sees the bot, which helps with consent, but auto-join settings can bring it into meetings unannounced |
| Botless recorders (for example Granola) | Records from your computer's audio, no bot joins | Granola says it works with Zoom, Meet, Teams and other apps. Nobody sees a bot, so you must announce the recording yourself |
Features and plans change quickly. Before you commit, record one real meeting and check the transcript on names, industry terms and crosstalk.
Is it legal to record a meeting? Consent rules in the US
Federal law and most states follow one-party consent: you may record a conversation you are part of. But a group of states requires the consent of everyone on the call. Legal guides such as the Digital Media Law Project commonly list California, Connecticut, Florida, Illinois, Maryland, Massachusetts, Montana, New Hampshire, Pennsylvania and Washington. Several others, including Oregon and Michigan, have nuances that depend on whether the conversation is in person or electronic, or on who is recording. The Reporters Committee's state-by-state guide goes into each state.
Why it matters now: in August 2025 a federal class action was filed against Otter.ai, alleging its notetaker recorded meetings and used the audio for AI training without the informed consent of all participants, including people who were not Otter users (NPR). Whatever the outcome, it shows where the risk sits: in auto-join settings and in participants who never agreed.
- The practical rule: on any call that crosses state lines, treat it as all-party consent. Announce the recording at the start and give people the option to object.
- Turn off auto-join for notetaker bots, or limit it to internal meetings.
- Meetings you should not record: HR conversations, sensitive negotiations, legal matters and anything personal. Write a summary afterward instead.
- Approved tools only: a meeting transcript is sensitive company data. Upload it only to tools your company approved, in their business version.
This is general information, not legal advice. Check with your legal team for your situation.
Step 4: A summary people actually read
Most transcription tools produce an automatic summary, but it is usually long, generic, and does not separate what was said from what was decided. The method that works: take the transcript and ask an AI assistant for a summary in a fixed, three-part format.
Prompt: meeting summary with owners and dates
You are an assistant who knows a meeting summary is only useful if every task has an owner and a date.
Here is the transcript or notes: [paste]
Attendees: [names and roles]
Write the summary in this format:
Decisions: what was decided, one line each.
Tasks: what needs to happen, who owns it, and by when.
Open questions: what was not settled and who will find out.
Rules:
- Do not guess an owner or a date. If it was not said, write "not set" and flag it.
- Separate decisions from general discussion. Things that were only mentioned are not decisions.
- Keep it short and plain.
Save this prompt as a reusable instruction (a Skill in Claude, a custom GPT or a Copilot prompt) so every summary in the team looks the same. For the first two weeks, compare the AI summary to what you would have written, note what is missing, and add it to the prompt.
Example: a launch meeting recap
Decisions: launch moves to Dec 15 to finish security testing. The campaign targets existing customers in the first month.
Tasks: Dana (engineering): finish security testing by Dec 1. Josh (marketing): draft the existing-customer campaign by Nov 25. Not set: owner for briefing the support team on the launch date.
Open questions: launch in Spanish too? Michelle checks with leadership.
Notice the "not set" line: that is exactly what the AI should flag instead of guessing. A task without an owner is the task that will not happen.
Step 5: The follow-up email within ten minutes
A recap sent the next day is far less useful, because everyone remembers the meeting differently. The target is a follow-up within ten minutes of the end, while everyone still remembers what was decided.
Prompt: ready-to-send follow-up email
Turn this summary into a follow-up email to the attendees: [paste summary]
- Subject: [meeting name] + "recap and next steps".
- A one-sentence opening, no "Hi all, thanks for joining".
- Three bold sections: Decisions, Tasks (owner and date), Open questions.
- One closing line asking people to flag anything inaccurate by [day].
- Tone: [direct / warm / formal], short enough to read on a phone in 30 seconds.
If your assistant is connected to Gmail or Outlook, ask it to put the draft straight into your mailbox. It drafts, you read and send.
Step 6: Task tracking, so the meeting is not forgotten
Many decisions die between the meeting and the task tool. AI closes the gap: it turns each task into a proper item in the tool your team uses, and spots the task nobody owns.
Prompt: tasks ready for your tracker
Take the tasks from this summary: [paste]
Turn each one into an item for [Asana / Jira / monday.com / Notion]:
task name (verb + outcome), owner, due date, and a short paragraph of context.
Then find the least clear task, without an owner or a date,
and write a short, polite message to the relevant person asking them to confirm an owner and a date.
Step 7: Recurring meetings that do not start from scratch
Weekly meetings collect topics that come back every week without moving. Once a month, let AI review the recent notes and suggest what to close, escalate or shorten.
Prompt: clean up a recurring meeting
Here are the notes from the last 4 sessions of our recurring [name] meeting: [paste]
1. Find topics that come up every time without progress.
2. For each, recommend one of three: close it, escalate it to a decision-maker, or time-box it.
3. Check whether the meeting still needs every attendee and all of its time.
4. Suggest a fixed agenda template for this meeting from now on.
What this means for your organization
AI notetakers spread inside companies the same way most AI tools do: one employee installs one, then the whole team has a bot in every call. According to Microsoft and LinkedIn's Work Trend Index, most people who use AI at work bring their own tools rather than waiting for the company. For meetings that means transcripts of internal discussions sitting in tools nobody approved, and recordings made without everyone's consent.
Three decisions are worth making now: which notetaker the company approves, and in which version; a clear rule on announcing recordings and on which meetings are never recorded; and one shared summary format, so every recap shows decisions, owners and dates. "The value of AI in meetings is not the transcript, it is the ten minutes after," I tell the teams I work with. "A recap with owners and dates, sent while everyone still remembers, is what turns a meeting into progress."
If you are planning AI adoption across teams, our guide to AI implementation in organizations covers policy, training and measurement. Want help setting this up in your company? Use the form below.
Frequently asked questions
What is the best AI meeting note taker?
It depends on your platform and policies. Google Meet, Microsoft Teams and Zoom have built-in AI notes on eligible plans. Bot notetakers such as Otter, Fireflies, Fathom and tl;dv work across platforms, and botless recorders such as Granola record from your computer. Test one real meeting before you choose, and pick a tool your company approved.
Is it legal to record a work meeting with an AI note taker?
Federal law and most states allow recording a conversation you are part of, but states such as California, Florida, Illinois, Maryland, Massachusetts, Montana, New Hampshire, Pennsylvania and Washington are commonly listed as requiring consent from everyone. The safe practice is to announce the recording and get consent on every call. This is not legal advice.
How do I write meeting notes with AI?
Give an AI assistant the transcript and the attendee list, and ask for three sections: decisions, tasks with an owner and a date, and open questions. Tell it not to guess owners or dates and to flag what is missing.
How soon should I send a meeting recap?
Within ten minutes of the meeting ending, while everyone still remembers what was decided. With a transcription tool and a saved prompt, it takes a few minutes.
Do AI note takers use meeting recordings for training?
Policies differ by vendor and plan. A 2025 class action against Otter.ai alleged recordings were used for AI training without all participants' consent. Check each vendor's data policy and prefer business plans that commit not to train on your data.
Talk to us about AI in your organization
We help companies operating in Israel map their AI systems, build an AI policy, prepare for the EU AI Act and Israeli privacy law, and train their teams. Leave your details and we will get back to you within one business day.
The Israel AI Organization helps companies and public bodies in Israel adopt AI responsibly. Our daily content is published in Hebrew. About us · Read this guide in Hebrew