First Reply Time in Zendesk: How to Measure It (and What Changes It)

First reply time (or first response time) is one of the core support KPIs: how long until a customer gets their first meaningful reply from an agent. In Zendesk you can report on it with Explore—but you need a clear definition, the right time basis (business vs calendar hours), and a sense of what actually moves the number. This post covers both: how to measure it and what changes it.

How to measure first reply time in Zendesk

Zendesk Explore has built-in support for first reply / first response time. In short:

• Metric — Time from ticket creation to first public agent reply (excluding automated replies if that’s your definition).
• Time basis — Business hours vs calendar hours: for teams that don’t work 24/7, business hours usually give a fairer picture.
• Aggregation — Median (recommended) or average; use the same everywhere and in your SLA.
• Trend — Report over time (by day or week) and compare to last period.
• Breakdown — By group, tag, or channel so you see where first reply time is slow.

For a full step-by-step, see How to report on first reply time in Zendesk and First reply time in Zendesk.

What changes first reply time

1. Volume and capacity — When ticket volume or backlog grows and you don’t add capacity, first reply time tends to rise. Check volume and backlog when FRT spikes; see ticket backlog dashboard and support metrics dashboard.
2. Triage and routing — Tickets that sit in a shared queue before assignment lengthen first reply time. Better routing and time to first assignment can help; see reduce first response time.
3. Templates and macros — A fast, meaningful first reply (e.g. “We’re looking into it”) can be sent quickly with macros; that lowers FRT without sacrificing quality.
4. Coverage — If first reply time spikes at certain times, you may need better coverage (shifts, part-time, or overflow).
5. Definition and time basis — Switching to business hours or excluding auto-replies can change the number; don’t change definitions without documenting and communicating.

For more levers, see How to reduce first response time.

What to do when first reply time spikes

1. Check volume and backlog — Is capacity the issue?
2. Check segments — Which group, tag, or channel is slow? Focus there.
3. Drill to tickets — Open the list of slow first-reply tickets so you can fix patterns (e.g. a tag that always waits).
4. Tie to one action — One triage, one process change, or one capacity decision; don’t try to fix everything at once.

For a full set of metrics and a weekly cadence, see support metrics dashboard and support ops metrics.

Track first reply time without exports — start free