How to Report First Contact Resolution in Zendesk

Last updated: March 16, 2026

How to Report First Contact Resolution in Zendesk

First contact resolution (FCR) measures the share of issues resolved in the first interaction, without follow-up or repeat contact. It is one of the best indicators that your support process is both efficient and effective.

It is also a metric that trips teams up, because Zendesk does not hand you a perfect one-click FCR report. You need a definition your team trusts. This guide shows how to define FCR in Zendesk, how to build a workable report, and how to keep the number honest.

Start with the definition

Before you open Explore, decide what counts as first contact resolution for your team.

A practical definition for email-based support is:

  • the issue is solved after the first public agent reply
  • the customer does not send another message about the issue
  • the ticket is not reopened within a review window

A common review window is three to five business days. That protects the metric from false positives where the ticket is solved immediately, then reopened the next morning.

Why FCR matters

High FCR usually means:

  • agents have the context and authority to solve the issue
  • routing gets tickets to the right person early
  • your knowledge base and macros support fast, accurate resolution
  • customers do not need repeated follow-up to get an answer

Low FCR often shows up alongside high reopen rate, poor CSAT, and longer resolution time.

How to build the report in Zendesk

Option 1: Operational FCR using ticket rules

This is the simplest and most maintainable method.

  1. Create the logic for what counts as an FCR candidate. Example: ticket solved after one public agent reply.
  2. Add a tag or custom field such as fcr_candidate when the rule is met.
  3. Remove or override that flag if the ticket is reopened or receives another customer reply inside the review window.
  4. Report on the final field in Explore as your numerator.
  5. Divide by total solved tickets for the same period.

This approach is easier to trust than rebuilding the logic inside every report.

Option 2: Analytical FCR using Explore event data

If your team is comfortable with Explore modeling, you can approximate FCR from update sequences:

  • count tickets with one public agent reply before solve
  • exclude reopened tickets
  • exclude tickets with later customer responses tied to the same issue

This approach is flexible but more fragile, especially if ticket workflows vary by channel.

Best ways to segment FCR

FCR becomes much more useful when broken down by:

  • Group - Which teams solve issues in one touch most often?
  • Channel - Chat usually behaves differently from email.
  • Issue type - Password reset and refund requests should not be compared with bug investigations.
  • Assignee - Useful for coaching when interpreted alongside complexity.
  • Tag or form - Helps identify root-cause categories that create repeat contact.

What good FCR looks like

A healthy FCR pattern usually includes:

  • stable or improving CSAT
  • low reopen rate
  • reasonable resolution time
  • no evidence that agents are solving tickets too aggressively just to protect the metric

If FCR goes up while reopen rate also goes up, your team may be closing tickets too early.

Common mistakes

1. Counting every fast solve as FCR

Speed alone is not enough. If the customer comes back, the issue was not resolved on first contact.

2. Using the same definition across all channels

Chat, phone, and email often require different FCR logic. Keep the definition comparable, but do not force identical workflow assumptions everywhere.

3. Ignoring ticket complexity

A lower FCR rate may be normal in queues that handle highly technical or multi-step issues.

4. Using FCR as the only quality metric

FCR is powerful, but it is not sufficient on its own. Always pair it with reopen rate, CSAT, and touches per ticket.

How to improve FCR

  • Improve routing - First contact resolution starts with sending the ticket to someone who can actually solve it.
  • Empower agents - Reduce approvals for common fixes.
  • Strengthen macros and knowledge - The fastest path to better FCR is often better decision support.
  • Audit repeat-contact themes - Look for issue types that routinely require extra touches.
  • Review solved-too-soon patterns - If tickets reopen quickly, your solve criteria may be too loose.

Add FCR to your dashboard

FCR should sit beside reopen rate, resolution time, and first reply time in your support metrics dashboard. Together those metrics show whether the team is fast, accurate, and durable in its resolutions.

FAQ

What is a good FCR benchmark? Benchmarks vary widely by issue type and channel. A better starting point is your own baseline by queue, then improvement over time.

Is reopen rate the same as inverse FCR? Not exactly. Reopen rate is a strong quality signal, but FCR is about one-touch resolution at the front of the interaction. They are related, not identical.

Should I track FCR per agent? Yes, but only with context. Complexity, ticket mix, and authority level all influence the score.

Track one-touch resolution without wrangling Zendesk exports - start free