A complaint resolved without telling the customer and without recording the cause will come back. A complaint process with one log, defined response times and a closed loop.
Key takeaways
- A complaint handled without a record is not learning, only firefighting.
- Every complaint needs three clocks: acknowledgement, handling, and getting back to the customer.
- Collecting all complaints in one list matters more than the tool managing it.
- Keep categories short - five, not twenty - or nobody will fill them in.
- What turns complaints into improvement is a monthly review, not handling each one well.
Complaints in a small business are usually handled well: someone reads, someone fixes, the customer gets a reply. What is almost always missing is the two ends - the customer does not always learn the handling finished, and nobody recorded why it happened. So the same complaint arrives from a different customer two months later.
Where complaints arrive, and why that is the first problem
In a typical business a complaint can arrive on WhatsApp, by phone, by email, through a website form, as a Google review, or verbally in the shop. Some get recorded, most do not, so "how many complaints did we have this month" is a question with no answer.
The first step is not cutting channels but adding one collection point: every complaint, from every channel, recorded in the same place. It can be a sheet, a table in a system, or a ticket queue - what matters is that there is one, and the full logic of such a queue is in managing service tickets.
What to record for each complaint
| The field | Why it is there |
|---|---|
| Date and time | The basis for measuring response time |
| Customer | To spot a customer complaining again |
| Channel | To learn where people actually reach you |
| What happened | In the customer's words, not your interpretation |
| Category | To spot repeats |
| Owner | A name, not "the office" |
| What was done | The actual action |
| Date the customer was told | Proof the loop closed |
The last field is the one that gets dropped. Without it there is no way to tell a resolved complaint from a forgotten one, and both look identical in the list.
The three clocks to define
- Acknowledgement - how fast the customer knows you received it. Hours, not days.
- Handling - how fast a substantive reply goes out, not necessarily a full fix.
- Closure - when you come back to say what was done.
The distinction between the second and third is the point. A complaint needing a supplier investigation may take a week, and that is fine - provided the customer got an acknowledgement on day one and an update when it finished. Most anger in complaints is not about the problem but about the silence.
A short classification people will actually use
Five categories cover most businesses: product, delivery, billing, service, other. Twenty categories look more precise and stay empty, because whoever is filling them in is in a hurry and picks the first roughly-right option.
"Other" is deliberate - it prevents wrong classification, and it is also the best signal of a missing category: if a quarter of complaints land in "other", there is a category waiting to be added.
What turns complaints into improvement
A half-hour monthly review, over the whole list rather than a single case. Three questions:
- Which category is largest this month, and what changed from last month.
- Which complaint repeated across more than one customer - that is a broken process, not an incident.
- What was actually fixed from last month, and what was only flagged.
A repeating complaint is the most valuable information a business gets for free, because it points at a process rather than an incident. How to find the process producing it is covered in finding the bottleneck in your process.
What about a complaint that is not really a complaint?
A sizeable share of what gets logged as a complaint is actually a misunderstanding: the customer did not know what was included, misread the delivery date, or read the invoice differently. It is easy to file those as "customer error" and close them.
That is a mistake, because the same misunderstanding will return. A repeating misunderstanding is a communication problem in the business - in the quote wording, the order confirmation or the confirmation email - so it is worth its own category and one fix to the wording.
In practice, most businesses that start measuring find the misunderstanding category is among the largest, and also the cheapest to fix: changing one sentence in a template removes enquiries for months.
A complaint from a returning customer
A customer who bought ten times and complained once is not the same case as a new customer complaining on their first purchase, which is why the customer field in the log is not decoration. In practice a long-standing customer who complains usually does so after absorbing one or two problems quietly - so the complaint that arrived is the third, not the first.
The operational conclusion is not to give them special treatment but to check the history before replying: what they bought, what happened before, and whether there is an earlier case closed without closing the loop. Two minutes of checking changes the answer, and mainly prevents the sentence "this is the third time I am telling you this".
What to measure, and what not to
Two numbers are enough for most businesses: complaints per month by category, and the share of complaints closed with the customer told. The second is the honest one - it is the only measure that separates a handled complaint from a forgotten one, and it is usually far lower than anyone expects on the first month it is counted.
What is not worth measuring early is satisfaction after a complaint. It needs a survey, the response rate is low, and it answers a softer question than the two above. Once the loop reliably closes, it becomes worth adding; before that it measures a process that does not yet exist.
What not to do
- Do not run complaints on WhatsApp alone - the history exists but cannot be counted.
- Do not compensate before investigating - it ends the conversation and hides the cause.
- Do not classify by severity at intake; severity is interpretation, category is fact.
- Do not leave a complaint without an owner - "someone will handle it" means nobody will.
- Do not close without telling the customer, even when the fix seems obvious internally.
Sources
Frequently asked questions
Do you need a system to manage complaints?
Not at first. A sheet with eight columns holds up to a few dozen complaints a month. Moving to a system becomes necessary when you need assignment, reminders and per-customer history - not before.
What is a reasonable response time?
Whatever you declare and meet. Acknowledgement within hours on the same business day is realistic for most businesses; what damages trust is not a long time but an unknown one.
What do you do about a negative public review?
Handle it as a normal complaint in the log, and additionally reply publicly and briefly while moving the substance to a private channel. Recording matters especially here, because repeating public reviews almost always point at the same process.
Who should read the complaint summary?
Whoever can change a process. A summary reaching only the service person changes nothing, because they handle cases rather than causes.
Keep reading
Related service
Customer Service
One queue across every channel, with an owner and a deadline.
About the author
Yehonatan Saadia
Freelance automation, web & MVP developer
I'm Yehonatan Saadia, a senior developer who builds business automation, custom websites, and MVPs for small and mid-sized companies across the US, Europe, and Israel. These guides come from real client work, not theory.
Work with meHave a project like this?
Tell me what you're trying to automate or build and I'll tell you the fastest reliable way to ship it.