Complaint Handling Procedure

A customer reports that a repaired car has the same fault again, and without a clear process the service desk may forward the message to several teams so that nobody owns the answer. A procedure gives the complaint a reference, an owner and a next step.

It should make complaining easy through appropriate channels and explain what information helps the review without demanding irrelevant personal details. Acknowledge receipt and state when the customer can expect an update, and note that a business can set its own target where law does not prescribe one, so a twenty-four-hour acknowledgement is an example, not a universal legal deadline.

Record the complaint, product or service, dates, customer account and requested remedy, separating the customer's description from the organisation's findings, so that an accurate log allows a reviewer to follow the case without repetition. Assess urgency and risk too, since a safety defect, data incident or vulnerable customer may need immediate escalation outside the ordinary queue while a routine billing query may use a simpler route.

Assign a person or team with authority to investigate, who should collect relevant records and speak to people involved, and a serious allegation about someone's own conduct should not be judged by that person without suitable oversight. Listen to the customer's desired outcome, because a refund, repair, explanation or apology may each be appropriate in different cases, and promise only what the business can lawfully and practically deliver.

Set realistic response times and communicate delays, agreeing how often the customer will hear from the owner, since a complex investigation may take longer than a simple correction but silence makes the problem worse. ISO 10002 gives guidelines for an organisational complaints process, including accessible feedback, resolution and analysis for improvement, and it addresses product and service complaints, not employment disputes or external adjudication.

The process should be adapted to the business and regulatory setting. Distinguish a complaint from a request for information without using the label to avoid responsibility, because a person who asks why a bill is wrong and requests correction is likely raising a service problem and should be routed to someone who can fix it.

Explain the decision with evidence and next steps: if the business accepts fault, state the remedy and timing, and if it disagrees, give reasons and tell the customer what review or external route is available where applicable. Escalation should be real, so define when a supervisor, specialist, insurer or regulator needs to be involved, because a five-day escalation target is only useful if an owner can actually act at that point.

Close a case only when the decision has been communicated and promised action is completed or tracked, since marking a ticket resolved after sending a template reply can hide unfinished repairs or refunds. An illustrative within-target rate is complaints resolved within a defined target divided by complaints closed in a period, and if 170 of 200 meet it, the rate is 85%, although reopened cases and target changes should be excluded or explained before comparing months, and speed is not the only measure, as a rushed rejection may meet the target but create another complaint, so repeat contact, remedy completion and customer feedback should be reviewed alongside timeliness.

Analyse patterns by product, site, root cause and severity, because ten complaints about the same part may signal a wider quality issue, and protect complaint data by restricting access, since records can include health, financial or identity details. For owners, a good complaint procedure produces a fair answer for the person who spoke up and evidence for improving the service, and frontline workers should be trained to own the handoff so that customers never repeat the story from the start.