Claude Joins Webex as a Teammate—but the Feature Is Still “Soon”

On October 7, 2026, Webex’s product announcement set out Cisco’s plan for Claude Managed Agents to join Webex spaces, meetings and calls as a team member. The agent would pick up the context of a conversation and help complete work arising from it. Its arrival is described as “soon,” without a release date. An existing connection that sends Webex context to OpenAI dots is available now, but it is a separate capability.

At WebexOne in Austin, Cisco’s Webex Suite and AI leader Amit Barave told UC Today, “You don't manage them, you govern them.” He described long-running work in which Claude-powered agents, Webex agents and agents built by customers could pursue a shared goal after a team has logged off. For organizations assessing the announcement, the distinction is immediate: that collaborative role is planned, while some related connections and administrator controls already exist.

What the Claude teammate is meant to do

Claude’s proposed role starts inside a team conversation. A space, meeting or call would give it shared context for the work participants are discussing, rather than requiring each person to brief a separate assistant from scratch. From there, Claude Managed Agents are intended to help with analysis, generated content, recommendations and coordinated action. The plan describes an agent that can work alongside participants and continue a task through multiple steps.

Other collaborative agents are part of that proposed workflow. An agent invited into a Webex conversation could operate within a defined role, use the context it needs and share a result where the team can see it. Approved agents, skills, connectors and applications could then support further work across Webex and other tools. Those descriptions explain the ambition behind the teammate role; they do not establish that organizations can invite Claude into a Webex meeting today.

What context could follow a conversation?

The clearest stated input for the planned Claude participant is the context of the space, meeting or call it joins. That could help it understand a request in relation to the discussion that produced it and return work to the same team. The broader Webex design also describes bringing together earlier discussions, decisions, open items and relevant people when preparing someone for a later conversation. Those are descriptions of how shared work context could make an agent useful across interactions.

They are not a published inventory of everything Claude will be allowed to read. The announcement does not specify a Claude-specific scope for message history, recordings, files or connected business systems. Access to a conversation therefore should not be taken as access to every source an organization stores or connects to Webex. The proposed design puts an agent’s role and the organization’s approved applications and connectors around the work it can perform.

That distinction matters when a task moves beyond conversation. Using meeting context to recommend an action, retrieving information from another system and changing a record there would require different permissions. The public description explains the intended flow from discussion to action, but it leaves the precise Claude access rules and approval steps for that flow to a future release.

Controls already available in Webex

Administrators have controls for the existing Cisco AI Assistant. Webex’s Control Hub guide documents settings for messaging, meetings and calling, including options managed at the organization, template or user level. Meeting settings cover summaries, whether outside participants can use the assistant and whether participants can ask a host to turn it on. These controls govern features of the current assistant.

Search settings show why the product distinction is consequential. For the current assistant, administrators can allow searches of selected meeting summaries, transcripts, recordings and messages, as well as calling summaries and transcripts. External sources such as Glean, Amazon Q and Microsoft repositories require their own integrations and, where applicable, service licenses. A switch that enables one of those sources for Cisco AI Assistant is not, by itself, a published grant of access to a future Claude participant.

The current guide also separates meeting, messaging and calling controls rather than treating all conversation data as one pool. It describes limits that vary by feature, including settings for meeting participants and sources used for answers. Organizations can use those documented controls now, while the permission model for Claude Managed Agents remains unspecified.

What is available, planned or undated

The announcement places several related capabilities next to each other, although they have different release statuses:

• Claude Managed Agents in Webex — planned, undated. Claude is intended to join spaces, meetings and calls as a team member, use shared conversation context and help complete multi-step work. “Soon” is the stated timing, with no launch date.
• Other collaborative agents — described, undated. The proposed experience includes agents that teams can invite into conversations to work within defined roles and use approved applications. No general release date for that collaborative experience is specified.
• Webex Suite MCP connection to OpenAI dots — available now. The Model Context Protocol connection brings context from Webex meetings, calls, messages and conversations into dots. It sends Webex context to a separate product; it does not place Claude in a Webex conversation.
• Dots as a teammate inside Webex — planned, undated. A personal-agent role within Webex is also described as coming soon. It is a separate planned experience from the Claude teammate.
• Control Hub settings for Cisco AI Assistant — documented for current use. Administrators can manage existing assistant features and selected search sources. Those settings do not yet define Claude-specific access.

The next consequential detail for prospective users is a dated Claude preview or release, together with eligibility and permission rules. Until those are published, the available MCP connection and AI Assistant controls answer different needs from the promised teammate that participates in Webex conversations.

Also read:

• Apple Tightens Full Disk Access—but the New Controls Have No Date
• Vocca Raises $20M—One Million Monthly AI Calls Still Need Context
• Uber and Pony.ai Will Test London Robotaxis—A Launch Date Is Still Missing