Founder's note
What I'd do with these numbers
If cost per ticket is rising, or well above similar teams:
Three likely causes
- Ticket volume that could be avoided: unclear product screens, missing self-service answers.
- Low occupancy: the team is staffed for peaks it rarely meets.
- Expensive channels (phone) carrying simple questions that chat or help articles could handle.
What to check next
- Sort contact reasons by volume and ask which ones a better help article would remove.
- Compare staffing with hourly volume to find the over-staffed hours.
- Split the cost per channel, not only the average.
One thing to do this week
Write or fix the help article for your single most frequent contact reason and link it where customers get stuck.
What cost per ticket tells you
Cost per ticket = total monthly support cost ÷ tickets handled that month: the fully loaded cost of solving one customer request. It turns the support budget into a unit cost, so you can compare months, channels and teams, and price the effect of a change such as self-service or a new tool.
The cost per ticket formula
Cost per ticket = total support cost for the month ÷ tickets handled in the same month. The hard part is not the division but deciding what goes into the cost.
| Include | Examples |
|---|---|
| People | Agent salaries, benefits, payroll taxes, bonuses, overtime |
| Leadership and quality | Team leads, QA, workforce planning, trainers (their share of time) |
| Tools | Helpdesk, telephony, chat, knowledge base, QA and WFM software |
| Outsourcing | BPO invoices for the tickets they handle |
| Overhead | Office or remote-work allowance, equipment, a share of IT |
Where the money usually goes
- People 70%
- Leads and QA 10%
- Software 10%
- Overhead 10%
People are most of the cost in nearly every team, which is why fewer contacts saves more than cheaper tools.
Worked example
A team of 10 agents costs $4,000 each a month with benefits, so $40,000 in total, plus $5,000 of software and $5,000 of overhead, and handles 4,000 tickets. Total cost is $50,000, so cost per ticket is $50,000 ÷ 4,000 = $12.50, and each agent handles 400 tickets a month. Enter 10, 4,000, 5,000, 5,000 and 4,000 in the calculator to see the same result.
If the same team deflects 600 tickets to the help center without adding cost, the next month costs $50,000 ÷ 3,400 = $14.71 per ticket. The total spend did not move, but the unit cost went up. That is why cost per ticket must be read together with volume and total cost.
Cost per ticket benchmarks
| Type of support | Typical range per ticket |
|---|---|
| E-commerce, simple order questions | $3–$10 |
| B2C software and apps | $8–$20 |
| B2B SaaS, product questions | $15–$40 |
| Technical or enterprise support | $40–$100+ |
| Phone support, any industry | Often 1.5–2× the same team's email cost |
Rough ranges from public industry reports; your own trend matters more than any benchmark.
Cost per ticket by channel
Calculate the cost per channel when the same team works on several: split agent time by channel using the helpdesk's handle-time report, then divide each channel's share of the cost by its tickets. Phone is usually the most expensive per contact, chat sits in the middle because agents handle conversations in parallel, and self-service costs very little per issue once the content is written.
Use this split before moving customers to a cheaper channel. If chat costs half as much as phone but customers need two chats to solve what one call solved, the saving disappears.
Common mistakes
- Counting only agent salaries. That can halve the real cost and makes outsourcing look more expensive than it is.
- Dividing by tickets created instead of tickets handled in the same month.
- Comparing channels without the same cost base: chat agents often handle several conversations at once.
- Cutting cost per ticket by closing tickets faster. Reopens and repeat contacts bring the cost back next month.
How to lower cost per ticket without hurting CSAT
- Remove the reasons for contact first: unclear emails, missing order status, known bugs. Fewer tickets is the biggest saving.
- Answer the ten most frequent questions in the help center and inside the product.
- Improve first contact resolution: every reopened ticket is paid twice.
- Route by skill so complex cases do not bounce between agents.
- Use macros and AI drafts for repeated answers, with a human check on tone and facts.
How often to report cost per ticket
Report it monthly, next to total support cost, ticket volume and CSAT. A falling cost per ticket with rising total cost means volume grows faster than efficiency. A rising cost per ticket with falling volume can be good news, if the drop came from removing contact reasons.
Cost per ticket formula in Excel or Google Sheets
Put the inputs in column B from row 2, then paste the formulas below. They work the same in Excel and Google Sheets.
| Cell | What | Value or formula | Example |
|---|---|---|---|
| B2 | Salaries and benefits (month) | 40000 | 40000 |
| B3 | Software and tools (month) | 5000 | 5000 |
| B4 | Other overhead (month) | 5000 | 5000 |
| B5 | Tickets handled (month) | 4000 | 4000 |
| B7 | Total support cost | =B2+B3+B4 | 50000 |
| B8 | Cost per ticket | =ROUND(B7/B5,2) | 12.5 |
Get the ready-made spreadsheet
The same calculator as an .xlsx file, with the formulas set up. Free: enter your email and the download starts here right away. Your email also joins Clarivoxx Insights (a weekly article and a monthly newsletter; unsubscribe in one click).
Go further with the ebook
The Professional Customer Support Playbook
Better replies, fewer escalations, a clear path from agent to leader.
$19.99 · 103 pages · View the book
Frequently asked questions
- How do you calculate cost per ticket?
- Add up everything support costs in a month: agent salaries with taxes and benefits, software such as the help desk, and allocated overhead. Divide by the number of tickets handled that month. 10 agents at $4,000, $2,000 of tools and 5,000 tickets give $8.40 per ticket.
- What is a normal cost per ticket?
- It varies widely by channel and complexity: simple B2C email or chat tickets can cost a few dollars, while technical B2B tickets often cost $15–$50 or more. Track your own trend and compare channels inside your team.
- How does ticket deflection lower support costs?
- Every ticket solved by a help center article, chatbot or in-product guidance is one your agents do not handle. Savings = deflected tickets × cost per ticket, as long as the self-service answer actually solves the problem.
- What should be included in cost per ticket?
- Include every monthly cost of the support function: salaries, benefits and payroll taxes, team leads and QA, helpdesk and telephony software, training, outsourcing fees and a share of office or equipment costs. Divide by tickets handled in the same month.
- Is there a cost per ticket formula template?
- Yes. The Excel version below has salaries, software and other overhead as inputs and the formula =ROUND((B2+B3+B4)/B5,2). It opens in Excel and Google Sheets, so you can track the number month by month.
- What is the difference between cost per ticket and cost per contact?
- Cost per ticket divides support cost by issues handled; cost per contact divides it by every call, chat and email, and one ticket often needs several contacts. $42,000 over 5,000 tickets is $8.40 per ticket, but if those tickets took 7,000 contacts, cost per contact is $6.00. Use the same one every month so the trend stays comparable.
- How do you calculate cost per ticket for an IT service desk?
- Use the same formula, but split it by support level. Level 1 tickets solved at the first line usually cost far less than tickets escalated to level 2 or 3, where more expensive specialists spend time on them. Divide each level's share of staff and tool cost by the tickets it worked on, and track how many tickets you resolve at level 1.
About the author
Abdessamad Ghanem
Customer Experience & Customer Success Consultant · Founder of Clarivoxx
Abdessamad Ghanem works across Customer Support, Sales, Customer Success, Account Management and Partner Management. He writes Clarivoxx Insights for B2B SaaS professionals who own retention, adoption and customer outcomes.