Cisco Brings Persistent AI Agents to Webex With Dialog
Cisco is adding AI agents to Webex, its cloud system for meetings and customer service, with a new management toolset called Dialog detailed on Oct. 7. Engadget
Cisco calls Dialog an "agentic harness," a control layer that tells the AI how to handle customer contacts. The company says it turns scattered calls and chats into continuous customer relationships.
The central point is that agents keep working after the conversation ends. They can coordinate across people, other agents and company back-end systems, instead of stopping at a handoff or when a customer changes channel.
Cisco explains setup in hiring terms. Dialog onboards agents like new employees, with access to handbooks, knowledge bases and operating procedures. The company says agent performance improves with every interaction. Safety controls were developed with Splunk for what Cisco calls a safety-forward experience.
Agents can also join more places in Webex. Workspace members can invite an agent into spaces, meetings and calls to complete multi-step tasks in Webex and in outside apps. That puts agents on the same invite and presence system as people, able to act in Cisco and third-party tools.
This follows earlier steps. Webex App Hub already supports Agentic Apps, AI-based apps designed so agents can work together. Webex Contact Center has been refining how agent availability is tracked, including Granular Agent State Control by Media Type. Last year Cisco connected Webex Suite to Amazon Q, Microsoft 365 Copilot and Salesforce for automated workflows with agents, and in June it introduced a new generation of collaboration infrastructure built for the agentic era. Separately, Cisco introduced DefenseClaw, an open-source secure framework for agents doing security and inventory tasks.
The broader context here is familiar from earlier waves of workplace software. Automatic transcription and summaries were simple to ship. Letting an agent take action is harder. It needs verified identity, clear permissions, audit trails that show who did what, and reliable access to systems of record, the databases that hold official business data. A harness addresses that by putting coordination and rules around the model instead of trusting the model alone.
Worth flagging for administrators are the operational questions raised by long-running agents. An agent that works after the meeting is a persistent service, not a meeting feature. How is its identity limited. What can it read or change when no person is watching. How are handbooks updated, and who approves a change. If performance keeps improving, what exactly is learning, where is that feedback kept, and how do you undo a bad update.
In my view, the Splunk work is the part to watch. Cisco has a large security and monitoring footprint, and agent projects often stall in risk review rather than on the quality of the AI itself. If Dialog arrives with working guardrails, logging and least-privilege access to handbooks and back-end systems, adoption will move faster than if safety is only paperwork. The onboarding idea also gives IT a familiar starting point, since assigning handbooks and procedures is close to existing practices for role-based access and knowledge management, without requiring a whole new control system. None of that removes the integration work around API coverage, error handling and clear paths to a human when needed. If those controls hold, the payoff is practical automation for contact centers and internal teams, and collaboration software that tracks work, not only calls.
