CX orchestration has quietly replaced automation as the hardest problem in customer experience, and the industry has spent two years discovering that the difficult part was never the model. It was everything the model has to talk to. Enterprises have pushed AI agents, voice AI and automated messaging into production faster than the architecture underneath could absorb them, and the bill for that mismatch is now arriving.
The argument was set out on 26 August 2026 in a VentureBeat feature presented by Tata Communications, built around an interview with Gaurav Anand, the company’s global head of Customer Interaction Suite. It is sponsored content, and it should be read as such. But the diagnosis it offers is one that independent analysts, three multi-billion-dollar acquisitions and a fair amount of failed pilot work all point at from different directions.
This article separates the diagnosis from the sales pitch. It covers what Anand actually said, why the shift from automation to CX orchestration is real rather than marketing, the consolidation wave that has reshaped the contact centre market in eighteen months, the evidence that most agentic projects still fail, the interoperability standards now emerging underneath all of it, and the questions any buyer should put to a vendor before signing. Some of it flatters the vendors. Some of it does not.
Table of contents
- What the CX Orchestration Argument Actually Says
- Why CX Orchestration Is Replacing Automation as the Priority
- The Legacy Trap: Bolting AI Onto Systems Never Built for It
- Shared Context Is the Layer Under Every CX Orchestration Claim
- The Consolidation Wave Behind the CX Orchestration Push
- Where the Network Fits Into CX Orchestration
- CX Orchestration and the Human Agent
- Ontologies, Context Graphs and CX Orchestration Standards
- What Tata Communications Is Actually Selling
- The Evidence That CX Orchestration Projects Fail
- A CX Orchestration Readiness Checklist for Buyers
- Risks and Open Questions in CX Orchestration
- Frequently Asked Questions About CX Orchestration
- References
What the CX Orchestration Argument Actually Says
The piece is short, and the substance sits in four claims rather than the headline.
Deployment has outrun architecture
The opening premise is that enterprises are deploying AI agents, voice AI and automation across messaging, voice and digital channels faster than the architecture meant to support it. Most of that deployment, Anand says, has involved attaching conversational AI to legacy systems never built for it. That is a claim about sequencing, not about technology quality, and it is the one part of the argument that almost nobody in the market disputes.
The direct quote
“In the rush to deploy AI, organizations have largely bolted conversational AI onto legacy systems,” Anand says. “As a result, while many enterprises have adopted digital tools, very few have platforms that are truly integrated, scaled, and capable of seamless orchestration.” The phrase doing the work there is “truly integrated”. Adoption and integration have been counted as the same metric for three years, and they are not.
The cost lands on people
The consequence described is a heavy cognitive load on human agents, who must piece together context across disjointed tools simply to work out what an AI system has already told a customer. That is a specific, testable failure mode. It is also the one that never shows up in an automation business case, because the saving is booked against the deflected contact and the cost is absorbed by the person who picks up what the bot dropped.
The architecture claim
Traditional CX architecture, the piece argues, was built for linear, human-driven routing rather than for managing real-time data flows between autonomous AI systems, data lakes and human workers. The problem is framed as the absence of a shared enterprise context connecting customer identities, interactions, transactions, policies, journeys and operational systems into a common understanding.
The four claims at a glance
| Claim in the piece | What it rests on | How testable it is |
|---|---|---|
| AI has been bolted onto legacy systems | Vendor observation across an install base | High — audit your own integration layer |
| Human agents carry the reconciliation cost | Vendor observation, widely corroborated | High — measure handle time after a bot handoff |
| Coordination now beats added intelligence | Argument, not measurement | Medium — depends on how many tools you run |
| A shared context layer is the fix | Product thesis of the sponsor | Low — this is where the sales pitch begins |
Why CX Orchestration Is Replacing Automation as the Priority
The distinction between automation and CX orchestration is not a semantic one, and it changes what a buyer should be purchasing.
Anand’s definition
“Automation solves individual tasks, whereas orchestration connects them into end-to-end outcomes,” Anand says. “The next evolution is context-aware orchestration, where AI agents, applications, and human workers operate using a shared understanding of customers, processes, and business intent rather than isolated system records.” Strip the vendor language and the claim is that per-task automation has a ceiling, and that the ceiling is coordination.
The combinatorial problem
As organisations accumulate more bots, agents and AI tools, managing them grows exponentially more complex. That is arithmetic rather than opinion. Two systems have one interface between them; ten have forty-five. Every one of those interfaces is a place where customer context can be dropped, duplicated or contradicted, and none of them appear on the licence schedule you signed.
Where advantage now sits
The competitive advantage, on this reading, sits less in deploying automation and more in how intelligently systems hand off work, collaborate and escalate. That is a meaningful reframing for procurement. A vendor demo that shows a single agent resolving a single query tells you almost nothing about the behaviour that will actually determine your customer satisfaction score.
Automation versus CX orchestration
| Dimension | Automation | CX orchestration |
|---|---|---|
| Unit of work | A task | An outcome across systems |
| Success measure | Containment or deflection rate | Resolution without repetition |
| Failure mode | The bot cannot answer | The customer repeats themselves to a human |
| Data requirement | Access to one system | A shared model of the customer |
| Cost of scaling | Linear with tasks | Combinatorial with tools |
| Who owns it | A contact centre team | Nobody, usually — and that is the problem |
The CX orchestration ownership question nobody answers
The last row deserves more attention than it usually gets. CX orchestration crosses service, sales, marketing, IT and data functions, which means it crosses budget lines. The technical work is tractable. Deciding which system is authoritative when two disagree about a customer’s status is a governance decision, and governance decisions do not get made by procurement.
The Legacy Trap: Bolting AI Onto Systems Never Built for It
The sharpest paragraph in the source article is also the least commercial one.
Recreating the phone menu
Companies that simply place a voice AI agent in front of an existing system, the piece argues, end up recreating the deterministic phone menus that AI was supposed to replace. That is a precise description of a great many 2025 and 2026 deployments. The interface changed from keypad to speech; the underlying decision tree, and the dead end at the bottom of it, did not.
Why it happens
It happens because the front end is the only part a project can change in a quarter. Replacing the routing logic, the customer data model and the case management system is a multi-year programme with no demo. Adding a conversational layer is a six-week engagement with a very good demo. Incentives do the rest, and this pattern repeats in every workflow automation programme that starts at the interface.
The tell
There is a simple diagnostic. Ask the agent something the underlying system cannot answer and see what happens. If the response is an apology and a transfer to a queue where the customer starts again, you have bought a new interface to an old constraint. If the response is a partial answer plus a warm handoff carrying full context, some genuine CX orchestration exists underneath.
What the AI is actually supposed to add
Anand’s framing is that the real benefit of AI is the scale, speed and orchestration it provides. Two of those three are properties of the model. The third is a property of your architecture, and no vendor can sell it to you as a feature — which is precisely why so many buyers end up with the first two and assume the third arrived with them.
Shared Context Is the Layer Under Every CX Orchestration Claim
Every serious CX orchestration argument eventually arrives at the same place: a shared context layer.
What the layer has to do
“Today’s operational complexity is no longer about adding more intelligence,” Anand says. “It is about coordinating the existing intelligence across the enterprise, so the enterprise customer never feels the friction of those internal silos. That requires a shared context layer that allows AI systems, applications, and people to operate from the same understanding of the customer and the business.”
It is not the same as data access
The distinction matters commercially. Data access means the agent can query the CRM. Shared context means the agent, the human and the case management system agree on what the customer’s situation is, what has already been promised, and which policy applies. Most integration projects deliver the first and are sold as the second.
The evidence from outside the vendor
Salesforce’s own service research points the same way. Its published findings show that 88 per cent of service leaders are prioritising technology integration to bring data together and eliminate silos, and that organisations unifying their customer service channel data are 1.4 times more likely to report a very successful AI implementation. Neither figure is neutral — it is a platform vendor measuring demand for platforms — but the direction is consistent with what the CX orchestration argument predicts.
Where CX orchestration context has to persist
The claim in the source piece is that AI and human agents can move across voice, WhatsApp, chat, email and CRM workflows without losing customer context, with identity, intent and AI-driven insight flowing continuously across channels instead of remaining trapped in disconnected applications. That is a description of the destination, not of any shipping product. Treat it as the specification you test a vendor against.
The Consolidation Wave Behind the CX Orchestration Push
The most verifiable part of the argument is the one Anand only gestures at: the industry has been buying its way to a CX orchestration layer.
What he says
The piece points to a wave of consolidation across the industry, as established contact centre providers acquire AI-native firms to close capability gaps. The broader shift, it argues, reflects a recognition that enterprises need more than channels and automation; they need an intelligence layer capable of orchestrating AI, people, data and workflows across the business.
The three deals that make the case
That claim is easy to check, and it holds. In late July 2025 NiCE agreed to acquire the German conversational and agentic AI firm Cognigy for approximately $955 million, a price representing more than 25 times Cognigy’s 2024 revenue of about $37 million, with the technology destined for the CXone Mpower platform and an install base of roughly 25,000 businesses. Days later, on 31 July 2025, Salesforce and ServiceNow each put in about $750 million for a combined $1.5 billion investment in Genesys — two direct rivals underwriting the same contact centre platform.
The private equity leg
The third deal is structural rather than strategic. Thoma Bravo agreed to acquire Verint for $2 billion in an all-cash transaction and to combine it with Calabrio, its existing portfolio company, explicitly to build a broader AI-driven customer experience automation business addressing what the parties described as a $50 billion-plus market. Taken together the three transactions say the same thing: nobody believes a point solution wins this market.
The deal table
| Transaction | Value | Announced | What it buys |
|---|---|---|---|
| Thoma Bravo acquires Verint, merges with Calabrio | $2.0 billion | August 2025 | Workforce engagement plus CX automation scale |
| Salesforce and ServiceNow invest in Genesys | $1.5 billion | 31 July 2025 | A shared stake in the engagement layer |
| NiCE acquires Cognigy | $955 million | 28 July 2025 | Agentic AI capability for CXone Mpower |
| Tata Communications acquires Kaleyra | ~$100 million plus debt | Completed October 2023 | CPaaS channels underneath the Interaction Fabric |
What the money is really buying
The buyer’s read on CX orchestration
Consolidation is good news for CX orchestration and bad news for negotiating leverage. A single vendor owning contact centre, workforce management, analytics and agentic AI can genuinely deliver shared context, because it no longer has to integrate with anyone. It also removes the competitive tension that kept renewal pricing honest. Both things are true at once, and a five-year total cost model is the only way to see them together.
Where the Network Fits Into CX Orchestration
The least discussed constraint in the whole argument is latency, and it is the one a telecoms company would naturally raise.
Data gravity
Synchronising customer intent, conversation history, enterprise data and AI decision-making across channels only works without lag. Legacy networks not designed for modern data frequency create what Anand calls data gravity, producing latency and inconsistent journeys as users switch channels. The term is doing a lot of work, but the underlying point is real: context that arrives after the customer has finished speaking is not context.
The quote
“The underlying network needs to be engineered to be as agile as the AI systems running on top of it,” he explains. “Interactions stay synchronous and technology itself becomes invisible, leaving only an experience that feels effortless.” Coming from a company that sells global network capacity, this is unmistakably a commercial argument. It is also, for real-time voice, a correct one.
Where it matters and where it does not
Latency budgets are brutal in voice and forgiving almost everywhere else. A voice agent that pauses for two seconds while it retrieves a policy sounds broken. The same delay in a chat or email workflow is invisible. Buyers should push back hard on network upgrade proposals attached to asynchronous channels, and take them seriously for synchronous ones. The distinction is worth several hundred thousand pounds in a mid-sized programme.
The honest test
Instrument the round trip before you accept the diagnosis. If your voice agent’s response time is dominated by model inference rather than data retrieval, the network is not your constraint and a cloud architecture review will tell you so faster than any vendor assessment.
CX Orchestration and the Human Agent
The most useful section of the source piece is the one about people, because it describes a division of labour rather than a replacement.
What AI gets
Automated call summaries, real-time sentiment analysis and AI-powered assistance are described as providing agents with instant, actionable insights and suggested next steps directly within their workflow. The AI handles routine, high-volume tasks — password resets, delivery tracking, account updates. None of that is novel. What is notable is the explicit framing of the human as the recipient of context rather than the source of it.
The fraud example
Anand’s illustration is the strongest thing in the article. “If a customer is facing a sudden crisis like a fraudulent transaction, the AI can instantly block the card, but it cannot provide the emotional comfort and delicate communication needed in that moment of panic,” he says. “The answer to the dilemma is intelligent orchestration, rather than a choice between systems.”
How that resolves in practice
In the described flow, AI handles the immediate technical transaction while real-time sentiment analysis recognises the customer’s distress and routes the call to a human expert. This is a good specification precisely because it is falsifiable. Either the card is blocked within seconds and a human is on the line before the customer has to explain the situation twice, or the CX orchestration did not work.
The metric that exposes it
There is one number that tests all of this and almost nobody publishes it: how often a customer repeats information they have already given. Containment rate rises when the bot ends conversations. Repetition rate rises when the bot ends them badly. Any CX orchestration business case that reports the first without the second is measuring the wrong half of the system.
Division of labour
| Interaction type | Handled by | What must carry across the handoff |
|---|---|---|
| Password reset, delivery tracking | AI, end to end | Nothing — it should not reach a human |
| Account update with an exception | AI, then human | What was attempted and why it failed |
| Fraudulent transaction | AI acts, human reassures | Action taken, timestamp, customer sentiment |
| Complaint or vulnerability | Human, AI assists | Full history plus prior promises made |
| Multi-system dispute | Human, orchestrated | A single authoritative view of the case |
Ontologies, Context Graphs and CX Orchestration Standards
The technical vocabulary in the piece is unusually specific, and it is worth translating.
The enterprise ontology
The argument is that organisations increasingly need a common enterprise ontology: a shared business vocabulary aligning customer data, products, policies, standard operating procedures, transactions and workflows across otherwise disconnected platforms. In plain terms, everyone has to mean the same thing by “active customer”, “open case” and “eligible for refund”. Most enterprises do not, and discover it during the first CX orchestration workshop.
The context graph
The next phase, the piece says, is coordinating tasks through a shared understanding of the enterprise rather than merely across systems. Context graphs built on those ontologies connect customers, interactions, products, policies, decisions and outcomes across organisational silos, so AI agents and human workers operate from the same source of context. This is a graph database argument dressed for a CX audience, and it is a reasonable one.
What is happening in the open
Underneath the vendor layer, genuine interoperability standards have arrived faster than most buyers realise. Google published the Agent2Agent protocol on 9 April 2025 and donated it to the Linux Foundation on 23 June 2025. Version 1.0.1 landed in May 2026 with an extension mechanism, and by the protocol’s first anniversary more than 150 organisations backed it, with integrations across Google, Microsoft and AWS platforms.
The two-protocol picture
The division of labour between the standards is now reasonably settled. The Model Context Protocol connects an agent to its tools and data; Agent2Agent connects agents to each other. Both now sit under the Linux Foundation’s Agentic AI Foundation, launched in December 2025 with OpenAI, Anthropic, Google, Microsoft, AWS and Block among its founding members. For CX orchestration this matters more than any single product: it is the difference between buying a layer and standardising on one.
Why buyers should care
If your CX orchestration layer speaks these protocols, replacing one agent vendor is a configuration change. If it does not, it is a migration. That single question belongs in every request for proposal issued this year, and it costs nothing to ask.
What Tata Communications Is Actually Selling
Sponsored content earns the right to a product pitch, and this one is specific enough to evaluate.
The Interaction Fabric
The company’s stated solution is the Interaction Fabric, an orchestration layer that unifies contact centre, messaging, collaboration, AI and customer data while coordinating AI agents, channels and enterprise systems in real time. Underneath it is a context-driven architecture that continuously connects identities, conversations, transactions and operational data so interactions retain continuity across channels and touchpoints.
The named products
Three are named: Voice AI, AI Workers and Total Experience Hub. Total Experience is described as a unified model bringing together customer, employee and AI-driven experiences, with human agents supported by real-time conversational intelligence and next-best-action recommendations. The naming is conventional for the category; the ambition is broad enough that a proof of concept is the only way to size it.
Where the capability came from
Tata Communications did not build the channel layer from scratch. It completed the acquisition of the CPaaS provider Kaleyra in October 2023 for approximately $100 million plus assumed debt, a business that had reported revenue of $339.2 million for the full year 2022. That purchase supplies the messaging, voice and email plumbing on which any Interaction Fabric claim depends.
The disclosure that matters
None of this makes the diagnosis wrong. It does mean the article should be read as a company describing the problem its product solves, which is a legitimate genre with a predictable bias. The consolidation evidence, the Gartner forecasts and the protocol work all come from outside that frame, and they broadly agree with it.
The Evidence That CX Orchestration Projects Fail
The counterweight to the whole argument comes from the analyst community, and it is blunt.
The cancellation forecast
Gartner published a forecast on 25 June 2025 that over 40 per cent of agentic AI projects will be cancelled by the end of 2027, citing escalating costs, unclear business value and inadequate risk controls. Anushree Verma, a senior director analyst at the firm, characterised most current projects as early-stage experiments or proofs of concept driven by hype and often misapplied — a description that blinds organisations to the real cost of deploying agents at scale.
Agent washing
The same research warned about “agent washing”: rebranding assistants, robotic process tooling and chatbots as agentic without substantive capability. Gartner’s estimate was that only around 130 of the thousands of vendors claiming agentic capability were genuine. For anyone evaluating a CX orchestration platform, that ratio is the single most useful number in this article.
What buyers actually reported
A January 2025 Gartner poll of 3,412 webinar attendees found 19 per cent had made significant investments in agentic AI, 42 per cent conservative investments, 8 per cent none at all, and the remaining 31 per cent were waiting or unsure. That is not a market that has committed. It is a market conducting inexpensive experiments while it works out whether the CX orchestration story is true.
Investment posture
The other Gartner number
The same firm forecasts that by 2029 agentic AI will autonomously resolve 80 per cent of common customer service issues without human intervention, producing a 30 per cent reduction in operational costs. Daniel O’Sullivan, a senior director analyst in its customer service practice, called agentic AI a game-changer paving the way for autonomous, low-effort customer experiences. Both forecasts come from the same house, and they are not contradictory — a technology can be transformative by 2029 and still cancel four projects in ten before 2028.
The forecasts side by side
A CX Orchestration Readiness Checklist for Buyers
The practical value of the argument is that it turns into questions you can ask before spending anything.
Start with the repetition metric
Before evaluating a platform, measure how often customers repeat information after an automated interaction. Sample fifty escalated contacts and count. If the number is high, you have a CX orchestration problem and a new model will not fix it. If it is low, your constraint is somewhere else and you should spend the budget there instead.
Audit what is authoritative
List every system holding customer state — CRM, billing, case management, identity, marketing — and write down which one wins when two disagree. Most organisations cannot complete this exercise in a single session. That inability is the ontology problem the source article describes, and it is cheaper to resolve on paper than inside a platform migration. A structured data management and analytics review is the usual starting point.
Test the handoff, not the bot
Vendor demonstrations show resolution. Insist on seeing failure. Ask for a scripted scenario in which the agent cannot complete the task and watch what the human receives. Everything that matters about CX orchestration is visible in that thirty seconds, and almost nothing about it is visible in the successful path.
Ask the protocol question
Ask directly whether the platform speaks the Model Context Protocol and Agent2Agent, and what happens if you want to replace one agent with another vendor’s. Get the answer in writing. The difference between a configuration change and a migration is worth more than any feature on the comparison sheet.
Price the exit
Consolidation means your CX orchestration vendor may own most of your stack within three years. Model the renewal at year three and year five on the assumption that you have no credible alternative, because that is the position the market is engineering. Then decide how much of the stack you are willing to hand over. Organisations running mature intelligent automation programmes tend to keep the context layer independent for exactly this reason.
The checklist in table form
| Question | Good answer | Warning sign |
|---|---|---|
| Which system is authoritative for customer state? | One named system, documented | “It depends on the team” |
| What does the human receive on escalation? | Transcript, actions taken, sentiment | A phone call and a customer ID |
| Does it support MCP and Agent2Agent? | Yes, with version numbers | “We have an open API” |
| How is repetition rate measured? | Instrumented and reported monthly | Only containment is reported |
| Who owns the CX orchestration decisions? | A named cross-functional owner | The contact centre alone |
| What is the year-five licence exposure? | Modelled, with an exit path | Not modelled |
Risks and Open Questions in CX Orchestration
Several things in the argument remain unresolved, and buyers should hold them open.
The CX orchestration sponsor problem
The strongest version of the CX orchestration thesis currently comes from companies selling CX orchestration layers. That does not make it false, but it does mean the independent evidence base is thinner than the volume of commentary suggests. The consolidation deals and the Gartner forecasts are real; a controlled measurement of CX orchestration improving customer outcomes at scale is still largely absent from the public record.
CX orchestration centralisation risk
A shared context layer is a single point of failure by design. Every channel depending on one context graph means an outage there is an outage everywhere, and a data quality error propagates to every touchpoint simultaneously rather than staying inside one system. That trade is usually worth making, but it belongs in the risk register and in an IT governance framework rather than in the benefits case.
Governance of autonomous decisions
The hardest unanswered question is accountability. When an orchestrated system spanning four vendors makes a decision that harms a customer, the audit trail has to survive the handoffs. Nothing in the current standards work guarantees that, and regulated industries will find this out the expensive way.
The prediction to weigh
Anand’s closing position is that the future of CX will be defined by simplification — aligning data, infrastructure and operating models around clear customer outcomes rather than adding more models and tools — and that customer engagement will evolve from reactive to predictive and increasingly generative. It is a sensible prediction. It is also one that every enterprise software category has made about itself, roughly once a decade, with mixed results.
Where this leaves a buyer
The defensible position is neither enthusiasm nor dismissal. Fix the repetition metric, document what is authoritative, insist on protocol support, test the failure path, and keep the context layer portable. Those five moves cost very little and hold their value whether or not the CX orchestration story turns out as the vendors describe it. Firms building an AI strategy this year should treat them as the floor.
Frequently Asked Questions About CX Orchestration
What is CX orchestration?
It is the coordination of AI agents, applications, data and human workers so that a customer interaction reaches an outcome across systems, rather than being automated one task at a time. The defining feature is shared context: every participant works from the same understanding of the customer.
How is it different from automation?
Automation completes individual tasks. CX orchestration connects those tasks into end-to-end outcomes and manages the handoffs between them. A high containment rate can coexist with terrible CX orchestration, because the failures show up after the bot ends the conversation.
Who said orchestration is the new challenge for CX?
The argument was published by VentureBeat on 26 August 2026 in a feature presented by Tata Communications, based on an interview with Gaurav Anand, the company’s global head of Customer Interaction Suite.
Is the source article independent journalism?
No. It is sponsored content presented by Tata Communications, and it promotes that company’s Interaction Fabric, Voice AI, AI Workers and Total Experience Hub. The underlying diagnosis is corroborated elsewhere, but the piece should be read as vendor material.
What is an enterprise ontology in this context?
A shared business vocabulary that aligns customer data, products, policies, standard operating procedures, transactions and workflows across disconnected platforms, so that different systems and agents mean the same thing by the same term.
Do most agentic AI projects succeed?
Not yet. Gartner forecast in June 2025 that over 40 per cent of agentic AI projects would be cancelled by the end of 2027, citing cost, unclear value and weak risk controls, and estimated that only around 130 of the thousands of vendors claiming agentic capability were genuine.
Which standards should a CX orchestration platform support?
The Model Context Protocol, for connecting agents to tools and data, and Agent2Agent, for agent-to-agent communication. Both now sit under the Linux Foundation’s Agentic AI Foundation, launched in December 2025.
What single metric exposes a weak deployment?
The rate at which customers repeat information they have already provided. Containment and deflection rates measure how often the bot ends a conversation; repetition measures how often it ended one badly.
References
Orchestration is the new challenge for CX in the age of AI agents
Tata Communications Customer Interaction Suite
Tata Communications completes acquisition of Kaleyra
Gartner Predicts Agentic AI Will Autonomously Resolve 80% of Common Customer Service Issues by 2029
Gartner Predicts Over 40% of Agentic AI Projects Will Be Canceled by End of 2027
NiCE to Acquire Cognigy, Advancing the Leading CX AI Platform
Genesys Announces $1.5 Billion Investment by Salesforce and ServiceNow
Thoma Bravo to Acquire Verint to Join Forces with Calabrio
Linux Foundation Launches the Agent2Agent Protocol Project
More AI coverage: explore Progressive Robot's AI Models, Tools & Releases hub — hands-on reviews, setup guides and benchmarks in one place.