A company may resolve an individual complaint and still leave the cause of the complaint untouched. A refund closes one case, but the same misleading description remains online. An apology answers one customer, while a delivery handover continues to fail. A support team works through its queue without the authority to change the process creating that queue.
This gap matters because complaint handling has two distinct purposes. It should respond fairly to the person raising the problem, and it should help the organisation understand what needs to improve. When only the first purpose receives attention, repeated cases can become an accepted cost of doing business.
For business leaders, the useful question is whether complaints change operational decisions. That requires reliable records, clear ownership, proportionate investigation and a route from evidence to action. It also requires care when interpreting the data: the people who complain are not necessarily representative of every customer.
Make it possible to raise a problem
A complaint process starts before an agent opens a ticket. Customers need to know where to go, what information to provide and what response to expect. A company that hides contact details or forces people through irrelevant automated menus may receive fewer recorded complaints without improving the underlying service.
The ISO 10002 overview of complaints handling describes complaint handling as part of an organisation's quality management activity. Its public overview emphasises an accessible process, management involvement and using complaints to improve products and services. This provides a useful foundation for treating complaints as operational evidence.
Accessibility includes the clarity of the route as well as the availability of a channel. A customer should not need to understand the company's departmental structure to report a problem. Different channels may be appropriate for different users and tasks, but they should connect to a coherent process.
The intake process can ask for information necessary to investigate, while allowing the customer to explain the issue in their own words. If the initial categories are too narrow, important details may disappear. For example, a customer selecting “delivery problem” could actually be reporting contradictory promises made during checkout and fulfilment.
Give each case a clear owner
Customers can become frustrated when every team explains why another team is responsible. Internally, this may reflect a reasonable division of work. Externally, it creates a problem without a visible route to resolution.
The NSW Ombudsman's complaint management guidance is written for public agencies and relevant service organisations. Its discussion of complaint handling offers a useful operational comparison for companies, particularly around taking responsibility and coordinating responses. Its sector context should be recognised rather than presented as a universal corporate rule.
A company can assign one person or team to coordinate a case even when several departments must contribute. The coordinator does not need to perform every investigation personally. Their role is to keep the record coherent, obtain relevant evidence and explain the next step to the customer.
That role also needs authority. An agent cannot meaningfully own a case if they are unable to obtain information, request a decision or escalate an unresolved issue. Business leaders should examine whether the support function has practical access to operations, billing, sales and product teams.
Clear ownership can also help prevent duplicate remedies. If several teams contact the customer independently, they may offer inconsistent explanations or issue overlapping credits. A shared record and a defined decision route make it easier to understand what has already happened and what remains outstanding.
Investigate what happened and what was promised
An investigation should separate the customer's experience, the company's records and the commitments made at the time of the transaction. A product description, delivery estimate or sales message can matter as much as an internal policy.
A hypothetical software customer may complain that an advertised feature is unavailable on their plan. The support team can confirm that the feature works correctly for eligible accounts and still miss the issue. If the marketing page failed to explain the restriction clearly, the cause may sit in acquisition rather than technical delivery.
Useful evidence can include the relevant version of a description, order details, billing records, communications and actions taken by staff. The amount of evidence needed should reflect the issue. A straightforward correction does not require an elaborate investigation, while a repeated or serious allegation may warrant closer review.
Teams should distinguish what the evidence establishes from what remains uncertain. If a delivery record confirms dispatch but not receipt, the response should not imply that receipt has been proven. If a customer account differs from an internal record, the investigation should consider how that record was generated and whether it could be incomplete.
This approach supports more accurate explanations. It can also reduce the temptation to use standard responses that sound conclusive while failing to address the actual complaint.
Choose remedies that address the circumstances
A remedy should respond to the problem established by the investigation and the applicable contractual or legal obligations. Depending on the circumstances, that might involve correcting information, completing work, replacing an item, issuing a refund or explaining why a requested outcome is not supported.
Commercial discretion and required remedies should be distinguished. A goodwill credit may help preserve a relationship, but it should not obscure the customer's rights or substitute for an obligation the company must meet. Relevant requirements vary by market and transaction.
The OECD recommendation on consumer protection in e-commerce addresses fair business practices, information disclosure and dispute resolution, among other matters. It is a policy recommendation rather than a single rule applying identically to every business. Its relevance is that fair treatment continues after a transaction, including when a problem arises.
A response should explain the decision in language the customer can understand. It should identify any agreed action, who will perform it and the expected timing. Where further review or an external route is available, the customer should receive accurate information about that route.
Companies can review whether similar cases receive consistent treatment. Consistency does not require identical outcomes when circumstances differ. It requires a defensible explanation for differences and a process that does not depend solely on which agent receives the complaint.
Preserve the learning after a case closes
A closed case often contains information that is useful beyond the individual remedy. The company may have discovered an unclear instruction, a missing handover or an exception its systems cannot handle. That information needs to reach someone able to change the process.
The UK public ombudsman's principles of good complaint handling call for recording, analysing and reporting learning from complaints, and using it to improve services. These principles were developed for public service bodies. For companies, they offer a practical model for connecting individual cases with improvement work.
A case record can distinguish the issue reported, the cause identified, the remedy and the proposed preventive action. These are related but different. “Refund issued” describes an outcome; it does not explain why the problem occurred.
Classification should allow uncertainty. At intake, the company may know only the reported symptom. A cause can be added after investigation, with a record of the evidence supporting it. Forcing agents to choose a root cause immediately can create misleading data that looks precise because every field has been completed.
Improvement actions need an owner and a review point. If a fulfilment team agrees to change a handover, the complaint record should connect to that work. Otherwise, a recurring issue can be discussed repeatedly without anyone checking whether the promised change was implemented.
Read complaint numbers in context
Complaint volume is an incomplete measure of service quality. An increase could indicate deteriorating performance, more customers, a simpler reporting route or several of these factors at once. A decline could reflect improvement or greater difficulty in making contact.
Leaders should examine complaint rates alongside relevant activity, such as completed orders or active accounts. They should also consider severity, repeat contact, reopened cases and the stage at which problems arise. These measures support investigation, but no single indicator explains the whole customer experience.
A small number of serious complaints can deserve immediate attention. A large number of minor issues may reveal a process that wastes customer and staff time. The response should consider both the consequence of an individual failure and how often it occurs.
Customer groups and channels can provide further context, where data is collected appropriately. If one group has difficulty reporting problems, its experience may be underrepresented. The company should avoid treating absence from a complaint dataset as evidence that a service works well for that group.
Complaint analysis can also be compared with returns, cancellations, product research and support contacts. Agreement across several sources can strengthen an investigation. Differences between them can be informative too, especially when customers abandon a service without formally complaining.
Manage public reviews without distorting the evidence
A public review is not identical to a formal complaint, but it may reveal a problem that deserves investigation. A company should have a route for moving relevant information into its complaint process while protecting personal information.
Public responses should be accurate and proportionate. They can acknowledge the issue, explain how to contact the company and describe verified information without disclosing account details. Staff should know when a matter needs review before a public response is posted.
In the United States, the Federal Trade Commission's guidance on consumer reviews explains restrictions on certain review-suppression practices, including specified threats or intimidation intended to remove or change a review. The guidance also distinguishes review organisation from prohibited suppression. Companies need to assess the conduct and relevant jurisdiction rather than assuming all moderation is unlawful.
Operationally, trying to remove criticism can deprive a company of useful evidence. A more productive question is whether the review points to a repeatable failure. A negative comment does not automatically establish every allegation, but it should not be dismissed solely because it is uncomfortable.
Customer satisfaction measures also need honest collection practices. If staff are rewarded mainly for favourable scores, management should consider whether customers are being selected or pressured in ways that make the data less useful.
Close the improvement cycle
Suppose a hypothetical retailer finds that several customers received incorrect collection instructions. The immediate response may involve correcting each affected order and assisting the customers. The preventive work could require changing a message template and updating the store handover.
The company should then test whether the revised message contains the correct information and reaches customers at the right time. It can review subsequent cases involving the same issue, while recognising that a short period without complaints is not conclusive proof of success.
This creates a complete sequence: identify the issue, investigate, decide the remedy, change the process and check the result. The sequence can be proportionate. A small business may manage it through a shared record and a regular review, while a larger company may need formal reporting across departments.
Senior management involvement matters when a recurring problem reflects conflicting incentives. Sales may benefit from an attractive promise that operations cannot reliably fulfil. Resolving that conflict requires a decision about the offer and its economics, rather than asking support staff to apologise more efficiently.
Questions business leaders should ask
Is a low complaint count a reliable sign of success
Not by itself. Companies should consider transaction volume, reporting accessibility and other customer evidence. A low count may reflect good service, but it may also reflect customers giving up or leaving without reporting a problem.
Should every complaint trigger a process change
No. Some cases are isolated, unsupported or already covered by a suitable process. Every complaint deserves proportionate consideration, while preventive changes should follow the evidence, consequences and likelihood of recurrence.
What should happen when several teams are involved
One coordinator should maintain ownership of the response and obtain contributions from the relevant teams. The customer should receive a coherent explanation rather than having to manage the company's internal handovers.
How can management know whether learning is happening
It can ask which operational decisions changed because of complaint evidence, who implemented those changes and what subsequent checks found. Counts of closed tickets alone do not answer those questions.
Use complaints to improve delivery
A complaint process earns its place in business management when it helps the company respond fairly and deliver more reliably. That requires attention to the individual customer and to the conditions that produced the problem.
The strongest evidence of progress is a verified improvement in the underlying service. A well-written apology remains valuable, but it becomes more meaningful when the company can also explain what it has learned and what it has changed.
Reference links
1. International Organization for Standardization — ISO 10002 2018 Guidelines for complaints handling in organizations
https://www.iso.org/standard/71580.html
2. NSW Ombudsman — Effective Complaint Management Guidelines
3. UK Public Ombudsman — Principles of Good Complaint Handling Summary
https://www.ombudsman.org.uk/about-us/our-principles/principles-good-complaint-handling/summary
4. OECD — Recommendation of the Council on Consumer Protection in E Commerce 2016
5. US Federal Trade Commission — The Consumer Reviews and Testimonials Rule Questions and Answers
https://www.ftc.gov/business-guidance/resources/consumer-reviews-testimonials-rule-questions-answers