A meeting tool that only writes a summary after everyone leaves asks you to trust a memory of the call. Claude Meetings puts Claude in the call itself. Anthropic started the beta rollout on November 12, 2026. Claude joins Google Meet as a participant everyone can see, posts a notice in the chat, follows the talk, and can start a doc or a whiteboard while the talk is still going.
This tutorial sets it up in the order that avoids surprises. Owner controls first, then the calendar link, then one internal call on its own. Only after that call passes a check should anyone consider sending Claude into every meeting by default. The steps follow the Anthropic help page for Claude Meetings. No live call on our own account is claimed here. The Verification section tells you how to judge the result in yours. Our research review of Claude Meetings in Google Meet covers the wider case for and against the product.
What You Will Build or Learn
You will end with Claude ready to join a Google Meet call from your calendar, take notes and action items, answer questions in the call, and build a doc, a whiteboard or slides when someone asks. You will also have the three owner decisions written down before the first call. Whether outside guests are allowed. Which connected tools members may use in meetings. Who checks what Claude made after the call.
That last part matters more than the switch itself. Claude saves a transcript, a summary and descriptions of what was shown on screen. It does not save audio. A team that agrees where that transcript lives and who can open it will have a calm rollout. A team that learns those rules from a client call will not.
The calendar is the door. Claude reaches a call through Google Calendar in Claude, not through a Meet add on. Illustration: Dirty Static
Before You Begin
Check that everyone on the first test call is fine with being transcribed. Anthropic gives that advice in plain words, and the notice Claude posts in the chat when it joins is not a substitute for asking in advance. Put a short note in the invite for the test call, and keep the first test internal.
Note the beta limits before you plan dates around this. The beta is not open to organizations that use zero data retention, a HIPAA ready setup, or customer managed encryption keys. Anthropic calls that list part of the beta terms in its help pages, with no date given for a change. Support for other video platforms is listed as coming soon, with no names or dates in the help page. Google Meet is the only platform that works today.
Step 1: Confirm Your Plan Can Use the Beta
Action: open Claude and look for Meetings in Claude on the web or in Claude Desktop. Confirm your organization sits on a Team or Enterprise plan. Personal plans named Free, Pro, Max and Ultra do not include Meetings in the pages Anthropic publishes. If Meetings does not appear, note that the rollout is in beta and may not have reached your account yet, rather than assuming a setting is wrong.
Expected result: Meetings appears for members on an eligible plan, or you have a clear reason it cannot appear yet. That reason is either the plan, a blocked data setup from the list above, or a rollout that has not reached the account. Record which one applies before you change any other setting.
Step 2: Have an Owner Turn Meetings On or Confirm It Is On
Action: ask an owner to open Organization settings, then Products, then Claude Meetings (beta). On Team plans, Meetings is on by default and an owner can turn it off. On Enterprise plans, an owner turns it on for all of the organization or for part of it. For part of an Enterprise organization, the owner uses custom roles that carry the Claude Meetings capability.
Expected result: the owner can state, in one sentence, who in the organization may add Claude to a call. If that sentence names everyone, only some roles, or no one, the rest of the setup can match it. If nobody can state it, stop here and settle it, because guest and tool controls build on the same roles.
Step 3: Set the Guest and Tool Controls Before Anyone Joins a Call
Action: with the owner still in Organization settings, decide two controls and write the decisions down. First, calls with outside guests. On Team plans, Claude can join calls with outside guests by default and an owner can turn that off. On Enterprise plans, an owner must allow it first. Second, whether members may use their connected tools during meetings, where your plan shows that control. Each person also has a personal Meetings with external guests setting under Settings, then Capabilities, then Meetings, so tell members where that setting lives.
Expected result: your team has a written guest rule and a written tool rule. When guests are not allowed, Claude stays out of a call when someone from outside the organization is invited, and it leaves if an outside guest joins partway through. Anthropic counts another company notetaker bot as an outside guest for this rule. When guests are allowed, Claude listens and takes notes and posts its notice in the chat, but it does not reply in that chat, and guests do not get the meeting page or the recap email described in Step 7.
Step 4: Connect Google Calendar and Add Claude to One Call
Action: open Meetings in Claude on the web or in Claude Desktop. Connect your Google Calendar when Claude asks. The owner must have enabled Google Calendar for the organization first, or this link cannot be made. Pick one internal Google Meet call from the calendar shown in Meetings, then select Add Claude.
Expected result: the chosen meeting shows that Claude will join it. Claude usually joins without having to ask to be let in. If it does ask, the host can let it in. If the host declines, Claude does not try that call again unless someone adds it again, and you will see that it was declined. Pick a planning call or a team review for this first test, where a doc or a board would be useful if Claude builds one.
Step 5: Decide on the Setting That Adds Claude on Its Own
Action: only after Step 4 works, open Settings, then Capabilities, then Meetings, then the Auto-join setting. You can set Claude to join all your meetings, or all your meetings except calls with one other person. Owners cannot set this for you. It is a personal choice for each member.
Expected result: each member has either left this setting off, or has chosen one of the two scopes with a clear reason. Leaving it off is a valid result. Adding Claude call by call costs a few clicks and gives the room a moment to agree each time, which suits client work and any call where guests may appear.
Step 6: Use Claude During the Call
Action: when the call starts, confirm Claude appears as a participant and that its notice has posted in the Meet chat. Ask a question by saying Claude and then the question out loud, or by typing the question in the Meet chat. By default, Claude answers in writing in the Meet chat. Ask it to make a doc, a whiteboard or slides when the talk reaches a plan worth keeping. Those files attach to the meeting page, and people from your organization on the invite can edit them while the call runs. The Sheets and Whiteboards tools are the tools that build those files.
Expected result: Claude takes notes during the call, answers in the chat where the whole internal call can see the answer, and starts any file you asked for before the call ends. Its tile in the call shows what it is doing. You can ask it to stop listening to pause it, and resume it from the meeting page. To remove it, ask it to leave or use the remove control on the meeting page. If you add it again, it returns to the same meeting page. Claude can stay in a call for up to eight hours and warns before it leaves.
Step 7: Open the Meeting Page and Share It With Care
Action: after the call, open the meeting page for that call in Claude. Check the notes, which hold a summary and any action items, along with the transcript and everything Claude made. The calendar in Meetings lists past and upcoming meetings, so you can return to a past call or add Claude to the next one from the same place. In a regular chat later, you can ask Claude about past meetings you have access to.
Expected result: people from your organization who were on the invite get a recap email with a link to the meeting page. They can see the notes and edit what Claude made. The page can be shared with others in your organization. Outside guests do not get that page or that email, even when they were allowed on the call itself.
After the call, the work sits in one place. Notes, transcript and files share a single meeting page. Illustration: Dirty Static
Verification
Run these checks after the first internal call and record the results with the date. Claude appeared as a participant and posted its notice in the chat. The notes on the meeting page name the decisions and action items the room actually made, with owners where the room named them. The transcript is present and no audio file is offered, which matches what Anthropic says it saves. A file you asked for during the call sits on the same page and opens for editing by an invited member of your organization.
Finish with two access checks. An invited member of your organization can open the page from the recap email. A person outside the organization has no link to that page in their mail. If either check fails, fix the guest and sharing settings before the next call, not after a wider rollout.
Troubleshooting
| Problem | Likely cause | Fix |
|---|---|---|
| Meetings does not appear in Claude | The account sits on a personal plan, the beta rollout has not reached the organization, or the organization uses a blocked data setup | Confirm the plan is Team or Enterprise. Check for zero data retention, a HIPAA ready setup or customer managed encryption keys. If none applies, wait for the rollout and check the Anthropic release notes again |
| The calendar link cannot be made | An owner has not enabled Google Calendar for the organization | Ask an owner to enable Google Calendar for the organization first, then connect your calendar again from Meetings in Claude |
| Claude does not join a call it was added to | The host declined entry, or the guest rule kept it out | If the host declined, add Claude again only with the host agreement, because it will not retry that call on its own. If an outside guest was invited and guests are not allowed, that rule explains the absence |
| Claude leaves partway through a call | An outside guest joined while guests were not allowed for that call | Check the guest rule for your plan and the personal guest setting for the member who added Claude. Another company notetaker bot counts as an outside guest and can trigger the same exit |
| Outside guests hear Claude but see no answers and get no recap | Guests are allowed, and that is the behaviour Anthropic describes for guest calls | Claude takes notes on guest calls but does not reply in the chat, and guests do not get the meeting page or recap email. Share any file a guest needs through a route you choose, outside the meeting page |
| A tool request surprises the room | A member approved a connected tool and that approval carries forward, or an answer posted in the chat was visible to the whole call | Review which tools members may use in meetings with an owner. Keep sensitive checks out of the live chat, because answers there are visible to everyone on an internal call |
| Costs appear that nobody expected | Answers that use connected tools count toward a person usage and can lead to charges for the organization | Notes, transcripts and answers that do not use connected tools are included on Team and Enterprise plans. Docs and whiteboards made in a meeting are free through February 10, 2027. Track tool use during the trial and treat pricing after that date as unknown, because Anthropic has not published it |
| Claude warns that it will leave a long call | Claude can stay in a call for up to eight hours | Note the warning, save any file in progress to the meeting page, and add Claude again if the call continues past that limit |
Next Steps
Run the same setup on two or three internal planning calls before you widen it. Compare each meeting page with the notes your team would have written by hand. Where Claude missed an owner or a date, say so in the room next time while the people who decided it are still present to correct the record.
Then write the rollout rules as a short team note. Which calls get Claude by default, if any. Which calls never do. Which connected tools are allowed in meetings. Who reviews the meeting page when a call covers client work. That note, plus the guest rule from Step 3, is the real product of this tutorial. The switch takes minutes. The habits around the transcript are what decide whether the tool helps or merely records.
Facts checked against the Anthropic help page for Claude Meetings and the Anthropic release notes on November 15, 2026. Beta scope, pricing and platform support can change, so confirm each one in the help page before a wider rollout. This procedure was verified against those documents and is not presented as a personal test run.
Sources
- Anthropic Help Center, Use Claude Meetings, updated November 12, 2026: https://support.claude.com/en/articles/18325154-use-claude-meetings
- Anthropic Help Center, Release notes, November 12, 2026 entry for Claude Meetings: https://support.claude.com/en/articles/12138966-release-notes
- Anthropic, Introducing Claude Meetings, November 12, 2026, as described in the help page and release notes above
- Hero, calendar and meeting page images: Dirty Static illustrations
END OF TRANSMISSION
Stay curious. Question everything.
