Automation

What is ticket deflection?

Also known as: deflection, support deflection, deflection rate, ticket deflection rate, call deflection

Published September 10, 2026 · Last updated October 8, 2026 · Reviewed by the Fidiora team

Definition

Ticket deflection is any action that prevents a customer request from becoming a human-handled ticket. It counts help centre articles read instead of tickets filed, bot answers accepted, and in-product hints that resolve a question before it is asked. Deflection measures avoided contact, not necessarily a satisfied customer.

Why it matters

Deflection is the metric most support tools lead with because it is easy to inflate. A chat that ends because the customer gave up counts as deflected. That makes deflection a poor proxy for value: it can rise while satisfaction falls. Support leaders who budget against deflection often discover the avoided tickets simply reappeared on another channel a day later.

What to know

Deflection is measured as avoided contacts divided by total contact attempts, which means abandonment inflates it.
A high deflection rate paired with a falling CSAT score usually means customers are giving up rather than getting answers.
Deflection is channel-local. A customer deflected from chat who then emails has not been deflected at all, only moved.
The honest version of the metric is resolution: the customer asked, got a correct answer, and did not come back.
Vendors define deflection differently, so two quoted deflection rates are rarely comparable without reading the definition.

How to calculate it

Deflection rate = (contacts avoided / total contact attempts) x 100

An example

Example: a store shows a shipping FAQ before the chat box opens. Two hundred shoppers read it and close the window. All two hundred are recorded as deflected, even though some left because the FAQ did not answer their question and they gave up.

Deflection rate vs resolution rate: a worked example

One illustrative month of 1,000 help widget sessions, measured both ways.
Measure	What it counts	Count	Rate
Total contact attempts	Customers who opened the help widget	1,000	100 percent
Deflected	Sessions that did not become a ticket	700	Deflection rate: 70 percent
Of which genuinely resolved	Got a correct answer and did not come back within 14 days	450	Resolution rate: 45 percent
Of which gave up or moved channel	Left without an answer, or emailed instead	250	Counted as success by deflection

Common mistakes

Treating deflection and resolution as the same number
Counting abandoned chats as deflected contacts
Optimising for deflection without watching repeat contact rate
Comparing your deflection rate to a vendor benchmark computed differently

Where Fidiora fits

Fidiora does not bill for deflection. Abandoned chats, silent timeouts, and handoffs are never charged, so there is no commercial incentive to inflate the number. The metric Fidiora reports and prices on is genuine resolution, which is the outcome a customer actually experiences.

See Pricing

FAQ

Questions

What is the deflection rate formula?

Deflection rate equals contacts avoided divided by total contact attempts, multiplied by 100. If 1,000 customers open the help widget and 300 go on to create a ticket, 700 were deflected, a 70 percent deflection rate. The formula cannot tell customers who were helped apart from customers who gave up.

What is meant by deflection in customer service?

Deflection means steering a customer to an answer that does not need an agent, such as a help article, a chatbot reply, or an in-product hint, so no ticket is created. The term describes the avoided contact, not whether the customer actually got what they needed, which is why it needs a resolution check beside it.

Is ticket deflection good or bad?

Deflection is good when it happens because the customer got a real answer faster than a ticket would have delivered it. It is bad when it happens because the customer gave up. The metric alone cannot tell you which, so pair it with repeat contact rate and satisfaction.

What is a good ticket deflection rate?

There is no universal benchmark worth chasing, because vendors compute the number differently. A more useful target is a resolution rate on the questions your customers actually ask, measured alongside a stable or improving satisfaction score.

How is deflection different from resolution?

Deflection means a ticket was not created. Resolution means the customer got a correct answer and the issue closed. Every resolution deflects a ticket, but plenty of deflections resolve nothing.

Deflection rate vs resolution rate: what is the difference?

Deflection rate divides contacts that did not become a ticket by all contact attempts. Resolution rate divides issues genuinely solved, with no repeat contact in a set window, by all contacts. In the worked example, 1,000 sessions give a 70 percent deflection rate but only a 45 percent resolution rate. See deflection vs resolution for both formulas.

Get Started

See Fidiora resolve a ticket in 60 seconds.

No credit card, no sales call required. Connect your docs and watch it work.

Start Free Book a Demo

No credit card · Live in under an hour · Read the setup guide