First Call Resolution (FCR)
Also called: FCR, one-call resolution, first-contact resolution
First Call Resolution is the measure of whether a single call fully settles the reason the homeowner rang, with nothing left over that needs a second call or a promised callback. It counts calls that were actually finished, not calls that were merely ended.
What it means
First call resolution is the share of calls where the reason the homeowner rang is fully settled during that one call, with nothing left outstanding that requires them to call back or the business to call them. It is not a measure of how the call felt; it is a measure of whether the thing they rang about actually got answered.
The distinction that matters is between a call that ended and a call that finished. Every call ends eventually — the line goes quiet and the record closes one way or another. Not every call finishes what the homeowner rang to accomplish. First call resolution only counts the second kind.
Settling the reason for calling, not just booking a callback
A homeowner rings for a reason: they want to know when the inspection is, why the cheque was smaller than expected, or whether the crew is still coming this week. First call resolution asks whether that specific question got a real answer on this call.
It is easy to confuse this with simply avoiding a second call, and the two are not the same thing. An agent who tells a homeowner “someone will look into it and call you back” has ended the call without resolving anything — the homeowner is exactly as uninformed as when they dialled, just quieter about it for now. That call generates a callback whether or not one gets promised, because the reason for calling is still open. The honest version of that same call finds the answer in the file while the homeowner is on the line, or states plainly what is not yet known and gives a specific time to expect it — which is a resolved call even though information is still outstanding, because the homeowner now knows exactly where things stand and what happens next.
A callback the homeowner themselves asks for is a different case entirely. If a homeowner calls to check status and, once answered, asks to also be transferred or scheduled for something new, agreeing to a follow-up for that new request is not an unresolved first call. The original reason for calling was settled; the follow-up belongs to a different question the homeowner raised on their own terms.
Why it is the metric most easily gamed by disposition choice
Nothing independent checks whether a call was actually resolved. The number comes entirely from the disposition code the agent selects when the call ends, and that selection is a judgment call made by the same person whose performance the number describes.
That creates a gap with no alarm attached to it. A call that plainly needed a callback — the agent could not confirm an appointment, could not find the claim in the file, told the homeowner someone would look into it — can be coded as resolved, and nothing about that miscoding produces an error, a validation failure, or a complaint. The homeowner may well call back tomorrow still needing the same answer, but by then the two calls are two separate records, and nothing connects the second one to the first as evidence the first was miscoded.
This is the same structural weakness every disposition-derived rate carries, and first call resolution is the version of it most worth watching, because the incentive runs in one direction only. An agent measured on this number has a reason to code generously and no comparable reason to code honestly, since coding a call as unresolved when it was actually fine costs nothing to anybody, while coding it as resolved when it was not costs nothing today and only shows up later, disconnected from the call that caused it.
What actually moves it
Having the answer available on the call moves it more than anything an agent does in the moment. A status question that requires looking something up in a system the agent cannot reach gets deferred by necessity, however good the agent is. Giving agents the file, the schedule, and the claim history at the point of the call turns questions that used to need a callback into questions answered on the spot.
A genuine, specific answer moves it more than a reassuring one. “Someone will look into it” ends the call quickly and resolves nothing. “The adjuster is assigned, the inspection is Thursday at nine, and here is what happens after that” takes longer to say and actually closes the loop.
Empowering the agent to finish things, not just explain them, moves it further still. An agent who can rebook an appointment, correct an address, or check a payment status without escalating resolves more calls than one who can only explain that somebody else handles that.
Common mistakes
Reading a high number without checking how honestly it is coded. A rate built entirely from self-reported dispositions is only as trustworthy as the incentive behind the coding, and a number nobody has ever pulled the underlying calls to check is a number nobody has actually verified.
Treating every callback as a failure. A callback the homeowner asked for, about something new, is not the same event as a callback caused by an unanswered original question, and folding both into one count hides which calls actually went wrong.
Chasing the number by ending calls faster. A call rushed to a close before the homeowner’s actual question is answered may still get coded as resolved, which raises the number while making the underlying problem worse.
Measuring it in isolation. First call resolution trades against handle time — genuinely settling a complicated question usually takes longer than deferring it — so reading it without also reading what happened to call length hides which direction the trade went.
On the call
Before you close any call, ask whether the homeowner would have to ring back for the same reason. If the honest answer is yes -- you promised to check something, you could not confirm a time, you did not have the file in front of you -- the call is not resolved just because the conversation is over. Find the answer while they are still on the line if it is in the file, and if it genuinely is not, say so plainly and book a specific callback with a time attached rather than a vague one. Coding a call as resolved because it ended, rather than because the question was actually answered, is the fastest way to make this number stop meaning anything.
This is how our agents handle it on roofing leads booked as appointments and day-to-day roofing answering service intake.
Questions people ask about first call resolution
- What actually counts as a first call resolution?
- A call where the homeowner's reason for ringing is genuinely settled before they hang up: no unanswered question, no promise to check and call back, no follow-up call needed to finish what this one started. Booking a new callback for a request the homeowner raised on the call, like scheduling an inspection, is not a failure. A callback needed because the original question was never actually answered is.
- Why is first call resolution the metric most easily gamed by disposition choice?
- Because whether a call counts as resolved is decided entirely by the code an agent picks when the call ends, and nothing else checks that choice against what actually happened. A call that plainly needs a callback can be coded as resolved with no error, no alert and no complaint from anybody, so a team under pressure to show a high number can get one without changing a single conversation -- only the coding habits change.
- Does a callback always mean the call was not resolved?
- No. A callback the homeowner asked for, to schedule something or continue a conversation they chose to pause, is a normal next step and not a failed first call. The distinction is whether the original reason for calling was answered on this call. If it was, a later call about something new is a different call, not evidence this one failed.
Back to the full roofing claims glossary.