When you use Zendesk to support customers, a question that people commonly ask is “How long does it typically take for one of my agents to respond to a ticket after it’s first created?”
Zendesk Support records the time from when a ticket was created to the first public agent response. Zendesk Explore reads this value and makes it available in a metric named First reply time.
This article describes how first reply time works and how you can use it in your reports.
This article contains the following sections:
Related article:
How first reply time is calculated
The Zendesk first reply time metric measures the time between ticket creation and the first public agent comment after that.
After the first public reply, the system calculates the first reply time in calendar hours and business hours. Both metrics are stored with the ticket data, so you can use either (or both) to build reports.
First reply time works essentially the same way regardless of the channel from which the ticket originated. For example:
- A customer email creates a ticket. Timing starts when the ticket is created and ends at the first public agent comment.
- An agent creates a ticket. Timing starts when the ticket is created and ends at the agent's next public comment.
- An agent takes a phone call that creates a ticket and solves the ticket with no new comment. The customer later re-opens the ticket, and the agent then responds with a public comment. First reply time ends when that comment is posted.
When an agent adds a public comment from another account using ticket sharing, this doesn't count toward your account's first reply time.
Additional details for messaging and live chat first reply time
First reply time is calculated exclusively based on agent replies. That means automated or bot-related actions in conversations aren’t considered when calculating the first reply time. Across all channels, ticket creation starts the first reply timer. Live conversation channels are no exception. However, because public replies aren’t an agent response option for live chat and messaging tickets, the actions that stop the timer are different:
-
On messaging tickets, the timer stops
when the agent clicks Send on their first
Messaging reply to the conversation.
-
On live chat tickets with reply-time SLAs
turned on, the timer stops when the agent
clicks Send on their first comment in the
conversation.
Messaging and live chat tickets also have an additional metric: First reply time (sec). This metric is often a more accurate measure of first reply times for tickets from live conversations, which tend to move more quickly than tickets from other channels. Unlike the standard First reply time metrics, the First reply time (sec) metric ignores your messaging business hours and live chat operating hours settings.
Reporting first reply time
The following sections describe how to use the Zendesk reporting tools to read first reply time information.
Reporting using Explore
Explore reads first reply time information from Support. The reports:
- Read data from Support using the Zendesk API. They do not calculate calendar hours or business hours.
- Display information on pre-built reports in calendar hours. However, metrics for business hours are available and can be used in your own reports.
See Metrics and attributes for Zendesk Support, Metrics and attributes for Zendesk messaging, and Metrics and attributes for live chat.
Reporting using External analytic tools
If you're not using any Zendesk reporting methods, you can still read first reply time information using the Zendesk API. The first reply time information in calendar hours is stored together with the first reply time in business hours and clearly labelled. See API metrics documentation.
Reporting using the legacy Reporting Overview
The legacy Reporting Overview is not available if your plan includes Zendesk Explore.
The reporting overview can:
- Display the first reply time metric directly from Zendesk Support
- Display calendar hours only; business hours are not displayed
- Display average reply time for all tickets
Zendesk SLAs and first reply time
A service level agreement, or SLA, is a policy you define that specifies and measures the response and resolution times that your support team delivers to your customers. To determine these times, your SLA policies may also use the first reply time metric.
However, there are differences in the way that the first reply time metric work with SLAs:
- If a ticket is created with a public comment from an agent, the SLA first reply time target is not run.
- If a ticket is created with a private comment, the SLA
first reply time target will not start until the ticket gets
a first public comment from an end user.
An exception to this rule is that if the requester is a light agent, the first reply time SLA target starts at creation even without a public comment.
- SLA first reply time targets are fulfilled when a ticket is solved, even if the ticket never had a public comment from an agent.
- SLA targets can be run in calendar or business hours, but not both.
- Business hour SLA targets pause outside business hours, then restart when business hours begin.
For more information, see Defining SLA policies.
66 comments