First call resolution rate
First call resolution rate (also called first-visit resolution) is the percentage of service jobs a technician resolves completely on the initial visit, with no return trip required for the same reported issue.
The inputs.
- Jobs resolved on first visitJobs a technician resolves completely on the initial visit, with no return trip for the same reported issue.
- Total jobs completedJobs completed in the period, excluding visits scoped as planned multi-visit work from the start.
- Mirror metricCallback rate is the same underlying event from the opposite side — the share that needed a return trip.
How to read first call resolution.
How to calculate first call resolution rate
First call resolution rate equals jobs resolved on the first visit divided by total jobs completed in a period, excluding visits that were only ever scoped as multi-visit (a planned project with phased work, for example, isn't a first-call-resolution failure). The count of "not resolved" jobs is effectively the source data for callback rate, so the two metrics are two views of the same underlying event.
Why first call resolution matters for commercial contractors
A return trip costs a second dispatch, a second technician-hours line, and often a second set of parts — all against the same invoice or the same agreement-covered visit. On a book of business with 10 to 200 techs, a few points of first call resolution swing directly into margin, and it's one of the clearest signals a commercial customer's facilities team uses to judge whether a contractor is reliable enough to keep on a multi-site agreement.
What drives first call resolution
The biggest levers are parts availability — showing up with the right part the first time instead of diagnosing, leaving, and returning — accurate skill-to-job matching at dispatch, and visibility into the equipment's service history so the technician isn't diagnosing blind. All three depend on the technician having real data in hand before or during the visit, not just a work order description.
How Thermal tracks first call resolution automatically
Thermal links every work order outcome back to the specific equipment record, so a return visit against the same unit within a defined window is detected automatically rather than requiring someone to manually flag it as a repeat. That same equipment record carries prior service history and installed parts into the technician's hands before the visit, which is the data first call resolution actually depends on.
Questions attached to this term.
What's the difference between first call resolution rate and callback rate?
They're inverse views of the same event: first call resolution rate counts jobs closed successfully on the first visit, while callback rate counts the jobs that needed a return trip. A shop can track either or both.
What's a good first call resolution benchmark?
There's no single defensible figure — it varies by trade, equipment mix, and parts strategy, so treat it as a number to improve against your own baseline rather than an external target.
How does parts stocking affect first call resolution?
Directly — a large share of failed first-visit resolutions trace back to a technician not having the right part on the truck, which is why inventory visibility at dispatch time matters as much as technician skill.
Does first call resolution apply to preventive maintenance visits?
It's usually tracked for reactive repair calls rather than PM visits, since PM visits are scoped as inspection-and-maintenance work rather than a fault to resolve — though a PM visit that surfaces a repair need can still roll into the same equipment history.
These numbers, on your own book.
If you want to see them calculated from real work orders and agreements rather than a spreadsheet, that's a demo.