Zendesk Resolution Time by Brand Report

Overall resolution time tells you how long work takes to close across the whole support operation. Resolution time by brand tells you which brands are actually experiencing the slowest end-to-end support cycle.

That matters because one brand can quietly stay open longer than the rest even while the blended average remains acceptable. This guide shows how to build a Zendesk resolution time by brand report, how to interpret the differences, and what to change when one brand’s work keeps aging longer than it should.

What this report should answer

A useful resolution-time-by-brand report should answer:

Which brands take longest to close work?
Is slow resolution concentrated in one brand even while overall time to close looks stable?
Are long cycles tied to one queue design, issue mix, or brand promise?
Do slower brands also show backlog growth, SLA pressure, or poor CSAT?

For the metric definition, see resolution time. For closely related context, keep backlog, replies per ticket, and the Zendesk Multi-Brand Support Report nearby.

Why brand-level resolution time matters

Resolution time reflects more than raw effort. It captures workflow design.

One brand may stay open longer because it has:

more handoffs between teams
a more technical issue mix
slower vendor or product dependencies
a weaker knowledge base or self-service path
lower staffing depth for specialist questions

If you only watch one global median or average, those brand-specific delays get smoothed out. Brand-level reporting shows where the support journey is structurally longer, not just where the whole team looks slow.

How to build the report in Zendesk

Use the Support: Tickets dataset in Zendesk Explore. Monthly review is often the strongest default because resolution trends need enough volume to be meaningful.

1. Group by ticket brand

Add Ticket brand as your main row dimension. Clean up any inconsistent brand assignment first so one brand’s tickets are not leaking into another’s report.

2. Pair resolution time with ticket volume

Always review these together:

resolution time
solved or closed ticket count
ticket brand

A slow brand with ten tickets is a different problem from a slow brand with hundreds of tickets every month.

3. Add workflow context

The most helpful supporting cuts are:

assigned group
top tags or issue categories
priority mix
channel mix
replies per ticket or escalation indicators

These show whether a brand is slower because the work is heavier or because the workflow around that brand is dragging.

4. Compare business hours and calendar hours

If brands serve different regions or have different service schedules, compare both time bases. See business hours vs calendar hours so you do not confuse legitimate off-hours delay with broken operations.

5. Trend the gap over time

Trend the brands side by side. Persistent distance between brands matters more than one isolated spike.

The most useful report layouts

Resolution time by brand

This is the core comparison view. It quickly shows which brands stay open longest.

Resolution time by brand with ticket volume

This keeps the report grounded in business impact rather than small samples.

Resolution time by brand and assigned group

Use this when one brand touches multiple teams and you need to see whether the delay lives in a specific handoff or owner group.

Resolution time by brand and tag

This helps reveal whether the issue is broad brand friction or one recurring workflow that slows closure.

How to interpret the patterns

One brand is slow and high volume

This is usually a real operational problem. The brand is affecting enough customers to justify process or staffing attention.

One brand is slow but only in one issue category

That often points to a localized workflow gap rather than a broad brand problem.

One brand has slow resolution and high reply counts

This suggests the brand’s tickets need more back-and-forth, more coordination, or clearer intake before work can close cleanly.

One brand is slower while the overall time to close stays flat

This is the hidden-concentration pattern. Other brands are closing quickly enough to hide the local delay.

Common mistakes

Comparing brands without issue context. Resolution time alone does not explain cause.
Treating all delay as a staffing problem. Workflow design and routing often matter more.
Ignoring business hours. Cross-region brands can look worse than they are if you use only calendar time.
Reading averages without volume. A tiny slow brand does not mean the same thing as a core one.
Skipping ticket review. Numbers alone rarely tell you why one brand is slow.

What to do when a brand stands out

If one brand repeatedly shows longer resolution time:

Read tickets from that brand and look for repeated stall points.
Check whether one group, tag, or product area dominates the slowest work.
Compare it with Zendesk Backlog by Brand Report and Zendesk CSAT by Brand Report.
Decide whether the fix belongs in routing, enablement, product escalation, or staffing depth.
Recheck the same brand over time to confirm the change actually improves closure speed.

The goal is not perfectly equal resolution time across every brand. It is to stop one brand from quietly carrying much longer support cycles than the rest.

Where this report fits in your dashboard

This report works best beside:

Together, those views show whether one brand’s slower closure is isolated complexity or part of a broader operational problem affecting queue health and customer experience.

FAQ

Should I use median or average resolution time by brand?
Median is usually better for comparison because a few extremely old tickets can distort averages. If leadership expects averages, show both and explain the difference.

What if one brand is naturally more complex?
Complexity can justify a slower baseline, but it should still be stable and explainable. Rising delay without a clear change in mix is the real warning sign.

How often should I review this report?
Monthly is the best default, with weekly spot checks when one brand is under active change or pressure.

Track which Zendesk brands keep work open longest - start free