How to Calculate Cost per Ticket: Formula, Costs and Example

How to calculate cost per ticket: divide your fully loaded support costs by the tickets handled or resolved in the same period. This is the formula for calculating the cost to service a ticket; the result depends on what you include in support costs and how you define a ticket. The result depends on what you include in support costs and how you define a ticket. For software, check whether the fee is per agent, per resolution or usage-based, then add the plan fee and any billable usage to your operating-cost view.

Calculate cost per ticket with a consistent denominator

Use this formula:

Cost per ticket = fully loaded support cost for the period ÷ tickets handled in that period

For a quick check, compare this result with a cost per ticket calculator, using the same cost scope, period and ticket definition.

For cost per resolution, use resolved tickets as the denominator instead. Those are related measures, but they do not answer exactly the same question: handled-ticket cost includes all tickets your team worked on, while cost per resolution counts only the tickets the team resolved.

Before calculating, define what counts as a ticket. A conversation, email thread, phone call or case can each be a unit, but mixing those definitions makes the result hard to interpret. For example, if every resolved chat conversation counts as a ticket in one month but every individual message counts in the next, changes in the result could reflect a counting change rather than a change in support efficiency.

Write down which statuses count. Decide how to treat tickets that are open, pending, abandoned, duplicated, merged, reopened or closed without a confirmed resolution. A stale ticket marked closed can make cost per ticket appear lower without representing a resolved customer problem. If you cannot confidently identify resolved cases, start with tickets handled and label the metric accordingly.

Use the same denominator definition from period to period. If you need both views, report cost per handled ticket and cost per resolved ticket separately. The distinction is useful: the first tells you what the operation spends on its workload, while the second relates spend to completed customer problems. Avoid switching between them in a trend line without clearly marking the change.

Build a fully loaded support-cost numerator

A fully loaded numerator includes the costs of running support, not only frontline agent salaries. Add agent pay and benefits, team leads, quality assurance, management, helpdesk and other tool licenses, and a reasonable allocation of overhead. A salaries-only calculation can understate the cost of providing support.

List costs as separate lines so another person can understand and repeat the calculation. Depending on how your team operates, the list may include training, recruiting, contractors, overtime, outsourced coverage and the cost of covering service hours. Include only costs that belong to support, and use a written allocation rule for shared resources such as office space or company-wide software.

Be consistent about management and shared labor. If a support lead spends part of their time on support operations and part on other work, allocate the support share rather than assigning the entire salary to the ticket calculation. Apply the same logic to shared tools or overhead. Do not include a shared cost once as a direct expense and again inside an overhead allocation.

Keep the scope clear. A support operating-cost metric is not automatically the full business cost of a customer issue. It can exclude customer downtime, lost productivity, replacement products or broader incident impacts. Those may matter for a separate business case, but combining them with support operating costs makes the unit metric answer a different question.

Use one period and reconcile costs to ticket dates

Choose a monthly period and pair monthly support costs with tickets handled or resolved in that same month. A monthly cost table can have one row per cost line and period, with the source of the figure and the allocation method noted. Ticket records should use the helpdesk’s timestamps and the same date boundaries.

This matters when payroll, invoices and ticket activity do not line up neatly. Decide whether costs are recorded when incurred or when paid, then use that convention consistently. For recurring support tools, match the cost to the period the tool served. If a cost covers a longer contract period, document how you spread it across months.

A practical worksheet can include the month, cost category, amount, allocation share, channel, ticket tier or topic, handled count and resolved count. Keep the full support-cost total beside the per-ticket result. That makes it easier to spot whether a changing unit cost comes from a change in spending, ticket volume or case mix.

Compare like with like. If one month includes seasonal coverage or a staffing change, note it before drawing a conclusion from the trend. Compare the same ticket definition, cost scope and time period. For more detailed analysis, segment by channel, tier or topic—but preserve the overall figure so a segment view does not hide the operation’s total spend.

Work a monthly example from payroll to resolved-ticket cost

Here is a simple illustrative calculation using the published ticket-labor example of six hours of IT work priced at £50 an hour. To calculate an average ticket price in this context, divide the support cost by the number of tickets using the same period and definition. The labor cost is six hours × £50 = £300. If that work resolves one ticket, the resolved-ticket cost in this simplified example is £300 ÷ one resolved ticket = £300.

That calculation demonstrates the division; it is not a benchmark or a complete estimate of a support team’s monthly costs. It excludes other costs that a fully loaded calculation should consider, such as benefits, management, tools and allocated overhead. For a real monthly figure, add the relevant costs for the chosen period and divide by the resolved tickets from that same period.

Keep broader business impact separate. A customer or employee may lose time while waiting for an issue to be fixed, but that lost productivity is not the same as the support team’s operating cost. If you need to quantify both, report them as separate measures and explain what each includes. Otherwise, readers may mistake the combined figure for the cost of staffing and operating support.

The example also shows why the denominator needs a plain definition. If the work generated several contacts or follow-ups, decide whether they belong to one case or several tickets before calculating. Keep that rule stable in the next reporting period.

Explain why channel, handling time, and complexity change the result

Cost can differ across channels because some tickets take more staff time than others. When allocating shared support costs by channel, use handle-time share where you have reliable handle-time data. Splitting costs only by ticket count can make a slower channel look cheaper than it is.

For example, a phone case may take more uninterrupted agent time than a chat that can be handled alongside other conversations. The point is not to assume a fixed cost difference; measure your own handling time and staffing mix. If you cannot measure time, a ticket-count allocation is still possible, but label it as an approximation.

