What Is a Good Ticket Deflection Rate? Benchmarks for 2026

Search the question and you get numbers between 15% and 80%. Not ranges within one study — flatly contradictory answers to the same question, presented with equal confidence.

The reason is not that the metric is hard. It is that almost everyone publishing a benchmark sells software whose value is measured by that benchmark.

Who wrote the page you are reading

On the day we checked, the first page of Google for this query was: Alhena, eesel, HappySupport, Bookbag, DevRev, Capacity, Decagon and OMQ. Every one of them sells support automation. One community platform made the page.

That is not a conspiracy, it is an incentive. A vendor whose product deflects tickets has no reason to publish a benchmark that makes deflection look modest, and every reason to define the metric generously.

We sell nothing. That is the only reason to prefer this page, and it is the reason we can print the low numbers.

The formula

Deflection rate is the share of support contacts resolved without a human agent.

Deflection rate = (self-service resolutions ÷ total support contacts) × 100

Every dispute in this category is about what goes in the numerator. Does a customer who closed the chat window count? Does one who got an answer and opened a ticket four days later still count?

Benchmarks by channel

The most careful published set we found separates by mode rather than quoting one figure, which is already better practice than most.

Agent assist deflecting zero is worth pausing on. It helps a human answer faster — a reported 14% reduction in handle time — but the human still answers. Any vendor quoting a deflection figure for a copilot product is measuring something else.

Headline deflection and true deflection

The distinction that matters most, and the one vendor pages skip. Headline deflection counts the session as resolved when nobody escalated. True deflection strips out the ones that came back.

True deflection runs roughly 30–40% below the headline. A customer who gets a wrong answer, gives up, and emails you on Thursday was counted as deflected on Monday.

So what is a good rate?

For a first-year deployment, 10–15% true deflection is the realistic figure for B2B SaaS. Vendor marketing implies 30–50%.

That gap is the single most useful number on this page. If you are building a business case on 40%, you are building it on a figure that describes a mature deployment with excellent documentation, measured generously.

• Year one, honest measurement: 10–15%
• Mature deployment, good documentation: 25–40%
• Top quartile enterprise, tier-one queries only: around 58%
• Anything above 60%: ask what the denominator excludes

The variable that moves it most

Not the platform. Your documentation.

Gartner surveyed 5,728 customers in December 2023 and found only 14% of service issues fully resolved in self-service, with the most common failure being customers unable to find content relevant to their issue, at 43%.

Which means the cheapest way to improve deflection is usually to spend a fortnight rewriting your twenty most-viewed articles, before you buy anything.

How the benchmark changes by industry

A single number for the whole category is not useful, because ticket mix varies more than software does.

If your ticket mix is mostly diagnosis, a 60% target is not ambitious, it is arithmetically unavailable. Sort last month's tickets into documented and undocumented before setting any target — the documented share is close to your realistic ceiling.

Deflection rate vs resolution rate vs containment rate

Three terms, used interchangeably in marketing, meaning different things.

• Deflection — the contact never became a ticket. Says nothing about whether the customer was helped.
• Resolution — the issue was actually solved. Stricter, and the only one that correlates with satisfaction.
• Containment — the conversation stayed in the channel. The most generous of the three, because a customer who gave up was contained.

A vendor quoting containment as though it were resolution is not lying, but they are letting you hear the better number. When you get a percentage on a sales call, ask which of the three it is and what happens when a customer abandons mid-conversation.

What practitioners report, as against what vendors publish

The reason people append “reddit” to almost every query in this category is that the ranking pages are written by sellers. So we went and read the threads. Three things recur.

The first is the gap between the dashboard and the customer. A support lead in r/CustomerSuccess described executives seeing a 40% deflection rate and concluding support was fixed, while the churn comments showed customers angry at having been ignored by a bot that answered a different question than the one asked. That is the exact failure our CSAT check above is for.

