Claude Meetings: Claude joins your Google Meet calls. The four settings to decide before anyone invites it
In brief
On November 12, 2026 Anthropic released Claude Meetings in beta for Team and Enterprise. Claude joins Google Meet as a visible participant, answers questions in the call chat, builds docs and whiteboards while people talk, and leaves notes and action items on a meeting page in claude.ai. It keeps transcripts and screen descriptions but no audio. On Team plans it is on by default. What it does, what it costs during beta, and the four decisions an admin should make first.
Contents
On November 12, 2026 Anthropic released Claude Meetings, in beta on Team and Enterprise plans. Claude joins a video call as a participant you can see, follows the conversation, and does work during the meeting instead of after it.
Google Meet is the only supported platform today. Anthropic says other platforms are coming.
What Claude does in a call
- Someone invites it. Add Claude to a calendar event from claude.ai, or turn on auto-join so it joins your meetings by default.
- It announces itself. Claude shows up in the participant list and posts a notice in the call chat.
- People ask it things. You can ask out loud or in the chat. By default Claude answers in writing in the chat, so everyone on the call sees the answer.
- It builds while you talk. Ask for a draft plan, a whiteboard of the options being discussed, or a doc, and Claude makes it during the call. Invitees can edit it at the same time.
- It writes up the meeting. Claude takes notes and action items and can post a recap before the call ends.
- It leaves a meeting page. Afterward, claude.ai has a page for that meeting with notes, the transcript, and anything Claude built. People from your organization who were invited can view and edit it, and it can be shared inside the organization.
Later, you can ask Claude about past meetings ("what did we decide about the Q1 launch date?") from a normal chat.
The whiteboards and docs it builds are the same Claude Whiteboards and artifacts released two days earlier.
What it keeps, and what it does not
- Kept: a transcript, a summary, and descriptions of what was shown on screen.
- Not kept: audio.
- Connected tools: Claude uses a person's connected tools, such as their Google Drive or CRM, only with that person's permission. It asks the first time, and a yes holds for later meetings. For spoken requests it confirms who is speaking each time, so a colleague cannot ask Claude to pull your files by talking.
Outside guests
By default, Claude stays out of any call that has someone from outside your organization on the invite, and leaves if an outside person joins later. An admin can allow it on external calls. When it is allowed, Claude still posts its notice but does not answer in the chat. What guests say still ends up in the notes and transcript.
What it costs during beta
| Use | Cost during beta |
|---|---|
| Notes and transcripts | Free on Team and Enterprise |
| Answers in the call | Free, unless Claude uses a connected tool. Then it counts toward plan usage |
| Docs, whiteboards, and other artifacts | Free through February 10, 2027 |
Plan for the artifact line to start counting after February 10.
Who cannot use it yet
During beta, Claude Meetings is not available to organizations with zero data retention (ZDR), a HIPAA-ready configuration, or customer-managed encryption keys (CMEK). If your organization is on any of those, nobody will see it.
The four decisions for admins
The defaults differ by plan. On Team plans, inviting Claude is on by default. On Enterprise, an admin has to enable it, for everyone or for part of the organization.
- On or off, and for whom. On Team, decide this week, because people can already invite it. On Enterprise, start with one group that runs many internal planning meetings, such as product or operations, before sales or HR.
- External calls. Keep the default (Claude stays out when a guest is invited) unless you have a specific reason. Sales and customer calls raise consent questions that differ by country and US state. Two-party consent rules apply to transcription the same way they apply to recording.
- Auto-join. Anthropic's own guidance is to confirm everyone is comfortable with transcription before adding Claude or turning on auto-join. Auto-join makes that confirmation easy to skip. A reasonable rule: auto-join allowed only on internal recurring meetings the user owns.
- Which connectors Claude can use in calls. Everything Claude answers in the chat is visible to everyone on the call. If a connector holds data not everyone in the meeting should see, such as compensation in an HR system, that is a reason to review it. See connector best practices.
Write the answers into your AI usage policy. The question your team will ask first is "can I bring Claude to a call with a customer?", and the policy should answer it.
If you already use a meeting notetaker
Anthropic named Gong, Attention, Granola, Fireflies.ai, Otter, and Plaud as partners for exporting transcripts into Claude. The difference with Claude Meetings is that Claude acts during the call: it answers, builds a draft, and checks a connected system while the decision is still being made. If your team only needs notes, the tool you have may be enough. If you want the plan drafted before people hang up, test Claude Meetings on a few internal meetings.
What to do this week
- Team admins: it is already on. Decide on external calls and auto-join, and tell your team the rule.
- Enterprise admins: pick one pilot group and enable it there only.
- Everyone: try it on one internal planning meeting. At the end, ask Claude for the action items with owners and dates, and compare them with what you would have written. For a pre-meeting routine that pairs well with this, see meeting prep with Claude.
Announcement: Introducing Claude Meetings.