CONVIRO
Customer Support

How to Calculate Cost per Ticket (and What It Tells You)

Cost per ticket is total support cost divided by tickets handled. The formula is easy; getting the inputs right is not. A worked example, a per-channel view and common traps.

Conviro
October 4, 20266 min read
How to Calculate Cost per Ticket (and What It Tells You)
In this article

Cost per ticket is your total customer support cost for a period divided by the number of tickets your team handled in that period. If support costs €18,000 a month and you handle 3,000 tickets, your cost per ticket is €6.

The formula takes one line. The hard part is deciding what goes into "total cost," what counts as a ticket, and how to read the number once automation starts answering some of the questions. Get those wrong and you'll make staffing decisions based on a figure that looks precise but isn't.

Here's how to calculate it properly, break it down by channel, and avoid the traps.

Key takeaways

  • Use fully loaded costs: salaries plus employer costs, tools, training and a share of overhead.
  • An average across all tickets hides big differences between channels and ticket types. Segment it.
  • When automation removes simple tickets, human cost per ticket can rise even as total cost falls. Track cost per contact as well.

The cost per ticket formula

The basic formula:

Cost per ticket = fully loaded support cost ÷ tickets handled

"Fully loaded" means everything it takes to run support for that period:

  • People: salaries, employer taxes and benefits for agents, plus the share of team leads' and managers' time spent on support
  • Tools: help desk, chat and messaging software, AI tools, telephony if you use it, add-ons
  • Training and quality: onboarding new agents, coaching, QA reviews
  • Overhead share: equipment, workspace, a fair slice of IT and HR costs
  • Outsourcing: any external agency or overflow team

For the denominator, pick one definition and stick to it. Most teams count tickets that were handled and closed in the period, exclude spam, and count a reopened ticket once.

A worked example (hypothetical numbers)

Imagine an online store with four support agents and a team lead who spends half their time on support. The numbers below are purely illustrative.

Cost item Monthly cost
4 agents, fully loaded (€3,500 each) €14,000
Team lead, 50% of time €2,500
Software and tools €600
Training, QA and overhead share €900
Total €18,000

The team handled 3,000 tickets this month, so:

€18,000 ÷ 3,000 = €6.00 per ticket

On its own, €6 means little. It becomes useful when you track it monthly, compare channels and ticket types, and see how it moves after changes.

Customer support cost per ticket by channel

Channels differ in how long each ticket takes. A simple way to split cost is by total handle time. Continuing the hypothetical example:

Channel Tickets Avg. handle time Share of handle time Cost per ticket
Email 1,200 9 min 53% €7.94
Website chat 900 6 min 26% €5.29
WhatsApp 600 5 min 15% €4.41
Instagram DM 300 4 min 6% €3.53

Total handle time is 20,400 minutes, so each minute costs about €0.88 (€18,000 ÷ 20,400). Multiply by each channel's average handle time to get its cost per ticket.

This view often surprises teams. Email may look "cheap" because it's asynchronous, yet long threads and back-and-forth make it the most expensive channel per ticket. Do the same split by ticket type (order status, returns, product questions, complaints) and you'll quickly see where the money goes.

Common mistakes that distort the number

  1. Counting salaries only. Leaving out tools, training and overhead can make support look far cheaper than it is.
  2. Mixing simple and complex tickets. One average blends 30-second order checks with hour-long damage claims. Segment by type.
  3. Inconsistent ticket counting. Merged tickets, reopened threads and spam all change the denominator.
  4. Optimizing cost alone. Rushing agents lowers cost per ticket and raises repeat contacts. Watch CSAT and first response time alongside it.
  5. Comparing with other companies. Different definitions make outside comparisons close to meaningless. Compare yourself with last quarter.

How automation and self-service change cost per ticket

This is where many teams misread their own data.

When an AI assistant or help center resolves routine questions, those contacts never reach an agent. The tickets that remain are the harder ones: complaints, exceptions, multi-step problems. So human cost per ticket often goes up, even though the business is spending less per customer helped.

That's why it helps to track a second number:

Cost per contact = total support cost (including AI and self-service tools) ÷ all customer contacts, however they were resolved

Continuing the example: say next year contacts grow from 3,000 to 4,000 a month. Without automation, you'd likely hire a fifth agent, bringing costs to €21,500, or €5.38 per contact. If an AI assistant absorbs the growth in routine questions and the team stays the same size, costs rise only by the tool's fee. With an illustrative €300 a month, that's €18,300 ÷ 4,000, or about €4.58 per contact. The bigger win is often capacity: your team has time for the conversations that need people.

Self-service follows the same logic. Our guide to self-service customer support covers what to automate first.

What cost per ticket tells you (and what it doesn't)

It tells you how efficiently your support operation turns money into handled requests, and how that changes over time. It doesn't tell you whether customers were helped, whether answers were right, or whether a cheap ticket led to an expensive repeat contact. Read it next to resolution rate, CSAT and repeat contact rate, as described in our chatbot analytics guide.

With Conviro, AI Assistants answer routine questions from your knowledge base across website chat, WhatsApp and Instagram, while the Live Inbox keeps the remaining conversations in one place with full context, so agents spend their time on tickets that need judgment.

Frequently Asked Questions

What is a good cost per ticket?

There's no reliable universal benchmark, because companies calculate it differently and handle very different ticket mixes. A store answering order-status questions and a software company handling technical issues will never be comparable. The useful benchmark is your own trend: track it monthly with a consistent formula and look for steady improvement without falling satisfaction.

What's the difference between cost per ticket and cost per contact?

Cost per ticket usually covers requests handled by your team. Cost per contact divides total support spend, including AI and self-service tools, by every customer contact, however it was resolved. Once automation answers routine questions, cost per contact gives a fairer picture of efficiency than cost per ticket alone.

Should cost per ticket include software costs?

Yes. Help desk, chat, messaging and AI tools are part of what it costs to support customers, and leaving them out understates the real figure. Include subscriptions, add-ons and usage fees, such as Meta's charges for WhatsApp template messages, and spread annual payments evenly across the months they cover.

Next steps

Pull last month's costs and ticket counts, calculate a fully loaded cost per ticket, and split it by channel and ticket type. That breakdown shows which questions are worth automating first. When you're ready to test that on your own conversations, get started with Conviro for free.

Share:

Published by

Conviro

Sharing insights on AI-powered customer support, chatbot automation, and SaaS growth strategies.

Plan with current numbers

Compare plans against your real support volume

Use the live pricing page as the source of truth, then model automation with your own ticket mix and escalation rate.

Related articles

More Posts