Cisco Webex Agentic AI Platform: Dialog, Claude Managed Agents, and AI Agent 360 — The Complete Guide for Agentic AI Architects (2026)
At WebexOne 2026 in Austin on October 7, Cisco did something no collaboration vendor has done before: it announced that AI agents — not copilots, not chatbots, but autonomous multi-step agents — can now be invited into Webex spaces, meetings, and calls as full participants. An analytics agent pulls usage stats mid-call. A presentation agent updates a PowerPoint deck while the team watches. A customer-service agent negotiates a refund internally for days after the customer hangs up, then sends an update on the customer’s preferred channel.
- What Cisco Announced at WebexOne 2026: The Full Picture
- Claude Managed Agents in Webex: How Anthropic’s Agents Work Inside Collaboration
- OpenAI dots in Webex: MCP-Powered Personal Agents
- Dialog: The Agentic Harness That Changes Customer Experience
- AI Agent 360 and Splunk Observability: Enterprise Governance for Agents
- The Multi-Model, Multi-Vendor Architecture: Why Cisco Is Hedging
- What This Means for RPA Teams: The Collaboration-Layer Shift
- 1. Processes Move Into the Communication Layer
- 2. Contact Center Automation Gets a Long Memory
- 3. MCP Becomes the Integration Standard
- 4. Governance Moves from Afterthought to Architecture
- Competitive Landscape: How Cisco Stacks Up
- Practical Deployment Framework: How to Evaluate Cisco’s Agentic Webex for Your Organization
- Step 1: Identify Your High-Value Collaboration Workflows
- Step 2: Assess Your Data Governance Readiness
- Step 3: Prepare Your Knowledge Bases
- Step 4: Start With a Bounded Pilot
- Step 5: Build Your Observability Baseline
- What to Watch: Timeline and Risks
- Frequently Asked Questions
- What is Cisco Dialog and how does it differ from traditional contact center chatbots?
- Does Cisco Webex only use Claude, or can I bring my own AI model?
- When will Claude Managed Agents be available in Webex?
- How does Cisco handle AI agent security and governance in Webex?
- Can Cisco Webex agentic AI replace my existing RPA workflows?
- Key Takeaways
- External References
This is not incremental. Cisco is rebuilding Webex around three pillars — Claude Managed Agents (Anthropic), OpenAI dots via Model Context Protocol, and a new agentic harness called Dialog — while wrapping the entire stack in AI Agent 360, a governance and observability control plane built on Splunk. The result is the first enterprise collaboration platform where agents are first-class teammates, not sidebar assistants.
For RPA professionals and agentic AI architects, this matters for a concrete reason: the processes you automate today — ticket triage, data aggregation, report generation, customer follow-up — are exactly the workflows Cisco is targeting. The difference is that these agents live inside the communication layer where decisions happen, not in a separate orchestration tool that feeds results back into chat after the fact.
This guide breaks down every announced component, explains the architecture, maps the competitive landscape, and gives you a practical deployment framework — so you can assess whether Cisco’s agentic Webex belongs in your enterprise automation stack.
What Cisco Announced at WebexOne 2026: The Full Picture
Cisco’s announcements span collaboration software, customer experience infrastructure, hardware, and governance. Here is the complete lineup with confirmed timelines:
| Component | Category | Status / Timeline |
|---|---|---|
| Claude Managed Agents in Webex | Collaboration AI | Coming soon (early 2027) |
| OpenAI dots via MCP integration | Personal Agent | Future release |
| Dialog (agentic harness) | Customer Experience | Beta Q1 2027 |
| AI Agent 360 + Splunk Observability | Governance | GA December 2026 |
| Webex Contact Center MCP Server | Integration | GA October 2026 |
| Agent-to-Agent protocol support | Interoperability | December 2026 |
| NVIDIA Nemotron voice agents (BYO) | Voice AI | GA November 2026 |
| Google Cloud Gemini Enterprise CX | Partner AI | Q4 2026 |
| Amazon Nova 2.5 Sonic | Partner AI | Early access December 2026 |
| SharePoint integration for AI Agent | Knowledge | GA November 2026 |
| Universal Harness On-Premises | Data Sovereignty | Q1 2027 |
| RoomOS 27 | Devices | November 2026 |
| Cisco Ceiling Speaker Pro | Hardware | Ordering Q4 2026 |
The scope is deliberately broad. Cisco President and Chief Product Officer Jeetu Patel framed it this way: “The next era of work isn’t about bolting chatbots onto yesterday’s tools. It’s about AI agents working alongside people and teams.” That framing — agents as colleagues, not features — drives every architectural decision below.
Claude Managed Agents in Webex: How Anthropic’s Agents Work Inside Collaboration
The headline integration is Claude Managed Agents, Anthropic’s cloud-hosted agent infrastructure, embedded directly into Webex spaces, meetings, and calls. This is not a sidebar chatbot or a post-meeting summarizer. Claude agents participate in the flow of work as it happens.
How It Works
Teams interact with Claude agents through @mentions in Webex spaces — the same interaction model used for human colleagues. When mentioned, an agent can:
- Analyze shared enterprise context — documents, conversation history, and data already in the space — without requiring users to copy-paste or re-explain
- Generate content — reports, summaries, code, proposals — using the team’s own context as grounding
- Coordinate multi-step workflows across Webex and connected third-party applications
- Produce recommendations and follow-up actions that other agents or humans can act on
The WebexOne Demo Workflow
Cisco demonstrated a concrete workflow on stage: a user @mentions an analytics agent in a Webex space to pull usage statistics from a connected data source. The agent retrieves and formats the numbers. The user then @mentions a presentation agent, which takes those figures and updates a PowerPoint deck — all within the same space, during a live call. No tab-switching, no export-import, no manual formatting.
This is a significant step beyond what Microsoft Copilot Autopilot offers today. While Copilot operates as a single persistent agent within the Microsoft 365 ecosystem, Cisco’s model allows multiple specialized agents to collaborate within a single workspace — an analytics agent handing off to a presentation agent handing off to a scheduling agent — each doing what it does best.
Why Anthropic, Not Just OpenAI?
Cisco is not making Webex Claude-only. OpenAI’s dots product also gets MCP integration (discussed below). But Claude Managed Agents get the deeper, first-class integration for a reason: Claude’s architecture is optimized for enterprise context windows. With a 1M-token context window on Claude Haiku 5.5 (released October 7, 2026) and Claude’s strength in document analysis and structured reasoning, it maps well to the collaboration use case where agents need to reason over long meeting transcripts, multi-threaded conversations, and enterprise knowledge bases.
From Anthropic’s perspective, this is what one analyst called “a real distribution win” — getting Claude embedded in a platform used by hundreds of millions of enterprise workers, rather than requiring users to come to Claude’s own interface. For Cisco, it hedges model risk: enterprises generally avoid single-vendor AI lock-in, and offering both Claude and dots signals openness.
OpenAI dots in Webex: MCP-Powered Personal Agents
The second agent integration uses Model Context Protocol (MCP) to bring OpenAI’s always-on dots agents into Webex. If you’ve been tracking OpenAI’s DevDay 2026 announcements, you know dots are persistent agents built on GPT-6 Astra that continue working between conversations, with their own cloud compute and memory.
How the MCP Integration Works
The Webex Suite MCP integration exposes Webex context — spaces, messages, calendar events, call logs — to dots agents through the Model Context Protocol. This means a dots agent can:
- Read and reason over Webex conversations and files
- Pull context from meetings and calendar events
- Take actions within Webex based on its ongoing goals
Cisco plans to go further: a future release will make dots available inside Webex as an always-on personal agent. Think of it as a persistent digital colleague that answers your calls when you’re busy, assesses urgency, schedules follow-ups, and sends messages on your behalf — all drawing on the full context of your Webex workspace.
Why MCP Matters Here
For agentic AI architects, the MCP integration is architecturally significant. It means Cisco is not building a walled garden. Any agent platform that speaks MCP can, in principle, interact with Webex context. The Webex Contact Center MCP Server — set for GA in October 2026 — makes this concrete: it’s an MCP endpoint that exposes contact center data and actions to compliant agents, whether from OpenAI, Anthropic, or an open-source framework like LangChain or CrewAI.
Dialog: The Agentic Harness That Changes Customer Experience
If Claude Managed Agents transform internal collaboration, Dialog transforms customer-facing operations. Dialog is what Cisco calls an “agentic harness” — a software layer beneath the Webex AI Agent platform that turns AI agents into persistent relationship managers, not just conversation handlers.
The Four Pillars of Dialog
Dialog’s architecture rests on four capabilities that, taken together, represent a fundamentally different approach to customer service automation:
1. Relationship Context (the “Relationship Cortex”)
Dialog merges enterprise data, customer history, and Webex CX data into what Cisco calls a unified “relationship cortex.” This is not a CRM lookup. It is a reasoning layer that understands customer lifetime value, interaction patterns, preferences, and history across every channel — phone, messaging, email, in-person. When an agent picks up a case, it already knows who the customer is, what they’ve tried before, and what matters to them.
2. Agent Onboarding
Rather than building agents from hand-crafted conversation flows (the traditional IVR/chatbot approach that RPA teams know well), Dialog agents are onboarded by indexing existing employee handbooks, knowledge bases, operating procedures, and policies. Cisco describes this as treating AI agents “like new teammates” — you give them the documentation, they learn the rules, exceptions, and escalation paths.
For RPA teams migrating from rule-based automation, this is the shift in practice: instead of mapping every decision branch in a process designer, you point the agent at the documentation and let it reason about edge cases.
3. Self-Learning Loop
Every interaction teaches Dialog something. The system learns from customer outcomes and employee judgment, within enterprise policy limits. This is not unsupervised drift — the learning runs within guardrails set by Cisco AI Defense — but it means agents get better at handling cases over time, much like a human agent who gets faster at recognizing patterns after hundreds of similar calls.
4. Long-Horizon Task Execution
This is the capability that most clearly separates Dialog from traditional contact center automation. A Dialog agent doesn’t just handle the conversation — it keeps working on the customer’s behalf for days after the call ends.
The WebexOne Demo: What Long-Horizon Execution Looks Like
Cisco’s on-stage demo told a specific story: a customer calls about a missed flight and asks for a refund that standard policy doesn’t cover. Here is what the Dialog agent does:
- Gathers context — the customer’s status, lifetime value, recent travel disruptions, and the specific policy exception process
- Tells the customer they no longer need to chase the issue — the agent will handle it
- Opens an internal ticket and begins negotiating with a human escalation specialist, citing the customer’s value and recent service failures as grounds for an exception
- Checks insurance details by contacting the customer’s own personal AI agent (agent-to-agent communication)
- Runs for days, coordinating across multiple internal rounds with staff, other agents, and back-office systems
- Sends daily updates to the customer on their preferred channel
As VP and GM of Webex Customer Experience Vinod Muthukrishnan put it: “It’s demonstrating agency, but it’s not making stuff up.” The agent operates within policy boundaries, but it pursues the customer’s outcome proactively — a fundamentally different model from reactive ticket queues.
This vision — an agent that acts as a customer advocate across time and systems — is what Muthukrishnan calls “managing relationships: thousands of conversations, hundreds of journeys, but one relationship.” If you’re familiar with Salesforce’s Agentforce long-horizon runtime, Dialog is Cisco’s answer: a persistent execution engine for customer-facing workflows that doesn’t stop when the channel closes.
AI Agent 360 and Splunk Observability: Enterprise Governance for Agents
Every agent platform needs a governance story, and Cisco’s is more concrete than most — because Cisco owns Splunk.
What AI Agent 360 Does
AI Agent 360 is the control plane for the entire Webex AI Agent platform. It covers the full lifecycle:
- Design and testing: Build, connect, and test agents in AI Agent Studio before deployment
- Deployment: Roll out agents with defined permissions, data access boundaries, and escalation rules
- Monitoring: Real-time telemetry on agent behavior, decision traces, and conversation outcomes
- Optimization: Continuous evaluation and red-teaming from a single interface
Agent Observability with Splunk
The December 2026 GA of Agent Observability with Splunk adds a layer that most competing platforms lack: full-stack observability that links agent behavior to business outcomes. This is not just “did the agent respond?” — it is:
- Agent health: Is the agent performing as expected? Where is it struggling?
- Escalation patterns: When and why do agents hand off to humans? What does that cost?
- Business impact: What is the resolution rate? How does agent performance correlate with customer satisfaction and revenue?
Muthukrishnan frames governance as the decisive factor: “It’s never been harder to make it enterprise grade.” And the threat surface is real — he estimates the opportunity surface grew 10x with agentic AI, but the threat surface grew 100x. The Splunk integration is Cisco’s answer: if you can observe it, you can govern it.
For automation architects building agent governance frameworks, this is worth studying alongside NVIDIA’s Open Agent Safety Platform. Where NVIDIA focuses on safety guardrails at the model layer, Cisco focuses on operational governance at the platform layer — they are complementary, not competing.
Cisco AI Defense
Sitting alongside AI Agent 360 is Cisco AI Defense, which provides security guardrails for agent behavior. Teams can create custom guardrails using natural-language instructions — “never share customer payment details with third-party agents,” for example — rather than writing complex policy rules. AI Defense determines what agents can access, what they can do, and how they act, with identity, security, and visibility controls applied uniformly across all agent types.
The Multi-Model, Multi-Vendor Architecture: Why Cisco Is Hedging
One of the most architecturally interesting aspects of Cisco’s strategy is its deliberate multi-vendor approach. The Webex AI Agent platform does not bet on a single model provider:
| Provider | Integration | Use Case |
|---|---|---|
| Anthropic (Claude) | Claude Managed Agents | Enterprise collaboration, analysis, content generation |
| OpenAI (dots) | MCP integration | Personal always-on agents |
| NVIDIA | Nemotron + Parakeet | Voice AI, multilingual agents |
| Google Cloud | Gemini Enterprise | CX agents |
| Amazon | Nova 2.5 Sonic | Voice agents (beta) |
| On-premises (BYO) | Universal Harness | Data sovereignty, compliance |
This is not accidental. Enterprise IT departments demand model portability, and Cisco’s collaboration hardware installed base — the devices in conference rooms worldwide — gives it a distribution channel that pure-software competitors cannot match. Aragon Research analysts Jim Lundy and Adam Pease noted that “Cisco’s endpoint hardware footprint is a differentiator that rivals without comparable hardware will struggle to match.”
The Universal Harness On-Premises option, coming in Q1 2027, is particularly relevant for regulated industries. It lets organizations host third-party AI models locally for data sovereignty and compliance — a capability that IBM watsonx Orchestrate also emphasizes, but that most SaaS-first agent platforms cannot offer.
What This Means for RPA Teams: The Collaboration-Layer Shift
If you build RPA workflows today, here is the concrete impact:
1. Processes Move Into the Communication Layer
Traditional RPA lives in the back office — attended bots on desktops, unattended bots in server rooms, processing data between systems. Cisco’s agentic Webex moves process automation into the place where decisions are made: the meeting room, the team chat, the customer call. The analytics-to-PowerPoint demo is trivial in isolation, but the pattern it establishes — agents executing multi-step work inside the collaboration flow — is a direct challenge to the “RPA processes data, humans communicate results” model.
2. Contact Center Automation Gets a Long Memory
Dialog’s long-horizon execution model is the biggest shift for RPA teams doing contact center automation. Today, most contact center bots handle a single interaction and then forget. Dialog agents maintain persistent context and pursue outcomes across days, channels, and internal systems. If your organization runs customer-service RPA — particularly in process orchestration — Dialog represents a fundamentally different approach that may reduce the need for separate bot-to-human handoff workflows.
3. MCP Becomes the Integration Standard
Cisco’s adoption of MCP for the Webex Contact Center Server and the dots integration adds another major enterprise vendor to the MCP ecosystem. For RPA architects already building MCP-compliant tool integrations, this means your agents can potentially interact with Webex context — spaces, meetings, contact center data — through a standard protocol rather than a proprietary API.
4. Governance Moves from Afterthought to Architecture
AI Agent 360 with Splunk observability sets a new bar for what enterprise buyers will expect from any agent platform. If you are building agent solutions on UiPath, Automation Anywhere, or open-source frameworks, expect your enterprise customers to ask: “How do we observe agent behavior end-to-end? How do we link agent actions to business outcomes?” Cisco just made those questions standard procurement criteria.
Competitive Landscape: How Cisco Stacks Up
Cisco is not entering the agentic AI market alone. Here is how its approach compares to the major players:
| Dimension | Cisco Webex | Microsoft (Copilot/Teams) | Salesforce (Agentforce) | Google (Gemini Agents) |
|---|---|---|---|---|
| Agent model | Multi-vendor (Claude, dots, NVIDIA, Gemini, Nova) | Single-vendor (GPT family) | Multi-model via Einstein | Gemini-first, with partner support |
| Primary surface | Collaboration (meetings, spaces, calls) + CX | Productivity (Office 365, Teams) | CRM and customer operations | Workspace (Docs, Sheets, Meet) |
| Long-horizon execution | Dialog (days-long tasks, Q1 2027 beta) | Copilot Autopilot (persistent agent) | Long-Horizon Runtime (GA) | Gemini Enterprise Agent Platform |
| Observability | Splunk-native (owned) | Azure Monitor / third-party | Einstein Trust Layer | Google Cloud Monitoring |
| On-premises option | Universal Harness (Q1 2027) | Azure Arc / hybrid | Limited (Hyperforce) | GDC / Anthos |
| Hardware integration | RoomOS 27, Ceiling Speaker Pro, Cisco devices | Surface Hub, Teams Rooms | None | Google Meet hardware |
| MCP support | Contact Center MCP Server, dots MCP | Limited | Via ecosystem | A2A protocol (related) |
Cisco’s differentiators are its multi-model openness, its owned observability stack (Splunk), and its physical hardware reach. Its risks are execution timelines — many of the most interesting capabilities (Claude Managed Agents, Dialog, Universal Harness) are “coming soon” or in beta, not GA — and the reliability gap that the Engadget article flagged: multi-step agent workflows currently fail 60–70% of the time across the industry, and a 95% per-step success rate still yields only 36% end-to-end success over a 20-step workflow.
Practical Deployment Framework: How to Evaluate Cisco’s Agentic Webex for Your Organization
Based on Cisco’s own recommendations, analyst guidance from Aragon Research, and the practical realities of enterprise agent deployment, here is a structured approach:
Step 1: Identify Your High-Value Collaboration Workflows
Start with workflows where decisions happen inside Webex today — not in a separate system. Examples: weekly business reviews that require pulling data from multiple sources, customer escalation processes that span multiple channels, project status updates that involve compiling inputs from several teams. These are the workflows where in-meeting agents deliver immediate value.
Step 2: Assess Your Data Governance Readiness
As Aragon Research recommends: strengthen data governance, security controls, and identity management before deploying agents. Connecting agents to multiple applications makes data permissions and oversight critical. Define what agents can access, what they can change, and what requires human approval.
Step 3: Prepare Your Knowledge Bases
Dialog’s onboarding model works by indexing existing documentation. If your knowledge bases are outdated, incomplete, or contradictory, agents will inherit those problems. Audit and clean your handbooks, SOPs, and policy documents before agent onboarding. This is the same “garbage in, garbage out” principle that RPA teams know from process mining — except agents can propagate bad documentation at scale.
Step 4: Start With a Bounded Pilot
TechRepublic recommends choosing a single workflow to test, confirming feature availability and licensing, and starting with a limited pilot that requires human approval for all sensitive actions. Do not attempt a broad rollout with agents that are still in beta (Dialog) or “coming soon” (Claude Managed Agents).
Step 5: Build Your Observability Baseline
When AI Agent 360 with Splunk observability reaches GA in December 2026, establish baseline metrics before expanding: agent resolution rate, escalation frequency, average handling time, and customer satisfaction correlation. You cannot optimize what you do not measure.
What to Watch: Timeline and Risks
The biggest risk in Cisco’s announcement is the gap between vision and availability:
- Available now or soon (Q4 2026): Webex Contact Center MCP Server, AI Agent for UCCE, RoomOS 27, AI Agent 360 with Splunk, Agent-to-Agent protocol, NVIDIA Nemotron voice agents, SharePoint integration
- Coming in Q1 2027: Claude Managed Agents (full capabilities), Dialog beta, Universal Harness On-Premises, deeper dots integration
- Timeline unclear: Dots as always-on personal agent inside Webex, full Google Cloud Gemini CX integration
Enterprise buyers should not plan production workloads around Q1 2027 betas. But they should be preparing: cleaning knowledge bases, defining agent governance policies, and running pilots on the capabilities that are available now (the Contact Center MCP Server and AI Agent for UCCE) so they are ready to move quickly when Dialog and Claude Managed Agents reach GA.
Frequently Asked Questions
What is Cisco Dialog and how does it differ from traditional contact center chatbots?
Dialog is an agentic harness — a software layer beneath Cisco’s Webex AI Agent platform — that enables long-horizon task execution for customer experience. Unlike traditional chatbots that handle a single conversation and forget, Dialog agents maintain persistent customer context across channels and time, continue working on the customer’s behalf after a conversation ends (for days if needed), and coordinate across people, other agents, and backend systems to resolve complex issues. Dialog learns from each interaction within enterprise policy limits and onboards by indexing existing documentation rather than requiring hand-built conversation flows.
Does Cisco Webex only use Claude, or can I bring my own AI model?
Cisco’s agentic Webex platform is deliberately multi-model. It integrates Claude Managed Agents (Anthropic), OpenAI dots via MCP, NVIDIA Nemotron and Parakeet for voice AI, Google Cloud Gemini for CX agents, and Amazon Nova Sonic. The Universal Harness On-Premises option (Q1 2027) will also let organizations host their own third-party models locally for data sovereignty. This multi-vendor approach avoids model lock-in and lets enterprises choose the best model for each use case.
When will Claude Managed Agents be available in Webex?
Cisco has announced Claude Managed Agents as “coming soon” with full capabilities expected in early 2027. The Webex Contact Center MCP Server and AI Agent for Unified Contact Center Enterprise are available now. AI Agent 360 with Splunk observability reaches GA in December 2026. Dialog enters beta in Q1 2027.
How does Cisco handle AI agent security and governance in Webex?
Cisco uses a two-layer governance approach: Cisco AI Defense provides security guardrails using natural-language policy instructions (e.g., “never share payment details with third-party agents”), while AI Agent 360 with Splunk observability provides real-time telemetry, decision traces, escalation pattern analysis, and business impact measurement. Teams can evaluate, red-team, and monitor agents from a single control plane, with identity and access controls applied uniformly across all agent types.
Can Cisco Webex agentic AI replace my existing RPA workflows?
Not directly, but it will reshape how some processes work. Cisco’s agentic Webex is strongest where decisions happen inside collaboration tools — meetings, team chats, customer calls. Processes that involve pulling data during discussions, updating reports in real time, or managing long-running customer cases are natural fits. Back-office processes that run without human interaction (batch data processing, system-to-system transfers) will still run better on traditional RPA or process orchestration platforms. The more likely outcome is coexistence: agentic Webex for the collaboration and CX layers, RPA for structured back-office automation, with MCP as the integration bridge.
Key Takeaways
- Cisco is making agents first-class Webex participants — able to join spaces, meetings, and calls, not just summarize them after the fact
- Claude Managed Agents and OpenAI dots handle internal collaboration; Dialog handles customer-facing workflows — together they cover both sides of enterprise communication
- Dialog’s long-horizon execution lets agents work on customer issues for days, across channels and internal systems, fundamentally changing contact center automation
- AI Agent 360 with Splunk sets a new bar for agent observability — linking agent behavior to escalation patterns and business outcomes
- The multi-model architecture (Claude, dots, NVIDIA, Gemini, Nova, plus BYO on-premises) avoids vendor lock-in and gives enterprises model choice per use case
- MCP adoption (Contact Center MCP Server, dots integration) signals Cisco is building for interoperability, not a walled garden
- Most headline features ship Q4 2026 through Q1 2027 — plan pilots on what’s GA now and prepare governance, knowledge bases, and observability for what’s coming
External References
- Cisco Newsroom, “Cisco Unveils New Agentic Collaboration Experiences,” October 7, 2026 — newsroom.cisco.com
- TechRepublic, “Cisco Announces Webex AI Agents: What IT Should Know,” October 2026 — techrepublic.com
- Engadget, “Cisco Is Bringing a New Agentic Framework to Its Webex Enterprise Platform,” October 2026 — engadget.com
- SiliconANGLE, “Cisco Broadens Agentic Features in Webex Collaboration Platform,” October 7, 2026 — siliconangle.com
- Aragon Research (Jim Lundy, Adam Pease), “Cisco Webex Strategy: Driven by Agentic AI,” October 8, 2026 — aragonresearch.com
- Startup Fortune, “Cisco Turns Webex Into an AI Agent Workspace With Claude Built In,” October 2026 — startupfortune.com
- CX Today, “WebexOne 2026: Cisco Dialog Turns AI Agents Into Advocates,” October 2026 — cxtoday.com
- Unite.AI, “Cisco Debuts New-Look Webex AI Agent Platform,” October 2026 — unite.ai
- CX Foundation, “Cisco Debuts New-Look Webex AI Agent Platform,” October 2026 — cxfoundation.com


