race, runner, running, time, chronometer, competition, marathon, woman, man, hand, timing, measure, endurance, athlete, gap, advantage, marathon, marathon, marathon, marathon, marathon, advantage, advantage
Photo by Tumisu on Pixabay

Support Reporting

Part of Support reporting technology

Measuring first response and resolution time separately

Define separate clocks for first response and resolution, then check time anchors, office hours and cases missing a measured duration.

Measure first response from the defined start of a case to its first qualifying team reply. Measure resolution from the case start to the completion event your team accepts. Keep them as separate series: one describes the initial wait, the other time to completion. Neither proves the customer received a useful answer.

Define the two clocks

For each measure, record its start, end, unit, service-hours setting and eligible cases. Decide whether a response must be a public human reply, whether a bot answer counts, and how to report a case closed without one. For resolution, decide whether to use the first completion or the latest completion after a return.

MeasureStartEndPopulation question
First response timeInitial customer contact or case creation, as definedFirst qualifying replyWhere do cases with no qualifying reply appear?
First resolution timeCase startFirst recorded resolutionHow is later reopened work shown?
Full resolution timeCase startLatest recorded resolutionHow are never-resolved and currently reopened cases shown?

These are reporting choices, not universal vendor labels. Zendesk measures first reply time from ticket creation to the first public agent response, with calendar- and business-hours values available for reporting. Check each vendor's definitions before placing results in one benchmark chart.

Label the reporting window

A case can arrive on Monday, receive its first reply on Tuesday and resolve on Friday. Grouped by creation date, a chart can place both durations under Monday; grouped by reply or resolution date, it can place them on different days. Record the event that assigns each result to a week before comparing weeks.

Also decide whether the clock runs continuously or only during stated service hours. An overnight wait can have different values under those settings even though the contact time is unchanged. Zendesk records calendar- and business-hours first-reply values.

Name the service-hours setting used on the chart.

Keep missing durations visible

A median first-response time describes cases with a measured first response. It says nothing by itself about customers still waiting. Show the number awaiting a qualifying reply beside the duration.

For resolution, show never-resolved and currently reopened cases separately from completed cases. A reopened case may retain an earlier resolution value, so current status and the chosen endpoint both matter.

For a reporting check, consider a case that receives a reply but remains open, one closed without a human reply, and one resolved then reopened. Establish where each would appear and why before setting a target.

Reporting Validation Steps for Missing Durations

  • Show number of cases awaiting a qualifying reply alongside median first-response time
  • Display never-resolved and currently reopened cases separately from completed ones
  • Distinguish between resolved cases that were later reopened
  • Test edge casesreply without closure, closed without human reply, resolved then reopened
  • Confirm where each case type appears in reports before setting targets
  • Source

More in Support Reporting