What a complaints procedure adds to good recovery
The service recovery and complaints guide sets out how to recover a single failure well: the recovery sequence from acknowledgement to learning, empowerment and escalation, public complaints and consumer rights at a general level. A procedure does not repeat that sequence. It makes sure the sequence happens every time, whoever is on shift and wherever the complaint arrived.
Without a procedure, complaints fall through the gaps between channels. One arrives as a phone call and lives only in the memory of the person who took it; another is a review nobody in support saw; a third is a note on a delivery form. Each may be handled well in isolation, yet nobody can say how many complaints the business had last month, what they were about, or whether any customer waited too long. The procedure fixes that by giving complaints one route, one record and one set of promises. Because the complaints procedureThe written process for complaints: what counts as one, how every channel feeds one log, the response promised, who decides and how customers escalate. is written down, a new starter or someone covering a holiday can follow it without asking how complaints are handled here. A complaint count that has risen month after month, with some complaints never logged and others answered twice, is diagnosed cause by cause in the troubleshooting page for customer complaints increasing.
It also protects the business. Recovery is partly goodwill and partly obligation, as the recovery guide explains, and a process that ignores customers' rights creates legal risk on top of the customer problem. A written procedure is the place to make sure staff never mislead customers about those rights. One boundary applies throughout: regulated sectors such as financial services and energy have their own complaint rules and ombudsman schemes. This tutorial does not cover them, and a business in such a sector should take qualified advice before writing its procedure.
Before you start
- Read the recovery guide. The procedure carries its sequence and its principles on empowerment, escalation and public replies; know them before writing.
- Gather a quarter of complaints from everywhere. Pull what you can find from email, chat, phone notes, social replies, reviews, app store reviews and staff paperwork. The mess you find is the case for the procedure.
- List the people involved. Who takes complaints today, who can authorise a refund or replacement, who owns each part of the operation that complaints are about.
- Know your contact reasons. Complaints should be tagged with the same reasons as other contacts, plus a cause. The tutorial on tagging support contacts by reason builds that list.
- Check what applies in your sector. If the business operates in a regulated sector, find out what its complaint rules require before deciding anything below, and take advice.
The steps
Define what counts as a complaint
Write a one-sentence definition staff can apply in the moment, for example: any expression of dissatisfaction about our products, service or staff where the customer wants something put right or wants it noted. Add what it covers regardless of channel or tone, so a polite email and an angry review are both complaints. Add the instruction that matters most: if unsure, treat it as a complaint. A complaint handled as a routine question is the one that returns louder. Note the things that are not complaints under this procedure, such as a request for information, so they go to the normal queue.
Open every channel into one log
List every place complaints arrive: email, web form, chat, phone, social messages and comments, reviews on listings and app stores, and anything staff in the field hear or write down. For each, name who moves the complaint into the log and how quickly. Public complaints still get their public reply, as the community management guide sets out for social channels and the routine for app rating prompts and review replies sets out for app stores, but the complaint itself is logged like any other. The log can be a field in your support tool or a shared register; what matters is that there is one. A business with several sites brings each site's phone and counter into the same log, which the guide to running customer service across several sites sets out alongside the other decisions the centre and the sites share.
Decide what the log records
Choose the fields before the first entry, using the table later in this page: who, what, when, how it arrived, what the customer wants, who owns it, what was done and why it happened. The log holds Personal DataAny information relating to an identified or identifiable living person, such as a name, email address, location data or an online identifier., so record only what handling and learning from the complaint need, limit access to the people who handle complaints, and keep entries no longer than the period the business has decided, as the site's data guides describe under the GDPR. The guide to data retention across marketing tools explains setting periods by purpose and making deletion reach every copy; whoever owns data protection sets the period.
Set your acknowledgement and response promises
Decide two promises the business can keep: how quickly a customer hears that their complaint has been received and who is handling it, and how quickly they receive a full response or an update on why it is taking longer. Set them from your own capacity and from what customers in each channel expect, as the support channels and self-service guide does for service standards. These are the business's promises, not legal deadlines; a regulated sector may impose its own. Track the promises as a KPIA metric tied directly to an objective. someone owns, because a promise nobody measures stops being kept.
Name who investigates and who decides
For each type of complaint, name who gathers the facts and who decides the outcome. Often they are the same person for simple complaints and different people for serious ones. A RACI matrix works well here: one row per complaint type, with the person responsible for handling it, the one accountable for the outcome, who is consulted (the driver, the warehouse, the account manager) and who is informed. The person who caused the problem can supply facts but should not decide the outcome of a complaint about their own work.
Write the response, not only the remedy
The full response is written, even when the conversation happened by phone. It restates the complaint in the customer's terms, says what the business found, apologises where it was at fault, sets out what it will do and by when, and tells the customer how to escalate if they are not satisfied. Standard remedies for common failures, and the limits staff can act within, belong in a separate remedy table so the procedure stays short; the tutorial on setting remedies and goodwill limits builds it. The log then records which row of 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. each remedy came from, or who approved anything outside it. Responses never mislead customers about their rights: as the recovery guide states from the Competition and Markets Authority's guidance for businesses, remedies such as repair, replacement or refund apply when goods or services do not match what was promised. Where a complaint arose because the customer believed a marketing claim, the Advertising Standards Authority's codes are the reference for whether the claim was acceptable, and the claim itself may need fixing.
Set the escalation stages
Define how a complaint moves up if the customer is not satisfied with the first response, or if it is serious from the start. A common shape is the person handling it, then a named senior person who reviews the case afresh; larger businesses may add a further stage. For each stage, write who handles it, what they can decide and the business's response promise. List the complaints that go straight to the senior stage, such as safety issues, legal threats, large sums and customers in vulnerable circumstances, which the recovery guide also names. Escalation must be a route customers can use, never a wall that makes them give up.
Close the complaint and record the cause
A complaint is closed when the customer has had the full response and the agreed actions are done, not when the ticket goes quiet. Record the outcome, any remedy given and, separately, the cause. Getting from the symptom to the cause is the job of the five whys: a damaged item is the symptom; the cause might be packing, handling or a product that cannot survive the journey. Where complaints involve AI-generated answers, the AI in customer service guide explains why complaints stay with people, and the log records the AI's part in the cause.
Publish the procedure where customers and staff find it
Write two versions. The staff version is the full procedure with the log fields, the promises, the RACI and the escalation stages. The customer version is short: how to complain, the channels accepted, what happens next, when they will hear back and how to escalate. Put it on the contact page, link it from order confirmations or terms where it fits, and tell staff where it lives. Online stores can link it from the returns page; the guide to the returns policy and returns experience explains why faulty and not-as-described goods are handled as complaints with remedies, not as change-of-mind returns. How the contact page gives the complaint line its own heading beside the other routes and their reply times is shown in the tutorial on designing a contact page.
Review the log every month
Once a month, read the log with the people who own the causes. Count complaints by reason and by cause, check how many met the acknowledgement and response promises, look at how many escalated and why, and read a few in full in the customers' words. Take the largest causes to the people who can remove them and record what they agreed to change. Compare complaining customers' behaviour afterwards with the churn rateShare of customers at the start of a period who left during it. of similar customers in your own records, read with care when the numbers are small. Revise the procedure when the review shows a step that does not work.
What the complaint log records: a table
| Field | What it holds | Why it matters |
|---|---|---|
| Reference | A unique number given to the customer | Both sides can refer to the same complaint |
| Received | Date, time and channel; who logged it | Shows whether every channel is reaching the log, and starts the promise clock |
| Customer | Name and contact details needed to respond, and the order or booking reference | Lets the business respond; nothing beyond what handling needs |
| Complaint | What the customer says went wrong, in their words | Keeps the customer's view, not a summary that softens it |
| Outcome sought | What the customer wants to happen | Stops the business answering a different question |
| Reason | The contact reason from the shared list | Lets complaints be compared with other contacts |
| Owner and stage | Who is handling it now and at which escalation stage | Nobody waits without an owner |
| Acknowledged and responded | Dates the promises were met | Measures the promises |
| Response and remedy | What was said and what was given, with any approval | Consistency and a record if the customer escalates |
| Root cause | The cause found, separate from the reason | Feeds the monthly review |
| Closed | Date and whether the customer accepted the outcome | Shows what is still open |
| Retention date | When the entry is deleted or anonymised under the business's policy | Personal data is not kept indefinitely |
A removals firm writes its first complaints procedure (illustrative)
Drozzvel Removals writes a complaints procedure and reads its first quarter
Drozzvel Removals, an invented home removals firm with 6 crews, finds complaints arriving by phone to the office, by email, in reviews on 2 listing sites and on the paperwork drivers bring back from each move. None is recorded in one place. When the owner gathers a quarter's worth by hand, she finds 47, of which 12 had never reached the office at all because they were written on job sheets.
She writes a one-page procedure. A complaint is anything a customer says went wrong that they want put right or noted. Every channel goes into a single log in the firm's job system, with drivers photographing job sheet notes on the day. The firm promises an acknowledgement by the end of the next working day and a full response within 10 working days, or an update saying why not. Stage 1 is the office manager; stage 2 is the owner, who also takes any complaint about damage over the firm's set limit, injury or a missed move date. The customer version goes on the contact page and in the booking confirmation.
In the first quarter under the procedure the log holds 53 complaints. 31 concern damaged items, and 24 of those are reported between 3 and 9 days after the move, once boxes are unpacked. Asking why with the crews traces most to items packed by the customer and loaded without a check. The firm adds a short packing check to the loading routine and a note in the confirmation email about reporting damage, and the next quarter's review tracks whether damage complaints fall.
Verify it worked
- Pick one complaint from each channel on your list: a call, an email, a review, a note from the field. Find every one in the log with a reference.
- Open a few closed complaints. Check each shows the acknowledged and responded dates, so you can compare them with your promises.
- Check each remedy entry names its row in the remedy table, or says who approved it outside the table.
- Read the cause field on closed entries. It should differ from the reason, so "late delivery" is never the cause.
- Ask someone who did not write the procedure to find the definition, the senior escalation owner and the customer version. They should not need to ask you.
If it goes wrong
- Complaints are missing from the log. A channel has nobody moving its complaints in. Name an owner and a speed for that channel.
- Staff disagree about what counts as a complaint. The definition is vague or lacks the "if unsure" rule. Rewrite it as one sentence and add the rule.
- Promises are broken in the first busy week. They were set from ambition, not capacity. Reset them from what the team can keep.
- The same causes keep returning. The log records symptoms. Apply the five whys to the largest causes and record each cause separately.
- Customers escalate, then give up. The route works as a wall. Check each stage names a handler, what they can decide and a response promise.
Next steps
- Build the remedy table so the log can record which row each remedy came from.
- Read the support channels and self-service guide to test your promises against what customers expect in each channel.
- Read the community management guide for replying in public to a complaint that also sits in your log.
Common mistakes
- No definition. Staff decide case by case what is a complaint, and the ones they judge wrong never reach the log.
- Logging only some channels. Reviews, social comments and field paperwork stay outside, and the log understates the problem.
- Promises nobody can keep. An acknowledgement promise set from ambition rather than capacity is broken in the first busy week.
- Treating the business's promises as the law, or the law as optional. Response promises are the business's own; customers' rights are not the business's to narrow, and regulated sectors have their own rules.
- Closing on silence. A complaint is closed when the customer has had the response and the actions are done.
- Recording the symptom as the cause. "Late delivery" tells nobody what to change.
- Keeping everything forever. The log holds personal data; keep what is needed for as long as the business has decided.
- Reviewing nothing. A log nobody reads monthly is a filing system, not a procedure. The service and support hub sets out how support insight reaches the teams that can act on it.
