How to Handle Customer Complaints: A Step-by-Step Process
By Bodhih Training · UpdatedThe short answer
To handle a customer complaint well, follow seven steps: receive it in the customer's own words, log it and acknowledge it with a severity level and a named owner, listen and reflect before you explain, investigate a written question with evidence, choose a fair remedy within clear authority, send a final response that gives a finding for every point and an escalation route, and fix the root cause so it does not happen again.
- Treat any expression of dissatisfaction that expects a response as a complaint, in every channel
- Severity levels decide how fast you acknowledge, answer and escalate
- Let customers feel heard before you explain: listen, name, narrow, then agree the next step
- Separate putting right the loss from goodwill, and protect every promise made during recovery
- Every final response needs a finding for each point and the next step, including any ombudsman route
- The service recovery paradox has mixed evidence: recover well, but fix the cause
What counts as a customer complaint?
Start with one definition the whole organisation uses. A practical one, close to the thinking in ISO 10002, the international guidelines for complaints handling, is this: any expression of dissatisfaction about your products, services, staff or complaint handling, where the customer expects a response or a resolution.
Two consequences matter. First, the customer does not need to use the word complaint. "This is the third time I've asked" in a chat counts. Second, if in doubt, log it. Logging a query by mistake costs a minute; missing a real complaint can cost a customer and leave a fault unfixed.
A falling complaint count is not automatically good news. It can mean customers find it hard to complain, or have given up. Better measures are how easy it is to complain, how quickly and fairly you resolve complaints, and how often the same cause returns.
What are the steps in a complaint handling process?
Most complaint failures are not failures of effort. They are steps skipped or done in the wrong order: explaining before listening, offering money before investigating, closing a complaint without telling the customer what they can do next. A clear sequence fixes most of this. The table sets out seven steps, what each produces and the mistake it prevents.
Underneath all seven steps sits one log. Whether a complaint arrives by phone, chat, email, letter, a public post or a review site, it should get one reference number, one named owner and one record, logged the same day. Without a single log you cannot see how long complaints take, which customers keep coming back or which causes keep recurring, and complaints fixed quickly on the phone, often the most useful data you have, simply disappear.
| Step | What it produces | Mistake it prevents |
|---|---|---|
| 1. Receive | The complaint in the customer's words, what they want, what they have tried | Guessing what the customer wants |
| 2. Log and acknowledge | One log entry with severity, owner, due dates; a specific acknowledgment | Complaints lost across channels; silence |
| 3. Understand | A conversation where the customer feels heard and the issues are agreed | Rising anger from early explanations |
| 4. Investigate | A finding for each point, based on evidence and a timeline | Defensive or one-sided conclusions |
| 5. Resolve | A remedy that fixes, puts right the loss and recognises the impact | Inconsistent or unauthorised payments |
| 6. Respond and escalate | A final response with an escalation route | Letters that restart the complaint |
| 7. Learn | Root causes with owners, dates and a check | The same complaint next month |
How fast should you respond to a complaint?
Set response targets by severity rather than one target for everything. A simple scale has four levels: critical (risk of harm, safety, data or legal breaches, or a vulnerable customer without an essential service), high (significant loss, repeated failure, media risk), medium (a clear failure with limited loss) and low (dissatisfaction with little loss). Each level gets an acknowledgment target and a final response target, and critical complaints go to a senior person the same day.
If you are regulated, your regulator may set the clock. In UK financial services, for example, the FCA's complaint rules expect a firm to send a final response, or a holding response explaining the delay, within eight weeks of receiving a complaint, and the response must tell the customer about the Financial Ombudsman Service. Other sectors and countries have their own rules, so check yours.
Whatever the target, promise customers the date of your next update rather than an outcome you do not yet control, and keep that promise even if there is nothing new to say.
How do you handle an angry customer?
People need to feel heard before they can hear you. In many difficult calls the agent starts explaining within the first minute. The explanation is accurate, and it makes things worse, because the customer is still trying to be understood. A simple sequence helps: listen until they finish, name the fact and the feeling back specifically, narrow to the one or two issues to solve first, and agree the next step with a time.
Reducing effort matters as much as warmth. In a 2010 Harvard Business Review article, Matthew Dixon, Karen Freeman and Nick Toman reported research with more than 75,000 people suggesting that going above and beyond made little difference to loyalty, while reducing customer effort mattered more. In a complaint, effort means repeating the story, being transferred and being told things that turn out to be wrong.
Anger is normal; abuse is not. Give staff a practised boundary: name the behaviour, warn once, then end the contact politely while keeping the complaint open, and debrief the person afterwards.
- Apologise for the experience straight away
- Apologise for the failure once you have checked the facts
- Never say "we're sorry you feel that way"
- Put the agreed next step in writing within the hour
How do you investigate a complaint fairly?
Give the investigation to someone who was not involved, and start by writing the question you must answer, such as "Why were two installation appointments missed?" Number the customer's points so each gets a finding. Log every piece of evidence with its source: system records, call recordings, chats, photos, job sheets. Then put events in a timeline; gaps and contradictions show up quickly.
Decide each point on the balance of the evidence and say plainly where evidence is missing. Before you finish, check your fairness: did you look for evidence that supports the customer, and would you reach the same finding for a different customer? Finally, name the root cause, because it links this complaint to the next one you can prevent.
Reading helps; measuring tells you what to work on. These AI-graded assessments on AssessAll pair with this topic:
What is a fair remedy for a complaint?
Think of remedies as a ladder. First fix the problem. Then put right the financial loss the failure caused. Then, where the failure caused real inconvenience or distress, recognise that with a payment, credit or gesture. Finally, prevent it happening to the next customer.
Record the loss and the goodwill separately. Refunding a wrong charge is not generosity; it is what the customer is owed. Goodwill is the part beyond the loss, and it is where consistency matters. Set authority limits so that most complaints can be settled by the first person the customer speaks to, check similar past cases before offering, and take extra care with anything involving injury, legal claims or personal data.
What should a final response letter include?
A good final response lets someone who knows nothing about the case understand it. It should acknowledge the complaint and when it arrived, list the customer's points, say what evidence was checked, give a finding for each point, describe the remedy and when it will arrive, apologise or express regret once and specifically, and explain what the customer can do next, including any ombudsman or alternative dispute resolution route and its time limits.
Letters that do not uphold a complaint deserve more care, not less. Explain the evidence and the reason, name the policy and what it is for, acknowledge why the customer saw it differently, and never leave out the escalation route.
Does good service recovery make customers more loyal?
Sometimes, and less reliably than is often claimed. The idea that a customer whose problem is fixed brilliantly ends up more loyal than one who never had a problem is called the service recovery paradox. A 2007 meta-analysis in the Journal of Service Research by de Matos, Henrique and Rossi found a positive effect on satisfaction, but no significant effect on repurchase intentions, word of mouth or corporate image.
So recover as well as you can, because poor recovery is costly, especially a second failure such as a refund promised and never paid. But do not plan on failing well. The better investment is finding and fixing the causes.
How do you find the root causes of complaints, and where does AI fit?
Code a root cause for every complaint, then rank causes by frequency. Usually a few causes produce most complaints, the Pareto idea. For the top cause, ask why until you reach a process, system or policy you can change (five whys), and map possible causes across people, process, systems, policy, partners and information (a fishbone diagram). Agree an owner, a date and a check date with the team that owns the process, and report the result to leadership monthly.
AI can help cluster complaint themes, summarise long complaints and draft replies, but customers are wary. A Gartner survey of 5,728 customers, published in July 2024, found 64% would prefer companies did not use AI for customer service, with the biggest worry being that it would be harder to reach a person. Use AI for drafting and analysis, tell customers when they are talking to an AI assistant, hand over to a person early, and keep findings, remedies and final responses with people.
If you want a ready-made system, the Complaint Handling and Recovery System from Bodhih Training includes a complaints workbook with severity, SLA flags, remedies, a root-cause Pareto and monthly MI, plus forms, letters and scripts for every step in this guide.
| AI can help with | A person must decide or check |
|---|---|
| Summarising and categorising complaints | Severity, especially safety, data and vulnerability flags |
| Drafting acknowledgments and letters | Every fact, amount and date before sending |
| Building a timeline from notes | The finding on each point |
| Clustering themes for root cause work | Root causes, owners and fixes |
| Answering simple questions in chat | When to hand over to a person |

