Diagnosing Communication Breakdowns with Service Advisors

Misdiagnosis does not always start with the wrong test or the wrong part. Sometimes it starts with the wrong information. Miscommunication between the customer, the service advisor, and the technician is one of the biggest causes of comebacks, wasted diagnostic time, and lost revenue in any shop. Fixing the communication problem fixes a lot of the diagnostic problems that follow it.

Written by Anthony Calhoun, ASE Master Tech A1-A8

Where Communication Breaks Down

Information passes through at least two handoffs before it reaches the technician. The customer tells the advisor. The advisor writes it on the repair order. The tech reads the repair order and starts diagnosing. Every handoff is a chance for critical information to get lost, changed, or misunderstood. Here is where it typically goes wrong:

• Vague customer descriptions: "It makes a noise" does not tell you what kind of noise, when it happens, or where it comes from
• Advisor translation errors: The customer says "it shakes when I brake" and the advisor writes "vibration concern" — dropping the braking context entirely
• Tech assumptions: The tech reads "vibration concern," assumes it is a tire balance issue, and never checks the brakes
• Missing conditions: The customer mentioned it only happens when cold, but that detail never made it to the RO
• Technical jargon vs customer language: The customer says "the car jerks" — that could mean a misfire, a transmission shudder, an engine mount, or a dozen other things

How to Extract Useful Diagnostic Information from Customers

Most customers are not car people. They cannot tell you "I have a P0301 and my coil pack is misfiring." They can tell you what they experience — and if you ask the right questions, that experience becomes useful diagnostic data.

The Five Questions That Matter

Listen First, Diagnose Later

The biggest mistake in customer communication is jumping to conclusions before the customer finishes talking. Let them tell you the whole story. The detail they mention last is often the most important — "Oh, and it also smells like something is burning" completely changes your diagnostic direction.

Writing Repair Orders That Communicate Clearly

The repair order is a legal document and a communication tool. It needs to tell the tech exactly what the customer reported, and later, it needs to tell the customer exactly what was found and done. Here is what a good RO looks like versus a bad one:

Bad RO

"Customer states noise from front end. Check and advise."

Good RO

"Customer states grinding noise from left front area when braking at low speed (under 20 mph). Started approximately two weeks ago. Noise is getting louder. No warning lights on dash. Last brake service was 18 months ago."

The difference is obvious. The first RO sends the tech on a fishing expedition. The second one points directly at left front brakes and gives context about service history. The tech can walk straight to the left front wheel and start inspecting.

Tech-to-Advisor Communication

Once you have diagnosed the problem, you need to communicate it back through the advisor to the customer. This is where many techs struggle — not because they do not know what is wrong, but because they explain it in tech language that neither the advisor nor the customer understands.

Translating Tech Language

• Instead of: "The TCC is shuddering due to worn friction material in the torque converter" — Say: "There is a component inside the transmission called the torque converter that is wearing out. It causes a vibration feeling at highway speed. It needs to be replaced."
• Instead of: "Mode $06 shows cylinder 3 misfire counts approaching threshold" — Say: "One of the spark plug coils is starting to fail. It has not turned on the check engine light yet, but it will soon. We should replace it now before it causes more problems."
• Instead of: "You have a parasitic draw of 350 milliamps from the BCM not going to sleep" — Say: "Something in the car's computer system is staying awake when the car is off, draining the battery overnight."

You do not have to dumb it down — you have to translate it. Give the advisor enough understanding to explain it to the customer with confidence.

When the Advisor Oversells or Undersells

This is one of the most common friction points in any shop. The tech recommends a brake job. The advisor sells a brake job plus a transmission flush plus a coolant flush plus new wiper blades. Now the customer feels like they are being taken advantage of, and they blame the tech.

On the flip side, sometimes the advisor undersells. The tech recommends immediate control arm replacement because the bushings are completely gone, and the advisor presents it as "something to think about" — then the customer comes back six months later with a destroyed tire because they thought it was optional.

How to Handle It

