What deflection actually measures
Deflection rate is the share of questions that live chat resolves before they become something heavier — a phone call, an email thread, a formal ticket, or a lost customer. It is a proxy for how much cheaper, faster work chat is absorbing. Like any proxy, it is useful right up until you start gaming it, so define it carefully before you celebrate it.
Define it honestly
The honest version counts a chat as deflected only if the customer's issue was actually resolved in chat and did not resurface through another channel. The dishonest version counts every chat that did not immediately become a ticket — which quietly includes the frustrated customer who gave up and churned. If your deflection rate and your re-contact rate both look great, trust it; if deflection rises while re-contacts also rise, you are not deflecting, you are deferring.
What pushes it up the right way
- Answers that actually resolve: a chat that ends with a working solution, not a “that should do it.”
- Good self-serve behind it: agents who link the right help article turn one deflection into many.
- Fast enough response: people escalate to phone or email when chat is too slow; speed keeps them in the cheaper channel.
A high number is only good if satisfaction holds
Deflection is a cost metric, and cost metrics are dangerous alone because the cheapest possible support is no support. A rising deflection rate paired with falling CSAT means you are pushing people away, not helping them. Always read deflection next to a satisfaction signal; the pair tells the truth that either one alone will hide.
How MyLiveChat helps you measure it
MyLiveChat's transcripts, tags, and reporting let you mark how chats resolved and spot the ones that came back, and its post-chat ratings give you the satisfaction signal to read alongside. That combination is what lets you claim a deflection number you can actually defend — resolved and satisfied, not just “didn't open a ticket.”