Explaining a repair in plain language customers actually approve
The single most consistent problem at the service counter is translating "camshaft position sensor" into something a customer will pay for without feeling handled. Service advisors report copying the tech's notes into AI and getting a clear, non-condescending explanation of what is wrong, why it matters, and what happens if it waits. The catch is that the model will happily invent a cause or a consequence that was never in your notes — so the prompt has to lock it to your words.
You are helping a service advisor at an independent auto repair shop explain a repair to a customer in plain language. Write a short explanation the advisor can say at the counter or send as a text. Repair the technician found: {{repair_finding}} Vehicle: {{vehicle}} What the customer originally came in for: {{customer_concern}} Write the explanation in three short parts: 1. What it is — the part or system, in everyday words, with the technical name in parentheses once. 2. Why it matters — what it does and what happens if it is not addressed, stated in terms of drivability, safety, or further damage. 3. What we recommend — the action, framed plainly. Hard rules: - Use ONLY the finding I gave you. Do NOT add causes, symptoms, mileage, prices, or safety claims I did not state. - Do NOT include torque values, fluid capacities, procedures, or part numbers — those are not customer-facing here and you must not guess them. - No scare tactics and no guarantees ("this will fix everything"). - Under 120 words, plain language, warm but straight. - If the finding is missing something the explanation needs, write [ASK ADVISOR: what's missing] instead of inventing it.
Fill in your details and the prompt updates live — then copy.
That noise you heard is your front brakes telling you they're done. The pads (the material that squeezes the wheel to stop you) are worn down to about 2mm, and the rotors — the metal discs they press against — are now thinner than the minimum safe spec, which is what's causing the grinding. Why it matters: once pads are this thin, you're braking on metal, which lengthens stopping distance and can damage other parts. It's a safety item, not a "wait and see" one. What we recommend: replace the front pads and rotors as a set so the new pads seat correctly.
The full workflow
- Paste the tech's finding, vehicle, and the original concern — no customer name.
- Run the prompt and read it against what the tech actually found.
- Resolve any [ASK ADVISOR] flag from the tech, never from memory.
- Add the price yourself; keep the AI out of numbers.
- Send it or use it as your script at the counter.
Watch out for
The AI writes the explanation, not the diagnosis — never let it add a cause, symptom, or 'this will also fix' claim your technician did not find; that is how a confident sentence becomes a comeback.
Never guess or include torque specs, capacities, or procedures in customer text — and never treat anything the model says about the fix as service data. OEM information and your own testing are the only source of truth.
Strip customer names, plates, VINs, and addresses before pasting — that data is regulated under CCPA and similar state laws, and consumer AI tools may retain what you enter.
Where this comes from
Every use case on this site is grounded in real reports from working auto mechanics — not invented by us.