Contact center convergence is becoming less about connecting tools and more about fixing the operating model underneath customer service.
CX leaders already know the pressure points. Customers expect fast, contextual service across digital channels, voice, AI agents, and human advisors. Agents are expected to handle more complex conversations while working across data, workflows, and systems that were not always designed to move together.
The risk is that AI ambition runs ahead of operational readiness. A business may add new automation, deploy an AI agent, or improve routing, yet still lose context when a customer moves from one channel to another. For Jonathan Kershaw, Director of Product Management at Vonage, the priority is clear:
“Close that gap between AI ambition and operational readiness.”
That gap is now the practical test for enterprise CX teams. If voice, CRM, CCaaS, and AI still operate as separate layers, agentic CX will struggle to move beyond isolated use cases.
Contact Center Convergence Needs Context First
The original promise of integration was simple. Connect the systems and the experience should improve.
Contact center operations have become more demanding than that. Voice, Customer Relationship Management (CRM), Contact Center as a Service (CCaaS), knowledge, workforce tools, and AI now need to support one continuous customer journey.
Kershaw pointed to context loss as one of the biggest issues in customer experience, particularly when customers move between digital channels, interactive voice response, AI agents, and human advisors.
Asked where organizations are feeling pressure most directly, Kershaw highlighted a problem that predates generative AI but has become more visible as automation enters live service journeys:
“For the customers, I think the biggest pain point is context loss.”
A technical connection between platforms does not guarantee that context follows the customer. The customer does not see the architecture. They experience the handoff.
When that handoff fails, the customer repeats information, the agent rebuilds the story, and the business loses the efficiency it expected from the technology.
Many organizations have spent years adding applications around the contact center.
That approach made sense when individual systems solved individual problems. A CRM stored customer records. A contact center platform managed queues. Unified communications helped teams collaborate. AI added summaries, routing support, and new forms of automation.
The challenge now is that agentic CX depends on those capabilities acting in sequence.
A collection of connected point solutions can still leave the agent doing the coordination work. They may have to check one system for customer history, another for case status, another for knowledge, and another for the interaction record. Kershaw framed the limitation directly:
“Just because you’ve got AI, just because you’ve got voice, just because you’ve got CRM doesn’t mean it’s actually going to work.”
The more complex the service journey, the more that fragmentation matters.
For buyers, the question now is “Can they support a real customer journey without forcing the agent or customer to stitch it together?”
Voice Is Where Convergence Gets Tested
Voice remains a high-stakes channel because it often carries urgency, emotion, and complexity.
If a customer has already tried self-service or an AI agent before calling, the voice interaction becomes the moment where the business either recovers the experience or compounds the frustration.
Kershaw noted that voice quality now has a wider operational impact because it affects transcription quality, and transcription quality shapes the usefulness of downstream AI. He connected that foundation to the wider AI toolset:
“You need high-quality audio under that to deliver high-quality transcription because it is that which will then drive all your AI tools on top of that.”
That matters for convergence. Voice can no longer sit as a separate channel where insight is captured later, summarized manually, or disconnected from CRM and workflow actions.
A converged model treats voice as a source of live context. It connects the conversation to the customer record, the agent’s next action, and the business outcome being measured.
For enterprise CX teams, that is where the difference between “integrated” and “operationally ready” becomes visible.
AI Changes the Agent’s Job, Not Just the Channel Mix
AI adoption also changes what human agents handle. If AI absorbs simpler contacts, the remaining human interactions may become more complex. That can make traditional measures harder to interpret, especially Average Handle Time.
A rising handle time does not always mean the agent is less productive. It may mean the agent is now handling work that requires empathy, judgment, investigation, or escalation.
That shift should change how leaders measure convergence.
Deflection alone is too narrow. A business may deflect more contacts while still failing to resolve the issues that matter most. Resolution, customer effort, context continuity, and agent confidence provide a better view of whether the operating model is improving.
Kershaw pointed to that measurement shift during the conversation, noting that CX leaders are starting to hear more language around “resolution, not just deflection,” and “charged by resolution, not by interaction.”
Start With One Value Workflow
The practical route forward is not to wait for a perfect platform moment.
CX leaders can start by auditing where voice, CRM, data, and AI capabilities sit today. They should identify where context drops, where agents switch systems, where customers repeat themselves, and where automation creates more effort than it removes. Kershaw advised leaders to avoid trying to solve everything at once:
“Don’t focus on the perfect platform moment, but one value workflow. Prove it.”
That might be a high-volume service request, a frequent escalation path, or a journey where customers often move from digital self-service into voice.
The goal is to prove that context can travel, agents can act faster, and the customer reaches a resolution with less friction.
The approach also helps build confidence with employees. Kershaw discussed how some organizations use employees as “customer zero,” giving teams a safer way to test AI workflows before exposing them to customers.
The Operating Model Is the Real Differentiator
The next stage of agentic CX will be driven by whether voice, CRM, CCaaS, and AI can work together in the moments where customers need help most.
That is also where the next article in this series will pick up the thread, with a closer look at what CX leaders still need from voice in the agentic era. Voice is often where convergence moves from theory to lived experience, because agents have little room for delay and customers expect context to follow them instantly.
For now, the enterprise decision is clear enough. Connecting tools is useful, but it is not the same as creating an operating model.
Agentic CX needs context that moves, workflows that hold together, and measurement that rewards resolution. Without those foundations, AI may be present in the contact center, but it will struggle to change the experience.