Zendesk Tickets per Customer Report

Total ticket volume tells you how busy support is. Tickets per customer tells you who is creating that load.

That distinction matters more than many teams realize. A queue of 500 tickets looks very different when it comes from 450 customers than when it comes from 30 customers. The first suggests broad product demand. The second often points to account risk, poor onboarding, repeated defects, or process friction concentrated in a handful of relationships.

This guide shows how to build a Zendesk tickets per customer report, what patterns to watch, and how to use it without turning support analytics into a customer blame exercise.

What this report should answer

A useful tickets per customer report helps you answer:

Which customers generate the most support demand?
Is support load concentrated in a small part of the customer base?
Are high-ticket customers also high-value, high-risk, or high-friction accounts?
Is repeat load rising because of one product area, one onboarding motion, or one customer segment?

For the metric definition, see tickets per customer. For account-level clustering, also review multi-ticket customers and organization health score.

Why support teams should track it

Many teams treat ticket volume as a single company-wide number. That is useful for staffing, but it hides concentration risk.

When one small customer segment creates a disproportionate share of demand, several things can happen at once:

the queue feels heavier than the top-line volume suggests
account managers escalate frustration late
product teams miss a concentrated defect pattern
leadership underestimates churn risk because the pain is localized

For B2B teams in particular, tickets per customer is one of the cleanest ways to connect support operations to account health.

How to build the report in Zendesk

Use the Support: Tickets dataset in Zendesk Explore and choose a time window that matches your review cadence, usually weekly or monthly.

1. Count tickets by requester or organization

The most common versions are:

by requester for individual behavior
by organization for account-level demand

If you sell to teams, the organization view is usually more useful because it avoids overreacting to one active contact inside a large account.

2. Sort descending

The report should immediately surface the accounts or requesters generating the most volume. A leaderboard table or horizontal bar chart works well here.

3. Add context columns

The raw ticket count is not enough. Add supporting fields such as:

ticket priority mix
channel mix
top tags or issue categories
reopen count
CSAT trend if available

This turns “who is noisy” into “why this account is generating demand.”

4. Trend the concentration over time

A static table is useful, but a trend is better. Track whether the share of total tickets created by your top 10 customers is rising or falling.

If the concentration is increasing, your queue may be getting riskier even if total volume is stable.

5. Pair it with quality and risk views

The best companion reports are:

The most useful report layouts

Top customers by ticket count

This is the operating view. It shows where support load concentrates right now.

Tickets per customer over time

Use this to distinguish one bad week from a persistent pattern. A customer that repeatedly appears in the top bucket needs a different response than one that spiked once during rollout.

Tickets per customer by issue category

This is how you separate “demand because the customer is large” from “demand because one workflow is broken.” If the same category dominates across several heavy accounts, the issue is likely systemic.

Tickets per customer and reopen rate

High volume alone is not necessarily bad. High volume plus reopen rate or repeat contact rate usually means the team is treating symptoms instead of fixing root causes.

How to interpret the patterns

This can mean:

concentrated product pain
weak onboarding or implementation
high-touch customers using support as a workflow channel
poor self-service for a specific segment

The next step is not “tell them to open fewer tickets.” It is to understand whether the demand is healthy, preventable, or a sign of account risk.

Large customers dominate, but satisfaction stays healthy

That may be normal. Enterprise or high-touch accounts often generate more support interactions because they have more users, more integrations, and more workflow depth.

Small customers generate outsized load

This is often more concerning. Heavy support demand from low-complexity customers can indicate onboarding confusion, pricing mismatch, or product friction that should not exist at that tier.

Ticket concentration is rising while total volume is flat

This is one of the easiest ways risk hides in a dashboard. Company-wide traffic looks stable, but a few relationships are becoming much more expensive to serve.

Common mistakes

Treating all high-volume customers as a problem. Some accounts are simply larger or more engaged.
Skipping segmentation. Account size, plan tier, and implementation stage all matter.
Ignoring channel mix. A customer with many low-friction chat tickets is different from one with a few complex escalations.
Looking only at one contact. Use organization-level reporting when the buying relationship sits at the account level.
Using the report without action owners. If support, success, and product do not agree on follow-up, the report becomes a leaderboard nobody uses.

What to do when an account stands out

When one customer or organization keeps appearing at the top:

Review the top tags, forms, or issue categories behind the load.
Check whether the volume comes from many users or a single contact pattern.
Compare requester wait time and CSAT for that account.
Decide whether the issue belongs to support, onboarding, product, or account management.
Track whether the account’s ticket concentration falls after the intervention.

The important point is to use the report to reduce avoidable demand, not simply to identify “difficult” customers.

Where this report fits in your dashboard

Tickets per customer is most valuable beside:

Those reports together tell you how much support demand exists, who creates it, and whether it signals healthy adoption or hidden churn risk.

FAQ

Should I report by requester or organization?
If you support individual users, requester is fine. For B2B teams, organization is usually the better default because it reflects the real customer relationship.

Is a high tickets-per-customer number always bad?
No. Large or high-touch accounts naturally create more demand. The signal becomes important when the volume is rising, concentrated, and tied to poor outcomes.

How often should I review this?
Monthly is a strong default for leadership and account reviews. Weekly can help if you are actively triaging at-risk accounts or a major rollout is underway.

See which Zendesk customers are creating the most support load - start free