Turn a customer complaint and your findings into an 8D reply, D1 to D8. Anything you haven't found yet stays marked for you to fill in.
A customer rejects parts at incoming inspection. They send a complaint and ask for an 8D reply. You have some findings, but not all the answers yet.
AI can put your findings into the eight sections fast. But AI likes to fill every gap. It may write a root cause you haven't proved, or a test you never ran. If that goes to your customer, it is your name on it.
Here is how to get a first draft that says only what you know.
Give it four things: the complaint, what you found, what you have already done, and who is on the team. For example:
Write what you found, not what you think happened. "Insert found chipped" is a finding. "The chipped insert caused it" is a cause. You may not have proved that yet.
Copy this into ChatGPT, Claude or Gemini. Put your own details in the brackets.
Write an 8D reply to this customer complaint.
Customer: [customer name and plant]
Part: [part name and part number]
Complaint: [what the customer rejected, how many, and why]
Findings so far: [what you checked and what you found]
Containment done: [what you held, checked and sent]
Team: [names and departments]
Rules:
- Use these headings in order: D1. Team, D2. Problem, D3. Containment, D4. Root cause, D5. Corrective action, D6. Action taken and checked, D7. Stopping it from happening again, D8. Closure.
- Fill each section only from what I gave you. Short sentences.
- Write what we found as findings, not as a proven cause. If my findings don't prove the cause, write [CHECK: what is missing] under D4.
- If I haven't covered a section, write [CHECK: what is needed]. Do not guess.
- Never make up a name, a measurement, a test result or a date.
- Keep every part number, lot, quantity and date exactly as I wrote it.
- No blame on people. Calm and factual.
You get eight sections. With the example above, D6, D7 and D8 will mostly be [CHECK] lines. That is correct. You haven't done that work yet.
Before you send it, check these things:
A customer can accept "we haven't confirmed this yet". A customer cannot accept a root cause that turns out to be wrong.
The rule "findings, not a proven cause" keeps D4 honest. The [CHECK] lines show you, and your customer, what is still open.
You can send the first reply within a day. Then send an updated 8D as each [CHECK] is closed.
Before you ask, give the AI the facts that are obvious to you and unknown to it.
Decide how you'll check a reply before you ask for it, so a wrong answer doesn't reach anyone.
Turn rough shop-floor notes into an SOP with safety, steps and checks. Every value stays, and a missing setting like a torque is marked, not guessed.
Answer a new customer's vendor registration questions from your own company fact sheet. Anything the sheet doesn't cover is marked, not guessed.
Five workflows that turn your own findings, readings and notes into 8D replies, RFQ answers, questionnaires, SOPs and deviation requests.