# Read AI Meeting Notes: Add It to Teams, Zoom and Google Meet > How read.ai meeting notes joins Teams, Zoom or Meet, what attendees can do and who gets the report. Free: 5 reports a month (shared count), 1-hour meetings. _Source: https://professionalstoolkit.com/articles/read-ai-meeting-notes — The Professional's Toolkit · updated November 2026_ --- When a participant named **read.ai meeting notes** appears in your call, it is Read AI's meeting assistant: a visible bot that someone on the invite added, which records, transcribes and sends a meeting report afterwards [1]. Adding it yourself takes a free account and one connected calendar, and by default it then joins every event on that calendar. The rules differ by platform. On Teams it joins as an anonymous guest, on Google Meet it can record without any bot, and since November 2026 it joins Zoom only when you connect your Zoom account and attend. The Free plan covers 5 meeting reports a month (reports shared with you count), with each meeting capped at 1 hour. **Nov 2026** — Since then, Read joins a Zoom meeting only with your connected Zoom account and you in the call - **5 a month** — Meeting reports on Free, shared ones included - **1 hour** — Longest meeting on Free (4 hours on Pro) - **10 min** — Window to admit Read or approve Meet native recording ## What the read.ai meeting notes participant actually is Read AI, Inc. is a Seattle company, and this assistant is the core of its product. It joins Zoom, Microsoft Teams and Google Meet calls with its own video tile, records and transcribes, then builds a report with a summary, chapters, action items, key questions and a transcript by speaker. Read AI's pages also call it Read Assistant or Read Meeting Notes. The display name can change. Free users pick from preset names, such as Meeting Analytics from Read or a first-name Assistant or Notetaker, while a fully custom name needs a paid plan. A custom logo on the tile is also paid, and it shows on Zoom only. Read AI says it never joins a meeting on its own: someone on the invite with a Read account added it, directly or through calendar auto-join. That second route explains most surprise appearances. Once a calendar is connected, the default joins **all calendar events with any participants**, and onboarding marks that choice as recommended. The alternatives are events you host, events Read is invited to (which joins nothing automatically), internal participants only, or auto-join off. Read arrives about 3 to 5 minutes early and leaves if nobody admits it or nobody joins within 10 minutes. Supported calendars are Google Calendar, Zoom Calendar and Outlook in Microsoft 365; Apple iCloud is not. ## Adding it to a Microsoft Teams meeting Teams draws the most searches, and it has the most admin conditions. Read joins a scheduled Teams meeting as an anonymous, unverified guest. That works only if your organization allows guest access and lets anonymous users join meetings. Read cannot pass the Teams human verification check, so tenants with bot detection switched on must pick the option that skips it. It then waits in the lobby until admitted, and the host can deny it there. It can join without you, though someone may still need to let it in. Calls started from a Teams chat are out of reach: use the desktop app or upload a recording instead. To add Read to a meeting already underway, install the free Read AI app for Teams from AppSource. It needs a paid Teams or Microsoft 365 account, and you must be the organizer, a co-organizer or a presenter. The app adds Read to the live call, shows the live dashboard in the sidebar and offers Ask Read during the meeting. You can also paste the meeting link into Add to live meeting in Read's web app, or use the browser extension on Chrome, Edge, Opera or Brave. **A manually added meeting** gets a generic title and does not auto-share the report to participants. > 💡 **Check Teams guest settings first:** Read joins Teams as an anonymous, unverified guest, so it never gets in where anonymous users cannot join meetings. Ask your Teams admin before blaming the calendar. ## Adding it to Zoom after the November 2026 change Zoom now requires every meeting bot to be authorized by a signed-in Zoom user. So since November 2026, Read joins a Zoom meeting **only if you have connected your Zoom account to Read and you are in the meeting, signed in to that account** [2]. It can no longer be sent alone. A free Zoom account is enough, but a connected calendar without Zoom captures no Zoom meetings at all. For hosts, the upshot is simple. The bot in your Zoom call belongs to someone who is present. Once inside, Read asks the host for recording permission. If the host refuses, or recording to computer files is switched off, the report shows a Restricted Data error and Read leaves after a few minutes. Hosts may see no admit request at all. To add Read mid-call, use Add to live meeting on the website, the Zoom App (desktop client only, Zoom 5.7.3 or later) or the browser extension, and the Auto-Join Unscheduled Meetings setting covers Zoom calls you start outside the calendar. Zoom Whiteboards are never recorded. Subscribers to Zoom One Pro, Business or Business Plus get a separate Zoom Apps plan free for 12 months, covering the first 5 meetings a month with 60-minute recordings and no playback, after which the account moves to Free. ## Adding it to Google Meet: agent, native recording or add-on Google Meet offers two modes. The AI meeting agent is the familiar bot participant, and it can join without you. Native recording uses Google's Meet Media API, so no bot joins and no extension is needed; Read AI recommends this mode once Google Meet is connected under Integrations [3]. The catch is consent. Someone must approve a pop-up within 10 minutes of the scheduled start. In a meeting hosted by a Google Workspace organization, that is someone from the Workspace; for a gmail.com host, it is the person who invited Read, who must be in the call. Native recording has firm exclusions. It cannot record meetings with underage participants, watermarking or client-side encryption, and conference-room devices that cannot show the pop-up cannot approve it. Closing the pop-up without confirming keeps Read from recording. The free Google Meet add-on, installed from the Google Workspace Marketplace, records through native recording and can start automatically from Google Calendar. Running the add-on and the bot assistant in one call produces two separate reports. Choose one. Google Workspace admins who want Read out entirely can disable the Meet Media API for third-party apps, and a host can switch off third-party apps for a single meeting. ## What everyone else in the call sees and can do In bot mode, nobody has to guess. On joining, the assistant posts a chat message with a recording notice, the name of the person who invited it and how to remove it. Two chat commands work for any participant, with no account and no host approval. Typing **Read stop** makes it leave and still produce a report up to that point. Typing **Opt out**, or using the opt-out link, makes it leave and delete everything, with no report. One opt-out covers everyone. Hosts can also remove it like any participant, from the Zoom participants list or the Teams People panel. Native recording on Meet changes the controls. Chat commands do not work there; any participant clicks the Read AI logo, then Stop sharing to keep a partial report, or opens the Read AI app from the 9-dot grid to opt out and delete. Desktop and mobile recordings differ again: Read is not a participant, so others see nothing and the user must collect consent. Several attendees with Read each bring their own assistant, and switching yours off never stops theirs. Our guide on [how to remove Read AI](/articles/how-to-remove-read-ai) covers every route, including auto-join settings and calendar disconnection. > ⚠ **The defaults share with everyone:** Once a calendar is connected, Read joins all calendar events and sends the recap to People with access by default, including during the 7-day Enterprise trial. Change both under Account Settings before your next meeting. ## Real-time notes and the report afterwards During the call, the live meeting dashboard shows a live transcript, bullet summaries refreshed roughly every minute, filler words, words per minute, Read Score, engagement and sentiment. You can star moments and keep private notes that only you see. If automatic dashboard sharing is on, Read posts the link in chat about 3 minutes in, and anyone holding it can view without an account. That link never appears with Meet native recording. Coaching stays private to each attendee and exists only for people with an active Read account at the time of the meeting. Most reports are ready within 5 to 15 minutes, and a meeting needs at least 50 words of speech to produce one. By default the recap goes to **People with access**, which Read marks as recommended; Only me and No one are the other choices. Reports are shared with everyone invited, internal participants as editors and external ones as viewers. Recipients need a free Read account unless link access is set to Anyone with the link, which effectively makes the report public. Anyone who adds Read gets editor access and can share under their own settings. Only the owner can block that, by marking the meeting private. > 💡 **Lock a sensitive report down:** Only the report owner can mark a meeting private, which sets participant access to none and stops other invitees from adding their own Read. ## What each plan covers per meeting Only one person in a meeting needs a Read account, and the report runs on the plan of whoever invited Read. That makes the inviter's plan the one that sets the length cap; on Free, a report shared with you still counts toward your own 5 a month. Enterprise+ requires 5+ licenses, and Read AI routes it through sales. The grid below lists Read AI's prices per user per month, read from the pricing page in November 2026. | Plan | Price per user per month | Meeting reports | Longest meeting | |---|---|---|---| | Free | $0, no card | 5 a month | 1 hour | | Pro | $15 per user per month billed annually / $19.75 per user per month billed monthly | Unlimited | 4 hours | | Enterprise | $22.50 per user per month billed annually / $29.75 per user per month billed monthly | Unlimited | 4 hours | | Enterprise+ (5+ licenses) | $29.75 per user per month billed annually / $39.75 per user per month billed monthly | Unlimited | 8 hours | On Free, the 5 reports include reports others share with you, and from the sixth the report shows as Out of quota, without a transcript [4]. Hitting the length cap does not lose the meeting: Read leaves and builds the report from what it captured. Upgrading reprocesses the past 30 days and unlocks those reports. Every new account starts with a 7-day Enterprise trial, no card, which joins all calendar meetings by default and then drops to Free automatically. For one user, Pro comes to $180 a year billed annually or $237 billed monthly, by our arithmetic. The full breakdown sits in [Is Read AI free?](/articles/is-read-ai-free). ## FAQ **Can Read AI join Webex or GoTo Meeting calls?** No. Read cannot join Webex, GoTo Meeting, RingCentral or Slack huddles as a participant; use its desktop app, which captures computer audio on any platform, or upload a recording. **Will Read join a meeting I was not invited to?** No. Read joins only meetings you are invited to, and meetings on a shared calendar never have Add Read switched on by default. **Can I skip Read for one meeting but keep auto-join?** Yes. Turn off Add Read for that meeting on Read's Calendar page at least 15 minutes before it starts, for that single meeting or the whole series. **Does Read capture the typed meeting chat?** No. Read does not capture typed meeting chat; the report comes from the spoken audio, and a meeting needs at least 50 words of speech to produce one. ## The bottom line The read.ai meeting notes participant is a visible, removable bot that someone on the invite chose to bring. Getting it into a call is easy, but each platform sets its own gate: anonymous guest access on Teams, your own signed-in presence on Zoom, and a 10-minute consent pop-up for Meet native recording. The defaults deserve the most attention. Read joins every calendar event and shares the recap with everyone who has access unless you change both before the first meeting. ## Sources [1] Read AI help: What should I tell attendees who ask what Read AI is? — https://support.read.ai/hc/en-us/articles/6186614697619-What-should-I-tell-attendees-who-ask-what-Read-AI-is (2026-11) [2] Read AI help: Upcoming Changes to Zoom Meetings — https://support.read.ai/hc/en-us/articles/48409575283347-Upcoming-Changes-to-Zoom-Meetings (2026-11) [3] Read AI help: Using Read's Google Meet Native Recording — https://support.read.ai/hc/en-us/articles/42785087487251-Using-Read-s-Google-Meet-Native-Recording (2026-11) [4] Plans & Pricing — https://www.read.ai/plans-pricing (2026-11) [5] Read AI help center — https://support.read.ai/hc/en-us/articles/22307341312275-What-are-the-different-paid-plans-that-Read-offers [6] Read AI Terms of Service — https://www.read.ai/termsofservice [7] Read AI Privacy Policy — https://www.read.ai/privacy-policy