Quality

Your Deflection Rate Is Up and Nothing Got Better

Deflection is the metric most support tools lead with because it is the easiest to inflate. A chat that ends because the customer gave up counts exactly the same as one that ended because they got what they needed.

Published September 10, 2026 · Reviewed by the Fidiora team

Short answer

If deflection is rising while satisfaction is flat or falling, customers are giving up rather than getting answers. Deflection counts avoided contacts including abandonment, so it can improve while the customer experience degrades. Measure genuine resolution and repeat contact rate instead.

Key takeaways

  • Deflection counts customers who gave up as successes.
  • Cross-channel leakage makes deflection look better than it is.
  • Rising deflection plus rising repeat contacts is the signature of failure.
  • Vendors define deflection differently, so quoted rates are not comparable.
01

Signs you have this problem

  • Deflection rose sharply after a configuration change
  • Satisfaction did not move or fell
  • Email volume rose shortly after chat deflection improved
  • Repeat contact rate is not tracked at all
  • Nobody can explain how deflection is calculated
02

Why it happens

  • Abandonment counted as deflection
  • Escalation made harder to find
  • No measurement of cross-channel repeat contacts
  • Success defined as avoided contact rather than resolved issue
  • Vendor reporting that does not disclose its definition
Optimising deflection produces a support experience that looks efficient and frustrates customers. The avoided contacts reappear on other channels or as churn, and because nobody is measuring the connection, the team keeps pushing the metric that is causing the damage.
03

The Fix

How to fix it

01

Find out how your deflection is 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 think.

02

Track repeat contacts across channels

Match by customer and topic within a two-week window. A deflected chat followed by an email about the same issue was never deflected.

03

Report deflection with satisfaction, always

Deflection alone is uninterpretable. Presented next to satisfaction and repeat contact rate, it becomes useful and much harder to game.

04

Stop hiding the escalation path

If deflection rose because the human option became harder to find, you have not improved anything except a number on a dashboard.

05

Measure and price on resolution

Fidiora bills only for genuine resolutions and never for abandonment, timeouts, or handoffs, which removes the commercial incentive to inflate the metric in the first place.

How Fidiora Helps

Fidiora does not report or price on deflection. The number that matters, and the number that generates a charge, is a genuine resolution where the customer got an answer and did not come back. That alignment is the point of outcome pricing.

See Pricing
FAQ

Questions

What is the difference between deflection and resolution?
Deflection means a ticket was not created, which includes customers who gave up. Resolution means the issue was genuinely solved. Every resolution deflects a ticket, and plenty of deflections resolve nothing.
Is a high deflection rate bad?
It is uninterpretable on its own. Paired with stable satisfaction and low repeat contacts it is good. Paired with falling satisfaction it means customers are abandoning rather than being helped.
How do I measure genuine resolution?
Define it before you start, exclude abandonment and handoffs, and verify by absence of repeat contact about the same issue within seven to fourteen days across all channels.
Get Started

See Fidiora resolve a ticket in 60 seconds.

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

No credit card · Live in under an hour