Other drivers include wage region, service hours, ticket complexity and the amount of follow-up needed. Coverage outside standard working hours may add scheduling demands or premiums. Tickets that arrive without the information needed to investigate—such as an order identifier, account email or product details—can require more back-and-forth. Structured intake can collect the details your team needs before the conversation reaches an agent.

Track ticket mix when the metric changes. If automation or self-service removes straightforward questions, the remaining tickets may be more complex. Average cost per ticket can rise even while total support spend falls, because the denominator now contains a different mix of work. Report total cost beside the unit figure, then segment by channel, tier or topic before deciding the team has become less efficient.

Compare support software pricing beyond the advertised tier

Software is one part of the numerator, not a substitute for it. Compare the billing model and calculate the likely fee at your actual volume, including peak periods. A plan’s headline price may not show the complete cost if usage, add-ons or implementation are charged separately.

Pricing model	What to include in your estimate	What to check
Per-agent	Base plan fee and the number of paid seats	Which team members need a seat, and whether the fee changes with the team size
Per-resolution	Base plan fee and charges tied to completed resolutions	How “resolved” is defined, and how incorrect classifications or disputed outcomes are handled
Usage-based	Base fee and billable usage at expected volume	When usage counts, how failures and retries are treated, and what happens at peak volume
Flat fee with included usage	Plan fee and whether expected usage fits within its included allowance	What counts as a billable conversation and what happens when usage exceeds the allowance

Do not assume that all vendors count an interaction in the same way. A conversation may count when a human replies, when an AI responds, or under another billable-use rule. Check how each plan treats multiple messages, unanswered messages, repeat contacts and usage beyond the included amount.

Build the monthly software estimate as:

Base subscription + usage charges + overages + add-ons + implementation or integration costs

Use a peak-month scenario as well as a typical-month scenario, especially before agreeing to an annual commitment. Include setup work where it creates real cost for your team, even if it is a one-time expense. If implementation is spread across months for internal reporting, state that method and keep it consistent.

The product uses a flat plan fee with included AI conversations per month, with no per-resolution fee or credit packs. Its helpdesk inbox is included on every plan, and conversations that the AI is not confident about can be handed to the team. Paid plans allow up to 25 AI replies in an AI conversation; Free allows up to 10.

momo plan	Price	Included AI conversations
Free	EUR 0	30 one-time
Starter	EUR 29 monthly or EUR 319 yearly	500 per month
Growth	EUR 129 monthly or EUR 1,419 yearly	2,000 per month
Scale	EUR 399 monthly or EUR 4,389 yearly	6,000 per month

Yearly billing is 11 times the monthly price. Compare the plan fee and included conversation volume with the conversations your team expects to handle; then add the rest of your operating costs to the calculation. For a closer look at AI pricing models, see this guide to AI agent costs.

Review cost with service quality before changing staffing

Pair cost per ticket with service measures such as customer satisfaction, reopen rate, resolution quality and response time. A lower unit cost can be a poor trade if customers need to contact you again, wait longer or receive an incomplete answer. Look at the measures together rather than optimizing the cost figure in isolation.

Investigate abandonment and unusually difficult cases before concluding that a team is inefficient. A high abandon rate can signal that customers are not getting through. A rise in average cost may reflect a shift toward complex work, more follow-ups or a change in channel mix rather than slower handling.

Use internal comparisons by channel, tier and topic. Broad comparisons between companies can be misleading because staffing, wages, operating hours and ticket complexity differ. Your own trend is most useful when the definition and cost allocation remain stable.

When reviewing a proposed change, ask what work it removes and what work remains. A self-service or AI workflow may reduce repeated questions, but the cases that reach a person still need appropriate coverage. Track total spend, resolved volume and quality together so a change does not look successful merely because it changes which tickets reach the team.

Frequently asked questions

Should cost per ticket use tickets received, handled, or resolved?

Use tickets handled when you want the cost of the workload your team worked on. Use tickets resolved when you want cost per completed resolution. Tickets received can be useful for measuring demand, but the number received may not match the number worked or resolved in the period. State which denominator you use and how you treat abandoned, open, duplicated and reopened tickets.

What costs should be included in fully loaded cost per ticket?

Include agent pay and benefits, leads, quality assurance, management, support tools and a consistent allocation of overhead. Add relevant recruiting, training, contractor, overtime, outsourcing and coverage costs. Keep shared costs from being counted twice, and document what is inside the calculation so the result can be reproduced.

How often should I calculate cost per support ticket?

A monthly calculation is a practical way to align costs and ticket activity. If you are asking how much to charge for your services, this support-cost metric can inform your pricing, but it is not by itself a recommended customer price. Keep the same date boundaries and definitions each time, and note unusual staffing or volume changes. Review the trend alongside total support spend and quality measures rather than treating a single month as a verdict.

How do I calculate cost per ticket across chat, email, and phone?

Use handle-time share to allocate shared costs by channel when reliable handling-time data is available. Ticket-count allocation is a simpler fallback, but it can misstate channel costs when tickets take different amounts of staff time. Record the method and use it consistently. If you are comparing the cost per person served, keep that separate from cost per ticket because one customer may create more than one ticket.

How do usage fees and AI resolutions affect software cost per ticket?

Add the base fee and any usage charges, overages or add-ons to the software-cost line. Check the vendor’s billing definition: a conversation, an AI reply and a completed resolution may be counted differently. Then include that software cost in the fully loaded numerator and divide by the handled or resolved tickets that match your chosen definition.

Put the calculation to work

Start with a stable definition, a monthly cost table and a denominator that matches the question you want to answer. If you are evaluating an AI support workflow, try momo free and compare its plan and conversation allowance with your team’s full operating costs.