Supporting More Customers Without Hiring More Support
Last updated:
Volume per customer is the number to manage
Total tickets rising with customer growth is expected. Tickets per customer rising is a warning, and tickets per customer staying flat means you are on a hiring treadmill.
The goal is falling contacts per customer, which is achievable and is entirely a product and communication question rather than a staffing one.
Fix the causes, in order
Categorise a month of tickets by underlying cause and rank. The top five almost always dominate, and most are preventable rather than answerable.
Each ticket is a customer telling you where the product or the communication failed. Answering it is service; fixing the cause is the only thing that changes next month's volume.
Prevent, deflect, then answer
- Prevent — fix the product issue or the unclear interface that generates the contact.
- Inform — proactive updates so people do not need to ask about status.
- Enable — self-service for the routine actions people contact you about.
- Answer — efficiently, with context attached and good templates.
Most teams start at step four and stay there, which is why volume never falls.
Make answering efficient
- Context attached automatically — account, plan, recent activity, previous tickets
- Saved replies for the common cases, personalised before sending
- Routing so specialists get specialist questions
- A knowledge base agents can search and link to rather than retyping
Then consider AI answering
Once volume is reduced and the remaining questions are documented, AI answering from your own material adds real capacity. Doing it before the documentation is good produces a system that confidently says the wrong thing.
Keep escalation prominent and measure re-contact rate rather than deflection.
When to hire anyway
When response times are slipping despite the above, when the team is working evenings, or when the work has become specialised enough that generalists cannot handle it.
Hiring is not a failure — hiring because nobody addressed the top five causes is.
Frequently asked questions
What is a reasonable contacts-per-customer figure?
Should support sit with engineering?
How do we handle out-of-hours?
What does support tooling cost?
Support volume rising with headcount?
Send us a categorised month of tickets. We will tell you which causes are preventable and what fixing them would save.
Related services
What we build for problems like this one