2.3 Documenting Customer Concerns & Requests

Documenting Customer Concerns & Requests

Quick Answer: Discuss the concern with the customer, listen actively, ask clarifying questions about symptoms and conditions, then document the request in clear repair-order language a technician can follow. Vague notes and interrupted interviews are common failure patterns on ASE C1 scenarios.

Task 3 — Discuss and document concern/request with customer — is one of the highest-leverage Communications skills. Everything downstream (diagnosis time, estimate accuracy, CSI, comebacks) depends on whether the repair order captures what the customer actually experiences.

Discuss First, Document Second

"Discuss" means a real conversation, not a one-line clipboard. The consultant invites the story, listens without rushing to a sale, and confirms understanding. "Document" means translating that conversation into written concern language on the RO.

Active listening behaviors C1 expects in spirit:

• Give full attention; minimize interruptions
• Use brief encouragers ("go on," "what happened next?")
• Paraphrase: "So the vibration starts around 45 mph only when braking lightly—did I get that right?"
• Note emotion without being controlled by it: acknowledge frustration, then gather facts
• Distinguish request vs. concern: "I'd like an oil change" may coexist with "and the car smells hot on the highway"

The Symptom Detail Framework

Technicians need reproducible details. Train yourself to collect a consistent set:

You will not ask every question robotically. You will steer the interview until the write-up answers: What should the technician try to verify?

Clarifying Questions vs. Leading Questions

Good clarifying questions open the description:

• "Does it happen cold, hot, or both?"
• "Is it a squeal, grind, or click—and can you imitate it?"
• "Any recent repairs, impacts, or dashboard messages?"

Official-sample nuance: asking a customer to imitate a noise is a useful interview technique, but ASE's own C1 sample item about a brake-noise concern keys the response that a technician will need to evaluate the vehicle—not the imitation request, a reassurance that the noise is "common on all vehicles," or an average price quote. Use imitation to sharpen the write-up; choose technician evaluation when the stem asks what the consultant should do about the concern.

Leading questions push a conclusion too early:

• "It's probably your brakes, right?"
• "You just need pads—how many miles are on them?"

On C1, premature diagnosis by the consultant is a trap. Your role is to gather and document; technicians diagnose. You may share general process ("we'll inspect and advise") without inventing a root cause in the lane.

Write-Up Language: From Vague to Actionable

Compare these concern statements:

Strong write-ups use customer-reported language plus conditions. They do not invent causes ("bad wheel bearing") unless the customer was told that elsewhere—and even then, document as "customer was advised previously that…" rather than as confirmed fact.

Requests, Maintenance, and Multi-Item Visits

Customers often mix requests:

1. Scheduled maintenance they want performed
2. Symptoms they want diagnosed
3. Questions about a noise a relative mentioned

Document each distinctly. Bundling everything as "LOF and check car" loses the diagnostic concern. If the customer only wants an oil change and declines diagnosis of a symptom they mentioned, document the mentioned symptom and the decline of inspection if your process requires it (decline documentation appears in later chapters—here, focus on capturing what was discussed).

Common Interview Failure Modes

Scenario Walkthrough

Customer: "My car is shaking."

Weak path: Write "vibration—check," quote an alignment, move on.

Strong path:

1. "Thanks for telling us—when do you notice the shake?"
2. Customer: "Around 60 on the highway, steering wheel shakes."
3. "Does it change when you brake or only while cruising? Cold or after a long drive?"
4. Document: Customer reports steering-wheel shake at ~60 mph during steady cruise; does not change under light braking; noticed for two weeks; tires recently purchased elsewhere.
5. Confirm by reading it back; then discuss next steps (inspection/road test process) and transportation if needed.

That write-up gives the technician a verification target. The weak path gives them a fishing expedition.

Linking to Later Communications Tasks

Documenting concerns feeds:

• Accurate estimates and authorization (you cannot authorize what you never captured)
• Status expectations (diagnosis vs. maintenance timelines differ)
• Addressing original concerns at delivery (sales skills later in the outline)
• Comeback prevention (if the RO never stated the real complaint, "fixed" may miss it)

For now, master the interview and the written concern line. C1 will often ask which note is most complete or which question the consultant should ask next.

Exam Focus

Prefer answers that show listening, clarifying symptom conditions, and documenting specific, technician-usable concern language. Reject answers that jump to a parts sale, mock the customer, or leave "check and advise" with no symptom detail when detail was available.