How to write an 8D reply to a customer complaint with AI

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.

What to give the AI

Give it four things: the complaint, what you found, what you have already done, and who is on the team. For example:

• Customer: Nashik Drive Parts
• Part: Flange, gearbox output, part no. FL-210
• Complaint: 8 flanges from lot 2609-03 rejected at incoming inspection. Bore diameter over the drawing limit. Quantity received: 600.
• Findings: Checked 150 pcs from our stock of the same lot. 5 had the bore 0.04 mm over the upper limit. Boring insert on CNC 2 found chipped. Insert changed on 12 Sep. Tool offset log not filled on the night shift.
• Containment: All 420 pcs of lot 2609-03 in our stock held and checked with a plug gauge. 600 replacement pcs sent on 14 Sep.
• Team: Ravi (QA), Deepak (production), Meena (tool room).

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.

What to ask

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.

What to check

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:

1. D4. It should list what you found: a chipped insert and a missing offset log. It should not say which one caused the fault, unless you proved it.
2. Numbers. 8 rejected, 600 received, 5 of 150 checked, 0.04 mm, 420 held. Compare each one with your notes.
3. Names. D1 should have only the people you named. Remove any role the AI added.
4. Dates. 12 Sep and 14 Sep, as you wrote them. Nothing new.
5. Every [CHECK]. Fill each one with real work, or keep it and tell the customer when you'll send it.

Why this works

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.