How to take meeting notes with AI: setup, consent and checks in the right order

How to take meeting notes with AI: the steps in order

• Step 1: name one owner for the notes and decide where recordings and transcripts are stored.
• Step 2: tell participants that the meeting is recorded, in the invite and again at the start.
• Step 3: choose the capture method: a bot that joins, device capture without a bot, or the notes built into your calling app.
• Step 4: run a five-minute test meeting with two colleagues and read the output.
• Step 5: run the real meeting, say decisions and names out loud, and verify the summary against the transcript before sending it.
• Step 6: file the notes where the team will find them and delete what you no longer need.

Prepare before the first meeting: owner, storage and consent

Before any tool runs, answer three questions. Who owns the notes and approves the summary? Where are recordings stored, and who can open them? Who has been told? Storage differs by tool. Microsoft's page says a Teams recording is uploaded to the organizer's OneDrive for private meetings or to SharePoint for channel meetings, and that people invited to the meeting can view it, while guests and external attendees see it only if it is shared with them. Krisp lists its own storage by plan, so a Krisp recording lives with Krisp unless you export it.

Put a short line in recurring invites, such as: this meeting is recorded and summarized with an AI tool. It costs nothing and answers most questions before they are asked.

Consent in plain words, and why a notice helps

This is background, not legal advice, so ask a lawyer about your situation. The Reporters Committee for Freedom of the Press, in a guide written for journalists, says federal law requires the consent of at least one party to record a conversation and that about 11 states primarily require every party's consent, including California, Florida, Illinois, Maryland, Massachusetts, Pennsylvania and Washington. The federal statute itself, 18 U.S.C. 2511, allows recording where one party to the communication consents, unless the purpose is criminal or tortious.

The same guide says recording is generally legal when the parties are warned and continue the conversation, and that recording each person's verbal consent is a best practice. When guests join from several states, telling everyone at the start is the simple rule. Google's help page adds that an administrator can require explicit consent before Take notes for me, Record or Transcribe starts, and that the setting is off by default.

Setup choices: bot, bot-free or your calling app's notes

• Bot that joins: it can attend when you cannot and is visible to guests. Krisp, Otter, Fireflies and Fathom each describe a bot option.
• Device capture without a bot: the tool records audio on your computer. In Krisp, select Krisp Microphone and Krisp Speaker in the calling app, turn the note taker on and pick transcript only, audio or screen recording.
• Built-in notes: Google Meet's Take notes for me and Copilot in Teams need no extra app but only work on their own platform. The team shortlist compares the options.
• Telling people: Krisp has a Notify others you're using Krisp setting under Privacy and Consent. Its help article warns that some platforms block chat messages or audio prompts, so say it aloud as well.
• Krisp example: what Krisp AI is explains the virtual devices behind this set-up.

Run the meeting, then verify the notes before anyone acts

Speak so the machine can follow. State names the first time someone talks, say decisions as complete sentences and read action items back at the end, for example: the marketing lead owns the vendor call, due Friday. Clean audio matters most, which is why Krisp's FAQ says transcript quality depends mostly on the speaker's clarity and microphone.

After the meeting, open the transcript beside the summary. Check each action item has an owner and a date, search the transcript for numbers, names and commitments, and fix anything the summary got wrong before you share it. For multilingual meetings, Krisp's help article advises audio recording so the transcript can be regenerated if it has mistakes. Treat the summary as a draft that a person approves.

Troubleshoot missing audio, wrong names and thin summaries

• Half the meeting is missing: Krisp's help article says to select both Krisp Microphone and Krisp Speaker in the calling app so the full meeting is captured.
• Speaker names are wrong: ask people to state their names early and fix labels in the transcript before sharing.
• The summary is thin: very short or noisy meetings give the tool little to work with. Add your own decisions in the notes.
• Nothing was captured on Teams: Microsoft's page says Copilot depends on the organizer's setting, so check the meeting options first.
• Guests object: pause the recording, explain how it is stored and offer to delete it.