Most complaint handling failures are not caused by bad people. They are caused by a process that makes it easy for a complaint to be missed, delayed or lost, and hard to prove what happened afterwards.
If your team handles complaints by email, even a well-run team can fall into the same traps. Below are the ten most common complaint handling mistakes we see, why each one hurts, and what to do instead.
Use it as a quick self-audit. If you recognise more than three, your complaints management process is probably relying on goodwill rather than structure.
What is complaint handling, and why does it matter?
Complaint handling is the process an organisation uses to receive, record, investigate, resolve and learn from customer complaints. Done well, it protects the customer relationship, satisfies regulators and ombuds, and shows you where your products and processes need to improve.
Done badly, a complaint becomes a bigger problem than the original issue. A customer who is upset about a delayed claim can forgive a delay. They find it much harder to forgive being ignored, passed around, or told three different things by three different people.
10 common complaint handling mistakes
1. Treating the complaints mailbox like any other inbox
A complaints mailbox without ownership, status and a clock is just a folder. Everyone can see it, so everyone assumes someone else is dealing with it.
In a typical shared mailbox, two people may reply to the same complaint while another goes unanswered for days. Nobody can say who is responsible, and nobody can tell at a glance what is overdue.
The fix: Give every complaint a single named owner and a visible status from the moment it arrives. If the owner is away or leaves, ownership should transfer without losing history.
2. Not separating a complaint from a query
A query asks for information. A complaint expresses dissatisfaction. When both land in the same queue and are treated the same way, genuine complaints get handled as routine queries and are never logged, escalated or reported.
Definitions vary between industries and regulators, and many define a complaint broadly as any expression of dissatisfaction, whether or not the customer uses the word "complaint". If your team only logs emails that say "I want to complain", you are almost certainly under-reporting.
The fix: Agree a clear internal definition, train front-line staff to recognise dissatisfaction, and make it quick to flag or reclassify an enquiry as a complaint so it enters the right process and the right reporting.
3. Measuring only the first reply
Fast acknowledgment is not resolution. A team can hit a one-hour first-response target on every complaint and still take two weeks to fix the problem.
First response matters, because silence is what customers hate most. But if it is the only number on the dashboard, the real delays hide behind it.
The fix: Track response time and resolution time separately, each against its own target. Use a visible clock, with colour coding or alerts that flag risk before a breach, not after. A complaint that is amber on day one is a conversation. A complaint that is red on day five is an escalation.
4. Making the customer repeat themselves
Every time a complaint changes hands and the story does not travel with it, customer effort goes up. The customer explains the issue, is transferred, and has to explain it again.
This usually happens because the history lives in individual inboxes, forwarded emails or someone's memory. It is one of the fastest ways to turn a mild complaint into an angry one. We cover this in more detail in why customers hate being transferred.
The fix: Chain every email, internal question and response to a single reference number, so anyone who picks up the complaint sees the full history in seconds.
5. Having no audit trail
If you cannot show who saw a complaint, who responded and when, you cannot defend your process. This matters most when a complaint is escalated to a regulator or an ombud, who will want a clear timeline.
Teams that rely on email often rebuild that timeline after the fact from forwards, calendar entries and memory. That is slow, stressful and rarely complete.
The fix: Use a system that records activity automatically: logins, views, replies and changes. The timeline should exist the moment a complaint is raised, not be reconstructed when someone asks for it.
6. Fixing the case but never the cause
Resolving individual complaints without analysing patterns means you keep receiving the same ones. If the same product, process or branch keeps appearing, the real problem is upstream.
Many teams close each complaint with a good outcome and move on, because they have no way of seeing trends across hundreds of cases.
The fix: Capture a consistent category and root cause on every complaint in your complaints register, and review trends monthly. Reporting should show where complaints come from, how long they take and where they get stuck, so leadership can act on the pattern and not just the case.
7. Going quiet while the issue is being worked on
Customers are far more tolerant of a slow answer than a silent one. When someone raises a complaint and hears nothing for several days, they assume nobody is dealing with it.
Complex complaints often need input from another team, such as compliance, claims or finance, and that can take time. The mistake is not the delay itself. It is the lack of any update in the meantime.
The fix: Set a standard for proactive updates: an acknowledgment straight away, a progress update at set intervals, and a final response. Keep approved templates for each stage so updates are quick to send and consistent in tone.
8. Reporting by hand at month-end
If your complaints report is built manually from mailboxes and spreadsheets, it is out of date before it is finished. It also depends on whoever builds it, and on their assumptions.
Manual reporting makes it easy to miss complaints, double count others, and spend hours on admin that should go into analysis. It also means problems only become visible after the month has ended, when it is too late to intervene.
The fix: Report from live data. Managers should be able to see open complaints, ageing, ownership and SLA status at any time, and generate regulator or executive reports without rebuilding them from scratch.
9. Allowing records to be lost or changed
A complaints record has to be complete and trustworthy. If emails can be deleted, edited or moved without a trace, the record cannot be relied on.
In a shared mailbox, one person tidying up their inbox can remove the only copy of a key message. That can look very bad later, even if there was no bad intent.
The fix: Use a system where complaints are retained and changes are logged, with permission controls on who can do what. Retention rules should be deliberate, not accidental.
10. Leaving escalation to chance
Escalation should be triggered by the clock and the severity, not by someone remembering to raise it. In many teams, a stuck complaint only escalates when the customer calls the CEO or posts on social media.
The fix: Define escalation rules in advance: when a complaint is escalated, to whom, and what happens at each stage. Make internal escalation visible so managers can step in early, while there is still time to fix the problem and keep the customer.
What does a good complaint journey look like?
Imagine a customer emails to query a change to her policy and is unhappy with the answer. In a well-run complaints management process:
- The complaint is captured automatically and assigned to a single owner.
- The owner needs input from compliance, so they raise an internal query on the same record rather than starting a separate email chain.
- A response clock runs the whole time. If it turns amber, the owner and their manager can both see it.
- Compliance responds on the same record, and the owner replies to the customer with a clear explanation.
- The full history, with every view, reply and change, is on record if it is ever reviewed.
Nothing here requires heroic effort from anyone. It simply makes the right behaviour the default.
How Kunye Cloud approaches complaint handling
Kunye Cloud is a shared inbox and SLA tracking platform that turns email-based enquiries and complaints into one accountable, reportable queue. It is built for South African teams that live and die by response time, and it addresses most of the mistakes above:
- Every enquiry has one owner, which can be transferred without losing continuity.
- A single reference number chains all related communication into one record.
- Response and resolution clocks run against your SLA targets, colour-coded so risk is visible before a breach.
- Internal escalation and templates keep complicated complaints moving and consistent.
- An audit trail records logins, views, replies and changes.
- Dashboards and reporting give managers and executives a live view across mailboxes, including regulator reporting with custom fields.
It works with Microsoft 365 and Google Workspace mailboxes, and includes security and compliance fundamentals such as encryption and single sign-on.
A simple complaint handling self-audit
Score your team honestly. How many of these can you answer "yes" to?
- Does every complaint have one named owner today?
- Can you see, right now, which complaints are overdue?
- Can you tell a complaint from a query in your queue?
- Do you measure resolution time, not just first response?
- Could you produce a full timeline of any complaint within minutes?
- Do you review complaint trends and root causes every month?
- Are escalation rules defined and visible?
If you answered "no" to three or more, it is worth looking at how your process, and your tools, support the people doing the work.
Frequently asked questions
What are the most common mistakes in complaint handling?
The most common mistakes are having no single owner for each complaint, not separating complaints from queries, measuring only first response time, making customers repeat themselves, having no audit trail, never analysing root causes, going silent while the issue is worked on, reporting manually, losing or altering records, and leaving escalation to chance.
What is the difference between a complaint and a query?
A query is a request for information or help. A complaint is an expression of dissatisfaction about a product, service or the way something was handled. Many organisations and regulators define a complaint broadly, so the customer does not have to use the word "complaint" for it to count. Check the definition that applies to your industry.
How should companies track customer complaints?
Every complaint should be logged on arrival with a unique reference, an owner, a category and a status, and tracked against response and resolution targets. A complaints register or a purpose-built complaints management system should show open items, ageing, escalations and outcomes at any time.
Can a shared mailbox be used for complaints management?
A basic shared mailbox usually cannot, because it does not track ownership, status, time or an audit trail. A purpose-built shared inbox with SLA tracking, ownership and reporting is better suited to complaint handling.
Why does an audit trail matter in complaint handling?
An audit trail shows who viewed, replied to or changed a complaint, and when. It lets you demonstrate a fair, consistent process if a complaint is escalated to a regulator or ombud, and it removes the need to rebuild the timeline from emails after the fact.
See how it works with Kunye Cloud
If your team handles complaints by email and you would like to see how a single owner, a single reference number and a visible clock work in practice, book a Kunye Cloud demo.