Zendesk Multi-Brand Support Report
If your Zendesk account serves more than one brand, your aggregate metrics hide the real story. One brand might hit every SLA target while another quietly falls behind—and a single-brand dashboard won’t reveal the gap.
A multi-brand support report breaks performance down by brand so you can compare first response time, resolution time, CSAT, and backlog side by side. This guide covers how to build that report, what to watch, and where teams get it wrong.
Why report by brand
Zendesk lets you assign tickets to brands, and Explore includes a brand attribute in most datasets. But the prebuilt dashboards show all brands together by default. That means:
- A high-performing brand masks a struggling one in the average.
- SLA policies may differ per brand, but your dashboard doesn’t show compliance per brand.
- Staffing decisions get made on aggregate numbers, not where the load actually sits.
Multi-brand reporting answers a simple question: is every brand getting the same quality of support?
How to build a multi-brand report in Zendesk Explore
Step 1: Start with the right dataset
Use Support – Tickets for most KPIs (volume, FRT, resolution time). Use Support – Ticket updates for reply-level metrics.
Step 2: Add brand as a column or row
In any Explore report, add the Ticket brand attribute as a row. This splits every metric by brand automatically.
Step 3: Choose the right metrics
For a useful brand comparison, start with:
| Metric | Why it matters |
|---|---|
| Ticket volume | Load per brand—useful for staffing. |
| First reply time (median) | Speed per brand. |
| Resolution time (median) | Efficiency per brand. |
| CSAT | Quality per brand. |
| Reopen rate | Resolution quality per brand. |
| SLA achievement rate | Compliance per brand. |
| Backlog (unsolved count) | Capacity pressure per brand. |
Step 4: Filter by date range and compare periods
Add a date filter (e.g. last 7 days) and a comparison period (previous 7 days) to see trends. A brand that’s stable this week may be slowly degrading month over month.
Step 5: Build a dashboard tab per brand (optional)
For accounts with 3+ brands, consider a separate Explore dashboard tab for each brand so team leads can bookmark their view. Use the same metrics on each tab for consistency.
Business hours vs calendar hours
Each brand may operate in different business hours. If Brand A runs 9–5 Pacific and Brand B runs 9–5 CET, using calendar hours will unfairly penalize whichever brand crosses more off-hours.
Set business-hours schedules per brand in Zendesk Admin (Business rules → Schedules) and use business-hours metrics in Explore so the numbers reflect real working time.
Common mistakes
- Comparing brands with different SLA targets — A 4-hour FRT target for Brand A and an 8-hour target for Brand B makes a raw median comparison misleading. Report SLA achievement rate alongside raw metrics.
- Ignoring brand-specific volume patterns — Brand A may spike on Mondays; Brand B on Fridays. Aggregate weekly averages smooth this out and hide staffing gaps. Break down by day.
- Missing the routing layer — Tickets assigned to the wrong brand distort both brands’ reports. Audit brand assignment rules periodically to keep data clean.
- Averaging CSAT across brands — CSAT is already a percentage; averaging percentages across brands with very different volumes gives a misleading number. Weight by volume or report per brand.
What to do when one brand lags
- Check volume trends — Is the brand growing faster than staffing? Look at ticket inflow per brand over the past 4 weeks.
- Check complexity — Longer handle time or more replies per ticket may indicate more complex issues, not slower agents.
- Check staffing — Are the same agents shared across brands? If so, priority routing may starve the lower-priority brand. Review agent utilization per brand.
- Check self-service — Does the lagging brand have a weaker help center? Look at self-service rate and ticket deflection by brand.
- Drill to tickets — Filter to the specific brand + slow tickets and look for patterns: tags, groups, or requester organizations.
Dashboard template: multi-brand comparison
A practical multi-brand dashboard has three sections:
Section 1 — Brand scorecard (table) One row per brand with: volume, median FRT, median resolution time, CSAT, reopen rate, SLA achievement. Color-code cells that miss targets.
Section 2 — Trend lines (one chart per KPI) Overlay brands on the same chart (e.g. FRT by week, one line per brand) so divergence is visible at a glance.
Section 3 — Backlog snapshot Current unsolved tickets per brand with age breakdown (0–24h, 1–3 days, 3+ days). This shows where pressure is building right now.
For a ready-made version of this layout, see support metrics dashboard.
FAQ
Can I set different SLA policies per brand? Yes. Zendesk supports conditions in SLA policies that filter by brand. Create one policy per brand (or per brand–priority combination) and report SLA achievement per policy.
How do I handle agents who work across brands? Report agent performance per brand by adding both agent and brand attributes in Explore. This shows whether an agent is fast on Brand A but slower on Brand B—often a training or context-switching signal.
What if I only have two brands? The same approach works. Two brands is actually the easiest case—put them side by side in a single report and spot divergence early.
Does TicketBoard support multi-brand breakdowns? Yes. TicketBoard pulls brand data from Zendesk and lets you filter or compare brands in any dashboard view—no Explore formulas required.