Closure Rate vs. First-Contact Resolution

Closure rate tells you how many tickets your team closed.

First-contact resolution tells you how many problems your team actually solved.

They are not the same number. In environments where closure rate is the primary performance metric and first-contact resolution is tracked loosely or not at all, the gap between the two numbers can be significant, and it is almost always invisible until someone looks for it.

What Does Each Metric Measure?

Closure rate is the percentage of tickets that move to a closed or resolved status within a defined period. It is a measure of throughput: how much work the queue processed. A high closure rate indicates that the team is working through tickets at a reasonable pace.

First-contact resolution (FCR) is the percentage of tickets resolved on the first contact, without requiring a callback, follow-up ticket, or escalation. It is a measure of quality: how effectively individual contacts are being handled. A high FCR indicates that issues are being resolved completely rather than partially.

A team can have a high closure rate and a low FCR simultaneously. Tickets that are closed without confirmed resolution, issues that reopen as new tickets within a short window, users who give up and stop contacting support rather than pursuing unresolved issues: all of these inflate closure rate without affecting FCR.

What the Gap Looks Like in Practice

Pull the contact history on your top repeat callers for any given month. In most environments running high closure rates without active FCR tracking, this list will contain users who have submitted three, five, or more tickets about variations of the same underlying problem.

Each ticket was closed. None of the underlying issues were fully resolved. The closure rate metric counted each closed ticket as a success. The FCR metric, if tracked, would show each one as a failure.

This pattern is especially visible in environments where ticket closure does not require confirmed resolution from the user. If an agent can close a ticket by selecting a resolution code without documenting user confirmation, the closure rate reflects how many times that action was taken, not how many times the problem was actually solved.

Why Does FCR Matter More Than It Looks?

First-contact resolution is the metric most directly correlated with user satisfaction, cost efficiency, and queue health.

User satisfaction: A user whose issue is resolved on first contact has a fundamentally different experience than a user who contacts support three times about the same problem. The repeat contacts erode trust in the support function regardless of how quickly each individual ticket is acknowledged or closed.

Cost efficiency: Every repeat contact is an additional ticket. An additional ticket requires triage, handling time, and documentation. In a high-volume environment, a low FCR multiplies the cost of every issue that is not fully resolved on the first contact. Improving FCR by five percentage points can meaningfully reduce overall ticket volume.

Queue health: A queue with low FCR and high closure rate will continuously generate its own backlog. Issues that are not fully resolved return as new tickets. The queue never actually clears. It just cycles.

Where the Gap Usually Lives

The most common causes of FCR gaps are not agent skill or effort. They are process and documentation issues:

Fix confirmed too quickly. The agent applies a resolution and closes the ticket before confirming with the user that the fix held. The issue recurs, and the user opens a new ticket.

Downstream dependency missed. A partial fix is applied: the primary symptom is resolved, but a related system is not updated. The user contacts support again when the secondary symptom appears.

Resolution not documented. The fix was correct, but the documentation in the ticket is insufficient. When the issue recurs with a different user or in a different context, the next agent starts from scratch rather than building on the previous resolution.

User not shown how to prevent recurrence. In cases where the issue is partially caused by user behavior, resolving the immediate symptom without addressing the underlying cause generates predictable repeat contacts.

Building FCR Into Your Reporting

If FCR is not currently tracked, adding it to your reporting does not require a major configuration change in most ITSM platforms. In ServiceNow, FCR can be measured by tracking tickets that reopen within a defined window (commonly 72 hours or seven days) after initial closure.

The operational value of adding this metric is not in the number itself. It is in what the number reveals. Organizations that add FCR tracking almost always find that their repeat contact patterns are concentrated in a small number of issue categories, agents, or time periods. That concentration is where the improvement effort should go.

Closure rate will tell you the team is working. First-contact resolution will tell you whether the work is sticking.