Plan requirement
| Subscription | Suite Enterprise or higher, Explore Enterprise |
| Access | Admin |
Live data components stop displaying data on 25 January 2027. Anything you are building new belongs in real-time monitoring instead.
On 25 January 2027 Zendesk removes prebuilt live dashboards, live data components, and the ability to create live dashboards from Explore. Components already sitting on your own dashboards stop displaying data on that date. Live monitoring moves to real-time monitoring, which is available on Professional and Enterprise. Nothing needs doing yet: the migration path opens when the replacement becomes generally available, and only then can you rebuild your own dashboards there. Zendesk names that replacement agentic analytics, which real-time monitoring runs on, and expects it to become generally available during 2026. Knowing the name is what lets you recognise the moment when it arrives.
The ending had a beginning that is easy to miss. Since 5 May 2026 the prebuilt live dashboard is only there for accounts that had already used Explore, so a newer account never had one and this article describes something it does not have. Real-time monitoring is where it looks instead.
So treat what follows as maintenance of something with an end date, and keep a list of which dashboards carry these components. That list is what you will need when the date approaches.
Adding one
- Create or open a dashboard in Explore and put it in edit mode.
- Select Add > Add live data.
- Choose the components you want on the Add live data page.
- Click Add live data.
- Reposition the components on the dashboard.
What you can show
You pick from a fixed list rather than building your own, which is the first surprise for anybody expecting the report builder.
| Support | Agents online and offline. New, open, pending, on-hold and solved tickets over the last 30 or 60 minutes, each with a change figure. |
| Talk | Calls in queue, ongoing calls, callbacks in queue, average and longest wait time, and agents online, offline, away or transfer only. |
| Chat | Chats in queue, active chats, average and longest wait, reply and duration, missed chats and satisfaction over 30 or 60 minutes. |
| Messaging | Active and inactive conversations, in queue and assigned, average concurrency, requester wait and handle time, and time in queue. |
Three limits worth knowing first
It stops updating after one minute and thirty seconds without interaction. That is the one that catches people: a dashboard on a wall screen that nobody touches goes stale, keeps showing numbers, and gives no sign that it has stopped. It resumes as soon as somebody interacts with it.
A hundred concurrent viewers. That is the maximum for a live dashboard, or any dashboard containing live components. Past that, updating is not guaranteed.
Near real time is 5 to 10 seconds in practice, and network speed and ticket volume both affect it.
Mark them clearly
They update on a different rhythm from everything else on the dashboard. A live figure next to a report from the last refresh will be compared, and the two will not agree.
Label them, and put them together rather than scattered among the historical charts.
Only where somebody can act
A live queue number on a monthly management dashboard is noise: nobody reading that report is going to pick up a ticket. It belongs on a dashboard a team lead has open during the day, which is also the only place where the ninety-second timeout is not a problem.
Watch what a number gives away
Live agent availability is visible to whoever opens the dashboard. Decide whether that should be on a screen the whole company can see.
Comments
0 comments
Article is closed for comments.