Ticket deflection calculator

What is ticket deflection?

Ticket deflection is when a customer finds the answer on their own, in a help article, a video or a chatbot, instead of opening a support ticket. A ticket deflection calculator estimates how many tickets that prevents and what those tickets would have cost. It is the simplest way to put a number on the ROI of a help center before or after you invest in one.

Deflection matters most for repetitive “how do I…” questions. Bugs, billing disputes and account problems usually still need a person, so a realistic estimate starts with the tickets self-service can actually answer.

The formula this calculator uses

The calculation has three lines:

1. Deflected tickets = tickets per month × share of how-to tickets × deflection rate
2. Agent hours freed = deflected tickets × minutes per ticket ÷ 60
3. Savings = deflected tickets × cost per ticket

If you don’t know your cost per ticket, switch to an hourly agent cost. The calculator then works out the cost per ticket as hourly cost × minutes per ticket ÷ 60. Yearly figures are the monthly ones × 12.

A short example. Say a team gets 1,000 tickets a month, half are how-to questions, and you assume better articles resolve one in five of those. That is 1,000 × 0.5 × 0.2 = 100 deflected tickets a month. At 10 minutes each, that frees about 17 agent hours. These numbers are only an illustration; use your own.

How to measure your deflection rate

There is no single agreed formula for a help-center deflection rate, and the common ones measure different things. Pick one, write down how you measure it and stick with it, so you can compare month to month.

Many published benchmarks come from vendors selling chatbots or help desks, measured in their own way. Treat any outside number as a starting assumption, not a target.

How to read the result

The output is an estimate of capacity, not cash in the bank. Freed agent hours turn into savings only if you hire less, cover more volume with the same team or move agents to work that earns money, such as onboarding or retention. Present the result as a range: run it once with a cautious deflection rate and once with an optimistic one.

To turn the result into a self-service ROI figure, compare the yearly savings with what your help center costs: the software plus the hours spent writing and updating articles and videos.

How to raise self-service deflection

Start from your top ticket reasons

Tag tickets for a month and write articles for the most common how-to questions first. A few articles often cover a large part of the volume.

Show, don’t only tell

For software questions, a short video or screenshots of the real screen answer what a paragraph leaves open.

Put answers where questions start

Link articles from the contact form, the product and your chat widget, and make the help center searchable.

Keep content current

An article that shows last year’s interface creates tickets instead of preventing them. Review articles after every release that changes the screens they show.