Ticket Merger

Zendesk Dashboards Worth Building

Everyone builds a Zendesk dashboard in week one. Almost nobody opens it in week six. The difference is whether it answers a question somebody actually has.

Start free trialAll guides

The four Zendesk dashboards that earn their place

The daily queue board. Unassigned count, oldest untouched ticket, tickets breaching within the hour. This is the only one a team lead needs open all day.
The weekly trend. Volume, median first response, CSAT, backlog age. Four numbers, twelve weeks of history, no more.
The agent view. Solved, handle time and CSAT together, because any one of those alone drives bad behaviour.
The topic board. Volume by tag or product area. This is the one you take to a product meeting, and it's the one that changes anything outside support.

Why dashboards die

Three reasons, and they're all avoidable.

The dashboard answers a question nobody asked. Somebody built it because the chart type looked good.

It has thirty widgets, so reading it's work. A dashboard that needs interpreting is a report, and reports get scheduled, not browsed.

Nobody owns it. A dashboard without a person whose job includes looking at it every Monday is decoration.

Schedule, don't browse

Explore can email a dashboard on a schedule. Use it. A number that arrives in an inbox on Monday morning gets read; a number that requires logging in does not.

Send the weekly trend to the whole team and the topic board to product. Keep the queue board live, since that one is genuinely operational.

One filter worth adding to everything

Exclude tickets tagged closed_by_merge from your volume and handle-time widgets.

Merged duplicates are administrative closures, not work. Leaving them in inflates volume, flatters your solved-per-agent number and drags your median handle time down, which makes the whole dashboard slightly wrong in a way that's hard to spot.

FAQ

Frequently asked questions

Is a Zendesk reporting dashboard the same as a live one?

No. A Zendesk reporting dashboard in Explore answers what happened, refreshed on a schedule. A live dashboard answers what's happening right now, and only the higher tiers include real-time data.

How many dashboards should we have?

Four. One live queue board, one weekly trend, one agent view, one topic board. Anything else is a report someone should schedule instead.

Can Zendesk dashboards be emailed?

Yes, Explore schedules deliveries. Scheduled numbers get read far more than dashboards people have to visit.

Dashboards that describe reality

Filter out merged duplicates and every number moves closer to what actually happened.

Start free trial

14-day free trial. No credit card required.

Keep reading

Zendesk Explore: Reporting Without the Frustration
What Zendesk Explore does, the reports worth building first, how datasets and metrics fit together, and the numbers that lie when your queue has duplicates.
Support Metrics That Actually Matter
The handful of support metrics worth reporting, the ones that mislead, and how duplicate tickets distort almost every number on your dashboard.
Zendesk Duplicate Tickets: Find and Merge Them
Zendesk duplicate tickets, found and merged automatically: Ticket Merger spots them and merges through the native API. Live in five minutes, from $29/month.
Zendesk Live Dashboard: Real Time Queue Monitoring
What a Zendesk live dashboard can show, which plan real time data needs, what belongs on a wallboard, and the behaviour a screen on the wall creates.
Zendesk Talk Partner Edition: What It Actually Is
Zendesk Talk Partner Edition puts a third-party telephony provider inside the agent workspace. What it gives you, what it costs to build, and when to skip it.
Zendesk FAQ Pages: How to Build Ones That Deflect
How to build a Zendesk FAQ in Guide: one long page or many short articles, how to structure the section, and how to tell which answers actually work.