Volume is a symptom, not a constant
Most teams treat ticket volume as a fixed input they have to staff against. It isn't. Volume is downstream of product friction, unclear docs, and gaps in self-service. Reduce the causes and the queue shrinks on its own.
Find the repeat offenders
Pull your last 90 days of tickets and tag them by root cause. In almost every team, 20% of issue types drive 60% of volume. Those are your targets — not the long tail of one-off questions.
The nine tactics
- Fix the top-5 deflectable issues at the source. A password-reset flow that confuses users generates hundreds of tickets a month. Fix the flow, not the queue.
- Write a KB article for every recurring question. If you've answered it twice, document it.
- Surface help in context. Link the relevant article from the exact screen where users get stuck.
- Add a contact-form deflector. Show matching articles as the customer types their subject line.
- Improve error messages. A clear, actionable error prevents the ticket entirely.
- Proactive status comms. During an incident, a status banner deflects the flood of "is it down?" tickets.
- Macros for the rest. What you can't deflect, answer fast with canned responses.
- Close the loop with product. Send the top issue types to engineering every month.
- Measure deflection. Track self-service resolution rate, not just ticket count.
What to expect
Teams that systematically attack their top issue types typically see 25–40% volume reduction within two quarters — without hiring a single additional agent.