# Claude Meetings and Runner: from action items to follow-ups

> Claude Meetings and Runner: bring your pipeline into the call, then turn the action items Claude leaves into a follow-up a person checks before anything sends.

Canonical: https://www.runtheworld.ai/guides/claude-meetings-and-runner

Updated: 2026-11-16

## What Claude Meetings does in the call

Anthropic announced Claude Meetings on November 10, 2026, alongside Claude Whiteboards and Claude Sheets. Claude joins a Google Meet call as a participant everyone can see, posts a notice in the meeting chat, and works while people talk: it drafts the plan under discussion, maps a timeline on a whiteboard and answers questions in the chat.

It is a beta for Claude Team and Enterprise plans, and Google Meet is the only meeting app at launch. Anthropic says Claude stays out of calls with external guests unless an admin allows it, and leaves if one joins. When the call ends, its notes and action items are waiting in claude.ai.

## Bring your pipeline into the call

Anthropic says Claude can pull from your connected work apps during a meeting. Runner is a Claude connector, so the account you are talking about can be one of them. Which connectors your Meetings beta may use is set by Anthropic and your Claude admin.

Once Runner is connected, Claude can search your accounts and opportunities by name, list a contact's meetings, and read an account's deal room as far as its sharing rules let an assistant see. It reads only the products you ticked when you connected, inside the role you already have in Runner.

## After the call, every action item needs an owner

A list of action items in claude.ai is a good start and a common place for promises to stall. The ones that matter to revenue, such as a proposal to send, a pricing answer or a check-in next month, need a next step on the deal and someone who owns it.

Open the meeting's action items in Claude, with Runner switched on, and ask it to turn the customer-facing ones into a follow-up. Name the account so Claude can find it, and say which promises belong to whom.

## Save the follow-up as a draft, not a send

Claude saves the follow-up in Runner as a draft journey: up to eight steps in order, each an email, a wait of 1 to 90 days, or a task for a person. It answers with a link to open the draft.

The draft admits nobody and sends nothing. A person in Runner picks who enters, chooses an approved campaign, reads the steps and turns the journey on. That part stays with a person, which is the point: the meeting moved fast, and the follow-up still gets a human check.

- Emails carry the recap and the promised material.
- Waits give the customer room before the next touch.
- Tasks keep the promises only a person can keep.

## Keep the record in Runner

The call is over in an hour; the deal runs for months. Keep the account, the opportunity's next action and the follow-up in Runner, where your team and your growth team can see them, rather than in a chat history only one person can open.

When the next step belongs in your product rather than with the customer, the same record becomes the brief for that work.

## Stay in control of what Claude can reach

Every connection is listed in Runner under Settings → MCP clients. Revoke one there and its next request is refused. An organization owner or admin also sees everyone's connections on that page.

Claude Meetings' own rules sit on top: it shows itself in the call, posts a notice in the chat, and keeps out of calls with external guests unless your admin allows it.

