What Is Zendesk Explore? Reports, Dashboards and Plan Limits Explained (2026)

Zendesk Explore is Zendesk's built-in reporting tool, included with every Suite plan, but only Suite Professional and above (Explore Professional or Enterprise) can build custom reports and dashboards. Suite Team, Suite Growth and standalone Support plans get Explore Lite, which shows Zendesk's prebuilt dashboards and refreshes once a day; Professional and Enterprise refresh hourly. Every custom report is the same shape: a metric, such as ticket count, sliced by attributes, such as channel or assignee, drawn from one dataset. Plan details below are checked against Zendesk's own documentation as of September 2026.

What is Zendesk Explore?

Explore is Zendesk's analytics layer. It connects to the data your Zendesk products already generate (Support tickets, Talk calls, Chat sessions, messaging conversations, Guide article activity) and lets you analyze it through dashboards and reports. It replaced the older "Insights" reporting (built on GoodData) and is now the native way to measure a Zendesk operation. Accounts migrated from Insights may still sit on a free "Explore Legacy" plan, which works like Professional but doesn't get features released after October 2022.

Explore is included in every Zendesk Suite plan; you don't buy it as a separate product (Support-only customers can buy Explore Professional or Enterprise as a paid plan). What differs by plan is how much you can do with it, which is where most of the confusion comes from. The mental model worth holding onto: Explore is read-only on your support data. It doesn't change tickets or run automations; it observes and reports. If you want a primer on which numbers are worth watching once you're in there, we keep a running list in Zendesk metrics to track.

What prebuilt dashboards does Explore include?

The fastest win in Explore is that you don't start from a blank page. Zendesk ships prebuilt dashboards for each of its products, and they populate automatically as soon as you have data:

• Zendesk Support dashboard: the big one. Ticket volume, who created and solved tickets, first reply time, full resolution time, reopens, CSAT, backlog, and agent/group breakdowns. For most teams this dashboard answers the bulk of "how are we doing?"
• Zendesk Talk dashboard: call volume, wait times, abandonment, talk time and agent activity for phone support.
• Zendesk Guide dashboard: knowledge base performance, including article views, searches, self-service ratio, and which articles deflect tickets.
• Messaging and Chat dashboards: conversation volume, response times and satisfaction for the web widget, mobile SDK and social channels.

Every Explore user, on any plan, can view these prebuilt dashboards. They're the baseline. The line that splits the product is whether you can go beyond them and build your own.

What are Explore datasets?

Before you can build anything custom, you have to understand datasets. A dataset is a curated collection of the metrics and attributes for one product or data source. When you start a new report, the first thing Explore asks is which dataset to use, and picking the wrong one is one of the most common beginner mistakes, because a metric simply won't exist in a dataset that doesn't track it.

The main datasets are:

• Support: Tickets (the workhorse: everything about ticket lifecycle, SLAs, and agent activity)
• Support: Updates history (granular, change-by-change ticket events)
• Talk (phone)
• Chat (legacy live chat)
• Messaging (the modern web/mobile/social messaging channel)
• Guide (knowledge base / help center)
• Sell (if you use Zendesk's CRM)

Rule of thumb: build agent and ticket reports on the Tickets dataset, channel-specific reports on that channel's dataset, and only reach for Updates history when you genuinely need to count individual changes (like how many times a ticket was reassigned).

What is the difference between a metric and an attribute?

If you learn one thing about Explore, learn this. Every field in a dataset is either a metric or an attribute, and reports are built by combining the two.

• Metrics are the numbers: the quantifiable things you measure. Ticket count, number of replies, first reply time, full resolution time, CSAT score, calls answered. Metrics get aggregated (summed, averaged, counted).
• Attributes are the descriptors: the qualitative things you slice by. Ticket status, assignee name, group, channel, priority, tags, ticket created date. Attributes don't get summed; they break a metric into segments.

The pattern of every report is the same: a metric, sliced by one or more attributes. "Number of tickets (metric), by channel (attribute)." "Average first reply time (metric), by agent (attribute), over the last 30 days (a date attribute as a filter)." Once you internalize "metrics are what I count, attributes are how I cut it," the query builder stops being intimidating.

How do you build a custom report in Explore?

Custom reports are built in the query builder (Zendesk calls a single report a "query"). The flow is consistent:

1. Pick a dataset (e.g. Support: Tickets).
2. Add a metric to the Metrics panel, say "Tickets."
3. Add attributes to the Columns and Rows panels to slice that metric, e.g. "Ticket group" on rows, "Ticket created - Month" on columns.
4. Add filters to scope it: date ranges, a specific brand, only solved tickets.
5. Choose a visualization: table, column, line, KPI, etc. Explore suggests a sensible default and you adjust.
6. Save the query so it can be dropped onto a dashboard.

Reports live independently and are then assembled onto dashboards. A dashboard is just a canvas of saved queries plus text, filters, and layout. Build the report once, reuse it on as many dashboards as you like.

How do sharing, scheduling and live dashboards work?

A dashboard nobody sees doesn't change behavior, so distribution matters.

• Sharing. Dashboards can be shared internally with agents and admins, and on Enterprise externally through link sharing with stakeholders who don't have a Zendesk seat.
• Scheduling. You can schedule a dashboard to be emailed on a recurring cadence (a Monday-morning support summary to the leadership inbox, for example), so reporting becomes a push, not a pull. A scheduled send also counts as the dashboard being accessed, which matters for the refresh rule below.
• Live dashboards (being retired). Explore has a prebuilt live dashboard that shows queue status, agent availability and channel activity, refreshing every 5 to 10 seconds. It requires at least Suite Professional: on Professional it's read-only (you can share it, but you can't clone, export, schedule, drill into it or build your own), while on Enterprise you can clone it, schedule it and build custom live dashboards and live data widgets. Two 2026 changes matter here. Only users who accessed Explore before May 5, 2026 get the live dashboard at all, and Zendesk says prebuilt live dashboards, live data components and custom live dashboards will be removed from Explore on January 25, 2027.
• Real-time monitoring (the replacement). Zendesk's newer real-time monitoring dashboards, on Suite Professional and above, cover the same ground with three use-case dashboards (incoming tickets, ticket progress and agent productivity), drill-in on every component, and up to 30 days of recent history. New teams should build their "ops wall" here, not on the live dashboard.

