The real cost of a support ticket, and how to calculate yours

A number most teams have never actually calculated

Ask a founder how much a support ticket costs and you'll usually get a shrug, or a number pulled from a blog post that has nothing to do with their business. It's a knowable figure, and it's worth working out before deciding whether adding a person, a tool, or an AI agent is the right next move.

The simple version

Cost per ticket is your fully loaded support cost divided by ticket volume for the same period. Two agents making $3,500 a month each, handling 900 tickets between them, comes to $7,000 divided by 900, or about $7.78 a ticket. You can run your own numbers through the support cost calculator instead of doing the arithmetic by hand.

That number gets more useful once you break it down by ticket type, since a password reset and a billing dispute don't cost the same to resolve even though they're both "one ticket" in most reporting.

What the number is actually for

Cost per ticket isn't interesting on its own. It's interesting as a baseline you compare against a change. If an AI agent could resolve a third of your volume without a human touching it, and you already know your cost per ticket is $7.78, you've got a real figure to weigh against whatever that tool costs, instead of a vague sense that automation probably helps.

The AI chatbot savings calculator runs on exactly this logic: current cost per ticket, times an estimated deflection rate, minus whatever the tool costs, to get a number you can bring to an actual budget conversation instead of a hunch.

Most support costs stay invisible because nobody adds up the pieces. Ten minutes with real numbers is usually enough to know whether a change is worth making.