Complaint escalation process: levels, owners and replies

A complaint escalation process says who handles a complaint first, when it moves to someone with more authority, and how long each step can take. It exists so a customer never has to chase you, and so nobody on your team has to guess whether a problem is theirs to fix.

Most small businesses don't have one written down. The owner handles the angry ones, everyone else handles the rest, and the complaint that falls in between waits. Writing it down takes an hour and saves the customers you'd otherwise lose to silence.

Big support teams run this with tiers, service level agreements and ticketing software. A team of 3 to 30 needs the same idea on one page. There's an international standard behind it, ISO 10002:2018, and ISO's own summary says it's meant for any organisation regardless of type or size, with an annex written for small businesses.

A complaint is any message, call or review where a customer says something went wrong and expects you to do something about it. It doesn't need the word "complaint" in it. "Still waiting for the invoice?" is one. So is a one-line WhatsApp message with three question marks.

Log all of them, even the ones you fix in five minutes. The small ones are where you spot a pattern before it costs you a customer.

Most complaints never need a second level, as long as the first reply goes well. Complaint guides list anywhere from four to seven stages, and they cover the same ground: log it, acknowledge it, find out what happened, fix it and follow up. In a first conversation, that's five moves.

1. Let them finish. Don't explain, correct or defend while they're still telling you.
2. Repeat it back in their words. "So the table arrived scratched, and nobody called back on Friday. Is that right?"
3. Apologise for the specific thing, not in general.
4. Say what you'll do and when they'll hear from you.
5. Do it by then, or message before the deadline to say why not.

If the customer is angry, stay with steps 1 and 2 for longer than feels natural. Most heat goes out of a conversation once someone feels heard. If a chat gets heated, offer a call, then write a two-line summary back into the chat so the agreement is on record.

For most small businesses, three levels cover everything. Every level you add is one more hand-over, and one more wait for a customer who's already unhappy.

Write the limits down. "Level 1 can refund up to [amount] or offer [gesture] without asking" saves a lot of messages that start with "can I...?".

When a complaint goes up a level

Move it up when any of these is true:

• Level 1 can't fix it within their limits.
• The customer asks for a manager. Don't argue about it; hand over politely.
• The customer has complained about the same thing before.
• There's a safety issue, a legal threat or a mention of a regulator.
• It's public: a review, a social post or a message copied to lots of people.
• The time limit has run out without a fix.

Going up a level isn't a failure by the first person. Say so to your team, or they'll sit on complaints to avoid looking bad.

Signs it's about to go up

Some complaints give a warning before they escalate on their own. Treat these as a reason to act today:

• A second message about the same thing before you've answered the first.
• Replies getting shorter and sharper, or written in capitals.
• A question of theirs you haven't answered yet.
• "This is the second time" or "last time you said".
• Someone else copied into the email or added to the chat.

Every complaint needs one named owner at every moment. When it moves up a level, the new owner messages the customer to say they've taken it over. The old owner stays in the loop but stops replying, so the customer never gets two answers.

Name a deputy for each level. Complaints don't wait for someone to come back from leave.

Teach it in one meeting

A process only the owner knows isn't a process. Spend 30 minutes with the whole team: read the three levels and their limits aloud, agree who the deputies are, and have each person say the first reply and the hand-up message to a colleague playing the customer. Do it again whenever someone new joins.

Keep the words short and specific. Customers want to know three things: that you heard them, what you'll do, and when.

First reply (level 1)

If you need information first, ask for all of it in one message: the order number, a photo, the date. Customers hate being asked for things one at a time.

Handing it up (level 1 to 2)

Taking it over (level 2 or 3)

Closing it

A week later

The complaint isn't over when the fix goes out. Check once, a week later, and only once:

What not to say: "those are the rules", "nobody else has complained", "you should have read the terms", or anything that argues about whose fault it was before the customer feels heard. Be honest about what you can't do, and offer the nearest thing you can.

A complaint that lives only in someone's chat history can't be followed up, handed over or learned from. Keep one record per complaint with:

• Customer, date and channel it came in on.
• What they said, in their words.
• Owner now, and level.
• Each action taken, with dates.
• The fix, and the date it was closed.
• The cause, in one line.

A shared spreadsheet is fine at first. If you already keep customer records in a CRM, put the complaint on the customer's record, so anyone who talks to them next sees it before they pitch anything. Talking notes in after a call is a quick way to get what they said down while it's fresh.

If your customers message you on WhatsApp, complaints will arrive there too, often with photos. That's good, because it's quick and the customer can see you've read it. It also brings three risks.

• The read receipt. The customer sees two blue ticks, and silence after that feels worse than on email. Reply within the hour, even if it's only "I've seen this and I'm on it. I'll come back to you by 3pm."
• The wrong phone. If the complaint lands on a salesperson's number and they're on leave, nobody sees it. Agree that complaints get passed to the level 1 owner straight away, and write down who that is.
• The thread. Complaints get buried under later messages. Label the chat, or copy it into the complaint record, so it doesn't vanish.

The WhatsApp Business app has the pieces for this built in. Its features page lists labels to organise and filter conversations, quick replies for messages you send often, and away messages for anything that arrives outside your hours. Save the five messages above as quick replies and make a "Complaint" label. For the rest of the Business app set-up, start with WhatsApp for sales.

If several people answer your WhatsApp numbers, a shared inbox lets you see who's waiting and hand a chat to the right person with the history attached. ActivityTracker's inbox reads chats from your own number, which you link to it as a device, the way WhatsApp Web works, and it isn't one of WhatsApp's own apps. WhatsApp's linked devices page warns that "linking your device through unofficial apps or websites may put your account at risk." So ActivityTracker spaces out the messages your number starts on its own, and stops them if WhatsApp warns the number. A complaint is a one-to-one reply anyway, never a broadcast.

Once a month, read the complaint records together and count them by cause, such as late delivery, a wrong item, a rude call or a bill nobody explained. The top cause is next month's fix.

Five numbers tell you whether the process itself works:

• Complaints this month, by cause.
• How long the first reply took, on average.
• How long the fix took, from first message to closed.
• How many went up a level, and how many reached the owner.
• How many came back after they were closed.

A rising count at level 3 means level 1's limits are too tight or nobody knows them. A complaint that comes back after closing means the fix treated the symptom.

This is where the process pays for itself. Fixing one cause stops dozens of future complaints, and customers who see a problem fixed tend to stay. Track whether they do: client retention rate shows how to count the customers you keep.

1. Write the three levels, who's at each, and what each can offer without asking.
2. Set the time limits and agree them with the team in one 30-minute meeting.
3. Copy the five messages above into your quick replies and change them to your words.
4. Start one complaint record, even a shared sheet.
5. Book a 30-minute review for the end of the month and count complaints by cause.

• ISO, ISO 10002:2018 Quality management, Customer satisfaction, Guidelines for complaints handling in organizations (abstract: any organisation regardless of type or size, Annex B for small businesses), read 27 October 2026
• WhatsApp Business, Business app features: labels, quick replies and away messages, read 27 October 2026
• WhatsApp Help Center, About linked devices, read 27 October 2026