How to calculate your ticket deflection rate
Stevia Putri
Katelin Teen
Last edited May 15, 2026
Ticket deflection rate is the metric AI vendors lead with, and for good reason. It translates directly into cost savings: a ticket resolved via self-service costs close to nothing, while a manually handled one runs $22 to over $100 per resolution according to MetricNet. So the number matters.
The problem is that most teams are calculating it in a way that flatters the number rather than reflects operational reality. A vendor shows you 80% deflection, you share it with leadership, and six months later CSAT is down and ticket volume hasn't budged. Understanding where the calculation goes wrong is more useful than the formula itself.
This guide walks through the formulas, the most common measurement mistakes, and how to benchmark what you find. Tools like eesel AI's Helpdesk Agent can surface deflection data automatically - but knowing the underlying mechanics helps you read any number with the right skepticism.
What ticket deflection rate actually measures
Ticket deflection rate is the percentage of inbound support contacts resolved through self-service tools - chatbots, knowledge bases, FAQ pages, community forums, or automated workflows - without a human agent handling them.
Before you calculate anything, it helps to know where deflection rate sits relative to two related metrics that often get used interchangeably:
| Metric | What it measures | Bar |
|---|---|---|
| Deflection rate | Contacts that didn't reach a human agent, regardless of outcome. Includes customers who gave up or abandoned the chat. | Lowest |
| Containment rate | Contacts where the customer completed the AI interaction without escalating. Excludes abandonment in well-implemented setups. | Middle |
| Resolution rate | Contacts where the AI fully solved the customer's problem, confirmed via CSAT or a resolution signal. | Highest |
When a vendor quotes you a deflection number, always ask which of these definitions they are using. The gap between them tells you exactly where your self-service is failing customers while appearing to succeed on paper.
The core formula
The standard calculation is straightforward:
Ticket Deflection Rate = (Support Requests Resolved via Self-Service / Total Support Requests) x 100
Worked example: Your team received 1,000 support contacts last month. 400 were resolved through your chatbot or knowledge base without ever reaching an agent. That gives you:
(400 / 1,000) x 100 = 40%
Simple enough. The complexity starts when you try to define each part of the formula precisely.
The calculation problem: three mistakes that inflate your number
These are the errors that produce impressive-looking numbers that don't match what your agents are actually experiencing.
1. Counting abandonment as resolution
This is the most widespread measurement error. A customer who closes a chat window because the bot gave them a useless response is "deflected" by most platform counting conventions, even though their problem went unsolved and they are likely to call back, email, or churn.
Voiceflow's analysis of enterprise deployments puts it directly:
"A 70% deflection rate sounds impressive. It might also mean 70% of customers who contacted you never got their problem solved." -- Voiceflow
2. Measuring at first touchpoint only
Many platforms flag a session as deflected the moment the bot responds - not after verifying the customer's issue was resolved. A bot that says "here's your tracking info" gets credit for deflection even when the customer emails again an hour later because the package never arrived.
This point came up clearly in a practitioner discussion on r/ecommerce:
"The real issue is most companies measure deflection at first touchpoint instead of tracking if customer actually got their problem solved - so bot says 'here's tracking info' and they mark it deflected even when customer still emails later because package never showed up." - u/MissionFar5475
3. Double-counting customers who escalate
When a customer starts in self-service and then escalates to an agent, a naive formula counts them in both the self-service total and the agent-handled total. This inflates the denominator and makes your rate look lower than reality, or inflates the numerator if you count the self-service interaction as a separate resolved session.
Alhena's corrected approach first calculates your self-service resolution rate, then adjusts the denominator:
Self-Service Resolution Rate = Self-Service Sessions Resolved / Total Self-Service Sessions
Total Support Requests (corrected) = Self-Service Sessions x Self-Service Resolution Rate + Agent-Handled Tickets
Deflection Rate = Self-Service Resolutions / Corrected Total Support Requests x 100
Worked example using the corrected formula:
- Self-service sessions last month: 1,000
- Self-service resolution rate: 90% (meaning 10% escalated to an agent)
- Agent-handled tickets: 200
Corrected Total = 1,000 x 90% + 200 = 1,100
Deflection Rate = 900 / 1,100 x 100 = 81.8%
Skipping the correction and adding raw self-service sessions to agent tickets would give you a denominator of 1,200 instead of 1,100 - a small difference in this example, but it compounds as session volume grows.
Channel-specific formulas
If you want to measure deflection by channel rather than overall, two formulas are worth having.
Help center self-service score (Zendesk's approach)
Rather than a percentage, Zendesk measures deflection as a ratio:
Self-Service Score = Total Help Center Users / Total Users Who Submitted Tickets
A score of 4 means 4 customers resolved their issue through self-service for every 1 ticket submitted. The ratio form sidesteps the denominator ambiguity problem. For more on Zendesk deflection by channel, the channel breakdown matters when you want to isolate where self-service is working.
Chatbot-specific deflection rate
Chatbot Deflection Rate = Total Users Interacting with Chatbot / Users Routed to Live Agents
This isolates the chatbot's contribution and is useful when evaluating whether a specific AI investment is paying off. If your chatbot handles 500 conversations and 100 of those get routed to humans, your chatbot deflection rate is 5 - meaning 5 customers resolved via chatbot for every 1 escalation.
For Freshservice and other ITSM tools, this same formula applies at the ticket channel level.
Industry benchmarks
Once you have a clean number, here is where it falls across performance tiers:
| Performance tier | Deflection rate | Context |
|---|---|---|
| Below average | < 15% | Portal not trusted or not visible |
| Industry average (tech) | ~23% | Pylon, Atera |
| Good (established brands) | 20-40% | Kustomer |
| Good (AI-enabled teams) | 40-60% | Pylon |
| High-performing IT | 60%+ | Atera |
| Best-in-class | 60-85% | Pylon |
E-commerce teams consistently achieve 50-60% on routine inquiries (order tracking, shipping, basic product questions) with well-implemented automation, according to community consensus from support practitioners. Highly optimized platforms push past 60% on those same ticket types. The caveat: vendor-marketed rates of 80-90% early in deployment should be treated with skepticism. At that level, either the interaction mix is unusually simple or "deflection" includes abandonment.
Real customer case studies give more grounded reference points. Kickfin achieved a 72% self-serve rate via Forethought after several months of iteration. Forma went from 30% to 39% over six months - a smaller number, but measured honestly. Everlane saw its live service deflection rate grow 4x after implementing AI, starting from 10% of conversations handled on day one.
The four numbers that actually tell you if self-service is working
Deflection rate on its own can be gamed by making it harder for customers to reach humans. Track these alongside it to get the full picture - see eesel's guide to customer support analytics for how these fit into a broader measurement framework:
| Metric | Formula | What it tells you |
|---|---|---|
| Successful containment rate | Contacts ended without escalation AND with a positive CSAT signal / Total AI contacts | Whether the AI actually solved problems, not just closed sessions |
| Re-contact rate | Customers who contact again within 24-48 hrs / Total AI-handled contacts x 100 | Most direct signal that deflection numbers are inflated |
| Escalation quality score | How well the AI hands off context when it does escalate | Low quality means failures compound into more expensive human-handled tickets |
| Cost per resolution | Total support cost / Total resolved interactions (AI + human blended) | The number that connects AI performance to business impact |
The re-contact rate is the one to add first if you currently track none of these. It is the earliest signal that your deflection number is telling the truth. A team achieving 60% deflection with a 5% re-contact rate is doing well. A team at 60% deflection with a 35% re-contact rate is mostly counting customers who gave up.
"What actually matters operationally is containment rate: of all contacts that entered the automated flow, what percentage never escalated. Anything above 40% containment on a well-configured system handling order status, returns initiation, and basic product questions is realistic. 60%+ is achievable with good intent mapping and fallback logic." - u/JMALIK0702, r/ecommerce
For a more complete picture of AI deflection vs human deflection, these metrics separate what the AI is genuinely resolving from what it is routing around.
What actually moves the number
Once you have a reliable baseline, three levers drive meaningful improvement.
Knowledge base quality and coverage
Your deflection rate is capped by the quality of your content. A chatbot or self-service portal can only resolve what it knows. Review transcripts where the AI failed and use them to fill gaps: missing articles, outdated policies, vague step-by-step instructions. Each gap you close opens a new category of interactions the AI can handle on its own.
Attempting to push up deflection rate before the knowledge foundation is solid causes CSAT and NPS to fall alongside it. More content without better content is not the path.
Integration depth
An AI that can only answer questions will always have a lower containment rate than one that can take action. Password resets account for roughly 30% of all IT support tickets. If your self-service can initiate the reset rather than just explaining how to request one, that entire category becomes deflectable. Each new system integration - order management, billing, returns workflows - opens up a corresponding category of ticket types the AI can resolve end to end.
Start narrow, then expand
Teams that try to automate everything at once get lower average containment rates than teams that start with the highest-volume, most predictable ticket types. Identify your top 10 contact reasons, build automations only for those, and route everything else directly to humans without making customers fight through the bot. Once containment rates on those categories are high, expand to the next tier.
This is how eesel AI's Helpdesk Agent typically gets deployed - starting with supervised coverage on Tier 1 tickets, then expanding scope as the AI proves its quality on each ticket type. Before going live, teams run the AI against hundreds of past tickets in simulation mode to see the expected deflection rate on each category before it touches real customers.
eesel AI for ticket deflection
eesel AI is an AI Helpdesk Agent that connects to your existing help desk - Zendesk, Freshdesk, Gorgias, and others - and handles support tickets autonomously. It learns from your past tickets, help center articles, and connected documentation, so it starts deflecting relevant questions from day one rather than from a blank slate.
What makes the deflection measurement more useful with eesel is the feedback loop. Every ticket the AI handles or escalates becomes a data point. eesel's reports dashboard surfaces the topics generating the most volume, identifies knowledge gaps, and tracks where escalations are happening - which is exactly the data you need to close the gap between your deflection rate and your containment rate. Mature eesel deployments reach up to 81% autonomous resolution on Tier 1 support.
Pricing is task-based at $0.40 per regular ticket, with no per-seat fees. A $50 free trial is available with no credit card required.
For a deeper guide on building a deflection strategy, see the AI support ticket deflection guide.
Frequently Asked Questions
Share this article
Article by
Stevia Putri
Stevia Putri is a marketing generalist at eesel AI, where she helps turn powerful AI tools into stories that resonate. She’s driven by curiosity, clarity, and the human side of technology.
