Ticket volume is the basis for deciding how many agents you need on shift each day. When it grows faster than your team’s capacity, queues build up and customers wait too long.
Adding an FAQ page or a chatbot does not guarantee a lower number. A Gartner survey of more than 5,700 customers found that only 14% of customer service and support issues are fully resolved in self-service.
This article explains what ticket volume is and why it is worth tracking. Later sections cover how to calculate it, why it rises, how to turn it into a staffing plan, and how to reduce it.
What Is Ticket Volume?
Ticket volume is the number of customer support requests logged as tickets during a given period, such as a day, a week, or a month. One ticket represents one issue, no matter how many messages or calls it contains.
For example, five WhatsApp messages from one customer about a package that has not arrived still count as one ticket. That is why ticket volume is usually much lower than the number of messages your team receives.
Some helpdesk tools call this metric support volume or case volume.
What Counts Toward Ticket Volume
Ticket volume counts only new tickets: every request for help opened during the period through email, WhatsApp, phone, live chat, web forms, or social media. Tickets carried over from the previous period do not add to the count, even if your team is still working on them.
Counting rules also differ between systems, since some tools log every chat session as a ticket while others only create tickets from email and web forms. Agree on the following rules so your numbers stay comparable from month to month:
- Log reopened tickets as reopens, not as new tickets.
- Merge one issue sent through two channels, such as an email followed by a WhatsApp message, into a single ticket.
- Exclude spam, auto-replies, and thank-you messages that do not ask for help.
- Separate internal employee requests, such as password resets, from customer tickets if the same team handles both.
Without these rules, ticket volume can rise just because one customer sent the same complaint to three channels. An inflated number like that makes the team look busier than it is and distorts your staffing calculations.
Why You Should Monitor Ticket Volume
You should monitor ticket volume because it is the basis for your customer service budget and the earliest sign that a product or process has a problem. If you operate in a regulated sector, it also determines whether you can meet complaint-handling deadlines.
Budget Planning and Cost per Ticket
Cost per ticket is your total monthly customer service cost divided by that month’s ticket volume. For example, if agent salaries, software licenses, phone charges, and training add up to IDR 120 million for 4,000 tickets, your cost per ticket is IDR 30,000.
This calculation makes budget discussions more concrete. In the example above, preventing 500 repeat tickets a month frees up agent capacity worth about IDR 15 million.
An Early Signal of Product Problems
A sudden spike in tickets almost always has a traceable cause, such as failed payments after an app update or a promotional email with a broken link. Teams that monitor volume by the hour can find the problem the same day instead of waiting for the monthly report.
Protecting SLA Targets and Compliance
When ticket volume exceeds agent capacity, first response times get longer and you start missing service level agreement (SLA) targets. Unresolved tickets then form a backlog that carries over into the next day.
For banks, finance companies, insurers, and fintech firms supervised by Indonesia’s Financial Services Authority (OJK), these delays are also a compliance issue. Under the OJK consumer protection regulation (POJK 22/2023), you must follow up on and resolve a complaint in writing within 10 working days of receiving complete documents.
That deadline can be extended by up to 10 working days in certain conditions. Monitor daily volume so you have time to add agents or reassign work before the deadline passes.
How to Calculate Ticket Volume
To calculate ticket volume, add up the new tickets from all channels within one period, such as a day or a month. The raw total only becomes useful for decisions once you break it down by channel, category, and hour, then compare it with your number of customers.
| Measure | How to calculate | Used for |
|---|---|---|
| Total ticket volume | Number of new tickets in one period | Budgeting and monthly reports |
| Volume by channel | New tickets from each channel, such as email, WhatsApp, phone, and live chat | Deciding which channels need more agents |
| Volume by category | New tickets by issue type, such as payments, shipping, or accounts | Finding the biggest sources of tickets |
| Volume by hour or day | New tickets in each time interval | Building shift schedules |
| Contact rate | (Ticket volume ÷ number of active customers or orders) × 100% | Comparing periods when your number of customers changes |
If you only have time to prepare one extra breakdown, choose volume by category, because it shows which problems need fixing. That breakdown is only reliable if every ticket gets a consistent ticket category from the moment it arrives.
Contact rate is the number of tickets per active customer or per order. Use it while your business is growing, because raw ticket volume almost always rises as you gain customers.
Example: Calculating Ticket Volume and Contact Rate
Suppose an online store receives 3,600 new tickets through email and WhatsApp in March and handles 48,000 orders that month. Its contact rate is 3,600 ÷ 48,000 × 100% = 7.5%, or 7.5 tickets for every 100 orders.
In April, tickets rise to 4,200, but orders also grow to 60,000, so the contact rate falls to 7%. Ticket volume is up about 17%, even though each order now generates fewer tickets.
In this situation, the team needs more agent hours, not an investigation into product problems.
What Causes Ticket Volume to Rise
Ticket volume rises when requests for help increase, either because the business is growing or because of problems that could have been prevented. These are the causes customer service teams run into most often:
- New customers who are still learning the product and often ask about their account, payments, or how to use it.
- Feature releases, app interface changes, or changes to pricing and refund policies.
- Technical problems, such as an app that users cannot open, payments failing at the payment gateway, or packages held up by a logistics partner.
- Seasonal peaks such as Ramadan and Eid al-Fitr (Lebaran), double-date sales like 11.11 and Harbolnas 12.12 (Indonesia’s National Online Shopping Day), paydays, or year-end closing for B2B services.
- Repeat contacts about unresolved issues, when the first answer did not solve the customer’s problem.
- Outdated help pages or FAQs that leave customers unable to find answers on their own.
Separate the causes you can plan for from the ones you can prevent. You can prepare for the Harbolnas spike with extra shifts, while repeat contacts and outdated help pages create volume that should never appear.
How to Use Ticket Volume to Calculate Staffing Needs
You calculate staffing needs by converting ticket volume into hours of work, then dividing those hours by the productive hours of one agent. The basic formula fits in a spreadsheet and takes four steps:
- Multiply ticket volume by average handle time (AHT), the average time an agent actively spends resolving one ticket.
- Calculate productive hours per agent: monthly working hours minus time spent in meetings, training, breaks, and leave.
- Divide the result of step 1 by productive hours per agent, then round up.
- Repeat the calculation by day and by hour to plan shifts for peak times.
Example: Calculating Staffing Needs
The online store from the previous example received 3,600 tickets in March with an AHT of 12 minutes, so its workload was 43,200 minutes, or 720 hours. One agent works 21 days × 8 hours = 168 hours, and assuming 75% of that time is productive, each agent has 126 productive hours.
The store needs 720 ÷ 126 = 5.7 agents, which rounds up to 6. That is the minimum for average volume and does not include a buffer for agents who call in sick or take unplanned leave.
Recalculate for Peak Hours
Monthly averages hide peak hours. If a third of daily tickets arrive between 7 p.m. and 10 p.m., six agents on a 9-to-5 shift will still leave a queue every evening.
For phone and live chat, where customers expect an answer within minutes, teams usually add a queueing model such as Erlang C on top of this formula. The model calculates how many agents you need to meet a service level target, such as the percentage of calls answered within a set number of seconds.
Read also: How to Calculate SLA and Monitor It Effectively to Avoid Missed Deadlines
How to Reduce Ticket Volume
The most effective way to reduce ticket volume is to prevent tickets that should not exist, such as recurring questions and repeat contacts about unresolved issues. Do not target every ticket, because requests that need a judgment call or empathy still belong with an agent.
1. Build Self-Service from Ticket Content
Self-service tools such as FAQ pages, a knowledge base, or a customer portal answer recurring questions without an agent. Rank your ticket categories from the last three months, then write answers to the most common questions in the top ten categories.
Base those answers on what customers actually ask in their tickets, not on your team’s guesses about what they want to know. Place them where customers look before contacting you, such as the order status page and confirmation emails.
An FAQ buried in the site footer rarely gets read, so it does little to reduce tickets.
2. Use a Chatbot for Routine Questions
Chatbots suit routine questions that your systems can answer directly, such as order status, delivery schedules, or how to change a password. Connect the chatbot to order or account data, because a bot that only replies with FAQ links passes the same questions on to your agents.
Offer a quick handoff to an agent when the bot does not understand, and pass along the conversation history so customers do not have to start over. Track the results with ticket deflection rate, the percentage of requests resolved through self-service without an agent.
If ticket volume falls while reopened tickets and social media complaints rise, the bot has only moved the problem somewhere else.
3. Fix the Root Causes in Product and Process
Send monthly volume by category to your product and operations teams, along with the cost of each category. For example, 300 tickets a month about one-time passwords (OTPs) that never arrive, at IDR 30,000 per ticket, cost IDR 9 million a month.
A cost figure like this is easier for the engineering team to prioritize than a general complaint that the queue is busy. After the fix ships, compare that category’s contact rate with the previous month to show that it worked.
4. Send Information Before Customers Ask
Proactive notifications, such as shipping delay alerts or notices of scheduled system maintenance, stop tickets before anyone creates them. A message that arrives first also reduces follow-up questions, because customers already know when the issue is expected to be fixed.
5. Resolve Tickets on First Contact
Every incomplete answer creates a second ticket from the same customer. Give agents access to order data and conversation history so they can solve the problem without asking the customer to get in touch again.
The metric for this is first contact resolution (FCR), the percentage of tickets resolved in a single interaction.
Read also: AI Chatbot vs Human Agent: When to Use Which
Conclusion
Ticket volume only becomes useful once you count it with consistent rules and read it alongside contact rate and category mix. From there, you can turn volume into an agent headcount and a list of the highest-impact product fixes.
A step you can take this week is to agree on ticket counting rules and pull the last three months of data by category. That data is enough to calculate contact rate and staffing needs, and to pick the ten largest categories as your first targets for improvement.
Optimize Your Customer Service
Schedule a demo of Adaptist Prose and see how an integrated ticketing system helps bring tickets, conversations, and customer data together in a single dashboard. With a more structured workflow, teams can respond faster, reduce operational burden, and maintain consistent service quality as the business grows.
FAQ
There is no normal number that applies to every business, because volume depends on your customer count, product complexity, the channels you offer, and the sales season. A more useful benchmark is your own contact rate over the last three to six months.
Count chatbot conversations separately, and add to ticket volume only the ones handed off to an agent or turned into a ticket. That way, you can see how many requests were resolved without an agent and how many still added to the team’s workload.
Multiply your average contact rate by the expected number of active customers or orders next month. Then adjust the result for your promotion calendar, feature releases, price changes, and seasons such as Ramadan or the year-end period that have pushed tickets up in the past.
Not directly, because ticket volume reflects customer demand, not agent ability. To evaluate agents, use resolution time, first contact resolution, the number of reopened tickets, and satisfaction scores per agent, adjusted for ticket complexity.
A monthly report only needs ticket volume compared with last month, contact rate, the five categories with the largest increases, and the actions already taken. Add a forecast for next month’s volume so management can approve extra shifts or budget before the spike arrives.
