What your support tickets really cost
Every ticket carries a dollar figure — your team's time. Here's how that cost is worked out, how much of it is deflectable, and where the savings come from.
How cost per ticket is calculated
Cost per ticket is just your agent's time priced out. Take the average handle time, convert it to hours, and multiply by the fully-loaded hourly cost — salary plus benefits, tooling, and overhead, not just base pay. Multiply by your monthly volume and you have your total support spend.
cost / ticket = (handle min ÷ 60) × $ / hr
What deflection is realistic
Deflection is the share of inbound resolved without a human. An AI agent grounded in your help center routinely takes 30–50% of volume off the queue, with best-in-class teams pushing higher. Here's the whole range — your slider result lands on this same scale.
Low — Most volume still reaches a human. A help center and AI agent have plenty of room to take the repetitive load off your team.
Typical — A solid self-serve baseline. AI grounded in your docs typically pushes this band higher within weeks.
Strong — The band most teams hit with an AI agent answering on top of a well-tended help center.
Best-in-class — Best-in-class. More than half of inbound resolved without a human ever touching it.
Where the savings come from
Deflection doesn't cut what a ticket costs — it cuts how many tickets reach an agent. Every deflected ticket gives back its handle time and its cost. Two levers do the work: an AI agent that answers the repetitive questions instantly, and a help center that catches the rest through self-serve. What's left is the work that actually needs a person.
saved / mo = tickets × (achievable − current)% × cost/ticket
