Core metrics

What is ticket volume?

Also known as: contact volume

Published September 10, 2026 · Reviewed by the Fidiora team

Definition

Ticket volume is the number of support requests received in a period. On its own it says little, because volume tracks customer count, product changes, and seasonality. It becomes useful when normalised, most commonly as tickets per hundred customers or per thousand active users.

Why it matters

Raw ticket volume is the number executives ask about and the number least worth targeting. A growing company should expect growing volume. What matters is whether volume per customer is falling, which is the only version of the metric that reflects product and documentation quality.

What to know

  • Normalise by active customers or usage, or growth will look like a support failure.
  • Volume by topic is where the actionable signal lives, and it requires tagging discipline to exist at all.
  • Spikes usually trace to a release, an outage, an email campaign, or a billing run, and all four are predictable.
  • Contacts per customer falling while total volume rises is the signature of a healthy scaling support function.
  • Volume reduction targets can be met by making it harder to contact you, which is why satisfaction must be watched alongside.

How to calculate it

Contact rate = tickets in period / active customers in period

An example

Example: volume rises thirty percent year on year and the executive team panics. Customer count rose forty percent, so contacts per customer actually fell. The support function got more efficient and the headline number implied the opposite.

Common mistakes

  • Targeting raw volume reduction without normalising for growth
  • Reducing volume by hiding contact options
  • Reporting total volume without topic breakdown
  • Treating a predictable seasonal spike as an anomaly every year
Where Fidiora fits

Fidiora reduces the volume that reaches humans without reducing the volume customers are allowed to send. Customers can always ask, and the routine share never becomes a ticket, which is the version of volume reduction that does not hurt anyone.

See Pricing
FAQ

Questions

What is a good ticket volume?
The question only works normalised. Track contacts per hundred customers and watch the trend. A falling contact rate with stable satisfaction is the goal, and the absolute number is meaningless across companies.
How do I reduce ticket volume?
Fix the product moments that generate contacts, document the top recurring questions properly, and resolve the repetitive share automatically. Do not reduce volume by making support hard to reach.
Why does ticket volume spike?
Releases, outages, billing runs, marketing campaigns, and seasonality account for most spikes. All are foreseeable, which means most spike pain is a planning failure rather than a surprise.
Get Started

See Fidiora resolve a ticket in 60 seconds.

No credit card, no sales call required. Connect your docs and watch it work.

No credit card · Live in under an hour