Ticket volume and contact rate for support teams

Most helpdesks, the ticketing systems support teams keep customer emails in, give it another name. Zendesk and Freshdesk count tickets created, in Zendesk’s Support metrics and Freshdesk’s analytics. Help Scout’s channel report and Intercom count new conversations, and HubSpot’s service reports call it support volume. Call centres say contact volume. A contact there can be a call, a chat or an email.

Volume against the size of your business

A project management app had 800 paying customers in March and received 120 support emails, a contact rate of 15 per 100 customers. April brought 1,000 customers and 140 emails. Volume rose by a sixth while the contact rate fell to 14.

That split is the reason to track both. Gorgias’s guide to ticket volume says raw volume “tells you how busy your team is”. Contact rate shows whether demand is outgrowing the business.

The right divisor depends on what you sell. A shop divides by orders. For subscription software, Decagon’s glossary on contact rate prefers contacts per active user per month, because it adjusts for how much customers use the product.

Merges, follow-ups and spam in the count

Merging two tickets does not always take one off the count. Zendesk’s reports counted both ticket numbers, according to a help article archived in November 2025. Zendesk’s recipe for leaving merged tickets out removes the ones tagged closed_by_merge. Freshdesk counts only the primary ticket. In Intercom’s merging, both conversations keep their own reporting.

A reply after a ticket closes is counted differently too. In Zendesk it opens a new follow-up ticket. Intercom reopens the old conversation, unless you block replies to closed Messenger conversations or set email replies to start a new one after some days. In Gorgias’s billing rules, a reply starts a new ticket after 10 days of silence on email or 3 days on chat. That holds whether the old ticket is open or closed.

Automated mail is kept out in some tools and not others. Zendesk holds out-of-office replies before they become tickets, and deletes tickets marked as spam from its reports. Its workforce planning tool counts spam anyway. Help Scout’s report leaves out spam and deleted conversations.

Help Scout also has a second count. Its total conversations includes every conversation touched in the period, replied to, assigned or closed, so it is larger than the number of new ones.

Pick one rule and keep it. Switching a setting such as Intercom’s reply option changes the count with no change in what customers asked.

Tickets per 100 orders in ecommerce

Gorgias publishes the median number of tickets per 100 orders for its merchants, by type of shop. The figures are for stores in its $10 million sales band with at least 30 tickets, in March 2026, from its Ecom Lab research.

To forecast, multiply your expected orders by your rate. Gorgias’s own example is 2,000 orders at 22 per 100, about 440 tickets. Its guide adds that the rate itself rises in busy seasons such as Black Friday, because first-time buyers ask more.

These rates sit far above the “below 5% per order” that Decagon’s glossary gives as a target for ecommerce, with no source. We found no published figure for tickets per customer in subscription software. Gorgias’s figures were read on 19 September 2026.

How much support ticket volume is growing

Four surveys asked support teams and their leaders about volume. We read them on 19 September 2026.

Survey figures get relabelled when they are repeated. HubSpot’s own customer service statistics post repeats the 75% as customer service reps, although the survey asked leaders.

One data set counts tickets directly. In April 2021, agents on Zendesk handled 30% more tickets than a year before, across the 90,000 companies in its benchmark snapshot. Volume was 20% above its level before the pandemic.

Backlog and cost follow from volume

Backlog is the unsolved tickets at a given moment. Zendesk’s help centre counts every ticket still new, open, pending or on hold, in its guide to support metrics. Plot tickets created against tickets solved, and a backlog grows whenever the first line runs above the second.

The deflection rate is the share of questions answered before they reach your team, so it lowers volume on purpose. Our guide to reducing support tickets starts by counting which questions come up most. Questions a chatbot answers are demand too, though no ticket is opened for them. Deacon keeps a record of each one. Its conversations list shows every chat on your website, answered or handed over.

Multiply volume by cost per contact and you have your support bill.