Handling a customer complaint means you acknowledge it quickly, resolve the actual problem, follow up to check the fix held, and learn from it so the same complaint does not come back again.
If you get this wrong, that one complaint can quietly turn into a churned customer, or a bad review, and sometimes both. And that costs you much more than just fixing the issue would have.
So in this post, we will go through the steps to handle a complaint in the moment, the common complaints you will see and how to resolve each one, and how to set up a process so complaints stop being a fire drill every single time.
What is a customer complaint?
A customer complaint is an expression of dissatisfaction with a product, service, employee, or experience that a customer makes to the company, or sometimes about the company in public.
People often mix a complaint up with customer feedback, but they are not quite the same. Feedback is just a signal about how things are going, good or bad. A complaint is that same signal, but with a request attached, the customer wants you to actually do something about it. That is the main difference between feedback and a complaint, and it matters because the two need different handling. One you can log and look at later, the other one needs a response now.
Complaints also don’t have a single channel to log in. Some come in on the channels you set up for it, like email, a phone line, or a ticket form. While some show up on the channels the customer picks instead, like social media, a review site, or a public Slack channel where the whole room can see it.
How to handle a customer complaint in 5 steps?
We have summarized the complaint handling process in 5 simple steps, and each of these steps also matters. The process starts with acknowledging, then you empathise and apologise, then you resolve it, and in the end you follow up.
Acknowledge the complaint quickly
Once a complaint is received, the very first important step is to acknowledge it. A customer must hear that you have received the complaint and start working on it, then a detailed summary when the issue is resolved.
The acknowledgement must be sent to the channel from which the customer registered the complaint. Additionally, you can also send an email.
Listen without interrupting
The best practice here and in life is to let the customer talk, while you listen to them patiently. Most people who complain want to be heard first, before they want any solution. So if you jump in with facts and a fix while they are still speaking, it only makes it worse.
You should ask them something open, like "Tell me what happened from your side," and then listen to it properly instead of waiting for your turn. Using positive language in customer service while they talk also keeps the conversation from heating up further. Saying the main points back to them, in your own words, shows you understood and lets them correct you if something is off. The common mistake is to defend or explain too early, before the person has finished venting. Even if you already know the fix, it is too early for them to hear it.
Empathize, then apologize
These are the two things people often mix up, but they are not the same, and empathy has to come first. Empathy just means you name what the person is feeling, something like "I can see why that would be frustrating." After that, the apology works better, where you own the actual problem and say sorry for what happened, and that it is not what you wanted for them. If you do it the other way around, or you go straight to sorry, it sounds like a script.
You should keep a few things in mind. First, don’t apologize for something that did not happen, and second, avoid saying sorry again and again. It also helps to keep a few ready phrases for handling angry customers within reach, so you are not hunting for the right words while the person is still upset.
Resolve, or commit to a clear next step
The next step is to work on fixing the issue. You should emphasize solving the complaint right there in the conversation. However, that is not possible all the time, when informed, the customers with the next step and the estimated time needed to resolve the complaint.
It also helps to be honest about what is possible and what is not, instead of half-promising a thing you are not sure of. The mistake here is over-promising just to get out of an uncomfortable chat, because once you break that promise, now you have two complaints instead of one.
Follow up to check the fix is holding
Once the complaint is resolved, most teams close it and start working on others. However, it is the time when you can build loyalty. A day or two after it is resolved, around 24 to 72 hours, send a small check-in to confirm the fix is still holding and the customer is fine with how it went. This way, the customer will feel valued and will feel more confident to be in business with you.
Common customer complaints and how to resolve them
If you are seeing that the same complaints are coming in, it is a sign that you have to work on the resolution process. Here is how you can ensure that common complaints are resolved properly:
- If someone is waiting in the support queue for longer, then you should route them to a real person quickly and fix the problem, so they do not queue again.
- If a product turns up broken, then it is your side of the part to fix it. Therefore, ensure you have a process for Same-day refund or replacement, free return shipping, a written apology from a named person, and a note on what went wrong.
- Money is something that people want to be well-spent, so if you get a complaint for a billing dispute, avoid getting defensive. Walk them through the charge, and if there was a real error, fix it on the spot and confirm it in writing with a date.
- When the complaint is about one of your own staff, thank them for saying it and make it right for the customer first. The agent side you deal with later and in private, as feedback, not a public telling-off.
- If an old ticket went unanswered, a lot of that is about the silence. Own the drop, find the ticket, and hand it to one named person to close out this time with a clear timeline.
- On a public review or social post, reply in public, short and calm, then move the detail to a private channel to fix it, and come back to the thread once it is done.
Where complaints come from (and why channel matters)?
Where the complaint comes from often changes the way to handle it. For instance, an issue on a phone call and on a public tweet are not the same job, because the speed, the audience, and the way you resolve it are all different.
- The phone is the fastest and most personal, the customer wants it sorted while they are still on the line, so the pressure is to fix it in the moment or set a clear callback time.
- Email support tickets are often slower, therefore, agents have time to go through the complaint and required information. But you should avoid taking too long to revert back to the customer with a resolution, or the next step you are following.
- Complaints arriving in Slack channels, especially a shared client one. In this case, you have to handle two things at once, a complaint and an internal team communication.
- A public post on social media is partly a complaint and partly a reputation event, since other people are watching, so you reply in public to show you are on it, then take the details to a private channel.
- A review site is the slow public one, where the complaint just sits there for a long time, so a calm reply still matters days later, because future customers will read it.
How to manage complaints as a process, not just an event
Handling one complaint well is good. However, when the volume increases, you should work on treating them as a process to ensure none of them are left unresolved. Here is how you do so:
- Every complaint becomes a record, even the small ones you fix in two minutes, because if it is not logged, you never see the pattern, and you can set this up by automating ticket creation so nothing quietly slips by.
- Each complaint must be assigned to a named owner to bring the sense of accountability.
- You keep a few simple time targets, time to first response, time to resolution, and time to follow-up, and watching the right metrics to track for complaint handling shows you where things are slipping.
- The right people at your company must be able to view the complaints and how they move, so they can see where the team is heading.
- At close, the complaint gets tagged with a cause, so when the third billing dispute of the week turns up, you actually spot it as a pattern and not three separate annoyances.
For teams that already work in Slack, this is where Slack-native ticketing fits. Suptask turns those complaint threads into tracked tickets with an owner and a status on them, so the conversation does not just scroll away once the channel moves on.
When and how to escalate?
Not every complaint is resolved by the first person who picks it up. Some need to go up a level, and the skill is knowing when. A complaint should move up when the customer asks for a manager, when the fix is bigger than the rep is allowed to approve, like a large refund, when the person turns abusive, or when an SLA is about to be breached, and someone more senior has to step in.
A simple tier structure takes most of the guesswork out of it:
A clear support tier structure behind this keeps reps from guessing where a complaint should go, and it stops the easy ones from landing on a manager's desk.
What not to do when handling a customer complaint?
Handling a customer complaint might go wrong because of a few things you should not do. Here we have outlined them, so you can avoid them:
- Do not get defensive, even when you are sure you are right, because arguing the point just tells the customer you care more about being correct than about their problem.
- Blaming another department is the next one to avoid. To the customer, it is all one company, and "that is not my team" only winds them up more.
- Over-promising just to end an awkward conversation backfires. A promise you cannot keep buys you ten quiet minutes and then a bigger complaint later.
- If you move the complaint to a private channel, tell them why first, because pulling it out of a public thread with no word looks like you are hiding something.
- You must not close the ticket before you have actually confirmed the fix was held. Closed on your side is not the same as solved on theirs.
How does handling complaints well drive loyalty?
Every support team has a KPI of driving loyalty by ensuring you stand with the customers at the time they need. So, when a customer who had a problem and watched you fix it properly often ends up more loyal than one who never had a problem at all. They have actually seen what you do when something goes wrong, and that tends to stick with them.
The cost of getting it wrong is real, though. In Zendesk's 2026 CX Trends report, 85% of CX leaders said a single unresolved issue is enough to lose a customer. So a complaint is not a small thing you can let slide, it is often the moment the customer decides whether to stay or go. This is a big part of what drives customer loyalty in the first place.
When you have a structured process to handle a complaint well, a complaint leaves more behind than just a calmer customer. It leaves behind an experience you can learn from, a root cause that got fixed so the next ten people do not hit the same thing, and sometimes a customer who tells a couple of friends how you sorted it out. That is the part that compounds over time.
Frequently asked questions
What are the 5 steps to handling a customer complaint?
The five steps are to acknowledge the complaint, listen to the customer fully, empathise and then apologise, resolve it or commit to a clear next step, and follow up afterwards to check the fix held. The order matters, you listen before you apologise, and you apologise before you jump to the fix. Run them out of order, and it tends to fall flat.
How do you respond to a customer complaint?
You respond by acknowledging it quickly so the customer knows they have been heard, listening to the whole thing before you react, and empathising with how they feel before you say sorry. After that, commit to a specific resolution with a timeframe rather than a vague promise, and follow up once it is done to confirm it actually worked. The quick acknowledgment at the start is the part that calms most people down.
What is the difference between a customer complaint and a customer review?
A customer complaint is a direct request to the company to fix something. A customer review is a public statement about the experience, written more for other customers than for you. The same incident can produce both, someone can complain to your support team and leave a one-star review about it on the same day.
What is an example of a customer complaint and resolution?
A common example is a customer who gets a broken or wrong product. A good resolution is to treat it as your problem to sort out, send a same-day refund or replacement with free return shipping, add a written apology from a named person, and log what went wrong so it does not happen again. The fix is specific, not just a quick sorry.
What is a customer complaint?
A customer complaint is an expression of dissatisfaction with a product, service, employee, or experience, made to the company or about it in public. It is different from general feedback because a complaint comes with a request to put something right.
