Ticket deflection rate is the percentage of potential support tickets resolved before a customer actually creates one, typically because a suggested self-service article solved their problem first.‍

‍

Why it matters

This is closely related to self-service ratio but measured from a different point, deflection is usually tracked at the moment a customer starts submitting a ticket, showing a suggested article first and counting how often they leave without submitting because it worked. It's a more precise signal than overall self-service usage, since it's tied to a specific intervention rather than general traffic to help content.

‍

‍The failure it can hide

A high deflection rate on paper can hide a real problem if customers are simply giving up rather than getting helped, since both look identical in the data, someone who saw a suggested article and left without submitting a ticket. Teams that take deflection seriously usually follow up with a quick did this solve your issue prompt, rather than trusting the raw deflection number alone.