First Contact Resolution: solving issues on the first contact
First Contact Resolution (FCR) is the share of requests fully resolved during the first contact without repeat contacts, escalations, or transfers within an agreed window (e.g., 24–72 hours). High FCR reduces team workload, raises CSAT/NPS, and lowers service costs.
What the metric measures
The team's ability to close issues in the first interaction across phone/chat/email/in-app channels, taking into account priorities, request types (reason codes), customer segments, and case complexity. It is important to distinguish resolution at first contact from "cosmetic closure."
Calculation
- FCR, % = Requests resolved at first contact / All relevant requests × 100
- Eligibility: exclude duplicates, spam, and requests that require mandatory follow-ups (KYC, technical site visits)
- Validation window: repeat contacts on the same topic within 24–72 hours void FCR
- Verified FCR (based on customer feedback) vs Operational FCR (based on system statuses)
- Phone: count without cold transfers; chat: one session with no repeat contact; email: one thread
Fix the rules: what counts as "the same request," how repeats are identified (ticket linking), what the window is, and whether bots/auto-replies are counted.
Calculation example
800 tickets came in a month: 600 were resolved on the first contact and 200 needed a repeat contact or a hand-off to another specialist. FCR = 600 / 800 × 100 = 75%. Payment questions cause the most repeat contacts, so the first line should get more authority there.
Data sources
CRM/Helpdesk/ITSM (triage, statuses, linked tickets), telephony/ACD/IVR, chat platforms, product analytics (repeat identification), QA monitoring of conversations, CSAT surveys/post-contact micro-surveys.
Interpretation
- FCR↑: high-quality diagnostics, knowledge of the knowledge base/scripts, first-line access to resolution tools
- FCR↓: knowledge gaps, missing access rights, complex verification processes, lack of integrations
- Assess the balance with AHT: cutting handle time too much can lower FCR and CSAT
- Compare FCR with Repeat Contact, Reopen Rate, CSAT, and escalations
Useful breakdowns
- Channel (phone/chat/email/in-app) and language/region
- Request type (reason code), product/service
- Priority/Severity; new vs returning customers
- Team/agent/shift; time of day/day of week; VIP/SLA segments
Dashboard visualizations
- FCR% and Repeat Contact% trend with target corridors
- FCR heatmap by channel/team/topic
- Pareto of reasons that block FCR (access rights, integrations, knowledge)
- Correlations FCR ↔ CSAT/NPS/AHT/TTR
- Funnel: created → first contact → resolved at 1st contact → escalation/repeat
How to set targets
Set targets by channel: phone/chat 70–85%, email 50–70% (market benchmarks depend on the domain). Define the validation window (e.g., 48 hours), requirements for linking repeats, first-line access rights, escalation scenarios, and knowledge-centered service.
Common mistakes
- Counting an "auto-reply" or bot as agent FCR
- A repeat validation window that is too short/too long
- No ticket linking → understated Repeat/overstated FCR
- Focusing only on FCR without monitoring CSAT/Quality Score
- Unequal conditions across channels/priorities
Questions for discussion
- Which topics most often require repeat contacts, and why?
- What access rights/integrations does the first line need to grow FCR?
- What is the impact of training/scripts/the knowledge base on FCR and AHT?
- Is the mechanism for linking repeat requests working correctly?