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.
