Where tech and advisor communication breaks down
The customer described the problem accurately. By the time it reached the bay it had become three words.
The telephone game nobody notices
A customer explains that there's a rattle, only over bumps, only when the car is cold, mostly turning left, started about three weeks ago. That's a genuinely useful description.
The advisor is on the phone with two people waiting, so what reaches the ticket is "rattle front end". The tech drives it warm on a smooth road, finds nothing, and writes "could not duplicate".
Nobody made a mistake exactly. The information was accurate at the start and lost in transit, and the cost is a wasted diagnostic hour plus a customer who now thinks you didn't look properly.
What gets lost, specifically
The details that vanish first are the ones that narrow a diagnosis fastest.
- When it happens. Cold, warm, at speed, braking, turning, over bumps.
- How long it's been happening , and whether it's getting worse.
- What changed just before it started. New tires, a pothole, work done elsewhere.
- Whether it's constant or intermittent , which is the difference between a ten minute job and a two hour one.
- What the customer already tried , including work another shop did for the same complaint.
Let the customer write it down
The single biggest improvement is taking the advisor out of the transcription business. A customer describing their own problem, in their own words, before they arrive, produces a better record than the same information relayed at a busy counter.
They'll include things an advisor wouldn't think to ask, they'll be more specific because they aren't being rushed, and the tech gets the original rather than a summary.
It also means the write-up isn't eating the first twenty minutes of the slot.
The return trip is just as lossy
Findings travel the same road in reverse. The tech knows exactly what's wrong and why. What reaches the customer is often the advisor's recollection of a conversation shouted across the shop while both were doing something else.
The detail that gets dropped is usually the *why*, and the why is what sells the job. "Needs a wheel bearing" is a price. "The bearing is noisy under load turning right, it'll get louder and eventually it's a safety issue" is a decision the customer can make.
Findings should reach the estimate as the tech wrote them, not as the advisor remembers them.
Stop the interruptions in both directions
A tech who has to find the advisor to ask a question loses time twice: their own, and the advisor's. If the advisor is on the phone, the tech either waits or guesses, and guessing is where comebacks start.
Written questions with written answers solve most of it. Less satisfying than a conversation, considerably faster, and it leaves a record of what was actually asked when something goes wrong later.
The exceptions are genuinely worth a walk: anything where the tech needs the advisor to see the car, and anything where the news is bad enough that tone matters.
The handover that matters most
When a job moves between techs, or across a shift, or sits overnight, is when the most gets lost. The second tech inherits a half-diagnosed car and a note that means something only to the person who wrote it.
It's worth being deliberate about it: what's been ruled out, what's been tried, what the next step was going to be. Ruled out is the part people skip and the part that saves the most time, because otherwise the second tech repeats the first tech's morning.
Pay attention to how the two sides describe each other
There's a diagnostic you can run without any data. Listen to how techs talk about advisors and how advisors talk about techs when the other isn't there.
In a shop where the information flow is broken, you'll hear that advisors sell work without understanding it and promise times nobody can meet, and that techs are slow, won't explain anything, and don't care that a customer is waiting. Both sides are describing the same broken handoff from opposite ends and attributing it to the other's character.
That framing is worth interrupting, because it's self-reinforcing. An advisor who believes techs are unhelpful stops asking questions and starts guessing. A tech who believes advisors don't listen stops explaining and writes three words on the ticket. Each one's coping strategy makes the other's complaint more true.
The fix isn't a conversation about attitudes. It's making the handoff carry the information so neither side has to rely on the other's goodwill to do their job.
The number that shows it
Track could-not-duplicate rates and comebacks, and when one happens, ask where the information was lost rather than who got it wrong.
It's almost never a person being careless. It's almost always a point in the process where something true got compressed into something shorter, by someone doing three things at once.