Cost per Ticket: How to Calculate It and Lower It

Cost per ticket is the average amount your support team spends to handle one customer request. The formula is total monthly support cost ÷ tickets handled that month. A team of 10 agents costing $4,000 each, with $2,000 of tools and 5,000 tickets a month, spends $42,000 ÷ 5,000 = $8.40 per ticket.

Want your own number in 30 seconds? Use the free Cost per Ticket Calculator: enter your team, costs and volume, and it also shows what self-service would save you.

The rest of this guide covers what belongs in the cost, how to read the result, and how to lower it without making customers pay for it.

The cost per ticket formula

Cost per ticket = (agent costs + support tools + allocated overhead) ÷ tickets handled in the same period

Two rules keep the number honest:

• Use the same period for cost and volume. Monthly works best: salaries and licences are monthly, and ticket volume moves with seasons.
• Count tickets the same way every month. Pick tickets resolved (or handled) and stick to it. Switching between created and resolved tickets changes the result more than most improvements do.

What to include in total support cost

Most teams underestimate cost per ticket because they only count salaries.

Include	Examples	Often forgotten
Agent cost (fully loaded)	Salary, employer taxes, benefits, bonuses	Team leads and QA reviewers who also work the queue
Support tools	Help desk, live chat, telephony, knowledge base	QA, workforce management and AI add-on licences
Allocated overhead	Equipment, office or remote-work stipends, training	Onboarding time for new hires

If you are unsure about overhead, start with agents and tools only. Say which method you used so the number can be compared month to month.

A worked example

Step	Calculation	Result
Agent cost	10 agents × $4,000	$40,000
Tools	Help desk, chat, knowledge base	$2,000
Total monthly cost	$40,000 + $2,000	$42,000
Tickets handled	Monthly volume	5,000
Cost per ticket	$42,000 ÷ 5,000	$8.40
Tickets per agent	5,000 ÷ 10	500 a month

These are the default numbers in the calculator, so you can change one value at a time and watch the effect.

How to read your cost per ticket

The number means little on its own. Three comparisons make it useful:

• Your trend. A rising cost per ticket with flat volume usually means tickets are getting more complex, or handle time is creeping up.
• By channel. Phone is usually the most expensive per contact, then chat, then email and self-service. Calculate each channel separately if you can.
• By tier or product. A technical B2B ticket can easily cost several times a simple password reset. Averages hide where the money actually goes.

Published benchmarks vary widely: simple B2C chat or email tickets can cost a few dollars, while technical B2B tickets often cost $15–$50 or more. Treat outside figures as a sanity check, not a target.

Five ways to lower cost per ticket without hurting CSAT

Cutting cost per ticket by rushing agents is easy, and it usually backfires: customers come back, ticket volume grows and CSAT drops. These five levers lower cost by removing work instead.

1. Fix the top contact drivers. Tag every ticket by reason. The top five reasons usually make up a large share of volume, and many of them come from product bugs, confusing billing or missing notifications. Fixing a cause removes those tickets for good.
2. Deflect repetitive questions to self-service. A help center article, in-app guide or chatbot that really answers "how do I…" questions takes tickets out of the queue entirely.
3. Raise first-contact resolution. Every reopened or escalated ticket is paid for twice. Better macros, clear escalation rules and access to account data let agents solve more on the first reply.
4. Route tickets to the right person first. Skills-based routing avoids transfers between agents and teams, which add handle time without adding value.
5. Staff to demand, not to averages. Too few agents at peak creates backlogs and repeat contacts; too many during quiet hours raises cost. The Erlang C staffing calculator shows how many agents each hour really needs.

What self-service is worth: a quick example

Deflection savings = deflected tickets × cost per ticket.

With the example above, deflecting 15% of 5,000 tickets means 750 fewer tickets a month. At $8.40 each, that is $6,300 a month, or about $75,600 a year. That is often enough to justify a knowledge-base project, a chatbot or a support operations hire.

Only count a ticket as deflected if the customer's problem was actually solved. If people read the article and then open a ticket anyway, you added a step without saving anything.

Five mistakes that distort cost per ticket

• Counting only salaries. Leaving out taxes, benefits and tools makes the number look much better than it is.
• Mixing channels. One blended number hides an expensive phone queue behind cheap email tickets.
• Ignoring reopened tickets. If a reopened ticket counts as new, cost per ticket falls while customers wait longer.
• Chasing the number down alone. Track it next to CSAT, first-contact resolution and backlog. If cost falls while CSAT drops, you have moved the cost to your customers.
• Changing the method mid-year. Write down what goes into the cost and which tickets count, so every month is comparable.

Calculate yours now

1. Open the Cost per Ticket Calculator.
2. Enter your number of agents, fully loaded cost per agent and monthly tool costs.
3. Add your monthly ticket volume.
4. Try a deflection rate of 10–20% to see what self-service would be worth.

Then put the result next to your quality metrics. The CSAT calculator and NPS calculator show whether savings are coming at your customers' expense. For more free tools, see all customer support, success and experience calculators.