During the call, Claude Meetings prepares the team’s documents

In beta on Team and Enterprise, Claude Meetings joins Google Meet to draft documents, respond in writing, and save a transcript.

During a Google Meet call, participants can now ask Claude Meetings to prepare a document from their discussion, then edit it together before the meeting ends. The assistant appears as a visible participant and can be addressed aloud or in the chat. It responds in writing by default. The feature is rolling out in beta on Team and Enterprise plans, with support for other video conferencing platforms planned for later.

The work produced extends beyond notes. In Anthropic’s example, a team planning an event has the assistant draft a plan, retrieve the previous event’s cost from connected tools, and organize the schedule on a whiteboard. Members of the organization listed on the invitation can refine the documents while the discussion continues.

Adding the assistant to a call starts from the calendar in Claude, after the organization has enabled the Google Calendar connection. Users can invite it to individual meetings or enable automatic joining, with an option to exclude one-on-ones. Enabling Meetings across an organization therefore does not automatically add the assistant to every call: auto-join remains a personal setting.

On Team plans, the feature is enabled by default and can be disabled by the organization’s owner. On Enterprise plans, it must be enabled for the entire organization or selected groups. The beta excludes organizations using zero data retention, a HIPAA-ready configuration, or customer-managed encryption keys, among others.

Pricing distinguishes between several uses. During the beta, notes, transcripts, and answers that do not use connected tools are included in Team and Enterprise plans. Connected-tool use counts toward the relevant person’s usage and may result in charges for the organization. Documents, whiteboards, and other artifacts created during meetings are free through February 10, 2027.

Access to connected tools follows each person’s permissions. Permission is requested on first use and remains applicable afterward. For spoken requests, the assistant currently asks each time to confirm who is speaking. On internal calls, information retrieved and posted in the video call’s chat becomes visible to everyone on the call, reaching a broader audience than a private lookup.

The presence of external guests depends on organizational settings and individual preferences. The Help Center states that organization-level permission is enabled by default on Team plans, while it must be granted on Enterprise plans. When external meetings are not permitted, the assistant stays out of calls whose invitations include someone outside the organization and leaves if an external participant joins during the meeting.

When allowed to attend calls with guests, the assistant posts its arrival notice in the chat but does not respond there. Guests’ remarks are nevertheless included in the notes and transcript. Those guests receive neither the internal meeting page nor the recap email. Documents and conversations with Claude remain accessible on the organization’s meeting page.

Each meeting has its own space in claude.ai, containing notes, action items, the transcript, and anything created during the call. People from the organization listed on the invitation can access the page and edit the outputs, then share it with other internal members. Users can subsequently ask Claude about past meetings they have access to.

The information retained includes a transcript, a summary, and descriptions of what appears on screen, but not audio. The assistant’s presence is indicated by its participant tile and a chat message. The provider asks users to ensure that participants agree to transcription before adding it, including when auto-join is enabled.

Transferring transcripts to partner tools remains a planned addition. The collaborations cited include Gong, Attention, Granola, Fireflies.ai, Otter, and Plaud; their inclusion does not mean these integrations are already available in the beta.