A related gotcha: data freshness differs by plan. On Explore Lite (Suite Team and Suite Growth included), historical data syncs once a day, at midnight in the account's time zone. On Professional and Enterprise, syncs run hourly: a new sync starts an hour after the previous one finishes, and it can occasionally take two hours or more. And if nobody opens a report or dashboard for more than 30 days, Zendesk drops the account to a weekly refresh until someone does. So if a dashboard looks "behind", it's usually the sync interval, not a bug.

Which Zendesk plan do you need to build reports in Explore?

This is the part worth pinning down before you promise anyone a custom report. Explore comes in three capability tiers, and they map to your plan (About the Zendesk Explore plan types, updated September 2026):

The headline: Lite can only look at the dashboards Zendesk built for you. It can't create custom reports or dashboards at all, and that includes Suite Growth, which many teams assume is enough. The ability to build your own reporting starts at Suite Professional, and advanced sharing and permissions are gated to Enterprise. If your team keeps hitting "you don't have permission to create this," Zendesk's own answer is that it's either the Explore plan or the user's Explore role, so check both. Zendesk's pricing page lists Suite Professional at $115 per agent a month on annual billing, against $55 for Suite Team, which is the real cost of custom reporting.

What are Explore's limits?

Explore is a capable reporting tool but it isn't a general-purpose BI tool, and a few realities catch teams out:

• It reports on Zendesk data, period. It won't natively blend in your CRM, billing system or product analytics. For cross-system reporting, Professional and Enterprise can export whole datasets as CSV files on a schedule, without the 50,000-row limit that applies to report exports, or you can pipe Zendesk data into a warehouse.
• Sync lag is real. Outside live and real-time dashboards, numbers are up to a day (Lite) or an hour or two (Professional and Enterprise) behind. Don't use a standard dashboard as a queue monitor.
• Datasets are siloed. You generally can't mix metrics from two different datasets in one report, which surprises people trying to combine, say, Talk and Tickets data in a single view.
• The learning curve is the query builder. Prebuilt dashboards are easy; custom reporting (calculated metrics, custom attributes, nested filters) has a real ramp.

What are the best practices for Explore reporting?

• Start from a prebuilt dashboard and clone it. Don't build from scratch. Copy the Support dashboard and tweak it; it's faster and you inherit sensible definitions.
• Pick the right dataset first. Decide Tickets vs. Messaging vs. Updates history before you start dragging fields, or you'll waste time hunting for a metric that lives elsewhere.
• Standardize your definitions. Agree as a team on what "resolution time" or "first reply time" means, and tie reports to your SLA policies so the dashboard and your commitments measure the same thing.
• Schedule the reports leaders actually read. A scheduled weekly summary beats a beautiful dashboard nobody opens, and it keeps your refresh rate from dropping to weekly.
• Date-filter everything. Unbounded reports get slow and misleading; default to a rolling window.

