A complaint needs a fair answer, not a defensive one.

Imagine a buyer arriving to collect a repaired item after being told it was ready. It is still on the workbench. The complaint is not only about the repair. It is also about the wasted trip and the promise that led to it.

Handling a customer complaint starts with understanding the problem and the outcome the person wants. Record the facts, assign someone to review them fairly, explain the decision and carry out any agreed remedy. An apology helps when it comes with a useful next step.

Listen for the request beneath the frustration

Let the person describe what happened without making them repeat details already in the record. Then reflect the concern in plain language: “You were told collection was ready, travelled here and could not collect the item.” Ask what would help now.

Do not agree to an unverified accusation or dismiss a problem because the tone is sharp. Separate the reported facts from what still needs checking. If there is threatening behaviour, follow your staff-safety process while keeping a suitable route for the underlying complaint.

Build a small factual record

Keep the timeline short and checkable

Record the relevant promise, event and contact. Link evidence through approved systems and avoid speculative labels about the customer or colleague. A neutral note is easier for someone else to review.

Ask who can review it fairly

Where practical, use a reviewer who was not directly involved in the disputed decision. The Ombudsman's complaint principles support fair review, accurate records and proportionate remedies. They concern UK public bodies, not the legal obligations of an Indian business.

Give an update even while the review is open

Acknowledge the specific concern and give a realistic review or update time. Do not use an internal investigation as a reason for silence. If the time slips, explain that before the customer has to chase.

Atlassian's incident-response handbook separates customer communication from investigation. That coordination idea transfers to an ordinary complaint: the person providing updates does not have to be the person checking every detail.

Use the escalation brief when you need a decision outside your authority. Keep one named contact responsible for the next update.

Explain the decision and the next route

Use an original response outline: “You raised [concern]. We checked [relevant evidence]. We found [supported finding]. We will [authorised action] by [confirmed time]. If you disagree or need a further review, [appropriate route].”

Give reasons when a requested remedy is not available, and describe any genuine alternative. Check the applicable policy and obligations with the responsible adviser where needed; this guide does not set legal deadlines, compensation amounts or limits on a customer's rights.

The reply-template guide helps keep the language clear. Avoid treating a refund as permission to ignore the underlying service failure.

Confirm the action and keep the lesson

Before closing, check that the promised correction actually happened. Record whether the customer received the explanation, whether anything is still open and how a further response will be handled. Silence is not proof of satisfaction.

Look for one process change: perhaps only the workshop can confirm collection readiness, and reception sends the message after that check. Review repeat reasons using the support-metrics guide. A complaint record becomes valuable when it prevents the same avoidable confusion from being built into tomorrow's routine.