What is first contact resolution?

Why it matters

Every additional touch on a ticket costs money and erodes goodwill. A second contact roughly doubles the handling cost of an issue and signals to the customer that the first attempt failed. Raising FCR is one of the rare levers that improves experience and cost at the same time, with no trade-off to manage.

What to know

• FCR is usually measured over a rolling window, commonly seven days, to catch delayed repeat contacts.
• Transfers between agents break FCR even when the customer perceives one continuous conversation.
• Low FCR concentrated in one topic almost always points to a knowledge gap rather than an agent skill gap.
• Automation raises FCR sharply for routine questions and can lower it for complex ones if handoff is clumsy.
• Measuring FCR by customer perception, through a single survey question, often beats measuring it by ticket data.

How to calculate it

An example

Example: a customer asks why an invoice looks wrong, gets a complete explanation and a corrected invoice in the same conversation, and does not contact support again. That is a first contact resolution. If the agent promises to check with billing and replies tomorrow, it is not.

Common mistakes

• Measuring FCR per ticket rather than per underlying customer issue
• Ignoring cross-channel repeats, where a chat becomes an email
• Pushing agents to close fast, which trades FCR for reopen rate
• Setting one FCR target across wildly different issue types

Questions