Made for Auto Mechanics
Turn a Customer Concern Into a Diagnostic Plan
Organize the customer's exact concern and known vehicle facts into a focused plan with likely systems, first checks, tools, questions, and decision points.
We'll use them to write your prompt.
Make Your Play
Give us the situation. We’ll build the prompt.
Avoid jumping straight to a part or test.
Your answers save as you type.
What you'll do
This is the plan inside your prompt. Add your details first. Then follow these steps with ChatGPT or Claude.
Make Your Play
Turn a Customer Concern Into a Diagnostic Plan
Tell us what the prompt needs to know
Start with the questions below. Each answer personalizes the playbook and builds the prompt you’ll use at the end.
Your situation
Enter the customer's wording as closely as possible, including sounds, smells, feel, timing, and expectations.
0/10000
Enter the year, make, model, mileage, engine, drivetrain, and any other confirmed identification details.
0/10000
List warning lights, messages, scan codes, freeze-frame facts, gauge behavior, and other confirmed symptoms.
0/10000
List recent repairs, maintenance, collisions, accessory installations, jump-starts, or parts replacement that may affect your starting point.
0/10000
Describe when the concern happens, how often it happens, and what temperature, speed, load, weather, or driving conditions are present.
0/10000
This playbook was updated. Review your inputs before copying.
What you'll do
Check a step when you finish it.
Fill in the fields above to generate your prompt preview.
Assembled prompt
Beginner instructions
Paste the customer’s wording without cleaning it up. Add every vehicle fact you already have, including the VIN details available to you, mileage, engine, warning lights, codes, recent work, and when the symptom happens. Run the prompt, then confirm each missing fact before you follow the plan. Use approved service information for specifications and procedures.
Advanced instructions
You can add scan data, freeze-frame values, waveform observations, test results, environmental conditions, and prior diagnostic steps. Use the plan as a starting hypothesis map, then adjust the order when your first verified result raises or lowers a system’s likelihood.
Use this when
Use this before you begin diagnosing a vehicle, especially when the concern is vague, several systems could be involved, or recent work may affect your starting point.
You'll need
- Customer's exact concern
- Vehicle details
- Warnings and codes
- Recent repairs
- Known conditions
You'll get
- One ordered diagnostic plan
- You can identify the concern to verify, immediate safety checks, relevant systems, unresolved intake questions, required tools, first tests, decision points, and evidence to record
- Not treated a code, symptom, or recent repair as proof of a failed part.
By the end of this playbook
You will have:
- One ordered diagnostic plan
- You can identify the concern to verify, immediate safety checks, relevant systems, unresolved intake questions, required tools, first tests, decision points, and evidence to record
- Not treated a code, symptom, or recent repair as proof of a failed part.