A short call is not automatically a good call. First contact resolution is one of the few metrics that moves cost and customer satisfaction in the same direction.
A short call is not automatically a good call.
If a team is measured only on average handling time, it will adapt its behaviour accordingly – reliably. Calls end sooner, follow-up questions go unasked, unclear cases get transferred. The metric improves. The calls come back.
What first contact resolution measures
First contact resolution (FCR) is the share of enquiries fully resolved on first contact – no callback, no second ticket, no transfer to another department.
It is worth watching because it links two goals that usually pull against each other: an enquiry resolved the first time costs less and leaves a more satisfied customer.
Measuring it properly
The most common error is the time window. Checking only whether a second contact occurs within 24 hours misses enquiries that resurface a week later. In practice a seven-day window is usually more meaningful.
Equally important: the second contact has to be tied to the same enquiry. Without that link you are measuring contact volume, not resolution quality.
What typically drags the rate down
- Permissions: agents cannot close the case they have already solved.
- Scattered knowledge: the answer exists, but sits in a document nobody can find mid-call.
- System switching: three applications for one process create wait time and transcription errors.
- Unclear escalation paths: when in doubt, transfer – it is faster than deciding.
Notably, none of these is solved by training alone. They are process and tooling questions.
A practical starting point
Before setting targets, take stock: which five enquiries most often lead to a second contact? In most operations a substantial share of repeat contacts traces back to a small number of recurring causes. Fixing those five achieves more than a blanket target for the whole organisation.
