First call resolution (FCR)
First call resolution (FCR) is the share of eligible caller issues fully resolved during the initial call without requiring another contact or unresolved follow-up.
How first call resolution works
FCR is calculated by dividing issues resolved on the first eligible call by all eligible first-call issues in the measurement period. The difficult part is defining “resolved,” “first,” and “eligible” consistently. A caller may present several issues in one conversation, return through a different channel, or contact the business again for an unrelated reason. Those cases need an explicit measurement policy.
Organizations also differ on transfers. Some count an issue as resolved if the caller reaches the right person and finishes everything during the same call. Others exclude any transferred interaction. Neither convention is useful unless it is documented and applied consistently. The observation window matters too: an issue that appears complete at hang-up may produce a repeat contact later.
FCR should be based on the caller's underlying need, not simply the absence of another call. A caller who gives up, switches channels, or silently works around the problem has not necessarily received a resolution. Evidence may combine dispositions, repeat-contact data, completed system actions, and customer feedback.
Why it matters for AI phone calls
For an AI phone agent, FCR tests whether the conversation produced a durable result rather than only a contained interaction. An agent might avoid a human handoff yet fail to solve the issue, so containment rate and FCR should not be treated as interchangeable. Conversely, a well-executed handoff can contribute to resolution under a policy that counts same-call transfers.
Improving FCR often requires examining where the agent becomes blocked. Common causes include missing knowledge, unavailable tools, unclear verification steps, narrow permissions, and escalation rules that send the caller elsewhere. The appropriate response is not always to give the agent more autonomy; some issues require a person, offline work, or a later confirmation.
Teams should segment FCR by call reason and review it alongside repeat contacts, escalations, handle time, and customer feedback. A broad average can improve because easy calls grew while a critical workflow stayed broken. Attempts to maximize FCR can also create longer calls or discourage necessary escalation, so resolution quality should remain the goal.