Median first reply time in Zendesk: a better FRT report for small teams
Average first reply time is easy to understand, but it is also easy to distort. A few unusually old tickets can make the whole team look slower than it usually is. That is why many support teams prefer median first reply time when they want a stable view of responsiveness.
This guide explains when median first reply time is more useful than average, how to report it in Zendesk, and how to use it in your support metrics dashboard.
Why median helps
See first response time and median first reply time in the glossary for the core definitions. In practice:
- Average is pulled up by a few very slow tickets.
- Median shows the middle experience for the typical ticket.
- Median is often better for weekly trend because it is less noisy.
That makes median especially useful for small teams, where one weekend queue issue or one misrouted escalation can swing the average dramatically.
How to report median FRT in Zendesk
Zendesk Explore supports first reply reporting. If your reporting setup allows a median aggregation, use it directly for first reply time and chart it over time. If not, you can still approximate the same idea by focusing on percentile-style cuts or by using a reporting layer that supports median more cleanly.
The report should include:
- Median first reply time by day or week
- Comparison to last period
- Breakdown by channel, group, or priority
- Business-hours logic if that is how your team measures responsiveness
Keep average first reply time nearby if leadership expects it, but do not let average replace the more decision-useful metric. For the standard Zendesk setup, see How to report on first reply time in Zendesk and Zendesk first reply time.
When median is more useful than average
- When a few outliers distort the story
- When you are reviewing weekly team health
- When you want a more stable service trend
- When ticket mix is uneven from week to week
Average still has a place. Finance or exec reporting may prefer a familiar mean. But for queue management and coaching, median often answers the better question: how quickly do customers usually hear back?
How to interpret the number
- Median improving while backlog is stable usually means the queue is healthy.
- Median flat but average rising often means outliers are getting worse. Investigate the slowest segments.
- Median rising with backlog usually means the team is genuinely falling behind.
- Median good overall but poor in one channel means segmentation matters more than the headline.
Do not read median in isolation. Pair it with ticket volume, backlog, and time to first assignment so you can tell whether the bottleneck is intake, routing, or reply speed.
Common mistakes
- Reporting median without business-hours clarity. If the team works defined hours, align the report to business hours vs calendar hours.
- Using only one segment. Channel and priority can change the story.
- Dropping average entirely when stakeholders still expect it. Keep both if necessary, but use median to guide operations.
- Treating median as a target by itself. A good median can still hide a bad long tail, so check outliers too.
FAQ
Is median first reply time better than average?
For operational review, often yes. It is more resistant to skew from a handful of unusually slow tickets.
Should we still report average FRT?
If leadership is used to it, yes. Just do not rely on average alone to judge queue health.
Where should median FRT sit in our workflow?
Right next to backlog and volume in your support metrics dashboard, especially for weekly review.