For those of you who may have spent the last few weeks under a rock, Salesforce has officially launched Agentforce Contact Center, marking its clearest step into the CCaaS space to date.
The company framed Agentforce Contact Center as a new chapter in how customer experience gets built and delivered in an AI-first world.
Across the industry, the reaction has been more tempered than the launch fanfare might suggest.
Simon Leyland, CEO of Cloud Interact, welcomes the announcement but is measured about what it actually signals:
“II think it’s really interesting, like it’s another indication that the industry is on the move.
“I don’t think anyone knows where it’s going to end up, but it just shows that, you know, the largest players are making moves.”
That’s probably the most honest read of where things stand. The convergence of CCaaS and CRM has been building for years, making Agentforce Contact Center less of a catalyst than a confirmation of a direction of travel that was already well established.
Jack Nichols, VP of Product Management at Genesys, makes that point directly. Describing it as “more of an acceleration than a reset.
“The industry has been moving toward more unified approaches, but AI is now raising the bar from simply integrating systems to executing coordinated, real-time experiences.”
For Nichols, the real change is what these unified platforms are now expected to do.
“What we’re seeing is a shift from platforms that manage interactions to platforms that can continuously understand customer intent and optimize outcomes in real-time,” he said.
That’s a different problem than integration, and it’s one that not every vendor’s architecture is built to solve.
The Case For and Against Consolidation
Salesforce’s argument is that AI delivers better results when customer data, interaction history, workflows, and automation all live in one place.
In short, less context-switching means cleaner data and faster decisions.
The problem is that most large enterprises aren’t structured that way, and haven’t been for a long time.
“There are still two distinct teams within most organizations, one which looks after the CRM and one which looks after the contact center,” Leyland said.
“And they’ve got very different operating procedures and very often very different staff.”
That’s an organizational gap as much as a technical one, and a platform migration doesn’t close it. The people, processes, and institutional knowledge built up on both sides don’t consolidate just because the software does.
Nichols frames the challenge differently, suggesting that “what we see in the market is a mix of strategic platforms across CRM, CCaaS, ITSM, HR and more. The challenge isn’t consolidation – it’s coordination.”
His argument is that consolidation for its own sake misses the point:
“AI depends on having a consistent, real-time view of the customer, but in reality, most large enterprises don’t operate in a single system – and they’re not trying to.”
“To unlock the full value of AI, organizations need a foundation that can unify context across that ecosystem and act on it in real time.”
For Genesys, that means an orchestration layer; one that connects systems, data, and workflows without forcing organizations to rip out the stack they’ve already built.
“It’s less about putting everything in one place, and more about ensuring everything can work together intelligently,” Nichols said.
“When that foundation is in place, organizations can deliver the same or better outcomes without forcing a complete rip-and-replace of their existing stack.”
That’s a direct counter to the Salesforce pitch. The distinction between the two positions could well define the competitive conversation for the next few years.
A Much Bigger Number
Behind all the platform strategy is a market opportunity that makes the scale of Salesforce’s ambitions clearer.
Leyland lays out the math: “We know the telecoms industry and the contact center industry is $20 billion, roughly. We know the services is around about $100 billion mark. But we also know that there’s $250 billion a year spent on human agents.”
That $250 billion figure presents a different strategic angle that Salesforce may be exploring.
Rather than simply a contact center feature expansion, Agentforce Contact Center could be seen as the vendor staking a claim on a pool of spend that dwarfs the markets it already operates in, as Leyland explains:
“You can see Salesforce say, ‘well, hang on a minute… we have to bring in the telephony so that we can then basically go and service that larger market.’”
CCaaS vendors aren’t standing still either. They’re pushing outward into customer data, journey management, and lifecycle ownership – territory where CRM has historically had the stronger footing.
Both sides are stretching toward the same ground, and neither is close to replacing the other.
Leyland sums this up nicely:
“Everyone is trying to own the experience layer because that’s where the value is.”
Why Full Convergence Is Harder Than the Strategy Decks Suggest
The most straightforward way to think about the CCaaS-CRM convergence debate is that the strategic logic is clean, but the execution is a little messier.
Contact centers operate under compliance requirements, workforce management constraints, complex routing logic, and real-time performance pressures that don’t map easily onto CRM deployment models.
For example, Leyland flags a specific gap in the current Salesforce offering. The Agentforce Contact Center solution lacks workforce management functionality and is limited in geographic availability, presently covering only the UK, US, and Canada.
For enterprise buyers with global operations or mature WFM requirements, that’s a significant limitation, regardless of how compelling the AI story is.
There’s a more fundamental issue with the single-platform pitch, too.
“There’s an assumption that putting everything in one place automatically solves the problem,” Leyland said. “It doesn’t.
“You can still have poor processes, bad data, and disconnected experiences inside a single platform.”
Consolidating architecture doesn’t automatically fix the underlying operational problems that fragmented CX experiences tend to reflect.
Nichols adds another dimension from the buyer’s side, arguing that is “isn’t a simple consolidation decision,” but is “more about defining the role of the platform in your architecture.”
For enterprises with complex requirements that span regions, industries, and regulatory environments, the evaluation goes well beyond which vendor offers the most unified product.
“A one-size-fits-all stack doesn’t work,” he said.
Leyland is equally skeptical about the pace of change:
“Enterprises haven’t spent the last 10–15 years building out complex architectures just to rip them out overnight.”
Convergence may well happen, but it will be on enterprise timelines, not product launch timelines.
The CRM Vendors Aren’t the Only Ones Watching
One of the more interesting subplots is the competitive pressure building from a different direction entirely.
Leyland points to activity in the M&A market as a signal of where the real anxiety sits. He sees moves like NICE’s acquisition of Cognigy as a direct response to the threat posed by hyperscalers like Microsoft, Google, and AWS, investing heavily in agentic AI capabilities that could cut across the established contact center market.
For established CCaaS vendors, the challenge expands beyond Salesforce pushing in from the CRM side to the cloud platforms pushing in from below.
He also offers an insight into Microsoft’s position that puts a different lens on the competitive picture.
The Dynamics team, he suggests, has gone quiet over the past six to eight months – with significant internal resource being diverted toward AI and Copilot development, potentially at the expense of the CRM roadmap.
If accurate, it represents a window of opportunity for Salesforce that its competitors may be slower to exploit than the headline battle between CCaaS and CRM would suggest.
Where the Contact Center Goes Next
Underneath the platform debate is a more fundamental contact center shift.
AI is changing it from a function that manages interactions into one that coordinates outcomes across the business.
A customer calling about a billing dispute can now initiate actions across finance, operations, and logistics in real time.
“The moment you start connecting the contact center into the rest of the business in real time, you’re no longer just managing conversations,” Leyland said. “You’re managing outcomes.”
Nichols maps out what the infrastructure for that looks like.:
“AI agents will increasingly move work across the enterprise, not just within the contact center.
“That means resolving an issue won’t stop at the front office – it will trigger actions and engage resources, both human and AI, across billing, logistics, operations, and beyond.”
A unified platform alone is not enough to make that possible. It will also require interoperability between systems that were never designed to talk to each other.
Nichols points to emerging open standards, specifically Model Context Protocol (MCP) and Agent-to-Agent (A2A), as the infrastructure layer that makes this feasible at scale:
“What we expect is an ecosystem approach where organizations design their own mix of systems and platforms, but rely on an orchestration layer to understand customer intents and drive outcomes across them.”
For Leyland, it comes back to a simple point about where the value actually sits.
“There’s no scenario where one platform owns everything,” he said.
Reset or Continuation?
Salesforce has presented Agentforce Contact Center as a defining moment in how CX platforms are built.
And there’s no denying that there’s something to that. The AI capabilities on show are real, and the intent to own a larger slice of enterprise spend is clear.
But the industry view is more grounded. The convergence of CCaaS and CRM has been underway for years. AI has raised the stakes and sharpened the competitive dynamics, but it hasn’t rewritten the map.
The organizational complexity, the infrastructure inertia, and the operational demands of running a contact center at scale remain exactly what they were before the announcement.
What Agentforce Contact Center has done is accelerate the conversation and force vendors on both sides to be more explicit about what their platform is actually for.
Whether it’s the orchestration approach Genesys is building toward, or the consolidated vision Salesforce is selling, the question enterprises now have to answer is the same: which model can deliver outcomes at scale within the architectures they already have?
That’s a harder question than the launch decks tend to acknowledge.
