Frankly Speaking: CX Truths

Your Deflection Rate Is a Lie

What your vendor dashboard isn’t showing you and three questions that will.

Umesh Jain · 26 May 2026

Your Deflection Rate Is a Lie

Your AI vendor is measuring the wrong thing.

They’re showing you how many calls didn’t reach a human. What they aren’t prioritizing, and in many cases can’t easily track, is how many of those customers actually got their problem solved.

Deflection and resolution are not the same metric. And right now, the entire industry is optimizing for the one that’s easier to measure.

Here's why it matters.

When a voice AI “handles” a call but doesn’t resolve it, the customer doesn’t disappear. They call back, now frustrated. The interaction is more complex and ultimately lands with a human agent who has to start from scratch. Your abandonment rate drops, your dashboard looks clean, and your repeat contact volume quietly climbs.

The AI isn’t solving problems. It’s rescheduling them.

I saw this play out recently with a telecom company that had hit its 32% deflection target. They brought me in to help build the case for expanding their AI budget. On paper, the numbers looked strong. Then we dug into what was actually happening.

First call resolution on voice AI: 53%.

On human agents handling the same call types: 76%.

TNPS for AI-handled interactions was down 30 points.

And the vendor's projected savings of 40–55%? Once you accounted for infrastructure, monitoring, and ongoing optimization, the real number was under 18%.

Nobody had misled anyone. But nobody had asked the right questions either.

Sound familiar?

This led to an observation that surprised even me.

The same process failures that had frustrated human agents for years were now running through the AI, faster and at scale. The difference is that experienced agents carry tribal knowledge: the unofficial workarounds, the escalation paths that aren’t in any manual, the things you learn after two years on the floor that nobody ever wrote down.

The AI had read every document. It hadn’t learned what your best agents actually do when the system breaks, which in most call centers is constantly. So it gave technically correct answers to problems the underlying system couldn’t actually resolve. Customers hung up. The company called it a 32% success rate.

This is not an AI problem. It's a measurement problem and a questions problem.

Before your next budget conversation, ask three things:

One, what is our resolution rate, not our deflection rate? If your vendor can’t produce that number, you don’t have the data to make this decision.

Two, what is our repeat contact rate for AI-handled calls versus human-handled calls? That number tells you what the dashboard is hiding.

Three, have we fixed the process, or just the speed? Automating a broken workflow doesn’t create efficiency. It creates bad customer experiences faster and at a scale human agents can no longer contain.

The telecom client didn’t scrap their AI investment. They rebuilt how they managed it, with warm transfers, real QA on AI interactions, and a serious look at the systems underneath. That’s the right outcome.

But they got there by looking past the number their vendor handed them.

Don’t let a green dashboard make a strategic decision for you.

What are your AI numbers actually telling you, and do you trust them? Tell me on LinkedIn. I read every comment.

Umesh Jain
Umesh Jain CEO at Now Analytics. Customer experience and contact center strategist. Twenty-eight years at the intersection of strategy, technology, operations and CX.

New editions every two weeks. Subscribe on LinkedIn.

All articles


Wondering what your own numbers look like?

Two minutes, and you get the figure whether or not you ever speak to us.