The second is that teams blame the knowledge base for a long time before they blame the tool. One r/SaaS post describes three months spent restructuring articles, tagging and escalation rules on the assumption the AI had not been trained correctly — with an 18-month contract already renewed underneath it.

The third is that the high numbers are real but they are journeys, not starting points. An e-commerce operator reporting 79% deflection notes they began around 40% on basic FAQs and canned responses. Nobody arrives at 79%.

A caution about this source. Searching these terms also returns seeded promotional posts — accounts opening with “I build custom AI systems for B2B companies” before quoting a deflection figure, and threads in vendor-run subreddits. Reddit is being astroturfed by the same vendors whose pages people use Reddit to avoid. Treat any number there as a claim, not evidence.

The four choices that make a deflection rate meaningless

When a vendor quotes a percentage, four decisions sit underneath it. Change any one and the number moves ten or twenty points without the software changing at all.

A vendor choosing the generous column on all four can honestly report 60% where the strict column gives 25%. Neither figure is a lie. Only one describes your business.

So the useful question on a sales call is not what deflection rate you achieve. It is which of those four choices you made, and whether you will put them in writing.

The same definition sets your invoice

On per-resolution pricing, the definition producing the marketing percentage is frequently the definition producing the bill. A generous reading inflates the number a vendor markets with and the number of billable events they charge you for, at the same time.

That is not an accusation. It is a structural conflict that exists whether or not anyone exploits it, and it is worth naming before signing. Ask directly whether the resolution you are billed for is the same event as the resolution in the case studies.

Three numbers worth more than deflection

• Cost per resolved contact, all in — licence plus usage plus the agent time still spent. The number a CFO would ask for, and almost nobody tracks it.
• Re-open rate on AI-handled conversations against your human baseline. If it is higher, part of your deflection is fictional.
• CSAT split by handler, AI against human, tracked separately rather than blended.

The third catches the failure the others miss. Deflection rising while AI-handled CSAT falls means you are suppressing contacts rather than resolving them, and the blended number will look fine throughout.

What a good deflection programme looks like in month one

Almost every disappointing deployment skipped the same fortnight of work, so it is worth stating as a sequence rather than advice.

• Week one: sort last month's tickets into documented and undocumented. The documented share is close to your realistic ceiling, and it is usually lower than the target somebody already committed to.
• Week two: rewrite your twenty most-viewed articles. Gartner's 2024 finding is that 43% of self-service failures come down to customers not finding relevant content, so this is the step that removes the most failures per hour spent.
• Week three: run the agent in simulation against historical tickets if the tool supports it, and read the transcripts rather than the summary percentage.
• Week four: launch on one channel or one ticket type, with re-open rate and AI-handled CSAT instrumented before go-live, not after.

The instrumentation point matters more than it sounds. Adding measurement after launch means you have no baseline, and without a baseline every subsequent number is unfalsifiable.

How to measure it honestly

• Set the window at 7 days. Anything shorter flatters you.
• Count a re-open as a failure, even under a new ticket ID.
• Keep out-of-scope queries in the denominator. Excluding what the AI cannot handle is how 80% figures get made.
• Exclude abandoned sessions from the numerator. Giving up is not resolution.
• Track deflection against CSAT. Deflection rising while satisfaction falls means you are hiding demand, not meeting it.

That last one is the check that matters. It is trivial to deflect 60% of contacts by making it hard to reach a human, and the metric will look excellent right up until churn arrives.

Figures on this page are read from published sources and cited below. We do not run tickets through these platforms, so none of these numbers are ours — the contribution here is the audit of where they come from and how they are defined.

WRITTEN BY AR · UPDATED 2026-07-30

I read the fine print. Vendor pricing pages, billing definitions, terms, funding filings and acquisition notices — then I do the arithmetic nobody publishes: what a platform actually costs at your volume, what its headline metric is really counting, and who owns it now. I do not run benchmarks, and no page here pretends otherwise.

Editorial policy