Support ticket volume and how to measure it

To measure it, count the new requests customers opened with you in a week or a month, across every channel, and count each one once however many messages it took. If customers started 90 email threads and 30 chats with you in March, your ticket volume for March was 120.

Helpdesks name it after their own unit. Zendesk counts tickets created, Help Scout counts new conversations, and call centres say contact volume, since a contact there can be a call, a chat or an email.

For a founder answering support alone, ticket volume is how often your inbox pulls you away from building. Deacon is an AI customer support agent that answers your customers’ questions on your site in seconds, from your own docs, so fewer of them reach your inbox, and it has a free plan.

How to measure ticket volume

As Gorgias’s guide to ticket volume puts it, raw volume “tells you how busy your team is”. The contact rate beside it shows whether demand is growing faster than the business.

A project management app had 400 paying customers in May and received 80 support requests, a contact rate of 20 per 100 customers. By September it had 600 customers and 96 requests. Volume rose by a fifth, while the contact rate fell to 16, so each customer needed help less often.

Divide by whatever fits what you sell. A shop divides by orders. For subscription software, Decagon’s glossary prefers contacts per active user per month, because it evens out how much each customer uses the product.

Rules that change the count

Two teams with the same customers can report different volumes, because ticketing systems split and count requests in different ways. These are the rules in three of them, read on 23 September 2026.

A reply to a closed ticket can count again. In Zendesk, any reply to a closed ticket creates a follow-up ticket, a new ticket with its own number. Gorgias starts a new ticket when an email arrives more than 10 days after the last message, or a chat message more than 3 days after, whether the old ticket is open or closed.

New and touched are different counts. Help Scout’s report gives new conversations, the ones customers or your team created, and total conversations, every one created, replied to, assigned or otherwise changed in the period. The second is always at least as big as the first.

Spam and deleted requests drop out. Help Scout leaves spam and deleted conversations out of that report, and Zendesk leaves deleted tickets out of its tickets dataset.

Choose one rule and keep it. A change of setting or tool can move your volume with no change in what customers asked.

How fast ticket volume is growing

Most published figures are surveys of support leaders, and every one below finds volume rising. These are the ones we found with a named sample, read on 23 September 2026.

McKinsey’s leaders put the growth down to more contacts per customer as well as more customers. That’s why the contact rate matters. Volume that grows with your customer base is growth, and volume that grows faster than it is a problem to find.

Tickets per 100 orders in ecommerce

Online shops have the one contact rate benchmark we found with a named sample. Gorgias publishes medians from its own merchants, and its March 2026 figures, for stores with about $10 million in sales and at least 30 tickets, run from 19.4 tickets per 100 orders for toys and games to 46.3 for electronics. These are eight of the 14 kinds of shop it lists.

Gorgias says a high rate isn’t good or bad. It reflects how complex the product is and how much buyers need to ask, so compare yourself with shops of your own kind. Its guide forecasts volume by multiplying expected orders by the rate, so 2,000 orders at 22 per 100 means about 440 tickets. It adds that the rate rises in busy seasons such as Black Friday, because first-time buyers ask more.

Decagon’s glossary says shops typically aim for below 5% per order, with no source. We found no published contact rate for subscription software with a named sample.

Ticket volume vs contact rate, backlog, deflection and cost per contact

Ticket volume feeds most of the other support measures.

To bring volume down, start with the questions that come up most. Our guide to reducing support tickets shows how to count them and fix each one where it starts.

Fewer tickets reaching you, with Deacon

Much of a founder’s ticket volume is the same few questions, asked again by each new customer. Deacon answers them on your site in seconds, at any hour and in the visitor’s own language, from your own docs. When your docs don’t cover a question, it says it doesn’t know instead of guessing and asks for the visitor’s email, so the questions that reach you are the ones that need you.

It gets better the more you answer. A question your docs didn’t cover shows up in Conversations with an Answer this button, and what you write there becomes a source Deacon answers from, so it can take that question the next time a customer asks. Fewer repeats land in your inbox, and it needs you less.

The questions Deacon answers are demand too, even though nobody opens a ticket for them. Every conversation is saved in Conversations, searchable by what visitors asked. Analytics › Widget counts messages and people over the last 7, 30 or 90 days or all time, with the change on each, shows the languages people wrote in, and names the page where people get stuck once one stands out. Topics cluster similar questions, count the people behind each cluster and label most of them, for example as a how-to, a bug report or a feature ask. You see what’s behind the questions, and what customers want you to build next.

Deacon can’t see your inbox, so it doesn’t report your ticket volume. Put its conversations beside the emails you received and you see how much of the demand now reaches Deacon first. FAQ chatbot shows how it learns a question it missed, and you can try it on the free plan, which needs no card.