Deflection counts avoided contacts, including customers who abandoned. Resolution counts issues genuinely solved. Every resolution deflects a ticket, and plenty of deflections resolve nothing. If deflection rises while satisfaction is flat or falling, customers are giving up rather than being helped.
Key takeaways
- Deflection and containment both count abandonment as success.
- Cross-channel leakage makes deflection look better than it is.
- Rising deflection plus rising repeat contacts is the failure signature.
- Vendors define deflection differently, so quoted rates are not comparable.
Deflection is the metric most support tools lead with, and the easiest one to inflate. Here is how to tell whether yours describes anything real.
What deflection actually counts
Deflection is any action that prevents a customer request becoming a human-handled ticket. Help centre articles read instead of tickets filed. Bot answers accepted. In-product hints that resolved a question.
It also counts a customer who opened chat, could not get an answer, and closed the window. That conversation is recorded as deflected, identically to one where the customer got exactly what they needed.
That is the whole problem in one sentence.
The three ways it lies
Abandonment counts as success. The formula is avoided contacts divided by contact attempts. A customer giving up reduces contacts and therefore improves the ratio.
Cross-channel leakage is invisible. A customer deflected from chat who emails an hour later has not been deflected, only moved. Chat deflection improves and email volume rises, and unless someone is matching those, both numbers look fine independently.
Definitions vary. Two vendors quoting deflection rates are frequently measuring different things. Neither is comparable to the other, and neither is comparable to yours.
The failure signature
Watch for this combination:
- Deflection rose sharply, often after a configuration change.
- Satisfaction did not move, or fell.
- Volume on another channel rose within a fortnight.
- Repeat contact rate is not being tracked at all.
That pattern means customers are giving up. The dashboard is recording a triumph.
The most common version: someone made the human option harder to find. Deflection improves immediately, and nothing else does.
What to measure instead
Genuine resolution rate. The share of contacts that ended with a correct answer and no repeat contact within a set window. Define it yourself before measuring anything, and exclude abandonment and handoffs explicitly.
Reopen rate across channels. Match by customer identity and topic, not by ticket thread. A resolved chat followed by an email about the same issue is a reopen even though the two systems treat them as unrelated.
Satisfaction, segmented. By topic, by channel, and by whether the issue was resolved or escalated. The aggregate hides everything useful.
Those three together cannot be gamed by making support harder to reach, which is the entire point.
How to audit your current numbers
Four questions, and you can answer all of them this week:
- How is our deflection calculated? Ask your vendor whether abandonment counts and whether escalations count. If the definition includes customers who gave up, the number is not measuring what you assumed.
- What is our repeat contact rate? If the answer is that nobody tracks it, that is the first thing to fix. It is the honesty check on every other metric you have.
- Did volume move to another channel? Compare chat and email volume over the period deflection improved. A rise in one matching a fall in the other is leakage.
- What did satisfaction do? Segment it. If it fell in the topics where deflection rose most, you have your answer.
Why this matters commercially
Because teams act on these numbers.
A support leader reporting rising deflection gets budget and credibility. If the underlying reality is customers abandoning, the consequence arrives two quarters later as churn, unattributed, in a different report. By then the connection is invisible and the programme that caused it is considered a success.
The teams that avoid this are the ones that put reopen rate on the same dashboard from the start. It is a cheap discipline and it makes every other number trustworthy.
The vendor incentive question
Worth asking directly: what is your vendor rewarded for?
If a vendor bills per conversation, they earn identically whether the customer was helped or gave up. If they report deflection as the headline outcome, the metric they are optimising counts abandonment as a win.
Neither is an accusation of bad faith. Both are incentive structures, and incentive structures produce outcomes regardless of intent.
Fidiora bills only on genuine resolutions and does not report or price on deflection at all. Abandoned chats, timeouts, and handoffs are never billed. We would make the same argument if we sold nothing: the metric you pay on is the metric you will get more of.
The one change worth making this week
Put repeat contact rate next to whatever automation metric you currently report.
That single addition makes the other number honest, and it costs nothing except the effort of matching contacts by customer and topic within a fortnight window. Every team that does this learns something in the first month.
Frequently asked questions
What is the difference between deflection and resolution?
Is a high deflection rate good?
How do I measure genuine resolution?
Why do vendors report deflection?
Resolve, don't deflect.
See Fidiora resolve a ticket, capture a lead, and keep the bill predictable.