Multi-brand Zendesk reporting: one dashboard for all your brands
If you run multiple brands in a single Zendesk instance, your reporting problem is not a lack of data — it is too much of it, spread across brands with no unified view. Each brand has its own volume, its own SLAs, its own agents. Zendesk Explore treats them as filter values, not as first-class reporting entities. The result: you either build one dashboard per brand (and lose the comparison view) or build one dashboard for everything (and lose brand-level clarity).
This post walks through how to structure multi-brand reporting so you can compare performance across brands, identify which brand is dragging down your numbers, and give brand managers the data they need without giving them access to everything.
The multi-brand reporting problem
Zendesk’s multi-brand feature lets you operate several customer-facing brands from one Support instance. Tickets are tagged with a brand, agents can belong to multiple brands, and customers see the branding for their specific product.
The reporting challenge comes from three directions:
-
Shared agents. An agent who works across Brand A and Brand B has their metrics blended. Their first response time is an average across brands — so if Brand A has a 1-hour SLA and Brand B has a 4-hour SLA, a single FRT number is meaningless.
-
Different baselines. Brand A might be a mature product with 2,000 tickets per month and a target CSAT of 4.5. Brand B might be a new product with 200 tickets per month and no established baseline. Comparing raw numbers without context misleads.
-
Permission boundaries. Brand managers want to see their brand’s data but should not see other brands. Explore’s permission model does not natively restrict dashboards by brand — you need workarounds.
What a good multi-brand dashboard looks like
Level 1: The executive comparison view
One page, all brands side by side. This is for the VP of Support or Head of CX who needs to know which brands need attention.
| Metric | Brand A | Brand B | Brand C | All brands |
|---|---|---|---|---|
| Ticket volume (this week) | 480 | 210 | 95 | 785 |
| Volume change vs. last week | +5% | -3% | +12% | +3% |
| Median FRT (business hours) | 1.2h | 2.8h | 0.9h | 1.5h |
| Median resolution time | 8.4h | 14.2h | 6.1h | 9.6h |
| CSAT | 4.3 | 3.8 | 4.5 | 4.2 |
| Backlog | 62 | 45 | 12 | 119 |
| Reopen rate | 6% | 11% | 4% | 7% |
This view answers the “which brand needs help?” question in 30 seconds. Brand B has higher FRT, lower CSAT, and an 11% reopen rate — that is where leadership should focus.
Level 2: The brand-specific deep dive
Each brand gets its own page with the full set of ops metrics: volume trend, backlog aging, FRT, resolution time, CSAT, reopens, and agent performance — all filtered to that brand. This is what a brand manager reviews weekly.
Use the same structure as your support dashboard template, just with a brand filter applied. The metrics are the same; the scope is narrower.
Level 3: The cross-brand agent view
For agents who work across brands, build a view that shows their metrics per brand:
| Agent | Brand A tickets | Brand A FRT | Brand B tickets | Brand B FRT |
|---|---|---|---|---|
| Maria | 35 | 0.8h | 22 | 2.1h |
| James | 28 | 1.1h | 30 | 3.4h |
This reveals whether an agent’s performance varies by brand — which often means they are more trained on one product than another, or that one brand’s tickets are inherently harder.
How to build multi-brand reports in Zendesk Explore
Filter by brand
Every report in Explore can be filtered by the Ticket brand attribute:
- Open or create a report in the Support: Tickets dataset.
- Add Ticket brand as a filter.
- Select the brand(s) you want.
For the comparison view, add Ticket brand as a row dimension instead of a filter, so each brand appears as a separate row.
Create brand-specific dashboards
For brand managers who should only see their brand:
- Create a dashboard.
- Add your standard reports (volume, FRT, resolution, CSAT, backlog, reopens).
- Add a Dashboard filter on Ticket brand and set the default to the relevant brand.
- Share the dashboard with the brand manager and instruct them not to change the filter.
The limitation: Explore does not enforce brand-level permissions on dashboards. A brand manager can change the filter and see other brands. If this is a concern, you need separate dashboards with pre-filtered reports — more maintenance, but true isolation.
Shared agent metrics by brand
Build a report with:
- Rows: Assignee name
- Columns: Ticket brand
- Metrics: COUNT(Tickets), MED(First reply time), AVG(CSAT)
This produces a matrix of agent × brand performance. Export it weekly for agent-level coaching.
Normalize for fair comparison
Raw numbers hide differences in brand maturity and ticket complexity. Add context:
- Tickets per 1,000 active users (if you track active users per brand) to normalize volume.
- FRT vs. SLA target (as a percentage) rather than raw FRT, so brands with different SLAs are compared fairly.
- CSAT vs. brand baseline (the brand’s own 90-day average) rather than cross-brand CSAT, so a new brand with volatile scores is not unfairly compared to a mature one.
Cross-brand patterns to watch for
Volume migration
When one brand’s ticket volume drops while another’s rises, customers may be migrating between products — or submitting tickets under the wrong brand. Track the trend and investigate if the shift is unexpected.
SLA performance divergence
If Brand A consistently meets SLA while Brand B consistently misses, the problem may not be Brand B’s team — it may be understaffing or routing rules that do not account for brand-specific complexity. See support SLA dashboard and Zendesk SLA breach by priority report.
CSAT drag
One brand with persistently low CSAT will drag down your overall average. When reporting company-wide CSAT to executives, always show brand-level breakdown so a single brand’s issues do not mask healthy brands (or vice versa).
Topic distribution differences
Different brands have different issue profiles. Brand A might be dominated by billing questions; Brand C might be mostly onboarding. Understanding the ticket distribution per brand helps you allocate specialized agents. See Zendesk ticket distribution report.
Common mistakes
-
One dashboard, no brand filter. The most common setup — and the least useful. Blended metrics hide brand-specific problems. Always either filter or segment by brand.
-
Comparing brands by raw numbers. A brand with 50 tickets per month and a brand with 500 tickets per month are not comparable on raw volume. Normalize by user count, revenue, or another relevant denominator.
-
Separate Explore instances per brand. Some teams create entirely separate Explore environments for each brand. This eliminates the comparison view and doubles (or triples) your maintenance. Use one Explore instance with brand as a dimension.
-
Ignoring shared agent performance. If agents work across brands, their metrics are blended by default. Split their reporting by brand or you will not know whether Brand B’s slow FRT is a staffing problem or an agent-training problem.
-
Reporting to brand managers on company-wide metrics. A brand manager for Brand B does not need to see Brand A’s data (and may not be authorized to). Deliver brand-specific dashboards or filtered views.
When to use a third-party tool
Explore’s multi-brand support works for basic filtering and comparison. It falls short when you need:
- Enforced brand-level permissions — Explore does not restrict dashboard access by brand natively.
- Automated brand-specific reports — Scheduled email reports in Explore can be filtered by brand, but setting up one per brand is manual and fragile.
- Cross-brand correlation — If you want to see whether a Brand A product change is causing Brand B tickets (e.g., an integration that affects both products), Explore’s filtering model does not support cross-brand linking.
- Real-time comparison — Explore dashboards refresh hourly at best. If you need live multi-brand monitoring, you need an external tool.
A dedicated Zendesk analytics dashboard or reporting tool can surface multi-brand comparisons with proper permissions and drill-down to individual tickets.
Start with the comparison page
If you are building multi-brand reporting from scratch, start with the Level 1 executive comparison view. One page, all brands, five metrics: volume, FRT, resolution time, CSAT, and backlog. Review it weekly. When a brand’s numbers move in the wrong direction, drill into the brand-specific Level 2 view to diagnose.
The goal is not more dashboards — it is the right view for each audience. Executives see the comparison. Brand managers see their brand. Agents see their performance per brand. Everyone sees the metrics that drive their decisions.