You know the call. A job you finished last week needs a return visit. Something settled. Something’s not sitting right. The customer wants you back out. It’s not a disaster. You’ll send a crew, they’ll sort it out in an hour, everybody’s happy.
So you file it under minor annoyance. An hour of labour, a little material, the cost of doing business.
But the hour fixing the problem may be the cheapest part of the callback.
You have to get there again
Think about everything that happens before that one-hour repair.
Someone figures out what happened. The return visit gets worked into the schedule. The crew loads what they need. They drive across town. Unload. Set up. Fix the problem. Pack everything back up. Drive to wherever they’re supposed to be next.
Suddenly an hour-long repair has punched a much bigger hole in the day.
And there’s one more cost that never appears on the invoice:
While they’re doing all of that, they’re not doing work you can bill for.
That’s the real bill. Not simply the hour spent fixing the problem. It’s the earning time you gave up to go back and collect nothing.
Look at the whole trip
Suppose a callback consumes half a day for a two-person crew, door to door. That’s eight crew-hours. You paid for those hours. The truck ran. Fuel burned. Whatever job was supposed to occupy that part of the schedule had to move somewhere else. And the callback produced exactly:
$0 in new revenue.
Now imagine that happening once. Not pleasant, but manageable. Imagine it happening three times this week. Then three times next week. Now stretch that across a season. A callback stops looking like a customer-service annoyance.
It starts looking like a profit problem.
Don’t eliminate callbacks. Find the expensive ones.
The goal isn’t zero callbacks. Things happen. Materials fail. Ground moves. Customers misunderstand. People make mistakes. Trying to eliminate every possible callback could cost more than the callbacks themselves. The useful question is simpler:
Why are we going back?
For one season, log every callback and the reason behind it. Nothing complicated. Just the honest reason you had to make the trip. A material that keeps failing. An installation step that gets rushed when the crew falls behind. Something the customer and estimator understood differently. A particular type of job that repeatedly causes trouble. A skill one crew hasn’t quite mastered.
After a while, you may start seeing the same reasons again. Those are the callbacks worth attacking. Fix the recurring causes and you don’t just save the cost of the repair. You eliminate the trip. And that’s where the real money is. Every callback is another mobilization that produces no new revenue.
The money isn’t in doing the redo faster.
It’s in not making the trip at all.