Who should own AI in a customer experience team?

Who should own AI in a CX team? When Gladly studied what retail's best AI deployments have in common, the answer became surprisingly clear. The strongest predictor of AI performance wasn't the model, the vendor, or the number of integrations built. It was whether one person was clearly accountable for results.

Every top-performing deployment in this dataset had one. The gap between teams that got results and those that didn't came down to this more than anything else.

An AI owner is the person accountable for how a customer service AI performs over time — maintaining it, improving it, and making sure it stays effective as the business changes. Not a committee, not a vendor, not a shared responsibility across the team. One named person inside the CX function who treats the AI like an operational system that needs regular attention.

What “owning AI” actually means

Owning AI in a CX context isn’t a technical job. It’s an operational one. The person who owns your AI is responsible for:

• Keeping workflows and knowledge base content current as policies, products, and procedures change

• Reviewing AI performance metrics on a regular cadence

• Identifying which conversation types should be added next based on volume and impact

• Coordinating with the rest of the team when AI behavior needs to change

• Escalating when performance dips and having a clear path to getting it addressed

This person doesn’t need to be an engineer. They need to understand your customers, your operations, and what good resolution looks like. They need to care whether the AI is actually working — not just whether it’s running.

What happens when ownership is unclear

In one case from the dataset, a company lost their AI lead without a replacement. What happened next was predictable: workflow updates stopped, configuration went stale, and their addressable resolution rate fell to 0.38%.

That’s not a technology problem. The technology didn’t change. The workflows didn’t break on their own. No one was updating them as policies changed, no one was reviewing performance, no one was catching emerging gaps. The AI kept responding — just with increasingly outdated information.

The contrast is just as instructive. Another company in the dataset had let their AI sit for nearly a year with no iteration. Resolution rate oscillated between 6% and 20%. Within two months of one person taking dedicated ownership, they launched new channels, refreshed their knowledge base, and added use cases. Resolution rate climbed to 48.9%.

Same technology. Very different outcomes.

Why shared ownership often fails

The instinct to distribute AI ownership across a team feels responsible. Multiple stakeholders, shared accountability. In practice, it produces the opposite: decisions that require five approvals, configuration updates that get stuck in back-and-forth, and performance gaps that everyone knows about but no one is tasked with fixing.

AI systems require fast iteration. Customer questions change. Policies update. Seasonal spikes create new inquiry types. The organizations that maintain AI performance over time are the ones where someone can make configuration changes without running a proposal through a committee first.

That person still has a team. They coordinate with product, with operations, with leadership. But the accountability is singular, and that’s what makes the difference.

Where in the organization this person usually sits

The pattern across top-performing deployments: the AI owner sits inside the CX function. They’re close to the customer journey, close to the team members handling escalations, and close to the data that tells you where the AI is falling short.

The role doesn’t require a full-time headcount in most cases. Across the companies in this dataset, it typically runs at 0.5 to 1 dedicated person, with engineering support available for integration work. Some organizations have a CX team member who owns AI alongside other responsibilities. Others have someone dedicated entirely to it. Either can work — as long as the ownership is clear and the person has the authority to act on what they see.

What good AI ownership looks like in practice

The leading beauty retailer in this dataset made 202 workflow updates in 30 days. 131 came in a single week. One person was driving those updates — responding to policy changes, product launches, and new customer questions showing up in the data.

That’s not a dramatic number if you think of it the way that person likely did: each update is a small correction, a gap closed, a customer who gets a better answer next time. The aggregate — 202 in 30 days — is what operational ownership actually looks like when it’s working.

The question isn’t whether you have someone “responsible” for AI in a broad sense. The question is whether someone reviews AI performance every week, has the authority to make changes, and has leadership visibility into how the AI is performing against business outcomes.

If the answer is no — or not sure — that’s where to start.

The AI owner belongs inside CX, because AI performance in customer experience is an operational problem, not a purely technical one. They need daily proximity to:

• What customers are asking

• How agents handle escalations

• When products, policies, or promotions change

In practice, this maps to roles like:

• CX operations manager or director

• Digital support manager

• AI program manager

• Service operations lead

• Customer experience technology lead