Salesforce said in 2023 that it did not want to become a Contact Center as a Service (CCaaS) provider. On March 10, 2026, at Enterprise Connect in Las Vegas, it launched one.

That reversal is the story — not the feature list, not the keynote rhetoric. What changed, and what does it mean for CIOs who built their customer experience stacks around the CRM-plus-CCaaS partnership model that Salesforce itself encouraged?

Nobody Is Staying in Their Lane

ServiceNow expanded its Sales and Order Management suite in late 2024, pushing into CRM territory. Salesforce responded with its own IT Service Management (ITSM) entry built on Slack — and by February 2026, 180 organizations had adopted Agentforce IT Service. HubSpot moved upmarket with its Breeze AI agent platform. Microsoft Dynamics 365 tightened its grip through Copilot. Now Salesforce has crossed into NICE, Five9, Genesys, and Amazon Connect territory.

The pattern: when AI agents become the execution layer, the vendor that controls the data wins. This CCaaS launch is as much about defending CRM from ServiceNow and Microsoft as attacking contact center incumbents.

What Agentforce Contact Center Is

A CRM-native CCaaS platform where telephony is built in, not bolted on. Unified agent desktop, real-time analytics across voice and digital, customer signals intelligence, and "agentic handoffs" where AI agents pass interactions to humans with full transcript and context. Voice data feeds back natively into the CRM. Generally available as an add-on to Agentforce Service in the U.S. and Canada.

Every major CCaaS vendor offers some version of these capabilities. The differentiation rests on one word: native.

Why Salesforce Broke Its Own Promise

For an AI agent to resolve an issue autonomously, it needs full customer context. When CRM and contact center are separate systems connected by APIs, that context arrives with latency and gaps. Salesforce concluded it could not win the AI agent race while outsourcing the engagement layer to partners.

This is a data-gravity play disguised as a contact center product. CCaaS is the vehicle to ensure every customer interaction feeds the data layer that powers Salesforce's AI agents. The contact center is the means; data gravity is the end.

The Gap Between Narrative and Traction

Agentforce reached $540 million in annual recurring revenue in Q3 FY26 (ended October 2025), with production deployments rising 70 percent quarter over quarter. But more than half came from existing clients, and only a fraction of Salesforce's 150,000-plus customers have moved to paid Agentforce plans. The ambition is running ahead of the installed base.

Salesforce is targeting the mid-market, yet its enterprise customers remain on third-party CCaaS. The strongest opportunity is organizations on premises-based systems from Avaya or Cisco, for whom this skips an entire generation of technology.

Partner Ecosystem Disruption

CCaaS vendors now face a competitor inside the platform their customers already use. "Good enough and natively integrated" has a long history of beating "functionally superior but requires integration" in the mid-market.

For systems integrators, integration revenue disappears if CRM and contact center are one platform. Salesforce is already reshaping its partner program — two tiers instead of four, 28 competencies instead of 170 badges, and the SI role reframed from "systems integration" to "outcome architecture."

Can a CRM Vendor Do Real-Time Telephony?

Voice inside a SaaS application is fundamentally different from adding a digital channel. AWS took years to mature Amazon Connect while owning the infrastructure. Salesforce is making the same leap from further back. Its argument: it only needs to be good enough for use cases where AI handles most interactions and humans handle exceptions. That has merit — but depends on AI resolution rates climbing at the pace the business model requires.

Where the Blast Radius Does Not Reach

Salesforce's play is desk-centric. It does not address what Mitel estimates to be 80 percent of the global workforce — nurses, hotel staff, manufacturing workers, field teams — who need voice-first, workflow-embedded communications, not CRM-native contact center software.

Mitel's WX framework, also announced at Enterprise Connect, takes the opposite approach: a role-aware communications layer for frontline, mobile, knowledge worker, and contact center roles. Where Salesforce says "bring the contact center inside the CRM," Mitel says "bring communications to where work actually happens." As CIOs consolidate desk-based CX, the question of what to do about the other 80 percent gets harder to ignore.

What CIOs Should Be Asking

The Viability Question

Salesforce has moved from platform neutrality to platform competition. It cannot reverse that. The question is whether it can mature real-time telephony before its CCaaS partners build their own AI-native data layers and make the "native CRM" argument irrelevant.

The CIO's decision is not "Salesforce or my CCaaS provider." It is "how long before the integration seam becomes the bottleneck for AI-driven customer experience — and which parts of my workforce does that even apply to?"