Salesforce didn’t announce a partnership at Enterprise Connect this week. It announced a replacement.

Agentforce for Contact Center is a full native CCaaS solution built directly into the Salesforce platform. Not a bolt-on. Not an integration. Not a “works with” badge on the AppExchange. A CRM-native execution layer that handles voice, digital channels, workflow automation, and AI-driven resolution without ever leaving Salesforce.

That matters because every mid-market and enterprise CCaaS deal in the channel involves a CRM conversation. Usually Salesforce. And until now, the answer was always the same: “We integrate with Salesforce.” Five9 integrates. NICE integrates. Genesys integrates. The entire CCaaS partner ecosystem has been built on top of Salesforce — which is a fine position right up until Salesforce decides it wants the layer underneath you.

That just happened.

What Agentforce actually is

Agentforce for Contact Center combines three things that previously required separate vendors:

Voice and digital routing. Salesforce is handling inbound and outbound voice, chat, SMS, and social messaging natively. No middleware. No CTI adapter. No telephony partner required for the basic motion.

AI agent automation. Agentforce’s autonomous AI agents handle customer interactions end-to-end, pulling from CRM data in real time. This isn’t a chatbot bolted onto a knowledge base. It’s an AI agent that reads the customer’s full history, takes actions in Salesforce objects, and escalates to human agents when confidence drops below threshold.

Workflow and resolution. Case management, routing rules, SLA enforcement, and post-interaction analytics all live inside the Salesforce platform. The pitch is simple: why buy a separate CCaaS platform when the CRM already knows your customers?

The channel problem

Here’s where it gets uncomfortable for partners.

If you’re a technology advisor selling Five9, NICE, or Genesys into Salesforce accounts, you now have an awkward conversation ahead. The customer’s CTO is going to ask: “Why am I paying for a separate contact center platform when Salesforce says they can do it natively?”

You can argue integration depth. You can argue voice quality. You can argue feature maturity. Those are all legitimate today. But “we integrate better with the platform that just built its own version” is a tough pitch to sustain over 24 months.

The bigger question is whether Salesforce’s channel program will support partner-led CCaaS motions or go direct-heavy. Salesforce has historically been direct-sales dominant with a partner ecosystem focused on implementation services, not product resale. If Agentforce follows that pattern, partners who built their business on CCaaS commissions have a structural problem.

Who should worry, and who shouldn’t

Worry if: Your business is selling standalone CCaaS into Salesforce-dominant accounts. The value proposition of “we integrate with your CRM” just got commoditized by the CRM itself.

Don’t panic if: You’re selling CCaaS into complex, multi-vendor environments where Salesforce isn’t the primary system of record. Healthcare, financial services, and government accounts with compliance requirements aren’t switching to Salesforce-native CCaaS overnight. The regulatory and integration complexity protects the incumbent for now.

Pay attention if: You’re an MSP with a deep Salesforce practice. This is a massive upsell opportunity into existing CRM accounts. Agentforce implementation services, AI agent configuration, workflow design, and migration from legacy contact centers are all partner-led motions. The product sale might go direct, but the services revenue is real.

What the TSDs should be doing

If you’re a TSD carrying Five9, NICE, or Genesys, you need to be having honest conversations with those vendors right now. Not about whether Salesforce will take market share. About how fast.

The smart play is to add Agentforce to your portfolio rather than pretending it doesn’t exist. Partners will sell whatever solves the customer’s problem. If Salesforce’s solution is genuinely better for CRM-heavy accounts, the TSD that enables that motion wins. The one that protects its existing vendor relationships at the expense of partner relevance loses.

The pattern

This is the same story we’ve seen play out in other categories. The platform vendor decides that the integration layer above it is actually a feature, not a product. Microsoft did it with Teams Phone. Google is doing it with Workspace contact center capabilities. Now Salesforce is doing it with Agentforce.

It doesn’t kill the standalone vendors overnight. It compresses their market to the accounts where the platform vendor’s native solution isn’t good enough. And that market gets smaller every year.

Five9 saw this coming. Their Fusion partner program expansion, also announced at Enterprise Connect this week, is designed to build ecosystem stickiness through ISV partnerships and third-party AI agent support. That’s the right defensive move: build an ecosystem the platform vendor can’t replicate in a single release.

Whether it’s enough depends on how fast Salesforce executes. And Salesforce, whatever else you think about them, tends to execute.