Zendesk Backlog by Brand Report

Your total backlog tells you how much open work exists in aggregate. Backlog by brand tells you which brands are actually holding that open work.

That difference matters because a queue can look manageable overall while one brand quietly traps most of the aged tickets. This guide shows how to build a Zendesk backlog by brand report, how to interpret concentration, and how to distinguish healthy demand from brand-specific queue drag.

What this report should answer

A useful backlog-by-brand report should answer:

Which brands hold the most open tickets right now?
Which brands hold the oldest unresolved work?
Is queue pressure concentrated in one brand even while total backlog looks normal?
Do the same brands also show slow resolution, poor CSAT, or rising SLA risk?

For the metric definition, see backlog. For age context, also review backlog aging and the Zendesk Multi-Brand Support Report.

Why brand-level backlog matters

Company-wide backlog is useful for leadership and staffing. But it is weak at showing concentration.

One brand can hold most of the queue pressure because it has:

weaker routing rules
a surge in one product area
slower specialist follow-up
more complex escalations
lower self-service effectiveness

If you only watch the total unsolved count, you can mistake a brand problem for a universal capacity problem. Brand-level backlog makes the concentration visible.

How to build the report in Zendesk

Use the Support: Tickets dataset in Zendesk Explore and filter to open or unsolved work.

1. Group by ticket brand

Add Ticket brand as the primary row dimension. Clean up brand assignment errors first so backlog is attributed to the correct customer-facing experience.

2. Count open tickets by brand

This gives you the core concentration view. A descending table or bar chart works well because it surfaces which brands carry the most queue weight.

3. Add aging context

Open ticket count alone is not enough. Pair it with age buckets or oldest-ticket age so you can separate:

a high-volume brand with mostly fresh work
a brand with less volume but much older unresolved work

For the setup details, see Zendesk Backlog Aging Report.

4. Add supporting dimensions

The most useful context cuts are:

top tags or issue categories
assigned group
priority mix
channel mix
ticket form if brands use multiple intake paths

These turn “Brand B has too much backlog” into “Brand B has old billing escalations in one queue.”

5. Trend concentration over time

The strongest version of the report shows each brand’s share of total backlog over time. That tells you whether risk is spreading across the operation or becoming more concentrated in one brand.

The most useful report layouts

Open tickets by brand

This is the simplest concentration view. It shows where open work is sitting right now.

Open tickets by brand with aging

This is the most practical operating view because it reveals whether the work is just numerous or genuinely stale.

Backlog by brand and tag

This helps identify whether the brand’s queue pressure is driven by one recurring workflow or broad operational friction.

Backlog by brand with resolution time

This pairing shows whether large open queues are also slow to close or simply reflect fresh demand.

How to interpret the patterns

One brand holds most of the backlog

That often means your queue problem is more concentrated than the headline unsolved count suggests.

One brand has high backlog but little aging

That can be normal for a busy or seasonal brand. High volume alone is not the same as unhealthy backlog.

One brand has moderate volume but very old tickets

This is usually the more urgent pattern. Even a smaller brand can create serious operational and customer risk when its work stays open too long.

Backlog concentration rises while total volume stays flat

This is a classic hidden-risk pattern. The team looks stable overall, but one brand is getting more fragile and more expensive to serve.

Common mistakes

Treating all high-volume brands as backlog problems. Fresh work and stale work are not the same.
Skipping aging. Backlog without age becomes a blunt workload count.
Ignoring issue-level context. Tags, queues, and channels often explain why one brand is heavier.
Using the report without ownership. Somebody has to act on the brand-level risk.
Assuming total backlog tells the full story. It rarely does in a multi-brand setup.

What to do when a brand stands out

If one brand repeatedly holds the most aging backlog:

Check whether the work concentrates in one tag, group, or ticket form.
Compare it with Zendesk Resolution Time by Brand Report and Zendesk SLA Risk by Brand Report.
Decide whether the fix belongs in routing, staffing, product escalation, or self-service improvement.
Separate fresh inflow from stale unresolved work before acting.
Recheck the same brand weekly until the age profile normalizes.

The goal is not to make every brand’s backlog identical. It is to catch the brands quietly trapping queue capacity and customer trust.

Where this report fits in your dashboard

This report works best beside:

Together, those views show which brands create open work, which of that work is getting old, and whether the pressure is becoming a brand-specific risk rather than a broad staffing issue.

FAQ

Is high backlog by brand always bad?
No. Large brands often create more open work. The real warning sign is backlog paired with aging, slow resolution, or rising SLA pressure.

Should I compare raw backlog or share of total backlog?
Both are useful. Raw backlog shows current load; share of total backlog shows whether one brand is becoming disproportionately heavy.

How often should I review this report?
Weekly works best for operations, with monthly review for broader brand-health discussion.

See which Zendesk brands are quietly trapping the oldest open work - start free