What an escalation process is for
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.
The pages that rank for this search describe ticket escalation in large support teams, with tiers, service level agreements and software. A team of 3 to 30 needs the same idea on one page.
Three levels are enough
| Level | Who | What they can do | Answers within |
|---|---|---|---|
| 1 | Whoever receives the complaint | Apologise, fix simple problems, give small goodwill gestures you've agreed in advance | Same working day |
| 2 | Team lead or manager | Refunds and credits up to a set amount, re-do the work, bend a rule once | One working day after it arrives |
| 3 | Owner or director | Anything larger, legal threats, public complaints, repeat problems | Two working days |
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.
Who owns each step
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.
What to say at each level
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)
Hi [name], thank you for telling us, and I'm sorry about [the specific problem, in their words].
I'm [your name] and I'll be looking after this.
Here's what I'll do: [the action]. You'll hear from me by [time or day].
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)
Hi [name], I've passed this to [manager's name], who can [what they can do that you couldn't]. They'll message you by [time or day]. I've shared everything you've told me, so you won't need to repeat it.
Taking it over (level 2 or 3)
Hi [name], I'm [name], [role]. [Colleague] has told me about [the problem]. I'm sorry this has taken longer than it should.
Here's what I can do: [the offer]. If that works for you, I'll [next action] by [date].
Closing it
Hi [name], [the fix] is done. Thank you for your patience, and for telling us, because it helps us fix [the cause]. If anything else comes up, message me directly on this number.
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.
Keep one record for every complaint
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.
Complaints on WhatsApp
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.
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. WhatsApp for sales covers setting up the Business app with labels and away messages.
When complaints arrive on WhatsApp, ActivityTracker's team inbox shows who's waiting, lets you assign the chat to a teammate, keeps private notes, and every chat lands on the client's record.
Fix the cause, not only the complaint
Once a month, read the complaint records together. Count them by cause: late delivery, wrong item, a rude call, a bill nobody explained. The top cause is next month's fix.
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.
Made-up example: a small furniture delivery business with 6 staff, taking complaints by phone, email and WhatsApp.
Week 1: they write the three levels on one page. Level 1 can offer a delivery-fee refund. The operations manager is level 2, up to a set refund amount. The owner is level 3.
Week 2: 9 complaints. 6 close at level 1 the same day, mostly late deliveries. 2 go to level 2: a scratched table and a customer who asked for a manager. 1 goes to the owner, a customer threatening a public review after a second missed delivery. She calls him that afternoon, offers a new delivery slot and a refund of the delivery fee, and he accepts.
Week 4: the monthly review counts 21 complaints. 13 are about delivery windows. Customers were told "between 8 and 6" and waited all day. They start sending a WhatsApp message with a one-hour window the evening before. The next month, delivery complaints fall to 4.
What to do first
- Write the three levels, who's at each, and what each can offer without asking.
- Set the time limits and agree them with the team.
- Copy the four messages above into your quick replies and change them to your words.
- Start one complaint record, even a shared sheet.
- Book a 30-minute review for the end of the month and count complaints by cause.