How to Track First Call Resolution in a Field Service Business
First call resolution (FCR) is the percentage of service calls fully resolved on the first visit. In HVAC, the benchmark is 78-88%. A tech running 65% FCR when the team average is 82% is triggering 17 callbacks per 100 jobs, each costing $85-$150 at no additional revenue.
Key takeaways
- HVAC FCR benchmark is 78-88%. Appliance repair benchmark is 65-80%. A tech at 65% FCR on a team averaging 82% generates 17 unnecessary callbacks per 100 jobs.
- Each callback costs $85-$150 in labor and parts at zero additional revenue. At 17 callbacks per 100 jobs, that is $1,445-$2,550 per 100 jobs in lost margin.
- A customer who receives a callback within 14 days has a 35% lower probability of leaving a 5-star review.
First call resolution (FCR) is the percentage of service calls fully resolved on the first visit without a callback, warranty return, or rescheduled repair for the same issue.
In HVAC, the industry benchmark is 78-88% FCR. In appliance repair, 65-80%. A tech running 65% FCR when the team average is 82% is generating 17 callbacks per 100 jobs. At $85-$150 in labor and parts per callback with no additional revenue, that is $1,445-$2,550 in lost margin per 100 jobs before any customer satisfaction impact is counted.
Most field service businesses do not track FCR systematically because it requires matching return jobs to original jobs, which is a data setup step most CRMs do not do automatically. This post covers the setup and the coaching use cases. For the playbook to actually bring the number down, see how to reduce callbacks in a field service business, and for the tech-level metrics view, technician performance metrics for home services.
Defining FCR for Your Business
Before you can track it, you need a specific definition that your CRM can support. Two decisions:
What counts as a callback? The standard definition is a return visit for the same complaint within a fixed window. The most common window is 14 days. Some businesses use 30 days. Anything beyond 30 days is difficult to attribute with confidence, because new failures on the same equipment are legitimately different events.
The 14-day window is the right starting point. It captures genuine first-visit failures without pulling in coincidental equipment failures weeks later.
What job types are excluded? Planned second visits (part orders where the repair is intentionally split across two days), customer-requested return visits for unrelated work, and follow-up inspections booked at the customer's request are not callbacks. Your definition needs to name these exclusions explicitly or your FCR number will be artificially low.
Write the definition down. Put it in your dispatcher's operating guide and your CRM tag dictionary. If two dispatchers would classify the same job differently, the definition is not specific enough.
Text Clint: "what is our callback rate by job type in the last 60 days, broken down as return visits within 14 days of the original job?"
How to Track It in Your CRM
FCR tracking requires two things in your CRM: a way to tag a job as a callback, and a way to link it to the original job.
ServiceTitan has the most native support. The Return Visit job type flag is built in, and the system can link a return job to the original automatically when the customer and equipment match. Under Reports, the First Time Fix Rate report shows tech-level FCR once the job type tags are applied correctly. ServiceTitan's help documentation on Callback Reports covers the setup.
Housecall Pro does not have a native callback report, but you can approximate it with a custom job tag. Create a tag called "callback-14d" and train your dispatcher to apply it on any return visit for the same complaint within 14 days. Then run the Jobs report filtered to that tag and count by tech. This is manual but it works if the tagging discipline is consistent.
Jobber requires the same manual approach as Housecall Pro, plus a custom field on the job record for the original job number. Without the link to the original job, you can count callbacks but you cannot tie them back to the original tech. The Jobber community has long threads on this gap. Most Jobber users who track FCR seriously export to a spreadsheet and match on customer, date, and equipment.
Workiz has a callback flag on work order records. Under Reports, the Callback Rate report shows total returns by technician. Setup requires enabling the callback flag in Settings and training dispatchers on when to apply it.
Text Clint: "which techs have the highest callback rate in the last 90 days?"
Benchmarks by Trade
Use these ranges as reference points for your team, not as absolute targets. Markets, equipment age profiles, and customer base composition all affect what a realistic FCR looks like for a specific shop.
| Trade | FCR Benchmark Range |
|---|---|
| HVAC (residential service) | 78-88% |
| Appliance repair | 65-80% |
| Plumbing (residential service) | 80-88% |
| Electrical (residential service) | 85-92% |
| Garage door (residential) | 88-94% |
Garage door and electrical tend to run higher because the failure modes are more discrete and parts availability is less variable. HVAC and appliance repair run lower because refrigerant system failures, board failures, and control diagnostics produce a higher rate of "could not fully replicate on first visit" scenarios.
If your HVAC team is running below 72% FCR, the issue is likely systemic: diagnostic training, parts inventory carried on trucks, or dispatching the wrong skill level to the job type. The dispatch-side fix sits in how to schedule HVAC technicians.
Text Clint: "compare our callback rate to last quarter, split by residential and commercial jobs."
What Causes Low FCR
Low FCR in a field service business comes from four sources:
Misdiagnosis on first visit. The tech identifies a component failure and replaces the part. The system still does not work because a second failed component was missed. This is a training and diagnostic checklist issue. The fix is a structured diagnostic sequence for common failure modes, not just fixing the obvious symptom.
Incomplete repair. The tech knows what needs to be done but does not have the part on the truck or does not do the full scope. Partial repairs on HVAC or appliance systems often produce a short-term functional result that fails again within 7-14 days. Train techs to document explicitly whether a repair is complete or provisional.
Customer expectation mismatch. The tech completes the repair correctly, but the customer calls back because the system behaved in a way they did not expect. For example, a properly repaired AC unit that still does not cool to 68 degrees on a 100-degree day is working within spec, but the customer expected it to hit 68 degrees. The call-back is not a repair failure, but it gets logged as a return visit. Fix this with customer communication at the close of the job: explain what was repaired, what to expect, and under what circumstances to call back.
Dispatching mismatches. Sending a junior tech to a high-complexity first call produces higher callback rates than sending a senior tech. If you are seeing high callback rates from specific tech-equipment combinations, the issue may be dispatcher routing, not tech skill.
Text Clint: "show me which job types have the highest callback rates and which techs are associated with each."
How to Use FCR in Tech Coaching
FCR data is only useful if it changes behavior. Here is how to use it in a coaching conversation without making it a performance ambush.
Start with the pattern, not the number. "Your callback rate is 19% vs. the team average of 9%" is a statement of a problem. "Three of your last five callbacks were refrigerant-related on R-410A systems. Walk me through your leak check process on a first visit" is a coaching conversation.
The goal is to identify whether the gap is equipment-specific, job-type-specific, or uniform across all work. A tech with a high FCR only on one equipment brand or one failure type has a training gap that is fixable. A tech with uniformly high callbacks across all job types has a diagnostic or thoroughness issue.
The questions to ask in the conversation:
- What do you carry on the truck for parts on common failure modes?
- Walk me through the last callback you had. What did you find on the return visit that you missed on the first?
- What is your process for closing a job with the customer? What do you tell them?
Document the answers. Set a specific 30-day target. Check the FCR number again at 30 days.
For the customer satisfaction link: a tech with a 65% FCR rate generates a materially higher complaint volume and a materially lower 5-star review rate. The customers who call back within 14 days have a 35% lower probability of leaving a 5-star review, regardless of how the return visit goes. FCR is not just a cost metric. It is a reputation metric.
How Clint Surfaces Callback Data
Text "what is my callback rate by tech in the last 60 days?" and Clint pulls return visits within the defined window from your CRM, groups them by the original assigned tech, and shows you the FCR percentage per tech alongside their total job count.
You do not need to export a report, build a filter, or match spreadsheet rows. The query runs against your CRM data directly, and the answer comes back in the same conversation where you were looking at revenue per tech.
That combination is where the coaching conversation starts: a tech's revenue per day alongside their callback rate tells you whether a high revenue number is being produced sustainably or at the cost of return visits that erode margin and reputation. The quarterly review framework that uses this data is in how to set up employee performance reviews in a home service business.
Sources
Frequently Asked Questions
4 questions home service owners actually ask about this.
01Is a 14-day window the right callback definition for all trades?
It is the most common starting point and produces consistent, defensible data. Some HVAC businesses use 30 days because refrigerant-related failures can take several weeks to manifest. Use 14 days to start, establish a baseline, and adjust the window only if your team produces evidence that 14 days is too short for your specific job types.
02What should I do if my CRM cannot link a callback to the original job?
Use a manual tagging system with a "callback-14d" job tag and a free-text field for the original job number. It is not as clean as a native link, but it produces usable data. Export weekly, match on customer and date range, and track in a simple spreadsheet until your CRM supports it natively.
03Can high FCR happen due to reasons outside the tech's control?
Yes. Parts that fail on arrival, manufacturer defects, and customer misuse are legitimate exceptions. Track these separately with an "excepted callback" tag. Review them quarterly to confirm they are genuine exceptions and not a pattern being miscategorized as outside the tech's control.
04How do I communicate FCR benchmarks to my team without creating anxiety?
Present FCR as a shared metric, not a gotcha number. "Here is where we are as a team, here is the industry benchmark, and here is the gap we are working to close" is a productive frame. Pair the FCR number with the coaching data (equipment type, job type, diagnostic gap) so the conversation is about improvement, not blame.
See Clint in action
Clint is the pre-built AI for home service shops. Connect your CRM, email, and phone system in minutes and the agents run on your real data.