The part of the job you did not hire them for
You hired a field technician for their technical ability, and you probably assessed exactly that. What determines whether customers request them again, leave a five-star review, or call the office angry is almost entirely the conversation on the doorstep.
A field tech works alone. There is no supervisor within earshot, no ability to mute and ask a colleague, and no script. They are the entire company as far as that customer is concerned, standing in the customer's home or business, frequently delivering news the customer does not want.
Technical training for this role is usually well covered by trade background or certification. The conversation half is almost never trained at all, and it is where the complaints come from.
Eight scenarios to run before the first solo call
1. The repair is bigger than the quote.
Persona: had budgeted for the quoted number, visibly unhappy, asks why nobody warned them.
What is being trained: explaining the discrepancy without blaming whoever quoted it, and getting authorization before proceeding rather than after.
2. The customer watching over their shoulder.
Persona: friendly, curious, and hovering. Asks what each step is for. Slows the work down.
What is being trained: staying courteous while keeping pace, and setting a light boundary without being rude. New techs either go silent or lose forty minutes.
3. "The last guy said something different."
Persona: quotes a previous technician, possibly from your company, whose diagnosis contradicts this one.
What is being trained: not undermining a colleague and not caving on a correct diagnosis. This is the hardest one on the list.
4. Delivering the news that it cannot be fixed today.
Persona: needs it working now, has a business or a family depending on it, presses for a workaround.
What is being trained: being clear about what is and is not possible, and offering the real interim option rather than a hopeful one.
5. The customer who caused the problem.
Persona: the damage is clearly from misuse, and they are asking whether it is covered.
What is being trained: explaining cause without assigning blame out loud, and handling the warranty question factually.
6. Suspecting a safety issue.
Persona: dismissive about a hazard the tech has spotted, wants the tech to just do the job they came for.
What is being trained: escalating clearly and refusing to proceed when required. New techs defer to the customer, which is exactly the wrong instinct here.
7. Explaining a bill at the door.
Persona: surprised by a line item, asks what a specific charge is for.
What is being trained: itemizing calmly and not discounting on the spot to end the discomfort. Unauthorized discounting is a common and expensive new-tech habit.
8. Their own mistake.
Persona: something the tech did caused a new problem, and the customer has noticed.
What is being trained: owning it immediately, calling the office rather than trying to hide it, and telling the customer what happens next.
What to look for when you review an attempt
- Whether they got authorization before proceeding. The single most expensive field-tech failure is doing work the customer did not approve.
- Whether they discounted without authority. Listen for anything resembling "I'll see what I can do about the price."
- Plain language. Whether the explanation was understandable to someone with no technical background. Techs often explain accurately and incomprehensibly.
- How they handled the contradiction. Scenario three specifically: did they hold the correct diagnosis without disparaging the previous tech.
- Safety escalation. Whether they held the line in scenario six. This one is pass or fail rather than a score.
How to run these without a ride-along week
The standard approach is to have the new tech ride with a senior tech for a week or two. It works, and it costs you most of two technicians' productive capacity, which at a company with four techs is a quarter of your service capacity for that period.
What ride-alongs do well is technical context. What they do poorly is conversation practice, because the new tech watches rather than speaks. Someone can complete two weeks of ride-alongs having never once delivered bad news to a customer themselves.
A practical split: keep a shortened ride-along for the technical and site-safety context, and move the conversation practice to scored role-play the new tech can run in the evening or between jobs. Scenarios one, four, and six should be complete before the first unaccompanied call.
What most companies get wrong onboarding field techs
- Assuming trade competence covers customer competence. They are unrelated skills and you assessed only one of them in the interview.
- Finding out about problems from reviews. By the time a one-star review names a technician, the pattern is months old.
- No practice on the money conversation. Quotes, overruns, and bills are where most field-service complaints originate, and almost nobody rehearses them.
- Treating unauthorized discounts as a character issue. It is a training gap. A tech discounts because they were never given language for holding a price while staying pleasant.