Free support tool

Free Ticket Deflection Rate Calculator

Ticket deflection rate is the percentage of support inquiries resolved by self-service - chatbot, help center, and FAQs - without reaching a human agent. This calculator turns your inquiry counts into a deflection rate, monthly cost savings, and annualized savings, so you can put a real dollar figure on your knowledge-base and chatbot investment.

Defaults use the commonly cited $15.56 cost per agent-handled ticket; override it with your own numbers for a more accurate read.

Calculate your deflection rate

All computation runs in your browser - nothing is sent to a server.

1. Inquiry volume

2. Cost assumptions

Your deflection rate

65%

6,500 of 10,000 inquiries deflected.

Best in class

Your self-service surface is doing heavy lifting. Focus next on quality of deflected interactions - bad self-service can hide as deflected.

Tickets deflected

6,500

Monthly savings

$100,490

Deflected x ($15.56 - $0.10)

Annualized savings

$1.21M

Monthly savings x 12

How to use this tool

Calculate deflection in four steps

  1. 1

    Enter your total support inquiries for the period (chat sessions, help-center searches with intent, plus tickets - the full top of funnel).

  2. 2

    Enter how many of those were resolved via self-service (chatbot, help center, FAQs) and how many escalated to a human agent.

  3. 3

    Adjust the cost-per-ticket assumptions if you have internal numbers - defaults use the common $15.56 industry average for an agent-handled ticket.

  4. 4

    Read your deflection rate, monthly cost savings, and annualized savings - all updated live as you type.

The deflection formula

Deflection % = (Self-service resolved / Total inquiries) x 100

Cost savings = deflected tickets x (cost per agent ticket - cost per deflected ticket). The standard agent-handled cost cited in support benchmarks (HDI, Forrester) is around $15.56 per ticket. Self-service cost is dominated by infrastructure - often pennies per interaction once the system is built.

Quick example

10,000 inquiries: 6,500 resolved by chatbot/help center, 3,500 escalated to agents. Deflection = 6,500 / 10,000 = 65%. At $15.56 vs $0.10 per ticket, that's ~$100,490 in monthly savings.

What is a good ticket deflection rate?

A common industry band is 30-50%, with best-in-class self-service operations clearing 50-70%. Below 20% usually means the help center is incomplete, hard to find, or not surfaced inside the support flow itself. Aim for steady month-over-month improvement rather than chasing a single benchmark - product complexity, channel mix, and customer technical fluency all shift what a healthy number looks like for your team.

Frequently asked questions

What is ticket deflection rate?

Ticket deflection rate is the percentage of potential support inquiries that are resolved by self-service resources (chatbot, help center, FAQs, community) without ever reaching a human agent. It measures how much load your knowledge base and automation actually take off the support team.

How do you calculate ticket deflection rate?

Deflection rate % = (inquiries resolved via self-service / total inquiries) x 100. If 6,500 of 10,000 monthly inquiries are resolved by your chatbot or help center, the deflection rate is 65%. Multiply the deflected ticket count by the difference in cost per ticket (agent vs deflected) to get the dollar savings.

What is a good ticket deflection rate?

Industry observations put a healthy deflection rate at 30-50%, with best-in-class self-service operations clearing 50-70%. Below 20% usually means the help center is incomplete, hard to find, or not surfaced inside the support flow. Numbers vary by product complexity, so use these as directional rather than strict targets.

How does a chatbot improve ticket deflection?

A chatbot lifts deflection by answering common questions in-channel before a ticket is created, by routing repeat questions to the right help-center article, and by capturing intent so simple flows (status checks, password resets, refund eligibility) never become tickets. The deflection rate moves the most when the bot is wired into your knowledge base, not when it answers from a script.

What's the difference between deflection rate and resolution rate?

Deflection rate measures how many inquiries never reached an agent at all (self-service caught them). Resolution rate measures how many of the tickets that did reach support were resolved successfully. Deflection lowers volume; resolution measures quality on what's left.