Safely manage your Zendesk from the AI assistant you already use, via the Deltastring MCP. Beacon configuration platform
← Back to news

Salesforce Agentforce Heats Up the Consolidation Fight, UJET Says It Could Backfire

Salesforce's Agentforce push into contact center capabilities has crystallised a long-simmering tension in CX procurement: the consolidation narrative assumes that adding voice and AI to an existing CRM solves fragmentation, but UJET's Baker Johnson argues this fundamentally misdiagnoses the problem. The real issue isn't missing features—it's architectural debt. Enterprises have spent a decade layering integration tools atop fragmented systems, creating what Johnson calls the "integration trap," where agents navigate four to ten systems simultaneously and IT teams manage sprawling operational dependencies. This isn't a feature gap; it's a structural problem that bundling more capabilities into Salesforce won't resolve. The evidence is stark: 70% of Salesforce's new revenue growth came from price increases rather than net new customer acquisition, suggesting organisations aren't choosing the platform but rather trapped by switching costs so prohibitive that accepting annual price hikes becomes the path of least resistance.

The implications for CX teams are uncomfortable. If you're already running Agentforce or considering it, Johnson's "integration trap" diagnosis should prompt hard questions about whether consolidation actually reduces complexity or simply concentrates it under a single vendor's renewal terms. The consolidation play works brilliantly for Salesforce's revenue model—lock-in deepens with each integration—but it may not work for your operational reality. Teams evaluating all-in-one platforms should resist the temptation to map existing tool sprawl onto a single vendor's roadmap. Instead, Johnson advocates starting from first principles: design the architecture you actually need today, then determine the vendor path that gets you there, rather than retrofitting your processes to fit an incumbent's product strategy. For support leaders and CX consultants, this reframes the renewal conversation from "which platform consolidates the most" to "which architecture minimises switching costs and operational debt"—a fundamentally different question.