Availability and pricing checked November 18, 2026.
Use Claude Meetings to draft a campaign brief during an internal planning call, then review it before anyone acts. The useful distinction is between what the team decided, what someone suggested and what nobody answered. Make those separate sections, rather than accepting a polished summary as an approved plan.
Anthropic announced Claude Meetings in beta on November 12, 2026. It adds Claude to Google Meet as a visible participant that takes notes, answers questions and creates documents during the call.
Below is a suggested workflow for founders and marketers, based on Anthropic's documentation. We have not tested it in a live meeting. The campaign-brief structure is our recommendation, not a built-in template.
What changed, and who should try it?
The change is that you can ask Claude to build a document during the discussion, not just read notes afterward. That makes an internal campaign-planning call a useful first trial: ask for a brief, inspect it together and correct it before ending the call.
As of November 18, Anthropic's release notes and setup documentation describe a rolling beta on Team and Enterprise plans in Claude and Claude Desktop. The documented meeting platform is Google Meet. Do not assume another meeting platform or an individual paid plan qualifies.
Some organizations are excluded during beta, including those with zero data retention, a HIPAA-ready configuration or customer-managed encryption keys. An eligible plan does not guarantee your organization has access.
Try this if you already have access and an internal planning meeting coming up. There is no need to make a purchase decision before understanding those limits.
Check consent, access and costs first
Before adding Claude, make sure everyone is okay with transcription and follow your organization's policy. Anthropic says Claude appears as a participant and posts a notice. It saves a transcript, summary and screen descriptions, not audio. That still means meeting content is saved.
Start with an internal meeting and check the invite list. As of November 18, the launch announcement and Help Center describe external-guest defaults differently. Check your organization's Meetings with external guests setting rather than relying on either presumed default.
The current Help Center also describes different behavior when outside guests are allowed: Claude takes notes but does not reply in Meet chat, and guests do not get the internal meeting page or recap email. Do not use a client call for this walkthrough.
Costs need the same care. As of November 18:
- 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.
- Connected-tool use counts toward your usage and can lead to organization charges.
Those are meeting-feature terms, not a free subscription. Check Anthropic's subscription pricing alongside the meeting documentation before committing to a plan.
1. Set up one internal planning call
An owner must enable Google Calendar for the organization before you connect it. On Enterprise, an owner also needs to enable Meetings for the relevant users; on Team, an owner can turn Meetings off.
For the first trial, follow Anthropic's documented setup:
- Open Meetings in Claude.
- Connect Google Calendar.
- Select the internal meeting.
- Click Add Claude after confirming participants are comfortable with transcription.
Add it manually rather than starting with broad auto-join. Keep the scope to creating and reviewing a brief. Check the organization's connector controls, and avoid asking Claude to retrieve information or act through connected tools during this trial.
2. Ask for a brief, not just a summary
During an internal call, Anthropic says you can address Claude out loud or type in Meet chat. It normally answers there in writing. Asking it to make a doc creates work attached to the meeting page.
Here is an example prompt to adapt. It is an untested instruction, not an official template or a technical permission control:
Claude, make a campaign-brief doc from this discussion. Separate confirmed decisions, proposals and unresolved questions. Include objective, audience, offer, deliverables, owners, dates, budget and measurement only where we explicitly agree them. Mark missing inputs as unresolved. Do not turn a suggestion into a decision. Do not use connected tools, send messages or publish anything. We will review the brief before acting on it.
Keep that last instruction in the prompt, but also use actual permission settings. A request not to use tools is not a substitute for controlling access.
3. Keep suggestions out of the committed plan
Use the document to ask concrete questions during the discussion:
- What outcome are we agreeing to pursue?
- Which audience and offer did we choose?
- Which deliverables are approved, and who accepted ownership?
- Which dates and budget are confirmed?
- How will we judge the result, and where will the data come from?
If paid search comes up but the team does not choose it, keep it under proposals. If nobody agrees a budget, leave the budget unresolved. If a task is suggested for someone, ask that person to confirm ownership before treating it as a commitment.
This is the team's review method, not a promise that Claude will distinguish every case correctly. Check the document while the people responsible are still available to correct it.
4. Review the brief before sharing or executing
Anthropic's documentation says the meeting page contains the live transcript, chat and created work. After the call, it holds notes, a summary, action items and the transcript. People from your organization on the invite can see notes and edit what Claude made; the page can also be shared within the organization.
Review the brief against the discussion and transcript. Ask the responsible people to resolve disagreements rather than treating the transcript as final authority. Check claims, owners, dates, budget and the proposed measurement source.
Do not treat a generated action item as permission to launch a campaign. Decide separately who approves the brief, who may share it and who may authorize execution. Share the reviewed version with the people who need it, following your organization's access rules.
Keep reviewed decisions with your marketing context
After review, keep the confirmed decisions with the context you use for later marketing work. If you use Magister, its Connect guide explains how compatible assistants access a brand's workspace, including its Library, files and memory. Treat this as a separate handoff of reviewed work, not an automatic Claude Meetings integration.
For this week's trial, aim for a brief the team can stand behind, not a longer transcript. Inspect whether decisions, proposals and unanswered questions stayed separate. If they did not, revise the instructions and the document before using either again.
The next action is small: choose an eligible internal call, confirm consent and try the prompt. Finish by reviewing the brief together—not by asking the agent to launch it.