13.2 Communicating Concerns to Staff & Understanding Tech Diagnosis
Key Takeaways
- Task 6 requires routing the customer’s concern or request to the right staff with enough detail that the next person does not have to guess
- Task 7 requires understanding the technician’s diagnosis and recommendations well enough to translate them into customer language and ask clarifying questions before presenting options
- Use structured handoffs (who / what / when / how to verify) and never alter tech findings to make a sale easier
- Clarify uncertain terms—intermittent, pending codes, related damage, “could be”—before you promise a cause or a completion time
- Effective internal communication reduces comebacks, incorrect authorizations, and CSI failures even when the repair itself is technically correct
Shop Operations Tasks 6 and 7 sit next to each other for a reason. Task 6: effectively communicate the customer service concern/request to appropriate staff. Task 7: understand the technician’s diagnosis and service recommendations. Together they describe the consultant’s role as the translator between the drive-up lane and the bay—and back again.
If either side of that bridge fails, the shop may fix the wrong thing, the customer may authorize the wrong thing, or a correctly diagnosed repair may still feel like a bait-and-switch at delivery.
Task 6: Route the Concern to the Right People
“Appropriate staff” means matching the request to the person who can act on it—not announcing the problem to everyone within earshot.
| Customer need / concern type | Primary staff to notify | What to include in the handoff |
|---|---|---|
| Noise, drivability, warning light, leak | Assigned / dispatched technician | Exact concern wording, when it occurs, prior history, customer availability for ride-along if needed |
| Parts status, ETA, supersession, core | Parts advisor / parts manager | Year/make/model/engine, VIN if required, part numbers already tried, promise time at risk |
| Warranty eligibility, policy exception, heated customer | Service manager / warranty admin | Prior RO, coverage question, customer expectation, safety flags |
| Body, glass, upholstery, alignment specialty | Sublet coordinator or specialty tech | Scope, insurance vs customer-pay, keys/photos needed |
| Shuttle, loaner, pickup timing | Dispatcher / rental coordinator / porter lead | Promise time, customer contact, vehicle readiness |
| Cashier / invoice dispute at delivery | Cashier + manager as needed | Authorized vs performed lines, declined work, tax/shop supplies |
Qualities of an effective handoff
A strong internal handoff is specific, timely, and owned:
- Who needs it (named role or person)
- What the customer said (quote the concern; avoid translating prematurely into a parts sale)
- When it must be addressed relative to the promise time
- How success will be verified (road test condition, scan, visual leak check)
- Where details live (RO line, photo, sticky note only if the shop’s system requires a redundant cue—never instead of the RO)
Vague handoffs create comebacks: “Customer says something’s wrong with the brakes” is not enough. Better: “Customer reports a soft pedal after sitting overnight; firm after two pumps; no ABS light; started after last pad job 8 months ago; needs verification before 3:00 p.m. promise.”
Do not “improve” the concern by guessing the part. If the customer says “it pulls right when braking,” write that—do not dispatch “replace RF caliper” until diagnosis supports it.
Task 7: Understand the Diagnosis Before You Sell It
Technicians speak in symptoms, tests, and component language. Customers buy outcomes and risk reduction. Your job is to understand the diagnosis well enough to explain it accurately—not to nod and hope.
Clarifying questions consultants should ask technicians
Use these until you could explain the story without looking at the RO:
- What confirmed cause did testing show (not just what might be wrong)?
- What tests ruled out related causes?
- Is the condition intermittent? What is the confidence level?
- What must be replaced vs cleaned vs adjusted vs further diagnosed?
- Are there related damaged parts or fluids that fail if we only do the minimum?
- What happens if the customer declines today?
- What verification will prove the repair (road test criteria, freeze-frame cleared, leak check after heat cycle)?
- Any parts delays or special tools that change the promise time?
If you cannot answer those for yourself, you are not ready to call the customer.
Translate tech language without dumbing it down
| Technician phrasing | Customer-friendly translation | What not to say |
|---|---|---|
| “RF outer CV axle clicking on lock” | “The right-front axle joint is worn; it clicks when you turn sharply because the joint is loose inside the boot area.” | “Your whole axle assembly exploded.” |
| “P0302 misfire; coil primary open” | “Cylinder 2 isn’t firing correctly; testing points to a failed ignition coil on that cylinder.” | “The computer is bad.” (unless proven) |
| “Front pads at 2 mm; rotors under min after cut” | “Brake pads are at the replacement limit, and the rotors are too thin to resurface safely—both need replacement for a proper brake job.” | “We always replace rotors no matter what.” |
| “Could be the pump or the filter; needs pressure test” | “We haven’t confirmed the failed part yet; the next step is a pressure test so we don’t replace parts by guesswork.” | “It definitely needs a full pump assembly.” |
Honesty about uncertainty is part of Task 7. “Could be” means more diagnosis—not a firm parts recommendation yet.
Bridging Tasks 6 and 7 in One Workflow
A clean consultant loop looks like this:
- Capture the customer concern precisely at write-up (feeds Task 6).
- Dispatch with complete symptom detail to the right tech.
- Receive diagnosis; ask clarifying questions until cause, options, and verification are clear (Task 7).
- Present recommendations with features/benefits and priorities (ties to Sales Skills chapters—but only after you understand the tech story).
- Relay the customer’s authorization or decline back to staff with updated scope and time (Task 6 again).
- At delivery, explain what was found and fixed in the same language you used on the phone.
Skipping step 3 is a common exam trap: a consultant who memorizes a parts pitch without understanding the diagnosis cannot answer “why this repair?” or spot an incomplete story.
Scenario: Intermittent No-Start
A fleet customer reports an intermittent no-start after overnight parks. You hand off to the electrical-driveability tech with temperature, time-of-day, and recent battery service history. The tech finds a parasitic draw and a failing aftermarket accessory. Before calling, you ask: Is the battery still good? Was the OEM circuit involved? What must be disconnected or repaired to verify? You then explain to the customer that testing found an accessory drawing power with the key off—not a “bad starter”—and present repair options with a verification plan (draw retest after repair). Internal clarity produced an accurate external recommendation.
Professional Boundaries
- Do not change tech findings to match what the customer wants to hear.
- Do not withhold related safety findings the tech documented.
- Do not claim manufacturer “required” replacement if the tech only recommended it.
- Do escalate when diagnosis and customer expectation conflict (manager/warranty).
- Do close the loop: after the customer decides, tell the tech and parts what was authorized so work and ordering match the RO.
Tasks 6 and 7 are scored shop-operations skills because poor communication creates the comebacks covered in Task 4—even when technicians are skilled.
A customer reports a soft brake pedal after sitting overnight. Which handoff BEST satisfies Task 6?
A technician says a noise “could be the water pump or a belt idler” and recommends a pressure/play inspection next. What should the consultant tell the customer?
Before presenting a technician’s repair recommendation, which clarifying question is MOST important for the consultant to ask?
After a customer authorizes only part of a technician’s recommended repairs, what should the consultant do next internally?