AI deflection vs. deflection theatre
"Deflection rate" is an easy number to inflate and a hard one to inflate honestly. A bot that answers "I don't understand, please contact our support team" technically deflects — it closes the AI turn of the conversation — while quietly guaranteeing a human has to redo the whole exchange later, now with an irritated customer.
We call this deflection theatre: metrics that look good in a weekly report and feel terrible in the actual chat thread.
What real deflection requires
Grounded answers. An agent that can see your actual SKUs, live stock counts, and order status doesn't have to guess — it can tell a customer their order shipped yesterday instead of reciting a generic "please allow 3-5 business days" that may already be wrong.
Honest escalation. A well-built agent knows what it doesn't know — a price dispute, a damaged-item claim, an angry repeat complaint — and hands those to a human immediately, with full context attached, instead of stalling with reassurances.
Measured by outcome, not by turn count. The metric that matters is: did this conversation need a human within 24 hours after the AI's reply? Not: did the AI send a reply at all.
The tell
If your deflection rate is high but your negative reviews mention "the bot didn't understand me" or "I had to explain everything again," you're running deflection theatre. The fix isn't a better script — it's giving the AI access to the same commerce context a good human agent would use: product catalogue, order history, shipping status, and the actual conversation history, not just the current message.