October 22, 2026 · Mitt Patel · 6 min read
You sent a technician back to a job on Tuesday afternoon to fix a system they'd already serviced that week. No invoice went out. The parts came off the truck, the hour came off the schedule, and by Friday you couldn't tell anyone what it cost you.
Why callbacks hide inside ordinary service work
A callback looks like any other visit on the schedule. The technician drives out, spends an hour on-site, maybe swaps a part, and leaves. In the field system, it often gets logged the same way as a paid job. In the books, the labor hits payroll like any other hour, and the part gets pulled from inventory like any other part.
The difference is there's no invoice behind it. No revenue came in to offset that labor and that part. So the cost doesn't disappear — it just stops being visible. It gets absorbed into your overall labor cost and parts cost for the month, blended in with all the paid work.
This matters because you make decisions off those blended numbers. If you're looking at technician productivity, or deciding whether a particular equipment brand is worth continuing to install, or pricing a maintenance plan, you're working from numbers that already have callback cost baked in — but you can't see how much, or where.
Say two technicians have similar billed hours this month. One of them is quietly spending four extra hours a week on callbacks the other technician doesn't have. Without tagging, they look equally efficient. With tagging, you'd know one of them needs a conversation, more training, or a different type of job.
A worked example
Say a technician installs a condenser on Monday. Three weeks later, the customer calls back because the system isn't cooling properly. The technician returns Thursday, spends two hours diagnosing and replacing a capacitor, and leaves. No invoice goes out because it's a warranty-type return visit.
The technician's time: 2 hours at a $35 loaded hourly cost, so $70 in labor.
The capacitor: $45 off the truck.
Total cost of that callback: $70 in labor plus $45 in parts, or $115 total.
If that callback isn't tagged, it shows up in your books as $70 of labor cost and $45 of parts cost for the month, mixed in with every other hour and every other part you used on paid jobs. Your gross margin for the month absorbs this cost without explanation, but you can't tell why. If it happens three more times that month across different technicians, you've got $345 more in cost with no record of where it came from or which jobs, technicians, or equipment brands keep generating it.
How to set it up
- Create a callback job type in your field service system. Most field service platforms let you tag a job as a category separate from "service call" or "install." Call it "callback" or "return visit" and use it every time, without exception.
- Link the callback to the original job. When you tag the callback, note the date and job number of the original visit it relates to. This lets you trace patterns back to a specific install, technician, or piece of equipment later.
- Record the callback as a job in QuickBooks Online with $0 revenue. Set up a zero-dollar invoice or use a job/class tracking feature, so the labor and parts cost attach to a callback job rather than disappearing into general service cost.
- Tag the parts used. When a part comes off the truck for a callback, record it against that callback job rather than lumping it into general inventory draw. If your inventory system supports job-level tracking, use it here.
- Tag the labor hours. Have technicians log their time against the callback job code, the same way they'd log time against a paid job. This is the step most likely to get skipped, so it helps to build it into your time tracking app or field service form as a required field.
- Run a monthly report by technician and by equipment brand. Once callbacks are tagged, pull a simple report: total callback hours and parts cost, broken out by technician and by the brand of equipment involved. This is where the pattern shows up — whether it's one technician, one brand, or a particular type of job.
The mistakes that undo it
- Treating callbacks as "no big deal" and not tagging them at all. If it's not tagged, it's invisible, and invisible costs don't get managed.
- Tagging the callback but not the parts. Labor-only tracking misses half the picture, especially on jobs where a part failed early.
- Lumping warranty callbacks in with customer-complaint callbacks. These have different causes — one is a parts failure, the other might be a workmanship issue — and mixing them hides which one is actually driving your cost.
- Only reviewing the report when something feels wrong. If you wait for a bad month to check callback data, you lose months of pattern that could have told you sooner.
- Letting technicians self-report inconsistently. If one technician tags every return visit and another doesn't bother, your by-technician comparison becomes meaningless. This needs to be a required field, not an optional one.
Monthly checklist
- Confirm every callback from the past month is tagged as a callback job, not folded into regular service work.
- Confirm parts used on callbacks are recorded against those jobs, not general inventory.
- Confirm technician hours on callbacks are logged separately from billed hours.
- Pull the callback cost report by technician.
- Pull the callback cost report by equipment brand.
- Compare this month's callback total to the prior two or three months to spot a trend, not just a single bad month.
Common questions
What counts as a callback versus a normal follow-up visit?
This depends on how your business defines it, but generally a callback is any return trip tied to work you already did — a repeat complaint, a part that failed early, or a system that didn't perform as expected after service. A separate, newly diagnosed problem on an older system is usually a new paid job, not a callback. It's worth writing down your own definition so technicians apply it consistently.
Should callback labor be costed at the technician's full loaded rate?
Yes, generally. The technician's time has a real cost to you — wages, taxes, and benefits — whether or not that visit produced revenue. Using the same loaded rate you'd use for billed work keeps your comparison honest.
What if a manufacturer reimburses us for a warranty part?
Record the reimbursement as a separate entry rather than netting it against the original cost. This way you can still see the full cost of the callback, and separately see what portion came back to you. How to record the reimbursement itself depends on your bookkeeping setup, so it's worth checking with whoever manages your books.
Is this worth doing if we only have two or three technicians?
The smaller the team, the easier the pattern is to see once you start tagging. With only two or three technicians, even a handful of untagged callbacks a month can meaningfully distort what you think each person costs you.
North Hudson Bookkeeping can help set up callback tracking inside your existing field system and QuickBooks Online, and help keep the monthly reports current so you have better visibility into where the time and parts are going. The first call is free.
