Deflection used to be an honest metric, and the video spends its first half defending it. The aisle signs in a supermarket that mean you never flag down staff to find the milk. The airport wayfinding system that gets passengers to a gate without asking anyone. The cash machine that let people take out twenty dollars without queueing for a teller, which remains the cleanest deflection story financial services has produced. In each case both sides won, which is why every industry copied it.

Then comes the formula, and the problem is what is missing from it. Deflection counts issues handled without a human and divides by issues raised. No satisfaction, no resolution, no measure of whether the person was helped. The sharpest turn in the argument is that AI has made this worse rather than better. Watch this if a vendor has recently quoted you a deflection percentage. It will change the question you ask them next.

What this video covers

• Where deflection came from, long before software, in store signage, airport wayfinding, and the cash machine
• Why phone trees were the first time the metric came apart, with dashboards improving while customers shouted for an agent
• What the standard deflection formula counts, and what it leaves out entirely
• The metric collapses three different outcomes into one bucket, the happy customer, the one who drifted off, and the one who closed the tab in frustration
• Why agents that reason, retrieve, and take real actions widen the gap between not reaching a human and actually being helped
• What to ask a vendor instead, and why resolution and satisfaction are the numbers that tell you the truth

Chapters

• 0:00 Why deflection rate is everywhere
• 1:05 Where deflection actually came from
• 2:59 Phone trees, and the first time it broke
• 3:46 The formula, and what is missing from it
• 4:30 Three outcomes counted as one
• 6:25 Why AI makes this worse, not better
• 8:14 What to measure instead of deflection