IBM has used its latest earnings call to detail how the company does not want to win the AI race by building the biggest model.
Instead, it is betting that enterprises will care more about what happens after the models arrive, including how agents are governed, where they run, and whether they can access the data needed to do something useful.
That was the clearest message from IBM’s Q2 2026 earnings call. And while the company did not announce a CCaaS deal, customer service deployment, or new CRM product, its strategy has a clear CX implication.
Indeed, during the call, Arvind Krishna, CEO, President, and Chairman of IBM, said:
“Value will increasingly shift towards the orchestration and data layers so that clients can optimize outcomes, cost and governance across multiple models and agents and keep control of their proprietary data.”
Contact center, CRM, and customer experience leaders know better than most that AI agents can only be as useful as the customer, operational, and product data they can access.
If that information is stale, fragmented, or poorly governed, the result is often a fast answer that is wrong, irrelevant, or impossible to explain.
IBM Wants to Be the Control Layer for Enterprise AI Agents
IBM positioned watsonx Orchestrate as the “control plane” for enterprise AI agents.
According to Krishna, the platform helps customers “build, manage and govern agents” across multiple models, cloud environments, and on-premises infrastructure. It is also designed to provide observability, evaluation, governance, identity management, and security.
While this may be a fairly vague claim, it does speak directly to a problem many enterprises are now encountering as AI pilots progress beyond a single chatbot or internal copilot.
Early deployments can be relatively contained: a virtual agent answers frequently asked questions, an agent-assist tool summarizes calls, and a sales copilot drafts follow-up emails.
Yet, as organizations introduce more agents across service, sales, IT, and marketing, the task becomes less about deploying a single AI feature and more about managing a growing network of automated decision-makers.
Which agent has access to which data? Which model is being used? How are outputs evaluated? Can the business identify why an agent took a particular action? And can it stop that agent from exposing sensitive customer information?
IBM is aiming to answer those questions with watsonx Orchestrate. Krishna argued that the vendor’s differentiation lies in its “neutrality and enterprise-grade operational control,” rather than locking customers into a single model or cloud ecosystem.
That could appeal to large, regulated organizations, particularly those trying to deploy AI across legacy systems, private environments, and public cloud platforms.
Real-Time Data Is the Other Half of the Equation
However, governing an AI agent is only half the battle. The agent also needs context.
That is where IBM is placing Confluent, the data-streaming company it acquired earlier this year, at the center of its AI strategy, as Krishna explained:
“Confluent delivers real-time governed data to models and agents across our control plane.”
Customer experience has increasingly become a real-time data challenge. A service agent or virtual assistant needs to know whether a payment has cleared, whether an order has shipped, whether a customer has already contacted support, and whether there is an active outage or service issue.
The same applies to journey orchestration. A brand cannot credibly trigger proactive outreach, next-best actions, or personalized offers if the underlying data is delayed, disconnected, or based on an incomplete customer profile.
IBM’s pitch is that Confluent can provide the real-time, governed flow of information into the AI agents managed by watsonx Orchestrate.
In theory, this could allow an enterprise to connect AI-driven service and engagement workflows to live operational events, while retaining control over data access and governance.
The significance of this lays in the fact that many AI agent conversations have focused on what an agent can say, while the more difficult question is whether it has the right information to act.
A CX Proposition, But Not a CX Product Launch
There is a caveat.
IBM did not use the call to announce a dedicated customer experience platform, a new contact center offering, or a named deployment of watsonx Orchestrate in customer service. There was no talk of AI-powered IVR, workforce engagement management, or a major CCaaS win.
As such, this is not evidence that IBM is about to challenge the likes of Salesforce, Microsoft, ServiceNow, Genesys, or NiCE in their core markets.
Still, IBM’s strategy offers a useful lens through which CX leaders can assess agentic AI. The next phase of the market will not be won solely by vendors with the most convincing demos. It will depend on whether enterprises can connect agents to live business data without creating a security, compliance, or operational mess.
IBM is making a play for that underlying layer.
The company also said it is investing in specialized technical and client-facing talent, including forward-deployed engineers, as customers move from AI experimentation toward enterprise-scale deployment.
Whether watsonx Orchestrate and Confluent can translate that ambition into customer-facing deployments remains to be seen.
