A support manager is asked whether an improvement is worth making. The fix would remove a recurring category of tickets.
She cannot answer, because nobody has ever calculated what a ticket costs. The conversation happens in general terms, the fix competes against other priorities on instinct, and it does not happen.
The calculation takes an afternoon. Once it exists, the same conversation takes four minutes and reaches a different conclusion.
What a ticket costs is made of
Four components. Direct handling time, the fully loaded cost of the person, the indirect costs around them, and the multiplier from reopens and escalations.
Component 1: handling time
Not just the reply. Reading, researching, writing, following up and closing, which is usually considerably more than the time spent typing.
Component 2: the fully loaded cost
Salary plus employment costs plus tooling plus a share of management, divided by productive hours rather than by contracted hours.
Component 3: the indirect costs
Systems, training, recruitment and the proportion of a manager's time spent on the queue rather than on improvement.
Component 4: the reopen and escalation multiplier
A ticket that reopens costs several times a single exchange, and escalated cases consume senior time at a considerably higher rate.
A worked example on a simple ticket
A few minutes of handling at a modest loaded rate produces a figure most people would consider trivially small.
The same figure across a year of volume
Multiplied by thousands of tickets, the same trivial figure becomes one of the larger operating costs in the department.
Why the average conceals the important part
A small proportion of tickets consume a large share of the total cost, and an average across all of them hides exactly where the money goes.
Why cost per resolution is more useful
Since a fast reply that produces three more exchanges has not resolved anything, and cost per resolution captures that where cost per ticket does not.
Why the number changes decisions
Hiring, automating, fixing a cause and rewriting a confusing page all become comparisons against a figure rather than arguments about priorities.
Why the recurring categories matter most
A category generating known volume monthly has an annual cost, which is the debt described in the cost of answering the same how to question daily.
Why seasonal volume needs separate treatment
Since temporary staff have a different cost profile, which is the ground in seasonal ticket spikes and temporary staff.
Why the customer's time belongs in the calculation
A figure covering only internal cost misses what the interaction cost the customer, which is what actually determines whether they stay, and which no cost per ticket model captures.
Why a falling ticket count can be a bad sign
Customers who stop contacting have sometimes stopped caring rather than stopped needing help, and a volume reduction should always be checked against retention before it is celebrated.
Calculate it once and use it constantly
An assistant handling a share of the volume changes both the ticket count and the mix, which makes the cost per resolution the number worth tracking, and which only becomes visible once somebody has calculated what a ticket costs in the first place. The metric is explained in the cost per conversation metric explained, and the queue dynamics in queue backlogs that never actually clear. See pricing, run the numbers on the chatbot ROI calculator, and the sector view sits under small business.