{"id":34996,"date":"2026-11-15T13:54:44","date_gmt":"2026-11-15T13:54:44","guid":{"rendered":"https:\/\/dr-business.com\/?p=34996"},"modified":"2026-11-15T13:54:44","modified_gmt":"2026-11-15T13:54:44","slug":"claude-meetings-google-meet","status":"publish","type":"post","link":"https:\/\/dr-business.com\/en\/claude-meetings-google-meet\/","title":{"rendered":"Claude Meetings in Your Google Meet Calls? Check Four Things First"},"content":{"rendered":"<p>Claude Meetings should join your Google Meet calls only after an owner on your account has checked four things. Anthropic&#8217;s two official pages even disagree on the riskiest default, whether Claude joins calls with outside guests. Check what your own guest setting says and whether members&#8217; connected tools may be used in calls, know who can open the meeting page, and decide how you will get consent, then trial it on internal calls before anyone acts on its action items.<\/p>\n<p>Anthropic&#8217;s <a href=\"https:\/\/claude.com\/resources\/articles\/claude-meetings\">launch article<\/a>, checked on 15 November 2026, announced Claude Meetings as a beta on 12 November 2026. Claude joins a Google Meet call, writes the notes and action items, and can use members&#8217; connected tools during the call.<\/p>\n<h2>Two Anthropic pages, two guest defaults<\/h2>\n<p>The launch article says: &#8220;Claude is set to stay out of calls when someone from outside your organization is invited.&#8221; It names no plan.<\/p>\n<p>Anthropic&#8217;s <a href=\"https:\/\/support.claude.com\/en\/articles\/18325154-use-claude-meetings\">help centre page<\/a>, checked the same day, splits the rule by plan: &#8220;On Team plans, Claude can join calls with outside guests by default, and an owner can turn this off.&#8221; On Enterprise plans, the same page says, an owner must allow guest calls first.<\/p>\n<p>On Enterprise, the two pages land in the same place: Claude stays out of guest calls until an owner lets it in. On Team, they point in opposite directions, so the pages cannot settle which default your account received. Your own admin screen shows it.<\/p>\n<p>The help centre page gives the approval rule for connected tools: &#8220;It asks the first time, and a yes applies going forward.&#8221; Requests spoken out loud get an added check: Claude asks each time to confirm who is speaking. For requests made any other way, a member who approves a lookup in a quiet internal call has approved it for next month&#8217;s client call as well.<\/p>\n<h2>Four things to check before Claude joins a call<\/h2>\n<p>The help centre page puts the controls under Organization settings &gt; Products &gt; Claude Meetings (beta). Have an owner open that screen and write down what the guest and connector settings say today, before anyone in the team adds Claude to a call.<\/p>\n<h3>Meetings with external guests<\/h3>\n<p>This setting is either internal only or guests allowed. Record what your screen shows.<\/p>\n<p>If guests are allowed, the help centre page says: &#8220;What guests say is included in the notes and transcript.&#8221; The meeting page is for invited members of your organization, so a client&#8217;s words end up in a record your team can read and the client cannot. If the setting is internal only, the same page says Claude is set to leave when someone from outside, including another company&#8217;s notetaker bot, joins partway through.<\/p>\n<p>Set it to internal only while you trial the feature. A client call is the worst place to find out what the transcript holds, and you can allow guests later, once the trial and the consent step are settled.<\/p>\n<h3>Members&#8217; connectors in meetings<\/h3>\n<p>This setting decides whether Claude may use <a href=\"https:\/\/dr-business.com\/en\/chatbot-answers-are-easy-permissions-are-the-risk\/\">members&#8217; connected tools<\/a> during a call. The help centre page gives two facts that set the stakes: a first yes persists, and &#8220;Anything Claude posts in the Meet chat is visible to everyone on the call.&#8221;<\/p>\n<p>Take a hypothetical case. On a client call with guests allowed, a sales manager asks Claude for last quarter&#8217;s discount figures from a connected system, Claude answers in the Meet chat, and everyone on the call reads the answer, the client included.<\/p>\n<p>The decision rule: allow connectors in meetings only when you can give members a list of the connected tools whose contents you would be willing to read out to everyone on the call. If you cannot draw that line yet, leave the setting off for now.<\/p>\n<h3>Who reads the meeting page<\/h3>\n<p>The launch article says Claude &#8220;saves a transcript, summary, and screen descriptions, not audio.&#8221; Each call gets a meeting page in claude.ai holding the notes, action items and the transcript, and invited members of your organization can view and edit it.<\/p>\n<p>Any invited member of your organization can change the action items, so the page is a working document and someone needs to own its final version. And neither Anthropic page states how long transcripts and meeting pages are kept. Get that answer from Anthropic before you put HR or legal conversations through the feature.<\/p>\n<h3>Consent and auto-join<\/h3>\n<p>Anthropic&#8217;s own instruction, on the help centre page: &#8220;Before you add Claude or turn on auto-join, make sure everyone on your call is okay with being transcribed.&#8221;<\/p>\n<p>Auto-join is a per-person setting, and owners can&#8217;t set it for others, so the consent rule your team sets has to reach each member directly. A workable version is a line in the calendar invite saying Claude will transcribe the call, plus a spoken check at the start before anyone adds Claude.<\/p>\n<h2>Trial it on internal calls before trusting the action items<\/h2>\n<p>The launch article puts the job plainly: &#8220;Claude writes the notes and action items, so no one on the call has to.&#8221; It makes no claim about how accurate those notes are.<\/p>\n<p>Google says of its own Meet note-taker, on its <a href=\"https:\/\/support.google.com\/meet\/answer\/14754931?hl=en\">Meet help page<\/a>: &#8220;Sometimes, the meeting summary can be incomplete, inaccurate, or not generated.&#8221; A COLING 2025 paper by Kirstein, Ruas and Gipp, <a href=\"https:\/\/aclanthology.org\/2025.coling-main.143\/\">What&#8217;s Wrong? Refining Meeting Summaries with LLM Feedback<\/a>, names omission among the error types it found in meeting summaries. Neither source is about Claude, and neither measures whether action items carry an owner and a date, so that check falls to you.<\/p>\n<p>The method for each trial call:<\/p>\n<ol>\n<li>Pick a person who keeps their own short list during the call: <a href=\"https:\/\/dr-business.com\/en\/meeting-notes-are-cheap-commitments-are-not\/\">who agreed to do what, by when<\/a>.<\/li>\n<li>After the call, open the meeting page and compare each written action item against that list.<\/li>\n<li>Count the items with a named owner and a date, the items with no named owner, and the items with an owner but no date.<\/li>\n<li>Count what was agreed on the call but never appears on the page.<\/li>\n<\/ol>\n<p>The numbers below are illustrative, not from a client: a hypothetical team running three internal calls.<\/p>\n<table>\n<thead>\n<tr>\n<th>Call<\/th>\n<th>Action items written<\/th>\n<th>Owner and date<\/th>\n<th>No named owner<\/th>\n<th>Owner, no date<\/th>\n<th>Agreed but not listed<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Weekly operations<\/td>\n<td>6<\/td>\n<td>3<\/td>\n<td>1<\/td>\n<td>2<\/td>\n<td>1<\/td>\n<\/tr>\n<tr>\n<td>Hiring sync<\/td>\n<td>4<\/td>\n<td>3<\/td>\n<td>0<\/td>\n<td>1<\/td>\n<td>0<\/td>\n<\/tr>\n<tr>\n<td>Client prep, internal only<\/td>\n<td>5<\/td>\n<td>2<\/td>\n<td>1<\/td>\n<td>2<\/td>\n<td>2<\/td>\n<\/tr>\n<tr>\n<td><strong>Total<\/strong><\/td>\n<td><strong>15<\/strong><\/td>\n<td><strong>8<\/strong><\/td>\n<td><strong>2<\/strong><\/td>\n<td><strong>5<\/strong><\/td>\n<td><strong>3<\/strong><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>In this example, 8 of the 15 written items say who promised what and by when. The other 7 need a person to fill a gap, and 3 agreements never reached the page at all. The missing agreements are the expensive ones, because nobody chases an item they cannot see.<\/p>\n<p>Copy the table and replace the rows with your own calls.<\/p>\n<p>Widen the feature to more calls when the No named owner and Agreed but not listed columns stay empty across several internal calls in a row, and the dates that are missing are ones the person who finalizes the page adds in a few minutes after each call. If agreements keep going missing, keep a person writing the action items and use Claude for the transcript.<\/p>\n<h2>Calls to keep Claude out of for now<\/h2>\n<p>Calls on Zoom or Microsoft Teams are out for now. The launch article says support is currently available for Google Meet, with other platforms coming soon.<\/p>\n<p>Some organizations cannot use it yet. The help centre page lists those with <a href=\"https:\/\/dr-business.com\/en\/zero-data-retention-ai-chats-stored\/\">zero data retention (ZDR)<\/a>, HIPAA-ready configurations or customer-managed encryption keys (CMEK) among them.<\/p>\n<p>Client calls wait until the guest setting, the connector setting and the consent step are settled, because what a client says goes into the notes and transcript.<\/p>\n<p>Calls where nobody will check the action items wait as well. A page of tasks that nobody compares against what was agreed looks finished and may not be.<\/p>\n<p>Claude Meetings is a beta, so any setting above can change. Read the admin screen again before you widen the feature to more calls, and before the first client call.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Before Claude Meetings joins your Google Meet calls, check four things: outside guests, connected tools, who reads the meeting page, and consent.<\/p>\n","protected":false},"author":113,"featured_media":34997,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"drb_seo_title":"Claude Meetings in Google Meet: Four Checks First","drb_seo_desc":"Before Claude Meetings joins your Google Meet calls, check four things: outside guests, connected tools, who reads the meeting page, and consent.","footnotes":""},"categories":[1631],"tags":[],"class_list":["post-34996","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-tools-teardowns"],"_links":{"self":[{"href":"https:\/\/dr-business.com\/en\/wp-json\/wp\/v2\/posts\/34996","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/dr-business.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/dr-business.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/dr-business.com\/en\/wp-json\/wp\/v2\/users\/113"}],"replies":[{"embeddable":true,"href":"https:\/\/dr-business.com\/en\/wp-json\/wp\/v2\/comments?post=34996"}],"version-history":[{"count":1,"href":"https:\/\/dr-business.com\/en\/wp-json\/wp\/v2\/posts\/34996\/revisions"}],"predecessor-version":[{"id":35000,"href":"https:\/\/dr-business.com\/en\/wp-json\/wp\/v2\/posts\/34996\/revisions\/35000"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/dr-business.com\/en\/wp-json\/wp\/v2\/media\/34997"}],"wp:attachment":[{"href":"https:\/\/dr-business.com\/en\/wp-json\/wp\/v2\/media?parent=34996"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dr-business.com\/en\/wp-json\/wp\/v2\/categories?post=34996"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dr-business.com\/en\/wp-json\/wp\/v2\/tags?post=34996"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}