Surveys in 2026 report a majority of business leaders expecting service volumes to rise by as much as a fifth within two years, while cost per contact climbs with labour costs. Headcount scales linearly with volume, so closing that gap requires removing work rather than adding people.
Key takeaways
- Volume growth compounds with customer growth. Headcount does not scale the same way.
- Rising expectations for instant, round-the-clock answers drive volume up independently of customer count.
- Normalise volume per customer or growth will look like a support failure.
- Only removing categories of work changes the slope rather than the height.
The structural problem in support right now is simple arithmetic. Volume is growing. Budgets are not growing at the same rate. Headcount scales linearly with volume. Those three facts cannot all be satisfied.
Surveys through 2026 report a majority of business leaders expecting service volumes to rise by as much as a fifth over the next one to two years, driven by rising expectations as much as by customer growth.
Why volume rises faster than customer count
Three drivers, and only one of them is growth.
More customers. The obvious one, and the one that is fine. More customers should mean more contacts.
Higher expectations. Customers increasingly expect instant responses, availability outside business hours, and support on whatever channel they already use. Each of those raises the contact rate per customer independently of how many customers you have.
More surface area. Every channel you add, every feature you ship, every pricing change you make generates its own contacts. Product velocity is a support volume driver that almost nobody models.
The second and third are why total volume frequently grows faster than the customer base, and why teams feel like they are falling behind while doing nothing wrong.
Measure the rate, not the total
The first correction is to stop reporting total volume.
A company that grew customers 40% and volume 30% improved. Reported as a total, that looks like a 30% problem. Reported as contacts per hundred customers, it is a 7% improvement.
Track the rate. It is the only version of the number that tells you whether the support function is getting better or worse, and it stops leadership reacting to growth as if it were failure.
Why headcount cannot close the gap
Because it scales linearly against something that compounds.
If contacts per customer stays flat and customers double, you need roughly double the agents. Efficiency programmes move that by a percentage: better macros, faster tooling, tighter handle time. Useful, and they change the height of the line rather than its slope.
Removing a category of work entirely is the only intervention that changes the slope. If access questions are 20% of your queue and they stop reaching humans, that 20% does not come back as you grow. It is gone at every future volume.
Where the removable volume is
Categorise a thousand tickets by topic and rank by volume times handling time. In most queues a short list dominates, and it is usually some combination of:
- Access and login questions
- Order, delivery, or status questions
- Billing and invoice queries
- One or two genuinely confusing parts of the product
The first three are documented or documentable. The fourth is a product problem wearing a support costume, and it is the cheapest fix available because changing an error message or an invoice line removes a whole category permanently.
We wrote up the method and what typically comes out of it.
The cost side
Cost per contact rises with labour costs, and it rises structurally when automation removes the cheap contacts first, leaving a harder human mix. That second effect looks like a regression and is arithmetic.
Which is why the metric to manage is cost per resolution rather than cost per contact. It captures both the spend and the outcome, and it does not punish you for successfully removing the easy work. Published benchmarks for either are close to useless, because they rarely state whether they include employer costs, tooling, after-contact work, or management time.
The honest summary
If your volume growth is coming from customer growth and your contact rate is flat, you have a scaling problem with a known solution.
If your contact rate is rising, something changed: a product release, a pricing change, a channel you opened, or documentation that went stale. Find it before you add capacity, because capacity does not fix a cause.
And if a short list of documented topics dominates your queue, that volume does not need people at all. Removing it is the only intervention that keeps working as you grow.
Frequently asked questions
Why is customer support volume rising?
How do I handle rising support volume without hiring?
Should I measure total ticket volume?
What does a support ticket cost?
Resolve, don't deflect.
See Fidiora resolve a ticket, capture a lead, and keep the bill predictable.