• Document your findings clearly: Write down exactly what you found and your recommendation with severity — "needs immediate attention" vs "monitor at next service"
• Use photos and video: A picture of a torn CV boot or a worn brake pad is worth a thousand words. It lets the customer see what you see.
• Prioritize for the advisor: "These are the safety items that need to be done now. These are maintenance items that can wait 3-6 months. These are things to keep an eye on." That gives the advisor a clear framework for the conversation.
• Speak up: If you see a safety concern being downplayed, say something. Document it on the RO. Your name is on that inspection, and your professional judgment matters.

Documentation as Communication

In a busy shop, verbal communication gets lost. The advisor gets busy, the tech gets pulled to another job, and that critical detail about the customer's intermittent stall gets forgotten. Documentation is the solution.

Photos and Videos

Take photos of everything significant — worn parts, fluid condition, damage, DTC screens, scan data PIDs. Most shop management systems let you attach photos to the RO. This serves three purposes:

• Helps the advisor explain the repair to the customer
• Protects the shop if the customer disputes the repair
• Creates a service history that helps the next tech who works on this car

Scan Data Screenshots

Screenshot your scan data — DTCs, freeze frame, live data, Mode $06 results. Attach them to the RO. If the customer goes to another shop for a second opinion, your documented scan data shows exactly what was happening in the vehicle's systems when you diagnosed it.

Shift Handoffs and Multi-Tech Jobs

When a job passes between technicians — shift change, specialist referral, or just a second opinion — communication failures multiply. The incoming tech does not know what was already checked, what was already ruled out, or what the customer specifically described.

The Handoff Checklist

• What is the customer's concern (in their words)?
• What has been tested so far?
• What has been ruled out?
• What is the current theory?
• What is the next step?
• Are there any parts already ordered or on the way?
• Is there a time constraint (customer waiting, rental, warranty deadline)?

Write this on the RO or a shop note attached to the RO. A verbal handoff at the end of a busy day is not reliable — write it down.

Real-World Miscommunication Failures

The Misfire That Was Not a Misfire

Customer told the advisor "the car jerks at low speed." Advisor wrote "misfire concern." Tech scanned for codes, found none, test drove and felt no misfire, wrote NTF. Customer came back furious. Turns out the "jerking" was a transmission shudder during TCC apply at 40 mph — not a misfire at all. If the advisor had written the customer's actual words and the speed at which it occurred, the tech would have gone straight to the transmission, not the ignition system.

The Brake Job That Became a Comeback

Tech recommended front brake pads and rotors. Advisor told the customer "you need brakes." Customer approved. Tech did the front brakes. Customer picked up the car and called back the next day — "I still hear the grinding noise." The noise was from the rear brakes, which were metal-on-metal. The tech only inspected and repaired the fronts because the RO said "front brake noise." The customer heard noise and assumed all brakes were being fixed. Nobody clarified which brakes were the concern.

The Electrical Diagnosis That Went Sideways

Customer reported dead battery every Monday morning. Advisor wrote "battery dies, check charging system." Tech tested the battery (good) and alternator (good), wrote "charging system tests normal, battery passed load test." Customer came back the following Monday with a dead battery. The real issue was a parasitic draw — but the RO said "check charging system," so that is what the tech checked. If the advisor had written "battery dies after sitting over the weekend," the tech would have immediately tested for parasitic draw instead of alternator output.

Building a Communication Culture

Good communication is not a one-time fix — it is a shop culture. Here is what works:

• Morning meetings: Five minutes at the start of the day to review the day's appointments and flag any complex jobs or returning customers
• RO standards: Establish minimum information requirements for every repair order. If the RO does not have the five key elements (what, when, how often, when started, any changes), send it back to the advisor
• Photo policy: Every multi-point inspection gets photos. Every diagnostic job gets scan data screenshots. No exceptions.
• Feedback loop: When a comeback happens because of miscommunication, review it as a team. Not to blame anyone, but to identify where the information was lost and how to prevent it next time
• Test drive with the customer: For subjective complaints (noises, vibrations, "feels weird"), ride with the customer if possible. Let them show you what they are experiencing. Five minutes in the car with the customer can save two hours of blind diagnosis.