Salesforce's contact center move is a bet that "resolved" beats "routed"
Salesforce's Agentforce Contact Center, reported on by No Jitter's Rob Hilsen on March 17, 2026, puts the company squarely into the contact center as a service (CCaaS) market for the first time, alongside Genesys, NICE, Five9, Amazon, and Zoom. Salesforce has spent years selling CRM and service-workflow tools into contact centers run by those vendors; this launch has it running the contact center itself. The framing Hilsen uses is architectural rather than competitive: the job to be done is shifting from getting a call or chat to the right place to actually finishing the interaction, with AI reading intent and triggering workflows across connected systems rather than just handing off to a human queue.
What's actually new here, beyond "Salesforce built a CCaaS"?
The product itself matters less than where Salesforce is placing the intelligence — inside the interaction, not around it.
For decades, contact center platforms optimized routing: get the call to the agent with the right skill, in the right queue, fast. Salesforce is arguing that once an AI system can interpret what a customer actually wants and pull the levers to fix it — refund, reschedule, update an account — routing stops being the valuable layer. That's a direct challenge to CCaaS incumbents whose platforms were built around queue and agent-desktop logic, not resolution logic.
Does entering CCaaS actually change what Salesforce can automate?
Owning the contact center layer lets Salesforce chain intent-detection to workflow execution without handing off between separate vendors' systems.
Previously, Salesforce's service AI sat on top of someone else's telephony and routing stack, which meant a resolution step still had to cross a vendor boundary. Folding voice and digital channels into one Salesforce-owned stack removes that seam — in theory. Whether it removes it in practice, for a specific customer's mix of legacy IVR, CRM records, and back-office systems, is a separate question buyers still have to test themselves.
Should buyers take Salesforce's resolution claims at face value?
No — ask who defines "resolved," how it's measured, and whether that number holds up outside a demo environment.
No Jitter's own reporting is a useful check here: a separate piece on the same site, published in August 2026, found that only about one-quarter of AI customer service use cases actually produce measurable ROI. That's the industry's track record on AI-driven support generally, not a claim about Agentforce specifically — but it's the right skepticism to bring into any vendor conversation about "resolution rates." A resolved ticket and a ticket the AI marked resolved are not always the same thing.
What should this change for a buyer evaluating CCaaS right now?
Ask incumbent vendors — Genesys, NICE, Five9, Amazon, Zoom — how their roadmaps respond to resolution-first architecture, not just routing upgrades.
If Salesforce is right that value is migrating from routing to resolution, every established CCaaS vendor now has to show how their AI actually closes an interaction end-to-end, across the customer's own systems, not just how well it triages. That's a harder, more specific question than "does your bot answer FAQs," and it's the one worth pushing on in any 2026 renewal conversation.
Frequently asked questions
Is Agentforce Contact Center available now?
The No Jitter report, published March 17, 2026, covers the launch and its architectural implications; buyers should confirm current availability and pricing directly with Salesforce.
Does this replace the need for a separate CCaaS vendor?
Not automatically — it gives Salesforce customers a native option, but switching contact center platforms is a major migration decision independent of any single vendor's messaging.
Who else is affected by this launch?
Genesys, NICE, Five9, Amazon, and Zoom are the incumbent CCaaS vendors Salesforce now competes with directly, per No Jitter's reporting.
Source: No Jitter, "Agentforce Contact Center signals a shift from routing to resolution," by Rob Hilsen, March 17, 2026.