Run your next complaint with every step ready
The Complaint Handling and Recovery System from Bodhih Training gives you an e-book, a complaints workbook, fillable forms, a script and letter library, a final response template and a 30-day rollout plan, so each step in this guide has a file ready to open.
Sources
- FCA Handbook: DISP 1.6 Complaints time limit rules
- ISO: ISO 10002:2018 Quality management, Customer satisfaction, Guidelines for complaints handling in organizations
- Harvard Business Review: Stop Trying to Delight Your Customers (Dixon, Freeman and Toman, 2010)
- Journal of Service Research: Service Recovery Paradox, A Meta-Analysis (de Matos, Henrique and Rossi, 2007)
- Gartner: Survey finds 64% of customers would prefer that companies didn't use AI for customer service (July 2024)
- FCA: FG21/1 Guidance for firms on the fair treatment of vulnerable customers
More from the Bodhih family
Questions people ask next
What is the first thing to say to a customer who complains?
Thank them for telling you, show you have understood the specific problem, and tell them what happens next. For example: "Thank you for telling us about the missed installation. I'm sorry you've had to chase us. I'm going to check the installer's records today and call you by 4pm."
Should every complaint be logged, even if it is fixed on the call?
Yes. Complaints resolved at first contact still tell you what is going wrong. If they are not logged, your root-cause data misses the most common, easiest-to-fix problems.
How do you handle vulnerable customers who complain?
Watch for signs that a customer may need extra support, ask what would help rather than assuming, record only what helps with their consent, adapt your process and signpost to independent advice. The UK FCA's guidance FG21/1 describes four drivers of vulnerability, health, life events, resilience and capability, which are a useful lens in any sector.
How should you reply to complaints on social media?
Reply publicly and quickly with a sincere apology and no excuses, move to a private message for details, resolve it through your normal process, and close the thread publicly with the customer's agreement. Never argue facts or share account details in public.
How can frontline staff get better at de-escalation?
Practise the conversation in pairs with real scenarios, listen back to recorded calls, and agree boundary wording as a team. AssessAll's Customer Aggression and De-escalation Assessment for Frontline Staff is one way to see where confidence is lowest before and after training.
How do you make a new complaint habit stick for a team?
Choose one behaviour, such as reading the full history before every complaint call, and write it as an if-then plan: if a complaint is transferred to me, then I read the last three contacts before I speak. Jobulary explains how if-then plans make work habits stick.
What complaint metrics should leadership see?
Complaints per 1,000 orders or customers, the share answered within target, average days to a final response, uphold rate, repeat complaints, external escalations, the cost of goodwill and the top root causes with their owners. Two pages a month is enough.