In this article, you'll learn more about some of the metrics built into Zendesk Support that help you measure the duration between two events.
Note: This article covers only the native Support metrics. SLA metrics might have identical names but their behavior is different because they are live counters. See: Defining and using SLA policies.
For more information about the metrics and attributes you can use with Explore, see Understanding Explore datasets.
The native duration metrics are not live counters, instead, they measure time duration between specific events. Support computes the time difference between two event timestamps and adds the results with the following behaviors:
- The new metric value is recorded on the ticket only after the specific events take place.
- The metric’s value will appear as null until two required events occur at least once.
This article contains the following topics:
- First reply time
- First resolution time
- Full resolution time
- Requester wait time
- Agent wait time
- On-hold time
Tip: In the graphics below, green indicates time counted and gray indicates time not counted.
First reply time
- Definition: The duration between ticket creation and the first public agent reply on the ticket.
- First timestamp: Ticket creation.
- Second timestamp: The first public comment by any agent.
- Exceptions: If the ticket is created by an agent and the first comment is public the second timestamp shifts to the second public agent comment. If the ticket is created via private sharing agreement, the first private note by any agent will be considered as the second timestamp. For more details see: Calculating first reply time
First resolution time
- Definition: Duration between ticket creation and its first resolution.
- First timestamp: Ticket creation.
- Second timestamp: The first time the ticket status is set to solved.
- Exceptions: If the unsolved ticket is set to closed by a business rule or API, this event is considered as the second timestamp.
Full resolution time
- Definition: Duration between ticket creation and its most recent resolution.
- First timestamp: Ticket creation.
- Second timestamp: The last time the ticket status was set to solved.
- Exceptions: If the unsolved ticket is set to closed by a business rule or API, this event is considered as the second timestamp.
Requester wait time
- Definition: The total combined time ticket was in the new, open, and on-hold statuses.
- First timestamp: Ticket status is changed to new, open, or on-hold.
- Second timestamp: Ticket status is changed from new, open, or on-hold to any other status.
Agent wait time
- Definition: The total combined time the ticket was in the pending status.
- First timestamp: Ticket status is changed to pending.
- Second timestamp: Ticket status is changed from pending to any other status.
On-hold time
- Definition: The total combined time the ticket was in the on-hold status.
- First timestamp: Ticket status is changed to on-hold.
- Second timestamp: Ticket status is changed from on-hold to any other status.