First Contact Resolution (FCR) is the percentage of issues fully resolved in the first interaction, with no callback, transfer, or follow-up on the same issue. It is outcome-based, not perception-based, which makes it one of the hardest support metrics to game.
At the desk, FCR is the honest test of whether the agent could actually act. A traveler calls to add a night: FCR means the agent confirms availability and rate with the supplier, modifies the booking, and sends the new voucher on that contact. “We’ll email the hotel and revert” is not FCR. On an airline customer service desk, a clean rebooking in one contact is high-value FCR; a bounce between reservations and ops is the opposite. The industry average sits around 71%, with world-class at 80% or more a level only a small minority of desks reach.
Edge cases: Supplier-dependent tickets structurally depress FCR, because the fix sits with a hotel or airline that answers on its own clock. Define FCR for these as “resolved without the traveler having to chase,” not “resolved during the first call.” FCR drops sharply when a traveler is put on hold or transferred, and complaints have the lowest FCR of any ticket type so measure it by intent, not as one blended number.
Common questions
Does a ticket count as FCR if we wait on the hotel but the traveler never has to chase? Yes, define FCR by whether the traveler re-contacts, not by whether a supplier replied instantly. If your desk owns the chase and closes the loop, it is first-contact resolution.
Is AI FCR comparable with human FCR? Only if both measure confirmed resolution. AI “resolution” often counts a silent customer as resolved, so compare like for like before benchmarking one against the other.