What a new service advisor needs in week one

The job is part diagnosis, part scheduling, part sales and part apology. Almost nobody arrives able to do all four.

The usual onboarding

Show them the system, sit them next to someone for a day or two, then put them on the phones because it's busy and they're keen.

What follows is predictable. They book work the shop can't do, quote from memory, promise times the bays can't meet, and take the blame for problems they were set up to create. Some survive it and become good. Plenty leave inside six months and get written off as a bad hire.

The gap isn't attitude. It's that the job needs shop knowledge nobody gave them.

Day one is the shop, not the software

Before any customer contact, they need a working model of what actually happens to a car in the building. Not the process on paper. The real one.

Walk a car end to end with them. Check-in, dispatch, inspection, estimate, approval, parts, the work, quality check, pickup. Have them watch each handoff and see where things wait.

An advisor who understands why a job waits can explain a delay to a customer. One who doesn't can only apologize, which satisfies nobody and makes the shop look disorganized.

What they need to know before touching a phone

This is the list that prevents most first-month damage.

• What the shop does and doesn't take. Including the awkward ones: diesel, EVs, transmissions, anything over a certain age.
• Roughly how long common jobs take , in real elapsed time, not book time.
• Who the specialists are and what queues behind them.
• What is never quoted over the phone , and the exact words to use instead.
• When to interrupt someone and when to write it down.
• What the shop will and won't do on a comeback , before they're standing in front of an angry customer inventing a policy.

Teach the phrase for I don't know

The most damaging habit a new advisor picks up is guessing, and they guess because they think not knowing looks unprofessional.

A guessed price becomes a promise. A guessed time becomes a complaint. A guessed diagnosis becomes a tech's wasted morning and a customer who was told something wrong.

Give them the actual sentence: "I don't want to guess at that. Let me check with the tech and come straight back to you." Then make sure coming back is fast, because that's what makes the sentence safe to use. If checking takes three hours they'll go back to guessing.

Let them write estimates before they present them

Writing a good estimate is the highest-leverage skill in the job and the one that takes longest to learn. It's also the one usually taught last, by trial and error on live customers.

Better to have them write estimates for a week that someone else reviews before sending. They get the reps, the customer gets a good document, and the corrections happen where they cost nothing.

Then have them present ones they didn't write. Splitting the two skills makes each easier to learn than being thrown at both at once.

The hard conversations need rehearsing

Four conversations account for most of the stress in the job, and every advisor will have all of them in the first month.

• The car isn't ready when promised.
• We found more than we expected and it's expensive.
• It's a comeback and the customer is angry.
• We can't fix it, or shouldn't, and the car isn't worth it.

Pair them with a tech, not just an advisor

Advisors learn the counter from other advisors, which is right, and it leaves a gap. They end up able to run the process without understanding what any of it means physically.

A day in the bay fixes more than a week of shadowing at the desk. Watching a brake job start to finish teaches why the labor number is what it is. Watching someone chase an intermittent electrical fault teaches why a diagnostic can't be quoted like a service, which is the hardest thing for a new advisor to explain to a customer because they don't believe it themselves yet.

It also builds the relationship the job depends on. An advisor the techs know and like gets straight answers quickly. One who is a voice on an internal line gets whatever the tech has time to say.

Give it a fortnight before judging

A new advisor is a net cost for a while. They take longer, they interrupt more, and someone has to check their work. That's the investment, not evidence of a mistake.

The thing to watch isn't speed. It's whether they're guessing. An advisor who is slow and accurate becomes fast. One who is fast and making things up gets faster at making things up, and that shows up as comebacks, disputes and customers who don't return.