Quick Answer (TL;DR)
Support Ticket Volume measures number of support tickets per period. The formula is Count of tickets per week/month. Industry benchmarks: Varies. Track this metric when measuring product usability.
What Is Support Ticket Volume?
Number of support tickets per period. Zendesk's annual Customer Experience Trends Report provides industry benchmarks for ticket volume per customer and resolution rates across sectors. This is one of the core metrics in the operational metrics category and is essential for any product team serious about data-driven decision making.
Support Ticket Volume measures the health and efficiency of your product infrastructure and team operations. While not a customer-facing metric, it directly impacts user experience and your team's ability to ship improvements.
Understanding support ticket volume in context, alongside related metrics, gives you a more complete picture than tracking it in isolation. Use it as part of a balanced metrics dashboard.
The Formula
Count of tickets per week/month
How to Calculate It
Aggregate the relevant events over your chosen time period (daily, weekly, or monthly). For example, if you count 12,500 events in a week, your support ticket volume is 12,500 per week. Track this consistently to identify trends.
Benchmarks
Varies
Benchmarks vary significantly by industry, company stage, business model, and customer segment. Use these ranges as starting points and calibrate to your own historical data over 2-3 quarters. Your trend matters more than any absolute number. Consistent improvement is the goal.
When to Track Support Ticket Volume
When measuring product usability. Specifically, prioritize this metric when:
- You are building or reviewing your metrics dashboard and need operational indicators
- Leadership or investors ask about operational performance
- You suspect a change in product, pricing, or go-to-market strategy has affected this area
- You are running experiments that could impact support ticket volume
- You need a quantitative baseline before making a strategic decision
How to Improve
- Automate monitoring and alerting. Do not rely on manual checks. Set up automated alerts that trigger when this metric crosses a threshold so your team can respond immediately.
- Invest in infrastructure and tooling. Operational metrics improve when you invest in better CI/CD pipelines, monitoring tools, and incident response processes.
- Set clear SLAs and track compliance. Define service-level agreements for this metric and hold teams accountable. What gets measured and targeted gets improved.
Common Pitfalls
- Treating this as a standalone number. No metric tells the full story alone. Always analyze this metric in context alongside related metrics to get an accurate picture.
- Setting thresholds too tightly or loosely. Overly sensitive alerts cause alarm fatigue while loose thresholds miss real issues. Calibrate against historical baselines and adjust as the system matures.
- Measuring without acting. Tracking this metric is only valuable if you have a process for reviewing it regularly and a playbook for responding when it moves outside acceptable ranges.
Related Metrics
- Error Rate: percentage of requests that result in errors
- First Response Time: time to first support response
- Page Load Time: time to fully render a page
- Time to Resolution: average time to resolve support tickets
- Product Metrics Cheat Sheet: complete reference of 100+ metrics