Zendesk Live Dashboards

A Zendesk live dashboard is three different features with three different jobs. Picking the wrong one is why your wallboard shows yesterday.

Three things people mean by "live"

They're not interchangeable, and the difference is mostly latency.

Views. A view is a live query over the queue. Open it and the counts are current. It's the cheapest real-time tool in Zendesk and every plan has it.
Explore live data widgets. Purpose-built real-time widgets that refresh on a short interval, designed to sit on a screen. This is what most people mean by a live dashboard.
Channel-specific real-time views. Voice and messaging have their own live monitoring, because a queue of people waiting on a call is a genuinely different problem from a queue of emails.

Standard Explore reports aren't in that list on purpose. They run on data that updates periodically rather than instantly, which is fine for a weekly trend and useless for a wallboard. The dashboards guide covers the non-live ones worth building.

Which plan a Zendesk live dashboard needs

Live data widgets sit on the higher Explore tiers rather than the entry-level one, and the exact split has moved between releases. Check the current Zendesk plan comparison before you promise anybody a wallboard, because this is the feature that most often turns out to need an upgrade.

If you're on a lower tier and the answer is no, you aren't stuck. A view with the count column, opened on a spare monitor and refreshed, gets you eighty per cent of the value for nothing. It's less pretty. It is just as true.

What belongs on a wallboard

The test for every widget: could somebody in the room do something about it in the next ten minutes? If not, it belongs on a weekly report instead.

Unassigned tickets. The number that should be near zero, and the one that means somebody needs to pick something up right now.
Oldest ticket waiting. A single number, in minutes. More motivating than any average.
Breaching within the hour. Tickets about to miss an SLA target, if you run SLAs.
Live conversations waiting, for chat and voice, with the longest current wait.
Agents available, if routing depends on it.

And what to keep off it. CSAT, because it moves too slowly to act on. Solved-per-agent, because a leaderboard on a wall changes behaviour and rarely for the better. Anything with a trend line, because trends are for meetings.

Five widgets is plenty. A wallboard people have to read is a wallboard people stop reading.

Size matters more than layout. Whatever the most important number is, it should be readable from the far side of the room, which in practice means two or three numbers at enormous size and everything else small. A dashboard designed on a laptop and then thrown at a television is always too dense, because the person building it was sitting sixty centimetres from the screen.

Making it survive on a screen all day

The practical bit nobody writes about. A dashboard on a TV is a browser session that has to stay logged in and awake for months.

Use a dedicated account for the display rather than a real person's login, so it doesn't die when they change their password. Check whether your session timeout kills it overnight. Disable screen sleep on whatever drives the TV. And put the screen where the team actually sits, not in the corridor where visitors see it, because a wallboard aimed at visitors becomes decoration within a fortnight.

Think about what happens when it breaks, too, because it will. A frozen dashboard showing a two-hour-old number is worse than no dashboard, since the team keeps trusting it. Put a visible clock or a last-updated stamp on the screen if the tool allows one, and make somebody responsible for glancing at it each morning.

One more: decide who is allowed to change it. A shared display that anybody can edit slowly accumulates widgets until it says nothing.

What a live board does to a team

Worth being honest about, because this is a management tool as much as a reporting one.

A live board is also the fastest way to settle an argument about whether the team is busy. Nobody debates a number that is on the wall.

A visible unassigned count creates useful pressure. People grab tickets. Response times drop. That's the whole point and it works.

It also encourages cherry-picking. When the room can see the queue, agents take the quick ones, and the awkward ticket that needs half an hour sits there getting older while the count looks healthy. Watch your oldest-ticket number, not just your queue size, or the board will optimise for the wrong thing.

A live board also makes duplicates visible in a way reports never do. Two rows, same customer, same subject, both unassigned. If you see that pattern several times a week on the wall, that's the queue telling you something.

FAQ

Frequently asked questions

Is a wallboard the same as real time reporting?

A Zendesk wallboard is the screen; Zendesk real time reporting is the data behind it. Only the higher tiers carry live data, so a wallboard on a lower plan is showing you the last refresh.

Does Zendesk have a real time dashboard?

Yes, through Explore live data widgets, plus channel-specific real-time monitoring for voice and messaging. Views are also live and available on every plan.

Which plan includes Zendesk live data?

Live data widgets sit on the higher Explore tiers. The exact split moves, so confirm against the current Zendesk plan comparison.

How often does a Zendesk live dashboard refresh?

Live widgets refresh on a short automatic interval. Standard Explore reports don't, since they run on periodically updated data.

Can I put a Zendesk dashboard on a TV?

Yes. Use a dedicated display account, check your session timeout, and disable screen sleep on the device driving it.

What should not go on a wallboard?

Anything nobody can act on in the next ten minutes. CSAT, trend lines and per-agent leaderboards all belong somewhere else.

Two rows, one customer

When the same requester shows up twice on the live board, Ticket Merger has usually already caught it.

Start free trial

14-day free trial. No credit card required.