Definition
A complaints procedure is a business's written account of how it handles complaints, from the moment one is recognised to the moment it is closed.
Its purpose is consistency rather than generosity. The recovery sequence still does the work with the customer; the procedure makes sure it runs for a complaint made on the phone as surely as for one made in a review. The tutorial on writing a complaints procedure drafts one step by step and sets up the review that turns the log into fixes.
The promises inside it belong to the business and are set from what it can keep; they are not legal deadlines, and nothing in a procedure can reduce what customers are entitled to. Some regulated sectors, financial services and energy among them, run separate complaint rules and ombudsman schemes, which a business in those sectors must follow and should take qualified advice on.
What a procedure contains, and what sits beside it
- A definition. One sentence staff can apply on the spot, with the instruction that a doubtful contact is treated as a complaint. A plain request for information goes to the ordinary queue instead.
- One log. Calls, emails, forms, chat, social messages, reviews and notes written in the field all end up in a single record. It holds personal data, so it records only what handling and learning need, for the period the business has decided.
- Promises. How soon the customer hears that the complaint has arrived and who has it, and how soon a full response, or an explanation of the delay, follows.
- Roles. For each type of complaint, who investigates and who decides. Someone whose own work is the subject can supply facts but does not judge the outcome.
- Stages. Who looks at the case afresh if the first answer does not satisfy, and which complaints go straight to a senior person.
- Closure and cause. How a case is closed, with its cause recorded apart from its reason.
Two things sit beside the procedure rather than inside it. What staff may offer for each common failure, and when they must ask, goes in a separate table, which the remedies and goodwill limits tutorial draws up from the complaint log; keeping it apart lets remedies change without rewriting the route. And a short customer version tells the public how to complain, what happens next and how to take it further.
In practice: the contact page, backlogs and service audits
The customer version needs a home. The tutorial on designing a contact page gives complaints their own line under a heading that uses the word, so that anyone with a complaint can tell the business expects to receive one.
A backlog tests whether it holds under pressure. The guide to clearing a support backlog keeps complaints out of the batch replies: any found in the queue are logged with the date they first came in, and the promises still apply.
The customer service audit scorecard asks whether it works in practice: it makes the complaint log a gate, and without one log that every channel feeds, its scores for recovery, remedies and causes stay provisional.
A joinery firm counts its complaints for the first time
Felkaur Joinery, a maker of fitted wardrobes and kitchens with 4 fitting teams, received complaints by phone, by email and in reviews on 2 directories. Whoever saw each one dealt with it, and nobody had ever added them up. The owner wrote a procedure of 2 pages: a one-line definition, one log that every channel feeds, acknowledgement within 1 working day and a full response within 7 working days. At the first monthly review the log held 19 complaints. 13 described doors or drawers that stopped closing properly after fitting, and the cause column traced 11 of them to one step: units levelled before the worktops went on. The fitting checklist now has the units levelled again after the worktops go on.
Related terms
An Escalation RouteA short written route naming who front-line staff contact, how and how fast, when a problem is beyond what they can decide alone. is the team's internal path to someone who can decide; the procedure's stages are the customer's way upward. The Remedy TableThe written list of standard remedies for common failures, keeping rights apart from goodwill, with an allowance staff use unasked and approval levels above. sets the standard offer for each common failure and the limit above which staff ask. A Repeat ContactA customer contacting the business again about the same problem, the clearest sign that the first answer did not end the customer's work. shows that a first answer did not end the problem, and the procedure's definition decides when such a contact is logged as a complaint. Each logged complaint carries a Contact ReasonThe main reason a customer contacted support, tagged by the agent from a fixed, defined list so volume and other service metrics can be read by cause. from the list used for every other contact, so complaints can be compared with the rest of the queue. A SLAA published promise between teams, or with a supplier, about what each type of request needs and how quickly it will be handled, agreed rather than imposed. is a promise between teams or with a supplier, where the procedure's promises are made to customers; both hold only when they are set from what is actually achieved.
Common confusions
- The procedure is a legal document, or the same as an ombudsman scheme. It is the business's own process with its own promises; a sector scheme sits outside the business, and in a regulated sector the procedure follows it.
- The procedure says what to give. Remedies and goodwill limits live in the remedy table; the procedure says how a complaint travels, not what it is worth.
- Only angry customers complain. A courteous email asking for something to be put right is a complaint as much as a furious review; tone and channel do not decide it.
- Replying to the review handles the complaint. The complaint is still logged, or the count misses it.
- Closed means quiet. A case is finished once the customer holds the complete response and whatever was agreed has been carried out, not when the conversation stops.
