Two pages at most, one structure for every customer, every sentence backed by a record. The structure matters more than the wording, because a reader who knows where to look reads the answer in two minutes and files it.
The six sections
| Section | What goes in |
|---|---|
| 01 The complaint | What the customer found, when, how many, which delivery and lot, in their words |
| 02 What is protected | Lots identified, quantities blocked, sorting results per quantity, marking, replacement with its date |
| 03 What we found | The cause and the escape point in plain words, with the evidence named |
| 04 What we changed | The action, the owner, the date it was in place, the document that changed |
| 05 The proof | Quantity checked, result, date, who checked, and the date of the next check |
| 06 What it means for you | Open quantities, next deliveries, anything the customer has to do or decide |
Section 02 is the one customers read first and the only one they can verify themselves. Give it numbers: 4,200 parts in three lots, 3,000 checked, 120 bad, 66 replaced on the next day.
If your customer requires their own form or a portal entry, fill it from your record. Do not keep a second case file, and note the requirement in the register next to the account.
What you do not write
- No guesses. A cause without evidence will be quoted back to you at the next case.
- No blame. Not a person, not a shift, not your supplier by name. The reader cares about your process.
- No promise without a date, and no date without an owner who agreed to it.
- No legal opinion and nothing about liability or warranty. That belongs to the responsible function in your plant.
- No internal cost figures and no comparison with other customers.
Why answers fail
| Fault | Why it hurts |
|---|---|
| It arrives late | The content stops mattering. A late answer reads as a plant without control |
| The cause has no evidence | The sentence becomes a precedent you cannot withdraw |
| An action has no date | The customer has to chase, and chasing is how escalations start |
| The containment is described in general words | Quantities and results are the only part a customer can check |
| Commercial and technical content are mixed | A credit discussion inside a technical report delays both |
Three contacts, not one
Between the acknowledgment and the final answer, plan the contacts instead of leaving them to the day. Within one working day: we have it, this is the number, this person owns it, you hear from us on this date. When containment is confirmed: what is protected, with quantities and results, and when the replacement arrives. With the final answer: cause, escape point, action, proof and the next check date.
An escalated case is usually a case with a slow answer, not a case with a bad fault. When a customer line stands and the phone rings every hour, agree one named contact and one call time per day, and put the containment status in writing after every call.
What it changed in the example
| Stage | Baseline | After twelve months |
|---|---|---|
| Acknowledgment to the customer | 2.5 days | 0.5 days |
| Containment confirmed | 6.0 days | 2.0 days |
| Cause and action agreed | 14 days | 6 days |
| Final answer sent | 19 days | 8 days |
Working days from the day the complaint arrived. The containment confirmation moved first, because it needs organization and no analysis. The share of answers that reached the customer by the agreed date rose from 42 to 92 percent, and that figure is the one worth reporting: it does not depend on how difficult your parts are or how fussy your customers are, only on whether your plant keeps the dates it set itself.