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 is the new ibex Sierra partnership, but the company’s offer goes a lot further than that. Ibex brings journey design, client-specific integration, analytics, Wave iX tools, and human contact center operations into the picture. Sierra supplies the autonomous agent engine. That’s a valuable move, but it creates a new question. Does ibex remain accountable when work crosses products, systems, channels, and teams?
The May 5, 2026 partnership announcement promises seamless, end-to-end CX, from AI agent to support team, at scale. Philippine Airlines is already rolling out the joint offer in phases, so this isn’t a roadmap item gathering dust. What’s missing is proof of the full handoff, the systems connected behind it, escalation outcomes, and the cost of each completed resolution.
Fortunately, the wider Ibex business still gives the promise some depth. Ibex reported more than 36,000 human CX experts and 138 million managed interactions a year, while its May 6, 2026 earnings call said digital and omnichannel services had grown 18% and represented 82% of revenue.
Buyers now need evidence that the technology underneath those operations is as joined up as the commercial pitch.
TL;DR: Does ibex CX Hold Up Past the Demo?
- Who owns what: ibex owns the managed service, client contract, Wave iX layer, implementation, analytics, and human operation. Sierra owns the autonomous agent platform.
- What’s live: Philippine Airlines is a named production customer, while separate Wave iX and Sierra deployments provide evidence for routing, authentication, transactions, and human handoffs.
- What remains unproven: ibex hasn’t published joint performance data for a complete journey after escalation or a channel change.
- The sharpest risk: split accountability. A failed workflow may involve Sierra, Wave iX, a CCaaS platform, or a client-owned connector, even though the customer experiences one service failure.
- The buyer test: force a failed transaction, inspect every data object passed to the human agent, and make one party contractually responsible for recovery.
What Is ibex CX, and What Does It Actually Own?
Ibex CX is a managed customer experience offer built from ibex operations, Wave iX technology, analytics, integration services, and human support. It isn’t a single CCaaS platform. The current Sierra partnership adds an autonomous AI agent engine to that operating model, while ibex remains the client-facing service provider and implementation owner.
In a contact center, ibex doesn’t own every component, but it’s committed to making the parts of the business behave cohesively. Buyers should experience one journey, one operating model, and one accountable recovery path even when several vendors and client-owned systems sit underneath.
Bob Dechant drew the product boundary clearly during ibex’s May 6, 2026 earnings call. Wave iX covers internally focused capabilities such as training simulation, agent assistance, analytics, translation, verification, and routing. Ibex chose not to build its own autonomous agent engine because management didn’t believe it could match a specialist, so Sierra fills that gap.
The commercial boundary matters too. Dechant said clients will contract with and be billed by ibex, while ibex builds the implementation and pays Sierra through a negotiated resolution-based cost structure. That gives buyers a logical primary owner, but the contract still needs to state what happens when the underlying failure sits outside ibex’s code.
Key Takeaways
- ibex’s differentiation is managed accountability across the journey, rather than ownership of every software component.
- Buyers should judge ibex CX by completed work and clean recovery, not by how many AI features appear in Wave iX.
What Does Deep AI Contact Center Integration Actually Mean?
Deep contact center AI integration lets an agent identify the customer, access live data, follow policy, complete approved actions, and hand unfinished work to a human without losing context. A shared desktop alone can’t prove integration. Buyers need identity, permissions, system state, and recovery rules to move across the complete workflow.
For businesses developing AI contact centers, integration needs to be judged on four levels:
- Knowledge access: The AI retrieves an approved policy, answer, or document.
- System lookup: It checks a live balance, booking, claim, order, or account record.
- Transactional action: It changes a record, submits a request, takes a payment, or completes another approved task.
- Orchestrated resolution: It handles identity, permissions, several systems, and the exceptions that block completion.
Level four marks the real dividing line. Put every tool on one desktop, and the setup may look integrated, even when the connections are mostly cosmetic. Unless the AI can update the system of record, retain authentication, and handle exceptions, employees are still stitching the process together behind the scenes.
Key Takeaways
- Judge integration by the deepest action the AI can complete safely, not by the number of systems visible to an agent.
- A workflow is not orchestrated until identity, action history, system state, and recovery survive the handoff.
Learn more about AI and human agent orchestration in this guide.
How Does the ibex CX Ecosystem Fit Together?
The ibex CX ecosystem combines owned capabilities, partner technology, and client-controlled systems. Its structure is sensible for enterprises that want one managed provider, but it is not a shared black box. Buyers need to know which party owns each layer, how data moves between them, and which connections require custom services.
ibex has used this partner-led model before. Its public ecosystem includes Genesys Cloud CX for omnichannel contact center infrastructure and a 2024 Parloa agreement for generative AI automation in North America. The new Sierra partnership now supplies the autonomous agent engine. ibex hasn’t publicly explained how those earlier relationships fit alongside Sierra in current deployments, though.
The key split is between technology ibex operates directly and systems it coordinates. Wave iX provides ibex-owned agent, customer, and insight layers, while Sierra provides agent building, testing, action, and handoff technology. ibex also reports more than 400 IT professionals, over 250 insights analysts, and upwards of 100 deployments.
Key Takeaways
- A partner-led architecture can give ibex stronger specialist products without forcing clients into one replacement platform.
- The same flexibility creates overlap, integration work, and incident boundaries that must be documented before deployment.
How Deeply Does ibex CX Connect to Enterprise Systems?
Ibex CX reaches enterprise systems through Sierra integrations, custom APIs, and ibex implementation services. The system supports read and write actions, payments, and controlled tool access, but right now, there’s no joint connector catalog. Buyers will need to separate a listed integration from a supported workflow in their own environment.
Sierra advertises more than 40 prebuilt integrations across knowledge sources, business systems, and contact centers. Agent Actions can update an external system or route work to a care team, while traces expose tool calls and decisions.
Still, Cybernews reported in July 2026 that Sierra lacked native Zendesk, Intercom, and Salesforce integrations and often required engineering work. That doesn’t invalidate the 40-plus claim, but prebuilt and turnkey are different. Ibex should identify which connectors are ready to use and which are rebuilt for each client.
| Public claim | What buyers must verify |
|---|---|
| 40+ Sierra integrations | Exact platforms, data objects, actions, and support status |
| Custom connections | Who builds, tests, maintains, and funds later changes? |
| Wave iX connects across the stack | Real-time read/write access or a managed-services claim? |
| Success-based pricing | Who defines resolution and handles repeat contact? |
Sierra’s April 7, 2026 payments release shows deeper action: Level 1 PCI-compliant flows support cards, ACH, payment plans, and real-time confirmation while sensitive data stays outside the conversational agent. Sierra also reported 85% resolution for one card-activation deployment, although the case study wasn’t for an ibex customer.
Sierra’s July 2026 MCP Gateway also shows how it can govern access to Salesforce, Slack, GitHub, and internal data. Buyers should still confirm that the same permission controls, audit records, and rollback tools extend to the ibex deployment rather than stopping at Sierra’s own platform boundary.