Callbacks From One Tech: A Coaching Decision Tree

Why this matters

A callback (a customer calling you back because the job was not right the first time) is the most expensive kind of work you do. You pay for the truck roll twice, you burn goodwill, and you earn nothing on the return trip. When one tech's callback rate is clearly above the rest of the crew, you have a coaching problem, not a punishment problem. Diagnose it the same way the tech would diagnose a no-cool call: simplest cause first.

Start here: confirm it is real and it is them

Before you coach anyone, look at the numbers, not the noise. Pull the last sixty to ninety days. Count callbacks against jobs completed for each tech so you are comparing a rate, not a raw count. A tech who runs twice the volume will show more callbacks while being your best closer.

If the gap disappears once you normalize by job count, there is no problem to coach. If the rate is genuinely higher, sort the callbacks into buckets before you talk to anyone: comeback for the same fault, a new fault on the same equipment, a part that failed, or a customer expectation that was never set. The bucket tells you the cause.

Branch 1: same fault comes back (the work was wrong)

This is a skills or diligence gap. Pull two or three of the callback tickets and walk them with the tech, calmly, asking what they found and what they checked.

• If they describe a step they skipped (did not check the other capacitor, did not test under load, did not confirm the drain ran), the cause is rushing or an incomplete mental checklist. Fix it with a written job-complete checklist for that job type and a ride-along on the next one.
• If they describe doing the right steps but reaching the wrong conclusion, the cause is a knowledge gap. This is teachable. Pair them with your strongest tech on that fault type, or send them to a manufacturer or distributor training session.
• If they cannot reconstruct what they did, the cause is documentation. They are not writing enough on the ticket to learn from. Require photos and a fault-found note before the job closes.

Branch 2: new fault, same equipment (scope or honesty)

The customer called back for something different, but it was sitting right there.

If the tech genuinely could not have seen it (intermittent, seasonal, unrelated system), this is not a callback against them, recode it. If it was visible and they missed it or chose not to mention it, you have either a thoroughness gap or a tech who avoids hard conversations with customers. Coach the inspection habit: every visit, eyes on the whole system, note anything aging even if the customer declines the repair. A noted-but-declined item is not a callback, it is a future sale.

Branch 3: the part failed (not the tech)

Warranty parts fail. If the failures cluster on one supplier or one part line across multiple techs, the problem is procurement, not people. If they cluster on one tech, look at handling: are they testing the part before install, are they installing it correctly, are they over-torquing or mishandling. Usually it is the part. Do not let a genuine warranty failure land on a tech's record, or they will stop trusting your numbers.

Branch 4: expectation was never set (communication)

The work was fine, the customer is unhappy anyway. They expected the noise to stop, or the room to get cold faster, or a different price. This is the easiest to miss and one of the most common. Coach the close-out conversation: before leaving, the tech says what was done, what to expect, and what was not fixed. A thirty-second summary at the door prevents the call the next morning.

How to run the actual coaching conversation

• Lead with the data and the buckets, not an accusation. "Your same-fault rate is running high, let's look at why" lands very differently than "you keep messing up."
• Coach one thing at a time. Pick the biggest bucket and fix that first.
• Make the standard concrete and write it down. "Be more careful" is not coachable. "Test the capacitor under load and photograph the reading" is.
• Set a check-in date and look again. Improvement you do not measure did not happen.
• Separate the can't-from the won't. A skills gap gets training and patience. A repeated refusal to follow a written standard, after coaching, becomes a performance conversation. Do not confuse the two, and do not jump to the second when it is really the first.

What to track in Manuall

Tag callback jobs so you can pull a clean rate per tech and per job type. Use the job notes and photo attachments as your coaching evidence. Over time, the callback rate by job type also tells you where your whole crew needs training, not just one person.

References

• OSHA General Duty Clause - safe and competent work practices as the baseline for any field role.
• Manufacturer and distributor technical training programs - the standard path for closing a documented knowledge gap.
• See related: Building a Training Culture, Not Just Onboarding.
• See related: Teaching Judgment, Not Just Procedure.