First contact resolution (FCR)
First contact resolution (FCR) is the share of client requests that are fully solved in the first contact, with no callback, transfer or repeat message needed.
What it is
A client writes with a question. Either the matter is closed in that conversation, or the client has to come back, wait for a transfer or explain everything again to someone else. FCR counts the first case. It is one of the few service metrics that the client feels directly.
How it is calculated
FCR = requests solved in the first contact / all requests × 100%.
The hard part is deciding what “solved” means. A common approach: a request counts as solved if the same client did not come back about the same topic within an agreed window, for example seven days. An illustrative example: 800 requests in a month, 120 of them came back on the same topic, so FCR = 680 / 800 = 85%. Some teams also ask the client directly at the end of the conversation, but self-reported numbers tend to be optimistic.
Why it matters
Every repeat contact is paid twice: once by the company in agent time, once by the client in patience. A low FCR inflates the volume, lengthens the queue and makes the whole line look understaffed when the real problem is unsolved first contacts. It also points at the cause: missing authority, a gap in training, or a process that forces a transfer.
The typical mistake
Counting a closed ticket or a finished chat as a solved problem. An agent can close a conversation in a minute and leave the client with nothing. Measure FCR by repeat contacts, split it by request type and by person, and fix what blocks the agent from finishing the job: rights, knowledge or a rule that sends simple cases upward.
More in Signals
- Call center KPIs for messaging apps: what to measure when agents type instead of talkIn messaging apps, classic call center KPIs change meaning: average handle time loses weight, while first response time, service level, missed conversations and resolution in a single conversation move to the front. New metrics appear that calls never had: concurrent conversations and promises kept. Measure them in working hours and together, never one at a time.
- CRM for a travel agency: who owns the client when everyone writes on WhatsApp and InstagramIn a travel agency the client takes weeks to choose, writes at night and on weekends, receives dozens of options and promises to send the deposit tomorrow. When each agent runs chats on their own phone, the owner can't see who handles a client or who was lost, and when an agent leaves, last year's travellers leave too. The fix starts with rules: numbers owned by the agency, one owner per client, deposit and document deadlines tracked, and the client on a trip handled first.