What a callback really costs
A callback is any return trip to fix or finish work you already did, usually without being paid for it. A warranty callback is the same thing under your workmanship or parts warranty. Either way, you pay twice: once for the trip, and again in the job you could have run with that slot.
Worked example (made-up numbers): a callback takes 2 hours including drive. At a burdened labor rate of $48 an hour, that is $96 in labor. If your average billable hour also carries $60 of overhead, that is another $120. And if that slot could have been a $400 service call, you also lost the profit on it. Two callbacks a week at that rate adds up fast. See job costing for contractors for how to charge return trips to the original job so you can see this.
Step 1: log every callback with a cause
You cannot fix what you do not count. Every return visit gets tagged to the original job, the original tech, and one cause from a short list:
| Cause | Example |
|---|---|
| Diagnosis | Fixed the symptom, missed the real problem |
| Workmanship | Loose fitting, missed step, not tested |
| Part failure | New part failed early |
| Incomplete | Job left unfinished or waiting on a part |
| Expectation | Customer expected something the job did not include |
| Unrelated | New problem, not caused by our work (bill normally) |
Then track your callback rate: callbacks divided by completed jobs, by month and by tech. A rising rate on one tech or one job type tells you exactly where to look.
Step 2: test and show before leaving
Many workmanship callbacks come from the last ten minutes of the job. Make "test, then show the customer" a rule:
- Run the system or fixture through a full cycle, not just a quick on and off.
- Check every connection you touched for leaks, heat or looseness.
- Show the customer it works and what you did.
- Take photos of the finished work.
- Clean up and remove old parts, unless the customer asked to keep them.
Put these on an end-of-job checklist the tech completes before closing the job. A checklist is not an insult to a good tech. It is how good techs stay consistent at the end of a long day.
Step 3: fix the diagnosis problem
Diagnosis callbacks are usually the most expensive, because the customer paid and the problem came back. Ways to cut them:
- Give techs a standard diagnostic flow for your common calls, so they test the likely causes in the same order every time.
- Read what the customer said on the call before arriving. The detail they mentioned to the office is often the clue.
- When a callback comes in, send the original tech back if you can, or send a senior tech with him on a ride-along so he learns what he missed.
Step 4: set expectations on the estimate
Some callbacks are not about bad work at all. The customer thought the repair would fix something it was never meant to fix. Write the scope plainly:
"Today's repair replaces the failed fill valve on the upstairs toilet. The wax ring and the downstairs toilet were not part of this job. If you see water at the base, call us and we'll quote that separately."
When the customer signs a clear scope, a later "it's still leaking" call is easier to sort out fairly, and the conversation stays friendly.
Step 5: coach from real callbacks
Once a month, pick the two or three most common callback causes and go through real examples with the crew. Show the photos, walk through what was missed, and add the fix to the checklist. Keep it about the work, not about blame. Techs who feel blamed stop reporting problems, and then your numbers stop being true. For newer techs, fold these lessons into your training; see how to train new technicians.
Common mistakes when trying to reduce callbacks
- Not counting callbacks at all. They hide in the schedule as "free" visits.
- Booking callbacks as new jobs. The original job's real profit is lost.
- Treating every return as the tech's fault. Parts and expectations cause plenty of them.
- Charging for warranty work you owe. If it is your workmanship, own it and fix it fast.
- Not linking callbacks to first-time fix. The same habits drive both; see improving first-time fix rate.
How SWITCHBOARD helps
In SWITCHBOARD, end-of-job checklists sit on the tech's phone and come first with no skip, job photos are time-stamped, and the tech sees what the customer said on the call before arriving. Switch, the AI, can draft a checklist for a job type for you to edit and approve, and job margins show after labor, parts and drive time, so return trips are visible.
Questions people ask
What is a good callback rate?
There is no universal target, because it depends on trade and job mix. Track your own rate by month and by tech and work to bring it down over time.
Should I charge for a callback?
If the return is caused by your workmanship or a part you warranty, no. If it is a new, unrelated problem, bill it as a normal job and explain why.
Who should go on a callback?
The original tech when possible, so he learns from it. For repeat or diagnosis callbacks, send a senior tech with him.
How do checklists reduce callbacks?
They make the last steps of the job, like testing, checking connections and showing the customer, happen on every job, not just when the tech remembers.