Every Callback Has a Lesson Your Senior Tech Already Knew

Your second-year tech is standing in a utility closet looking at a furnace that keeps locking out. He’s called your senior tech twice already today. The senior tech is in a crawl space across town and doesn’t pick up. So the new guy cleans the flame sensor, watches it run for ten minutes, and leaves.

Two days later the homeowner calls back. Same lockout. Your senior tech goes out, takes one look, and finds the thing he’s found on that model a dozen times since 2016. Twenty minutes, no charge, and a slot on the board that should have gone to a paying customer.

The lesson that would have saved that trip was in the building the whole time. It just wasn’t anywhere the new tech could reach it.

I’m not a tech, and I’ve never trained one. I spent almost 18 years running a digital agency, and these days I use AI to fix the problems that keep businesses stuck. What I see in a lot of trade companies is that the most valuable knowledge in the business lives in two or three heads, and the only way to get at it is a phone call those people are too busy to take.

Why this keeps getting harder

Most trade knowledge has always moved from person to person. The Bureau of Labor Statistics says most plumbers, pipefitters and steamfitters learn on the job through an apprenticeship, and it projects about 42,000 openings a year for those trades, on average, over the decade. That’s a lot of people learning from a lot of busy senior techs.

In your own shop, the cost shows up in a few places:

• Interruptions. Every call to a senior tech pulls them off their own job. A few minutes on the phone, plus the time to get back into what they were doing.
• The office as help desk. Model numbers, warranty lookups, “is there a procedure for this,” handled by someone who isn’t a tech.
• Callbacks. A return trip costs labor, fuel and a slot you can’t sell, and it costs a bit of the customer’s confidence.
• Questions never asked. The new tech who doesn’t want to bother anyone a fourth time and guesses.
• Retirement. When a senior tech leaves, everything they knew about your customers’ equipment leaves with them.

What a private knowledge assistant looks like

It’s built from your own material

Not the open internet. The assistant reads what your company already has:

• Your written procedures and checklists, rough as they may be.
• Years of job notes, especially the notes on callbacks and what finally fixed them.
• Equipment manuals and service bulletins you have on file and the right to use.
• Recorded answers from your senior techs. Ask them the twenty questions new hires ask most, record the answers, and transcribe them.

A new tech asks from the truck

Voice works best. “Furnace locking out after the second retry, already cleaned the flame sensor, what else has come up on this model?” The assistant answers in plain words and shows where the answer came from: a callback note from a past job, a procedure, a page in the manual, or the senior tech’s recorded answer.

It knows what it doesn’t know

If there’s nothing in your material that answers the question, it says so and tells the tech who to call. If the question is about code or safety, it says that too, points to the procedure, and sends the tech to a licensed person. It doesn’t improvise.

It gets smarter from the calls it can’t answer

Every question it routed to a person becomes a gap on a weekly list. Your senior tech answers it once, on the record, and the next new hire gets that answer from the assistant.

Run the numbers

Two pieces: the trips you shouldn’t have made, and the senior tech time you’re spending on the phone.

Callbacks. Callbacks per month, times the cost of a return trip, times the share a better answer would have prevented.

Say, for the sake of the math, that you have 14 callbacks a month and a return trip costs you $250 in labor, fuel and a lost slot. Say a third of those come down to something a senior tech already knew. Those numbers are made up. That’s about 5 trips a month, $1,250, or $15,000 a year.

Interruptions. Calls to senior techs per day, times minutes each, times working days.

Staying with made-up numbers: say your senior techs field 20 questions a day between them at 4 minutes each, counting the time to get back on task. That’s 80 minutes a day. If the assistant handles half of those, you get back 40 minutes a day of your most valuable people, or about 167 hours over 250 working days. What that’s worth depends on what a senior tech does with an extra 40 minutes, and you know that better than I do.

To run it for real, pull three numbers:

1. Callbacks per month, with a reason written down for each.
2. Your true cost of a return trip, including the slot you couldn’t sell.
3. Questions to senior techs per day. Give them a tick sheet for one week.

Picture a Monday, before and after

This scene is made up.

Before. Monday at 7:30, a new tech three weeks into the job gets a no-heat call at a house with a boiler he’s never seen. He calls the senior tech, who’s driving. He calls the office, who looks for a manual and can’t find one. He works it out, mostly, and leaves a note that says “relit, monitor.” It goes out again Wednesday.

After. Same Monday, same boiler. He asks the assistant what’s come up on this model before. It pulls two old job notes from the same neighborhood and a page from the manual on file, and lists the three things the senior tech always checks. One of them is the problem. He fixes it, records his note, and the senior tech never gets a call.

What has to be in place first

• Callback reason codes. If callbacks aren’t recorded with a cause, you can’t find the lessons. Start now even if you start rough.
• Job notes worth reading. Short, consistent notes on what was found and what fixed it. Voice notes help.
• Manuals in one place, organized by equipment you actually service.
• Senior techs who are in on it. Pay them for the hours they spend recording answers. It’s the most valuable thing they’ll make all year.
• One person who reviews flagged answers weekly.

Guardrails worth keeping

• Code and safety questions defer to the licensed tech and the code as adopted where the job is. The local inspector decides. The assistant says so and stops.
• Every answer cites its source, so a tech can judge it and the company can fix it.
• No guessing. If the material doesn’t cover it, the assistant routes the question to a person.
• Private, not public. Your job notes and customer addresses stay in business-grade tools that don’t use them to train public models.
• It supports supervision, it doesn’t replace it. Apprenticeship and licensing rules in your state still apply in full.

How you’ll know it’s working

• Callbacks per month, split by how long the tech has been with you.
• Questions to senior techs per day, from the same tick sheet a month later.
• Weeks until a new hire runs calls solo.
• Share of assistant questions answered from your material versus routed to a person.
• Gaps closed each week, from the routed list.

Where I’d start

Take your last six months of callbacks. Sit down with your senior tech for two afternoons and write the lesson for each one in a sentence or two. Load those, plus your procedures, into a private assistant, and give it to one new tech for a month. Count the calls to the senior tech before and after.

If this sounds like your week, send me a note through the contact page.