19 Min
Updated October 2026.
A parcel arrives broken. A bill shows a charge nobody agreed to. Meanwhile, a third customer has called three times about the same fault. They are all customer complaints, and how a team chooses to handle customer complaints like these decides whether the customer stays.
So this guide covers what a customer complaint is, why customers complain, the common types, eight steps that work on any channel and sample responses you can adapt. It closes with the complaint handling process that stops the same complaint from coming back next week.
Table of contents
- How to handle customer complaints: the short answer
- What is a customer complaint?
- Why do customers complain?
- Types of customer complaints
- 8 steps to handle customer complaints
- How to respond to customer complaints: sample responses
- LAST and HEARD: two quick frameworks
- A complaint handling process that stops repeats
- Dealing with customer complaints when the answer is the problem
- How Knowmax helps teams handle customer complaints
- Frequently asked questions about customer complaints
How to handle customer complaints: the short answer
To handle customer complaints well, listen to the whole problem without interrupting, acknowledge the impact and apologize for it, confirm the facts, fix the issue or give a clear next step with a time, then follow up to check the fix held. Finally, log the cause so the same complaint does not repeat.
What is a customer complaint?
A customer complaint is any expression of dissatisfaction with a product, a service or the way a company treated someone, where the customer expects a response or a fix. It can arrive as a call, an email, a chat, a review or a social post. Even so, a complaint is still useful information.
Customer handling is the wider skill around it. It covers how staff greet, listen to, inform and help customers. Complaints, however, are where that skill gets tested hardest.
Why do customers complain?
Most complaints trace back to a short list of causes. Some sit with the product. But many sit with the service around it, which means the support team can prevent them.
- A broken promise. Sales or marketing said one thing and the product or contract says another. The customer feels misled, even when nobody meant to mislead.
- Poor quality. The item is faulty, does not match the description or stops working early.
- Hard to reach. No clear contact route, long hold times, or an unanswered email.
- Hidden costs. Fees that appear only on the bill or at checkout.
- Repeating the story. Agents pass the customer around, so they explain the problem again at each step. In fact, 74% of customers find it frustrating to tell their story over and over to different agents, according to Zendesk CX Trends 2026.
- Wrong or different answers. An agent says yes, the next says no, and the customer trusts neither.
The last two causes deserve more attention than they usually get. They are not product faults at all. Instead, they come from agents who cannot find the right answer quickly, often because the policy sits in one tool, the product notes in another and the latest change in an email that half the team never opened, and that is a knowledge problem a team can fix.
Types of customer complaints
Sorting complaints by type helps a team route each one to the right person and spot patterns. Here are the types most support teams see.
| Type | Example | First move |
|---|---|---|
| Product quality | “The blender stopped working after two weeks.” | Confirm the fault, offer repair, replacement or refund under the policy |
| Delivery and fulfillment | “My order is five days late and tracking has not moved.” | Check the carrier status and give a new date |
| Billing and pricing | “I was charged twice this month.” | Verify the charge and reverse it if it is an error |
| Service and attitude | “The agent was rude and hung up on me.” | Apologize, review the interaction, follow up personally |
| Wait time and access | “I held for 40 minutes and nobody answered.” | Apologize, solve the original issue now, check staffing on that queue |
| Communication | “Nobody told me my plan was changing.” | Explain what changed and why, then offer options |
| Policy | “Why can’t I return this after 30 days?” | Explain the policy plainly, then check for any exception that applies |
| Repeat or unresolved | “This is my third call about the same problem.” | Take ownership, read the full history, escalate if needed |
Repeat complaints are the most expensive type on the list. Because every new contact costs agent time, the customer grows angrier with each call, while the original problem is still there.
A written escalation matrix stops those repeat cases from bouncing between teams.
8 steps to handle customer complaints
These steps work on the phone, in chat and over email. Only the pace changes.
1. Listen to the whole complaint
Let the customer finish before you speak. Interrupting to correct a detail tells them you care more about the facts than about them. Take notes. Never ask twice.
2. Acknowledge the impact
Name what went wrong for them in plain words. For example, “You waited a week for a part and it arrived broken” shows you heard. For more phrasing ideas, see these empathy statements.
Get the Knowledge Standard for CX Teams
3. Apologize, and mean it
A short, specific apology works better than a long, general one. Also, apologize for the experience even when the fault is still unclear. That is not an admission of liability.
4. Get the facts
First, ask for the order number, the dates and what the customer has already tried. Also, read the case history first. A customer who has already explained this twice should not have to explain it a third time.
5. Find the right answer
This is where most complaint handling slows down. The agent needs the current policy, the right fix and the right exception. And they need it while the customer waits. So a searchable knowledge base or an interactive decision tree matters more here than a script.
6. Resolve it, or give a clear next step
Fix it on the contact if you can. Do it now. If you cannot, say exactly what happens next, who owns it and when the customer will hear back. “Within 24 hours” beats “soon”. Then keep the promise.
7. Follow up
Check that the fix held. A short message a few days later turns a resolved complaint into a recovered customer. It also catches the cases where the fix did not work.
8. Record the cause
Log the complaint type and the root cause along with the outcome. Keep it brief. Teams skip this step more than any other, even though the log feeds the process that stops repeats.
How to respond to customer complaints: sample responses
Adapt these to your brand and your policy. These samples follow the same order: acknowledge, apologize, act, and set the next step.
Faulty product (email). “Thank you for letting us know the blender stopped working after two weeks. I am sorry; that is not what you paid for. I have arranged a replacement, which will ship today, and a prepaid label for the faulty unit. You will get the tracking number by email within the hour.”
Billing error (chat). “I can see the two charges on your account, and I am sorry for the worry this caused. I have reversed the duplicate charge now. Your bank may take three to five working days to show it. I will check on Friday that it has cleared.”
Late delivery (phone). “I understand you planned around that delivery date, and I am sorry it slipped. The carrier shows the parcel at the local depot. It is booked for tomorrow, and I have waived the delivery fee. I will call you tomorrow afternoon to confirm it arrived.”
Repeat complaint (phone). “I can see you have called about this twice already, and I am sorry you have had to explain it again. I am taking ownership of this case from here. I have read the full history, so you do not need to repeat it. Here is what I will do today.”
When the customer is already angry, these angry customer templates go further on tone and de-escalation.
LAST and HEARD: two quick frameworks
Many support teams train complaint handling with a short acronym, since agents can recall it under pressure. Both of these are common.
- LAST: Listen, Apologize, Solve, Thank.
- HEARD: Hear, Empathize, Apologize, Resolve, Diagnose.
Both say much the same thing as the eight steps above. HEARD adds the step most teams forget, which is to diagnose why the problem happened so it does not happen again. Pick one, train it and coach against it. Competing models in one team only confuse new hires.
See How One Retailer Put Its Knowledge to Work
A complaint handling process that stops repeats
Handling one complaint well is a skill. Handling ten thousand a month without the same ones coming back is a process. It needs five parts.
- One intake log. Complaints land in a single system, whatever the channel, with a type and a priority.
- Clear ownership. Each case has a named owner and a response time. Complex cases follow a written escalation path, such as this escalation SOP template.
- One source of answers. Agents, chatbots and the help center all draw from the same verified content, so the customer hears the same answer on every channel.
- Root cause review. Once a week, someone groups complaints by cause and sends the top ones to the team that owns them, such as product, billing, logistics or support.
- Measures that matter. Track a small set of complaint metrics, shown in the table below.
| Metric | What it tells you | How to calculate it |
|---|---|---|
| First response time | How long customers wait to hear back | Average time from complaint received to first reply |
| Resolution time | How long the problem stays open | Average time from complaint received to case closed |
| Repeat contact rate | Whether fixes actually hold | Complaints reopened or raised again, divided by complaints closed |
| Satisfaction after resolution | Whether the customer accepts the outcome | Share of positive answers in a short survey sent after closure |
| Complaints by root cause | Where the problems start | Count of complaints per cause each week |
Where self-service and chatbots fit
Self-service belongs in this process too, but with care. Customers want to fix simple issues themselves. However, self-service fully resolved only 14% of customer service issues in a survey of 5,728 customers, per the Gartner self-service survey. In that survey, 43% of the failures happened because customers could not find content relevant to their issue.
Chatbots raise the stakes further. Only 27% of customers would try a chatbot again after a negative experience, according to the Gartner chatbot survey of 3,566 customers. So a bot that cannot resolve a complaint should hand it to a person quickly, with the history attached.
Dealing with customer complaints when the answer is the problem
Plenty of complaint guides stop at tone. Of course tone matters, but a polite agent with the wrong answer still produces a second complaint. In practice, many repeat complaints start with inconsistent answers: one agent quotes the old return window, another quotes the new one, and the customer now has a fresh complaint about the first.
Here is the uncomfortable part. Even so, a knowledge tool will not fix a complaint caused by a bad policy, a faulty product or too few staff on a queue. Those need decisions from product, finance or operations. What a customer service knowledge base can fix is the share of complaints caused by slow, wrong or inconsistent answers, and that share is usually larger than teams expect. That is the part of how you handle customer complaints that software can genuinely change.
How Knowmax helps teams handle customer complaints
Knowmax is a knowledge management platform for customer service. It sits beside your help desk or CRM as the knowledge layer, rather than replacing either one.
For complaint handling, it gives agents a searchable knowledge base, no-code decision trees for policy and troubleshooting cases, visual step-by-step guides and MaxAI, an AI layer for search and answers across that content. As a result, the agent on the phone, the chatbot and the help center all give the same verified answer, and an expert updates a policy once for every channel.
Ready to Give Every Agent the Same Answer to Every Complaint?
Frequently asked questions about customer complaints
Listen to the full complaint without interrupting, then acknowledge the impact and apologize. Next, confirm the facts and read the case history. Fix the issue or give a clear next step with an owner and a time. Finally, follow up to check the fix held, and log the root cause so the complaint does not repeat.
Customer handling is the way staff manage every interaction with a customer: greeting them, listening, giving accurate information and resolving issues. It includes complaint handling, the hardest test of the skill. Good customer handling depends on clear processes and on agents finding the right answer quickly.
In short, the most common types are product quality, delivery delays, billing errors, rude or unhelpful service, long wait times, poor communication about changes, policy disputes and repeat complaints about an issue that was never fixed. Repeat complaints cost the most, because each new contact adds agent time while the original problem stays open.
LAST stands for Listen, Apologize, Solve and Thank. It is a short framework that helps agents remember the order of a good complaint response under pressure. A longer version, HEARD, adds Diagnose at the end, so the team finds the root cause and stops the complaint recurring.
Knowmax is a strong choice for teams that want consistent answers on every complaint, because it combines a knowledge base, no-code decision trees, visual guides and AI search beside your help desk or CRM. The right setup, however, depends on your volume, your channels and your policies.
Word Document)
Excel File)
