The Customer Said It Was Faulty. What Have You Actually Checked?
Separate the customer’s report, checked observations and open questions in a complaint record. Keep the case neutral without inventing a diagnosis or proof rule.

The case note says “faulty product”. Is that the customer’s description, an observation someone has checked or a conclusion the shop has already reached?
A complaint record is more useful when those states are distinguishable. The purpose is to preserve the customer’s report accurately and keep uncertainty visible while the case is handled.
Record the report without changing its meaning
Imagine a fictional specialty shop receiving a message about a lamp fitting. The assistant records what the customer describes, along with the relevant case context, without rewriting it as a technical diagnosis.
Use clear attribution where it matters: the customer reports a particular behaviour; a colleague has inspected a particular record; another question is still open. These statements can coexist without implying that the customer is being dismissed.
Avoid loaded labels that add suspicion or certainty the information does not support. A neutral record should make the case easier for another person to understand, not steer them toward an unsupported judgement.
Identify what has actually been checked
For each material observation, record its source and the relevant date. Distinguish an order-system entry, a supplied description and a direct inspection rather than treating all three as the same kind of evidence.
Keep the record proportionate to the task and the shop’s approved information-handling arrangements. Do not collect unnecessary personal material merely because there is space for another attachment.
If more information is needed, identify the decision it would help the responsible person make. This article does not establish a burden of proof, a compulsory photo requirement or a reason to postpone an action otherwise due in the case.
Leave the unknown question explicit
An unresolved question may concern the item, the sequence of events or the appropriate decision. Give it a clear description and a person or role who can review it.
Do not fill the gap with a plausible explanation. “The packaging caused it” is a conclusion that needs a basis, not a convenient default because the parcel arrived damaged.
Equally, avoid allowing the unknown detail to obscure everything that is already known. The case handler can preserve the report, existing commitments and approved next actions while a separate question is reviewed.
Compare two versions of the case note
Use a fictional example. In one note, write a broad conclusion without attribution. In another, separate the report, checked observations and unresolved question. Ask a colleague which next decision each note actually supports.
If they infer a certainty the source does not provide, clarify the wording or the evidence state. If a question remains outside the handler’s authority or expertise, route it appropriately rather than resolving it through confident prose.
A trustworthy case file is not the one with the strongest-sounding diagnosis. It is the one that lets the next responsible person see what was reported, what was checked and what still needs an answer.
Continue the case-handling question
See the related guide: Give the Next Handler One Coherent Case.
- The Customer Contacted You Twice. Is It One Complaint or Two?
- Your Colleague Is Away. Can You Continue This Complaint Without Starting Again?
For a written practice option, review the Complaint Handling for Small Online Shops course overview. It offers written case practice; people remain responsible for real decisions and practical follow-through.
Check the course contents and current terms. Affiliate link: Superstore may earn a commission if you buy.




Discussion 0
What did this article make you think about?