When a small number of customers create most of the support load

Support leaders often notice the problem before they can prove it.

The dashboard says ticket volume is stable, but the queue feels heavier. Agents say a handful of accounts keep coming back. Customer success flags frustration from the same names again and again. Leadership sees no obvious crisis in the top-line numbers.

This is what concentrated support demand looks like.

The issue is not always that the team has more work. Sometimes it has the wrong distribution of work. A small number of customers create a large share of tickets, and the dashboard hides that concentration by blending everyone together.

Why this pattern matters

When demand is concentrated, support risk rises faster than total volume suggests.

That is because concentrated demand often comes with one or more of these problems:

repeated product friction
weak onboarding or implementation
account-specific workflow complexity
poor documentation around one use case
unresolved issues being treated as separate tickets

If you do not see the concentration, you end up managing the queue as if the workload were broad and normal. It is not.

The top-line dashboard can hide it

A ticket volume chart is good at showing whether total inflow is rising or falling. It is bad at telling you whether the same five accounts are creating a growing share of that inflow.

That is why a queue can feel increasingly fragile even while ticket volume stays flat.

What changes is not the size of the work. It is the concentration of the work. And concentrated work is harder to absorb because:

it often clusters around hard or recurring issues
it creates local frustration with specific accounts
it pulls leaders into escalations more often
it can signal churn risk before revenue systems catch up

What to measure instead

Start with two simple views:

Those two reports answer slightly different questions.

Tickets per customer tells you which customers generate the most demand overall.

Multi-ticket customer reporting tells you how many customers are returning repeatedly in the same period, even if each ticket looks separate in the queue.

Together, they show whether the load is broad, concentrated, or repeat-heavy.

What concentration usually means

1. One workflow is broken for a few important accounts

This is common in B2B support. A handful of accounts use the most advanced workflows, so when one part breaks, they create repeated demand very quickly.

2. The queue is solving symptoms, not root causes

You can close each ticket individually and still keep the customer stuck in the same loop. This is why repeated demand often rises even when reopen reporting looks fine.

3. Support is carrying work that belongs elsewhere

Sometimes the concentration is really an onboarding issue, a product issue, or a customer success issue that support absorbs because it is the easiest visible path.

4. The customer relationship is at risk

Not every high-ticket account is unhealthy. Large or high-touch customers naturally generate more work. But if concentration rises alongside low satisfaction, long waits, or repeated issue types, the account is telling you something important.

How to review the pattern without blaming customers

This is the mistake many teams make first. They find the noisiest accounts and frame the insight as “these customers create too many tickets.”

That mindset is operationally useless.

The right questions are:

why do these customers need repeated help?
is the demand healthy or preventable?
is the issue account-specific or systemic?
what would reduce the future demand without hurting the relationship?

Support reporting is most valuable when it changes the system, not when it labels customers as difficult.

The four follow-up questions that matter

When one customer or organization stands out, review:

Top issue categories
Are the tickets clustering around one workflow, one feature, or one rollout?
Repeat behavior
Is the same issue returning, or is the account genuinely broad in its support needs?
Outcome quality
Are reopen rate, repeat contact rate, or CSAT also moving in the wrong direction?
Ownership
Does the fix belong to support, product, onboarding, documentation, or success?

Without those questions, concentration reporting just becomes an interesting chart.

What teams should do next

If concentrated demand is real, the next move is usually one of these:

create an account-specific action plan for the highest-load customers
fix the repeated issue category at the product or documentation layer
adjust onboarding for the segment producing repeated demand
separate strategic high-touch support from preventable support churn

And most importantly, re-check the concentration trend later. A useful report should show whether the intervention actually lowered future demand.

Why this matters for small teams

Small teams feel concentrated demand earlier than large teams do.

If three accounts create a disproportionate share of the queue, a small team can feel overwhelmed even when total ticket volume looks manageable on paper. That is why account-level concentration should be part of the same review as:

Small teams do not need more dashboards. They need the few views that explain why the queue feels heavier than the totals suggest.

The main takeaway

When a small number of customers create most of the support load, the problem is rarely “too many tickets” in the abstract.

It is usually concentrated friction, repeated demand, or hidden account risk.

If you only watch total volume, you miss that story. If you watch customer concentration, you can act before the queue normalizes around a pattern that eventually becomes churn.

See which Zendesk customers are quietly driving most of the queue - start free

When a Small Number of Customers Create Most of the Support Load