Cost per ticket: what support really costs you

Cost per ticket is the closest thing customer support has to a true unit price. Divide what support costs you in a month by the number of tickets you closed, and you get one honest number. Most guides on cost per ticket are written for corporate IT teams with forty agents and a service desk manager. This one is for the shop where one or two people answer everything. Here's the formula, a worked example, what a sensible figure looks like, and why the most popular advice for cutting it usually doesn't work.

What cost per ticket actually means

Cost per ticket is your total support cost for a month divided by the number of tickets you resolved in that month. The formula is the easy part:

Cost per ticket = total monthly support cost ÷ tickets resolved

The arguing happens over the top half. Most people count the software bill, forget everything else, and land on a number that flatters them. A figure you can trust includes:

• Wages for whoever answers tickets, plus payroll taxes and benefits. If someone spends half their week on support, count half their pay.
• Your own hours, priced honestly. This is the line small businesses skip, and it's usually the biggest one on the list.
• Software. Your help desk, your chat widget, anything else in the support stack.
• Anything that only exists because support exists. A phone line, a contractor who covers holidays, the hour a week you spend reading old threads to check the answers were any good.

Leave your own time out and the number is fiction. An owner answering thirty emails on a Sunday is the most expensive support team in the world, because those hours were always going to be worth something else. Price them at whatever an hour of your attention earns elsewhere and the picture gets a lot clearer.

None of this needs a spreadsheet you'll abandon. Twenty minutes with last month's numbers gets you a cost per ticket that's roughly right, and roughly right beats precisely never.

How to calculate cost per ticket for a small team

Take a real month. Not your worst week, not the quiet one in January. Add up the four buckets above, then divide by the tickets you closed. Here's a shop with an owner and one part-timer sharing the queue.

A worked example

• Part-timer, 20 hours a week on support at $21 an hour, plus payroll taxes: about $1,960 a month.
• Owner, 6 hours a week, valued at $50 an hour: about $1,300 a month.
• Help desk software on a flat monthly plan: $39.
• Tickets resolved that month: 180.

That $21 an hour is close to the $20.59 median that federal wage data reports for customer service reps, so it's a fair starting point if you're guessing.

Total support cost lands at roughly $3,300. Divide by 180 and your cost per ticket is about $18.

Now look at what that $18 is made of. Wages and owner time are about 99% of it. The software is the other 1%, around 22 cents a ticket. Hold on to that number, because it changes what you should do next.

Cost per ticket vs cost per contact

One trap before you divide: decide what counts as a ticket. If a customer emails, you reply, they email back, and you close it, is that one ticket or three? The service desk world separates cost per contact, which counts every individual interaction, from cost per ticket, which counts the whole issue from open to resolved.

For a small business, count resolved issues. That's the unit your customer experiences and the one your calendar feels. Counting every reply as its own ticket makes your cost per ticket look wonderful while your afternoon disappears.

Whichever you pick, pick it once and stick to it. A cost per ticket you measured one way in March and another way in June isn't a trend, it's noise.

What's a good cost per ticket for a small business?

Nobody has a trustworthy answer, and you should be a little suspicious of anyone who offers one with a straight face.

The benchmarks that get quoted everywhere come from corporate IT. Published benchmarking data from the service desk industry put North American desktop support at an average of $62 a ticket, with a range running from $27 all the way to $490. Those figures are from 2010, and they describe technicians who walk across an office to fix somebody's laptop. It's the wrong yardstick for a business where the owner answers the phone.

The wide range is the useful bit. When the same metric spans $27 to $490 inside one industry, an average isn't telling you much. Ticket mix drives the number more than efficiency does. A queue full of quick questions and a queue full of angry refunds produce very different figures from equally good teams.

So compare yourself to yourself. Work out cost per ticket three months running and read the trend. Rising while volume holds flat means tickets are getting harder or slower. Falling while volume holds flat means something you changed is working. That's worth more than any industry average you'll find.

Why cutting tickets doesn't lower cost per ticket

Here's the part most articles get wrong, and it catches people out.

Go back to the shop above. Say a decent help center and a support bot start handling the routine "where's my order" and "how do I reset my password" questions. Volume drops from 180 tickets to 135. The part-timer goes from 20 hours a week to 15. Total support cost falls to about $2,400.

That's $900 a month back in your pocket, about 27% off the bill. And the cost per ticket? Roughly $18. Exactly where it started.

The reason is simple once you see it. You removed the cheapest tickets. What's left is the refund dispute and the order that arrived broken, and those were always the expensive ones. Plenty of teams watch their cost per ticket sit still after automation, or even climb, and conclude the whole thing failed. Their bill is smaller and their queue is healthier. The unit price just can't see that.

Which is the real lesson: cost per ticket is a ratio, and ratios hide the thing you actually care about. Nobody pays a cost per ticket at the end of the month. They pay a total.

Four ways to lower cost per ticket

If you want the unit price itself to come down, only a few things move it, and every one of them is really about time.

1. Write the answer down once

The same eight questions produce most of your queue. Every time you type that answer fresh, you're paying full price for work you already did. A short help center article, linked from the reply, turns a ten-minute answer into a thirty-second one. The bot can serve those same articles around the clock, on every plan, with no fee per answer. Our guide on how to reduce customer support tickets walks through finding the repeat offenders.

2. Fix the cause, not the ticket

If forty people a month ask where their order is, the answer isn't a better reply. It's a shipping confirmation email that says where the order is. Support tickets are often a bug report about the rest of the business. The cheapest ticket is one that never gets written.

3. Keep what you can in writing

A phone call is one person, one problem, start to finish. Email and chat let one person work several threads and reuse text they've already written. Phone is the right tool for a furious customer or a genuinely tangled problem. For everything else it's the priciest way you own to say "yes, it shipped Tuesday."

4. Look at the software line last

Switching help desks to save $20 a month moves a $18 cost per ticket by about a penny. It's the smallest lever on the board. What does matter is whether that line stays still. Per-seat pricing that jumps when you add a part-timer, or per-resolution fees charged every time an automated answer fires, put your software bill on the same upward curve as your volume, which is the one curve you were trying to flatten. SupportifyGPT uses flat monthly pricing with every feature on every plan and no per-resolution fees, so the software line holds steady while you work on the parts that matter. If you want the fuller breakdown, we've written about what support software really costs.

The numbers to keep next to it

Cost per ticket on its own is a trap. Track three things together, once a month:

• Total support cost. What you actually spent.
• Tickets resolved. Whether the work is growing.
• Cost per ticket. Whether each one is getting harder.

Read any one of them without the other two and you'll fix the wrong thing. A rising cost per ticket with a falling total bill is a team doing well. A flat cost per ticket with a climbing total is a business growing into a problem. There are a few other support metrics worth tracking, but those three answer the money question on their own.

Work yours out this month. It takes twenty minutes and a calculator, and you can try the whole thing free for 14 days if you want the ticket count handed to you instead of counted by hand. Most owners are surprised by the result. Almost none of them are surprised by the software bill.