The first contact resolution formula is: FCR % = eligible issues resolved during the first contact ÷ total eligible issues × 100. If a team resolves 675 of 900 eligible issues during the first contact, its FCR is 75%. The useful part of that number depends on how the team defines an issue, confirms resolution and identifies related repeat contacts.
This guide explains the calculation with an original worked example, an Excel setup and practical reporting checks for BPO and customer service teams. All numbers and reporting rules in the examples are hypothetical; they are not industry targets or descriptions of any employer’s process.
Want to calculate FCR for your team? Use our free FCR Calculator to enter eligible issues and first-contact resolutions, combine non-overlapping groups and compare your target.
What is first contact resolution?
First contact resolution measures whether a customer’s issue was resolved during the initial service interaction, without requiring another contact for the same unresolved need. Genesys’ contact centre glossary describes the concept in terms of meeting the customer’s need on the first interaction and avoiding follow-up.
First call resolution usually refers to voice calls. First contact resolution can cover voice, chat, email and other channels. Keep that channel scope visible: a phone-only score cannot establish that the customer did not return through email.
Consider a customer asking how to download an invoice. If the agent explains the steps and the customer successfully obtains it during the conversation, that may satisfy the team’s resolution rule. If the customer must contact support again because the instructions were incomplete, the original issue was not resolved on the first contact.
The first contact resolution formula and denominator
FCR % = first-contact-resolved eligible issues ÷ total eligible issues × 100For this guide, the unit is a distinct customer issue represented by its initial contact. Count each eligible issue once in the denominator. Later calls or messages about that issue help establish its outcome; they are not additional new issues in this particular calculation.
Use the same starting cohort for both counts: the same team, initial-contact period, channels and eligibility rules. A dashboard based on all handled interactions or all solved tickets may use a different denominator. Record its definition before comparing its percentage with this issue-based measure.
The numerator must be a subset of the denominator. A zero denominator means there were no eligible issues to measure, so report N/A, rather than 0% or 100%. Negative counts, fractions of cases or more first-contact resolutions than eligible issues indicate a data problem.
Set the measurement rules before calculating
Write a short definition beside the report. For example: “Distinct account-access issues first handled this week; voice and chat included; outcome confirmed from the interaction and related case history; seven calendar days checked for a same-issue return.” That is an illustrative local rule, not a universal FCR standard.
- Issue matching: decide how the customer, case, product and contact reason will be linked. A new ticket number alone does not prove a new issue.
- Resolution evidence: specify what establishes that the customer’s need was met. A closed status or an agent’s selection of “resolved” may need verification.
- Observation window: define how long you check for related returns and when the clock starts. Choose a window suited to the service, then keep it consistent.
- Contact boundaries: define a call, chat session or email exchange. One chat can contain many messages; an email thread can span several service interactions.
- Transfers and follow-up: record whether a transfer within one continuous interaction is allowed, and how required callbacks or additional service work affect the result.
- Exclusions: state eligible issue types and excluded volumes before outcomes are reviewed. Track excluded categories separately so the score does not hide difficult work.
A seven-day rule needs seven complete days of follow-up for each initial contact. An issue first handled on Sunday is not fully observed just because the reporting week ended that night. Keep immature records provisional, or publish the completed cohort after the window closes. Also allow a defined lookback to distinguish a new issue from a return about an older one.
Worked example: calculate a 75% FCR rate
Suppose a completed initial-contact cohort contains 1,000 distinct issues. A rule agreed in advance places 100 issues outside the team’s eligible scope. The remaining 900 have complete outcome checks.
- 675 issues: resolved during the first contact and meet the evidence and repeat-contact rules.
- 150 issues: resolved only after additional service contact.
- 75 issues: still unresolved at the defined assessment point.
Eligible issues = 1,000 − 100 = 900
First contact resolution = 675 ÷ 900 × 100 = 75%The 150 later-resolved and 75 unresolved issues stay in this denominator. Limiting it to the 825 eventually resolved issues would produce 675 ÷ 825 = 81.82%, which answers a different question. Repeating interactions associated with the 900 original issues do not create new denominator entries.
If the business also reports an all-issue view, the corresponding result is 675 ÷ 1,000 = 67.5%, assuming those 100 excluded issues had no first-contact resolutions under that view. Label the two scopes. Neither percentage should be presented as directly comparable with a differently defined dashboard.
How to calculate FCR in Excel
Use one sheet for the underlying issue records and another for summary counts. For the example, enter:
- A2: Eligible issues; B2: 900.
- A3: Issues resolved on first contact; B3: 675.
- A4: FCR; enter the formula below in B4.
=IF(COUNT(B2:B3)<>2,"Check counts",IF(OR(B2<=0,B3<0,B3>B2,MOD(B2,1)<>0,MOD(B3,1)<>0),"Check counts",B3/B2))Format B4 as Percentage; it should show 75%. The formula flags blank or non-numeric inputs, a zero or negative eligible count, negative resolutions, fractional counts and resolutions above the eligible total. It validates arithmetic inputs, not whether a case was truly resolved. Some Excel regional settings use semicolons instead of commas between arguments.
Do not multiply the division by 100 again when the result cell uses percentage formatting. Store 75% as 0.75. For underlying records, useful columns include an anonymised issue key, initial-contact date, channel, reason, eligibility, outcome evidence, related-return flag and observation-complete flag. Avoid placing customer personal data in a public worksheet.
How to combine team FCR results correctly
Use counts when combining non-overlapping groups that follow the same rules. For example:
- Team A: 90 of 100 eligible issues resolved first time = 90%.
- Team B: 180 of 300 eligible issues resolved first time = 60%.
- Combined: (90 + 180) ÷ (100 + 300) × 100 = 67.5%.
A simple average of 90% and 60% gives 75%, overstating the combined result because it treats both teams as if they handled the same eligible volume. Do not combine overlapping case ownership without deduplicating the underlying issues. Keep channel and contact-reason views available, because a change in case mix can move the total without an improvement within either group.
Repeat contacts, transfers and one-touch tickets
A return about a different issue is not automatically an FCR failure. A customer may obtain an invoice today and ask about a new address tomorrow. Qualtrics’ FCR guidance highlights the need to distinguish a separate problem from a return about the original one.
Apply that distinction across channels. A failed chat followed by a phone call about the same login problem is still related contact. Conversely, no return is not conclusive evidence of success: a customer could abandon the attempt or move elsewhere. Treat repeat-contact logic as an indicator and validate a sample against the actual service outcome.
A transfer during the same call can be treated differently by different reporting rules. A stricter agent-level measure may reject it, while a continuous-contact measure may permit it if resolution occurs before that interaction ends. Publish the transfer rule and track transfer rate separately. Necessary escalation should not be discouraged to protect a score.
A platform’s one-touch ticket metric is also not automatically identical to your FCR definition. Zendesk documents specific rules involving solved or closed tickets and agent replies, including cases with no agent replies. Check the product’s current calculation before using its label as a substitute for verified resolution.
What is a good first contact resolution rate?
A useful target needs a comparable service and measurement method. Product complexity, channel, issue mix, exclusions and follow-up windows can change the result. NiCE’s FCR overview cautions that there is no universal benchmark across different definitions and contact types.
Build a baseline using stable rules, then review changes within comparable categories. Moving from 70% to 75% is an improvement of 5 percentage points, or approximately 7.14% relative to the original 70%. Those are different descriptions of the same change. Show eligible volumes beside the rates so a small sample is visible.
How to improve FCR without encouraging premature closure
- Review a focused sample of failed first contacts. Reconstruct the initial request and the reason additional contact became necessary. Separate an agent knowledge gap from a missing permission, broken workflow or unresolved product problem.
- Choose a specific change. For example, if customers return because reset instructions omit a required verification step, correct the instructions and check that agents can complete the verification workflow.
- Agree on the resolution evidence. Use QA calibration sessions to align reviewers on what counts as resolved and how related returns are classified.
- Coach an observable action. Ask the agent to verify the relevant outcome before closing, when practical, and explain any genuine next steps. Avoid scripting a resolution claim that the evidence does not support.
- Recheck a completed cohort. Compare the same contact reason after the change, allowing its observation window to mature. Examine quality and customer feedback alongside FCR.
Use the AHT formula guide to understand handling time and the CSAT calculation guide to interpret satisfaction. You can calculate those companion measures with the AHT Calculator and CSAT Calculator. A fast interaction, a positive survey and a first-contact resolution each describe a different part of service performance.
Frequently asked questions
Is FCR the same as first response time?
No. First response time measures how long a customer waits for an initial response. FCR measures whether the issue was resolved during the first contact. A quick acknowledgement alone does not establish resolution.
Does FCR always equal 100% minus repeat contact rate?
Only when the two measures classify the same cohort into exactly two complementary outcomes under the same rules. Unresolved cases with no repeat, immature records or different repeat-contact denominators break that relationship. In the worked example, the 75 unresolved issues cannot automatically be labelled repeated contacts.
Can I measure FCR with a customer survey?
You can report customer-confirmed resolution among valid responses to a clearly worded resolution question. Label that denominator as responding customers or surveyed issues, as appropriate. It is a different evidence base from all eligible cases, and non-response or survey timing can affect interpretation. Keep a general satisfaction rating separate from a resolution question.
Does an essential callback count as first contact resolution?
Under this guide’s strict first-contact definition, a callback needed to complete the original issue means it was not resolved during the initial interaction. A courtesy confirmation after an already completed resolution is different. If a process inherently requires several stages, show that category separately using a declared rule.
Can an FCR calculator decide which contacts qualify?
A simple percentage calculator can divide the counts you provide; it cannot verify issue identity, resolution evidence, duplicates or observation windows. Establish those rules in the source records first. Explore the CXMetricWorks tools for other service calculations.
Sources and methodology
External references support the general definitions and the named platform distinction. The worked numbers, issue-cohort convention, reporting checklist, Excel setup and improvement scenario are original teaching examples. Apply your organisation’s documented rules to live reports.