Callback rate: definition, formula, and dashboard example
Callback rate measures how often a technician returns to a job that should have been done right the first time. Here is what the metric means, how to calculate it, what the numbers signal, and how to track it on a live service dashboard.
Formula
Callback rate = callbacks ÷ completed jobs × 100
Count the service calls where a technician returned to a job within a defined window (typically 30 days) because the original work was incomplete, incorrect, or failed. Divide by total completed jobs in the same period and multiply by 100. The definition of a callback, and the time window, must be fixed before you start tracking.
Some teams track a 30-day window; others use 60 or 90 days depending on trade and warranty policy. Standardize your window first and hold it constant so trends are comparable.
What is callback rate?
Picture a plumbing tech who wraps a water heater install at 3 PM, hands the homeowner a receipt, and drives to the next call. Twenty-two days later, the same homeowner calls back: the pressure relief valve is leaking. Another tech is dispatched. That return trip is a callback, and it costs the company the labor, the fuel, the parts, and the slot on the dispatch board that another paying customer could have filled.
Callback rate is the percentage of completed jobs that required a technician to return within a defined period because the work was not right the first time. It is the primary quality-of-workmanship metric for field service and skilled-trades companies. A rising callback rate eats margin, strains scheduling, and damages the company's review scores. A low and stable callback rate is a signal that your technicians are diagnosing accurately, completing jobs fully, and setting clear customer expectations.
How the math works
To calculate it, divide the callbacks logged in a period by the completed jobs in that same period, then multiply by 100. Read the rate next to the job count rather than on its own: a shop running high job volume absorbs the occasional return with less rate movement than a smaller shop does. Owners watch a number that often looks small because of what it costs. Every callback consumes a return trip's labor, parts, and a dispatch slot a paying customer could have taken, so even a low single-digit percentage erodes real margin over a month, and that cost hides inside closed-job counts that otherwise look like completed revenue.
What counts as a callback?
Not every return visit is a callback. The three types that belong in the callback count are: a rework (the repair failed or was incomplete), a wrong diagnosis (the tech fixed the wrong thing), and an improper install (a part was installed incorrectly). Return visits for unrelated new problems, agreed follow-up installs, or customer-requested warranty claims under a service agreement may or may not count, depending on your definition. The key is to document the definition in your CRM and apply it consistently. How it reaches a datacube board depends on the CRM: in ServiceTitan the count is the Recalls Caused figure on the Technician Performance Report (datacube shows it as Recalls on the service board and Callbacks on the install board); in Housecall Pro it is the number of completed jobs flagged Call back = Yes on the Profit-by-date report. The raw metric datacube pulls is the callback count per technician; the rate is that count over completed jobs for the same period.
Who owns callback rate and how often to review it
The service manager owns callback rate. Field supervisors and dispatch managers use it to catch patterns before they become customer complaints. Review callback rate weekly by technician (it sits alongside technician scorecard metrics and revenue per technician) and monthly at the department level. A live dashboard showing callback rate per tech, updated from your CRM, is how you move from a lagging monthly report to an in-the-moment quality signal.
Callback types: what to count and what to separate
| Callback type | Counts in rate? | Root cause | Improvement lever |
|---|---|---|---|
| Failed or incomplete repair | Yes | Job closed before root cause was fixed | Dispatch checklist; tech review before close |
| Wrong diagnosis | Yes | Rushed troubleshooting or training gap | Ride-along review; diagnostic training |
| Improper install | Yes | Tech skill gap or parts mismatch | Senior tech sign-off on installs; parts QC |
| Unrelated new problem | No | Different system failure, not the prior job | Log separately; track as new demand |
| Agreed follow-up install (multi-day job) | No | Planned; dispatched intentionally | Tag in CRM as a continuation, not a callback |
| Warranty service call (within agreed contract) | Depends on policy | Part failure within warranty window | Track separately so you can spot recurring part defects |
What callback rate movement signals
There is no single universal target. Set your baseline from the past 90 days and treat the signals below as directional reads, not industry rules. Targets vary by trade, technician experience mix, job complexity, and how strictly the CRM flags a return visit.
- Callback rate trending down over 60 daysQuality improvements are holding; coaching and checklist changes are workingGood
- Current
- Target
- Callback rate flat and below your internal targetStable quality; review tech-level breakdown to find outliers to coachGood
- Current
- Target
- Callback rate flat but above your internal targetProblem is not getting worse but it is still costing margin; identify the repeat offenders by job typeWatch
- Current
- Target
- One tech's callback rate is 3x the team averageIsolated to one person: coaching or retraining opportunity before it becomes a review problemWatch
- Current
- Target
- Callback rate spikes after onboarding new techsExpected with new hires; pair them with senior techs and set a 90-day ramp targetWatch
- Current
- Target
- Callback rate climbing while completed jobs are also climbingGrowth is stressing quality; dispatching too fast without enough oversightPoor
- Current
- Target
- High callback rate with declining average star ratingQuality failures are reaching public reviews; act before the pattern compoundsPoor
- Current
- Target
| Metric | Current | Target | Status |
|---|---|---|---|
| Callback rate trending down over 60 daysQuality improvements are holding; coaching and checklist changes are working | Good | ||
| Callback rate flat and below your internal targetStable quality; review tech-level breakdown to find outliers to coach | Good | ||
| Callback rate flat but above your internal targetProblem is not getting worse but it is still costing margin; identify the repeat offenders by job type | Watch | ||
| One tech's callback rate is 3x the team averageIsolated to one person: coaching or retraining opportunity before it becomes a review problem | Watch | ||
| Callback rate spikes after onboarding new techsExpected with new hires; pair them with senior techs and set a 90-day ramp target | Watch | ||
| Callback rate climbing while completed jobs are also climbingGrowth is stressing quality; dispatching too fast without enough oversight | Poor | ||
| High callback rate with declining average star ratingQuality failures are reaching public reviews; act before the pattern compounds | Poor |
Info
Coaching moment: the spread is the story
On most service teams, the top quartile of technicians produce almost no callbacks while the bottom quartile account for a disproportionate share. The team-level average hides that spread. A service manager who only watches the overall callback rate misses the coaching conversation that could move the number. Break callback rate by tech every week. Find the pattern (job type, system type, day of week) and make it a structured discussion, not a performance review surprise.
Warning
Data visibility gap: callbacks buried in closed jobs
Many home-service companies undercount callbacks because the return visit is logged as a new service call rather than linked to the original job. If your CRM does not tag a job as a callback, the number never makes it into the report. Check your dispatch workflow: is there a required field that flags a return visit? If not, your callback rate is almost certainly lower than reality. In ServiceTitan the return visits show up as Recalls Caused on the Technician Performance Report; in Housecall Pro there is a Call back field on the job that the Profit-by-date report can filter on. Pull that into your dashboard to make the count reliable.
Callback rate on a live service dispatch board
How callback rate appears on a datacube service board, displayed on an office TV and refreshed from the CRM throughout the day, so a service manager can spot a quality pattern before the week closes.
Figures are illustrative. Your datacube board reflects your own connected CRM, call tracking, and field operations data.
KPIs to read alongside callback rate
| KPI | Why it pairs with callback rate |
|---|---|
| Technician scorecard | Groups callback rate alongside average ticket, close rate, and member sales per tech for a full quality-and-revenue picture |
| Average ticket | A tech with a high average ticket and a high callback rate may be upselling work that is not ready; the two move together on quality-focused teams |
| Revenue per technician | Callback cost reduces effective revenue per tech; the margin impact is invisible without both numbers |
| Average star rating | Callbacks that become bad reviews show up here; quality and reputation lag by days to weeks |
| Job profitability | A job that gets a callback often shows negative margin once the return-trip cost is added; job profitability surfaces this |
Owner takeaway
- Callback rate is a margin metric, not just a quality metric: every return trip consumes labor, parts, and dispatch capacity that could have served a paying customer.
- The team average hides the spread. Break callback rate by technician every week to find the specific coaching conversation, not the department trend.
- Define your callback window and job type in the CRM before you start tracking. An inconsistent definition produces a number you cannot trust or act on.
- Pair callback rate with average star rating. Quality failures that reach public reviews compound faster than quality failures that stay internal.
Callback rate FAQs
See your callback rate live on a service dashboard
Connect your CRM and watch callback rate update in real time, broken out by technician and job type, so your service manager can coach during the week instead of explaining quality problems at month-end.
Keep exploring
Related
Go deeper