Ibex CX's partnership with Sierra positions the vendor as a managed integration layer rather than a monolithic platform, but the model introduces a critical accountability gap that will define its enterprise viability. The May 2026 Sierra partnership adds autonomous agent capability to ibex's existing Wave iX suite, journey design, and human operations, creating what appears to be an end-to-end CX offer. Philippine Airlines is already live, and ibex's operational scale—36,000 human agents, 138 million managed interactions annually—provides credible infrastructure. Yet the architecture deliberately fragments ownership: Sierra owns the autonomous agent engine, ibex owns the client relationship and implementation, and customers often retain their own CCaaS platforms and enterprise connectors. This raises an uncomfortable question for buyers already running Agentforce or similar integrated stacks: does a partner-led model actually reduce complexity, or does it simply redistribute it across contract boundaries? When a transaction fails mid-handoff, when authentication drops during an omnichannel transfer, or when a custom API breaks, the customer experiences one failure but the responsible party remains ambiguous.
The evidence gap exposes the real risk. Ibex has published strong individual component results—Wave iX achieved 70% authentication success and 20% less repetitive work in a retailer deployment, while Sierra demonstrated deep system integration in healthcare environments. However, no joint customer data exists for complete journeys after escalation, failed actions, or channel changes. The published metrics cover isolated capabilities, not the orchestrated resolution that separates genuine integration from cosmetic dashboard consolidation. Ibex claims six-week launches and up to 60% containment, but these remain vendor assertions without scoped customer evidence. The omnichannel challenge is particularly acute: Puzzel's 2026 survey found only 3% of contact centers run on a single platform, yet the average organisation manages 3.9 technologies. A customer switching from voice to chat can lose authentication state, workflow ownership, and case context before anyone detects the failure. Craig Cotton's observation that a 1% handoff failure rate affects millions of customers underscores why this matters operationally.
Enterprise buyers should demand contractual clarity before shortlisting. The contract must name which party owns each connector, define what "resolution" means for billing purposes, specify who approves production changes and rollbacks, and establish recovery rules when failures cross product boundaries. Ibex's ISO/IEC 42001 certification is meaningful, but buyers must confirm its scope covers Sierra agents, custom connectors, and data exchanges—not just ibex-owned systems. The success-based pricing model is attractive only if the definition of success is explicit and measurable. For teams seeking a fully integrated native stack with complete technical control, ibex remains a weaker fit; for enterprises willing to trade some autonomy for managed accountability across a heterogeneous environment, the vendor belongs on the shortlist provided the failure path is tested as rigorously as the happy path.
Ibex CX is starting to look stronger as the managed integration and operations layer for customer experience leaders. Still, buyers need proof that Wave iX, Sierra, enterprise systems, and human agents can behave like one contact center when a journey fails. The biggest update from ibex CX this year
Ibex CX Integration: Is AI-to-Human Handoff the Real Test? CX Today