First call resolution is the share of contacts solved without the customer coming back. How to define and measure it without gaming the number, and the changes that move it.
First call resolution (FCR) is the proportion of customer contacts fully resolved in the first interaction, with no callback, no follow-up ticket and no second attempt by the customer. It correlates with satisfaction better than almost any other support metric, because a repeat contact means the customer spent their time twice on the same problem. It is also one of the easiest metrics to report favourably while the underlying experience stays unchanged, which is why the definition matters more than the number.
Never set first call resolution as an individual agent target on its own. It rewards closing tickets prematurely and discourages the escalations some problems genuinely need. Measure it at team and journey level.
Teams under pressure on average handle time will end conversations early; teams pushed only on resolution will over-invest in simple cases. The useful pairing is first call resolution with contact rate per customer: if resolution rises while contacts per customer fall, the improvement is real. If resolution rises and total contacts stay flat, the definition is probably leaking.
Ettex Chat helps on the operational side: conversation history per customer across sessions, so an agent can see whether this is a repeat before answering, and canned responses that keep the correct answer one click away. Repeat contacts become visible in the history rather than hiding behind a closed ticket.
Commonly quoted benchmarks sit between 70% and 80%, but the definition varies so much that comparing your own trend over time is more useful than comparing to a benchmark.
First contact resolution covers all channels — chat, email, messaging — while first call resolution originally referred to telephone support. Most teams now use them interchangeably.
Use a repeat-contact window: check whether the same customer contacts again about the same issue within seven days. Surveys add perception but are usually answered by too few customers to drive operations.
Async is not just slower chat. It is a set of habits — writing decisions down, replying in full, and not expecting an answer within minutes — and adopting the tools without the habits makes things worse.
An escalation matrix exists so that nobody has to decide, during an incident, whether this is bad enough to wake somebody. That decision is made in advance or it is made badly.
Below a certain volume a shared mailbox beats a help desk, and above it the mailbox quietly starts losing people. Knowing which side you are on is the whole decision.