How does first contact resolution work?
- Formula: first contact resolution equals issues resolved on the first contact divided by total issues, multiplied by 100.
- Decide what counts as resolved: no repeat contact on the same issue within a window such as 7 days, or a customer confirmation.
- Tag tickets and calls by issue type so you can see which problems come back and which are solved once.
- Give front-line agents the access and authority to fix common issues without a handoff.
- Review repeat contacts monthly; each one points at a missing permission, a missing macro or a missing answer in the knowledge base.
A worked example
A meal kit company in Toronto tracked support tickets and found that delivery-address changes were being handled twice: the first agent promised a change, then a second ticket arrived because the change had not reached the warehouse system. First contact resolution for that issue type was under half. The fix was giving the support assistants direct edit access to the delivery system and a macro that confirmed the new address with a cutoff time. Repeat tickets for address changes fell to a handful a week, and the company's overall first contact resolution rose enough to notice in the satisfaction survey.
Where does first contact resolution show up in your tools?
Zendesk, Freshdesk and Gorgias can flag reopened tickets and repeat contacts from the same requester, which is the practical way to measure FCR. Phone systems such as RingCentral and Dialpad show transfers and repeat callers, and HubSpot ticket pipelines can report reopen rates by category.
Common mistakes
- Closing tickets quickly to make FCR look good, then counting the customer's angry reply as a new issue.
- Restricting agents to messages only, so every real fix requires a second person and a second contact.
- Measuring FCR without issue tags, which tells you the rate but not which problems to fix.
Why does first contact resolution matter?
Every repeat contact costs a second handling and a chunk of customer goodwill, and customers remember how many times they had to ask. First contact resolution turns support from a queue into a fix-it-once discipline. Improving it usually costs nothing but permissions and documentation, which is why it deserves a place next to response time.
How does AssistBPO handle first contact resolution?
AssistBPO support assistants are set up during onboarding with the permissions and macros needed to close the common issues on the first contact, and the team lead reviews reopened and repeat tickets each week to find what is still bouncing. First contact resolution by issue type is part of the weekly review. Where a fix needs your team, the handoff is documented so it happens once.
Tickets resolved by agents who learn your productGet a staffing plan