Ticket Deflection Rate Calculator
Work out gross and net deflection rate — how many conversations skip a person, and how many come back anyway — plus the monthly cost it actually avoids. Free tool.
Deflection rate gets quoted as one clean percentage, usually the vendor's, usually optimistic. The number that matters to a support lead is smaller: not how many conversations touched a bot or a help article, but how many never needed a person at all — because the ones that bounce back after a failed self-service attempt haven't saved anyone anything, they've just added a step.
Enter conversations per month, how many were resolved without a person, how many of those came back to a person anyway, and what a human-handled conversation costs you. It reports gross deflection — the raw share resolved automatically — and net deflection, the share that actually stayed resolved, alongside how many conversations reached a person either way and the monthly cost avoided by the ones that didn't. Nothing you enter leaves your browser.
Gross = resolved ÷ total. Net removes the ones that came back. Cost avoided = net deflected × cost per human conversation. Nothing you enter leaves your browser.
This ran in your browser on what you typed. The product runs on your actual calls, chats and emails.
Measure your own deflection — start freeWhat each input means
- 01
Conversations per month (all channels)
Chat, phone and email together, whatever your helpdesk or chat platform reports as total conversations for the period. Use resolved-or-closed volume so it lines up with the deflection numbers below.
- 02
Resolved by self-service or an agent without a person
Conversations that ended without reaching a human agent — a help article that answered it, a bot that resolved it, an AI agent that closed it out. Your chat platform or bot analytics usually reports this directly.
- 03
Of those, how many came back to a person anyway (fell through)
Of the conversations you just counted as resolved, how many reopened, restarted as a new ticket, or the customer contacted you again on the same issue within a few days. This is the number vendors' headline deflection rates usually leave out.
- 04
Cost per human-handled conversation ($)
What a conversation costs once a person is involved — agent time plus a share of tooling and overhead. The cost per ticket calculator on this page gives you this figure if you don't already have it.
Questions about this tool
For a team with a maintained help center and a reasonably good bot or agent, 40–60% is a realistic range for genuinely resolved conversations. Above 70% is unusual and worth checking for fall-through before you plan headcount around it — a high gross number with a lot of come-backs isn't the same as a high net number.