First contact resolution: the metric that quietly sets your volume
A quality metric on paper, a volume metric in practice
First contact resolution — the share of contacts fully resolved in one interaction, with no follow-up needed — lives in the quality column of most scorecards. That framing undersells it. For the workforce planner, FCR is one of the most important volume levers in the building, because every contact that isn’t resolved the first time comes back as a second contact, and sometimes a third. The customer who didn’t get their answer doesn’t go away; they re-enter the queue, and the planner has to forecast and staff for them all over again.
That makes FCR a number that sits underneath the volume forecast, silently inflating or deflating it. Improve FCR and tomorrow’s demand falls without a single customer being turned away. Let it slip and demand rises even though nothing changed about how many customers you have or what they wanted. A planner who treats FCR as someone else’s metric is missing one of the few demand levers the operation actually controls.
The repeat-contact multiplier
The arithmetic is unforgiving. If FCR is 70%, then 30 of every 100 contacts generate a repeat — and a share of those repeats fail too, generating a third contact. The total volume an underlying need produces is therefore not the number of needs but the number of needs amplified by the repeat chain. Drop FCR by a few points and you don’t add a few points of volume; you add the whole geometric tail of repeats behind them. This is exactly the failure demand loop, seen from the metric that measures it most directly.
Why it’s hard to measure honestly
FCR is genuinely difficult to measure, and the easy ways of measuring it are the misleading ones. Asking the agent “did you resolve it?” flatters the number, because the agent who didn’t resolve it often doesn’t know. Asking the customer (a post-contact survey) is more honest but biased by who responds. The most reliable signal is behavioural: did this customer contact again, about the same thing, within a sensible window — a few days for most issues, longer for complex ones? That requires linking contacts to a customer and a reason, which many operations can’t do cleanly, and it’s why FCR is so often quoted with false confidence. Measure it by repeat behaviour where you can, treat agent-reported FCR with suspicion, and be honest about the window you’ve chosen.
What the planner does with it
Three things. First, track it as a demand driver, alongside volume and AHT, and watch it for drift — a slide in FCR is a leading indicator of a volume rise that hasn’t arrived yet. Second, connect it to the forecast: an FCR change is a legitimate, quantifiable adjustment to projected volume, and one of the few you can defend with a clear mechanism. Third, build the business case for fixing it: a point of FCR has a pound value in avoided repeat contacts, and the planner is usually the only person who can size it across the whole operation. Pair that with the quality team, who own the resolution behaviours, and you have a genuine demand-reduction lever rather than just another scorecard number to defend.
The reframe is the takeaway: FCR is not a soft quality metric the planner can leave to QA. It is a volume control, and one of the highest-leverage ones available — because the cheapest contact to handle is the second one you never receive.
Pair this with failure demand, linking QA to the staffing plan, and decomposing demand by call reason.