What mistakes make Explore reporting wrong?

• Chasing vanity metrics. Raw ticket volume and "tickets solved" feel good but say little about quality. Pair them with first reply time, full resolution time, reopen rate and CSAT.
• Using the wrong dataset. Building a messaging report on the Tickets dataset (or vice versa) produces numbers that look plausible and are quietly wrong.
• Confusing Solved with Closed. They're different statuses with different report implications. A "solved tickets" count and a "closed tickets" count won't match, and that's expected.
• Ignoring sync lag. Treating an hourly-synced dashboard as live, then panicking when it doesn't match the agent's screen.
• Building new work on the live dashboard. It leaves Explore on January 25, 2027. Put real-time views on real-time monitoring instead.
• Letting only one person know Explore. When the single "reporting person" leaves, the dashboards calcify. Document your custom metrics.

How does AI automation show up in Explore?

If you're running automation on top of Zendesk, it surfaces in Explore like any other activity, and that's a useful way to keep automation honest. An AI agent layer such as Macha sits on top of your existing Zendesk (it's not a help desk and not a Zendesk replacement). When it triages, drafts or resolves tickets, those actions land on real tickets, so the impact shows up in your normal Explore dashboards: first reply time, volume handled without a human, reopen rate on AI-touched tickets.

Two framings worth keeping straight. First, watch reopen rate and CSAT on AI-handled tickets, not just deflection; a high deflection number with rising reopens isn't a win. Second, on cost: Macha bills per ticket (one conversation, charged once, whether the agent summarizes, tags, routes, looks up data, drafts or resolves) on one plan priced by volume, from $299 a month for up to 750 tickets. It's never per resolution, so the bill doesn't hang on an outcome definition you don't control. Explore is where you'd check whether that work is paying off. If you want to see it in your own reporting, you can try it with $50 of free usage, no credit card required.

Frequently asked questions

What is Zendesk Explore? Zendesk Explore is Zendesk's reporting and analytics product. It connects to the data your Zendesk products generate (Support, Talk, Chat, messaging and Guide) and turns it into dashboards and custom reports so you can measure response times, resolution times, volume, agent performance and customer satisfaction. It's included in every Zendesk Suite plan.

Is Zendesk Explore free / included in Suite? Yes. Explore is bundled with every Zendesk Suite plan; you don't buy it separately. What changes by plan is capability: Suite Team and Suite Growth get Explore Lite, which only shows Zendesk's prebuilt dashboards, while building custom reports and dashboards requires Suite Professional (Explore Professional) or Enterprise.

What's the difference between a metric and an attribute in Explore? A metric is a quantifiable number you measure: ticket count, first reply time, CSAT. An attribute is a descriptor you slice by: status, assignee, channel, priority, date. Every report combines them: a metric, broken down by one or more attributes.

Can I create custom dashboards in Zendesk Explore? Only on Explore Professional or Enterprise. On Explore Lite you can view the prebuilt dashboards Zendesk created, but you can't create custom reports or dashboards. If you're seeing "no permission" errors when trying to build, check your Explore plan first and then your Explore role.

What is the Explore live dashboard? A prebuilt dashboard showing queue status, agent availability and channel activity, refreshing every 5 to 10 seconds. It requires at least Suite Professional, is read-only on Professional, and is only available to users who accessed Explore before May 5, 2026. Zendesk is removing it from Explore on January 25, 2027 in favor of real-time monitoring dashboards.

How often does Zendesk Explore data refresh? On Explore Lite (Suite Team and Suite Growth), data syncs once a day at midnight account time. On Professional and Enterprise it syncs hourly, starting an hour after the last sync finishes. If no report or dashboard is opened for 30 days, the refresh drops to weekly until one is.

What should you set up first in Explore?

Zendesk Explore is the lens that turns a busy help desk into something you can manage. It comes with every Suite plan, the prebuilt dashboards answer most day-one questions, and custom reporting rests on one idea: a metric, sliced by attributes, drawn from the right dataset. Get two things straight before you rely on it: your plan tier (Lite views, Professional builds, Enterprise adds advanced sharing) and your definitions, so the dashboard and your SLAs measure the same thing. Move any real-time monitoring off the live dashboard before January 2027, schedule the reports leaders read, and watch quality metrics, not just volume. Then Explore becomes the feedback loop for everything else in your Zendesk.

Explore plan types, refresh intervals and live dashboard status re-checked against Zendesk's documentation on 24 September 2026. Zendesk updates its product and plan packaging periodically, so confirm specifics in your own account before relying on them.