First vs Full Resolution Time: What They Mean Operationally

Resolution time can mean two things: first resolution (time until the ticket is first marked solved or closed) and full resolution (time until the ticket is finally closed, including any reopens). Both matter operationally. This post explains the difference and when to use each.

Definitions

• First resolution time — Time from ticket creation to the first time the ticket is marked solved (or closed). If the customer reopens, that “first solve” is still the end point for this metric.
• Full resolution time — Time from ticket creation to the ticket’s final close (after any reopens). This is the total time the customer waited for a complete resolution.

For formal definitions, see resolution time and average resolution time in the glossary.

When to use which

• SLA and “time to close” — Many teams use full resolution for SLA and for “how long did the customer wait in total?” So: report full resolution for targets and for customer-facing commitments.
• Process and quality — First resolution tells you “how fast we thought we were done.” If first resolution is short but reopen rate is high, you may be closing too early. If first resolution is long, you may have process or complexity issues. See ticket reopen rate and Zendesk resolution time report.

So: report both if you can—first resolution for process, full resolution for SLA and customer experience. Use the same definition everywhere (e.g. to “closed” in Zendesk) and the same time basis (business hours if you don’t work 24/7).

How to report in Zendesk

Zendesk Explore supports resolution time metrics. You need to define:

• End state: “solved” vs “closed” (and whether you count first solve or final close).
• Time basis: business hours vs calendar hours.
• Aggregation: average or median.

For step-by-step, see Zendesk resolution time report. For how resolution time fits with first reply time, see first reply time in Zendesk and support metrics dashboard.

What to do when resolution time spikes

1. Check if reopens went up — If reopen rate rose, full resolution time can rise because tickets are solved, reopened, and solved again. Focus on quality and handoff; see ticket reopen rate.
2. Check segments — Which tag, group, or priority got slower? Focus there (knowledge, process, or staffing).
3. Drill to tickets — Open long-resolution tickets so you can spot patterns.

For a weekly cadence that includes resolution time, see support ops metrics and support dashboard template.

See resolution time and trends — start free