Home / Guides / Complaint handling standards in Australia
Compliance · 7 min read
Complaint handling in Australia: the standard, and the complaints you never receive
Australia has a well-drafted complaint handling standard, and most organisations that follow it still have a blind spot: the standard governs complaints that reach you. The majority never do.
What the standard covers
AS/NZS 10002:2022 Guidelines for complaint management in organizations is the reference point in Australia and New Zealand. It is a guideline rather than a law, but it is widely adopted, referenced by regulators and ombudsman schemes, and is a reasonable definition of what a competent complaints process looks like.
Its themes are unsurprising and sound: make it easy to complain, acknowledge promptly, be fair and objective, resolve within stated timeframes, keep the person informed, record complaints properly, and - the part organisations most often skip - analyse complaint data to find and fix systemic causes.
Sector schemes layer on top. Financial services, telecommunications, energy and water each have their own binding requirements with specific timeframes. If you are in one of those, the sector rules are the operative ones and this is a floor rather than a ceiling.
The assumption underneath it
Every complaint handling framework assumes the same first step: a complaint is made. Everything downstream - acknowledgement, timeframes, escalation, reporting, root cause analysis - is triggered by that event.
Which means the quality of your entire complaints programme is capped by the proportion of dissatisfied customers who actually complain. If that proportion is small, then a well-run process is doing excellent work on an unrepresentative sample.
Why most dissatisfaction never becomes a complaint
Lodging a complaint costs the customer time and emotional energy, and requires a belief that it will change something. Plenty of people who have decided to leave have neither. Others do not think of what happened as complaint-worthy - they think of it as how this business is.
What those customers do instead is mention it. On a call, in passing, usually politely, often to someone who is not in a position to escalate it and who was asked a different question. That mention is the complaint. It just never gets recorded as one.
Your complaints register is not a record of your service failures. It is a record of the failures that a customer had the energy to formally report.
Systemic analysis needs a bigger sample
The most valuable clause in the standard is the one about analysing complaint data to identify systemic issues. It is also the one most weakened by the sampling problem.
If only a fraction of failures are ever lodged, systemic analysis is being run over a sample that is both small and biased - biased toward customers who are confident, articulate, and angry enough to act. The failure modes that produce quiet resignation rather than anger are systematically under-represented, and those are frequently the ones that cost the most revenue.
Widening the input
The practical fix is not a better complaints process. It is a second input into the same process:
- Treat unlogged dissatisfaction as complaint data. A customer who rings a third time about an unresolved matter has told you something, whether or not they used the word complaint.
- Capture it where it actually happens. For most businesses that is the phone, and it is already recorded.
- Feed it into systemic analysis, not just into individual resolution. The point is finding the cause that recurs.
- Keep the record honest. If something is identified proactively rather than lodged by the customer, record it that way. Merging the two makes your complaint statistics uninterpretable.
What this looks like operationally
When every recorded call is read rather than a sample, the calls where a customer was left worse off surface within minutes of the call ending, whether or not the customer chose to complain. A manager reviews the alert, decides whether it is genuine, and either resolves it or routes it.
Two things follow that matter for the standard. Service recovery becomes possible while it is still recovery rather than a post-mortem - a failure found the same day can be fixed with a phone call. And systemic analysis gets a far larger and less biased input, because it is no longer limited to people willing to complain.
WiseSentry is built for exactly that first step - what gets flagged sets out where the line sits, including the failures it deliberately ignores because they were not yours.
Common questions
What is AS/NZS 10002?
AS/NZS 10002:2022 Guidelines for complaint management in organizations is the Australian and New Zealand standard for handling complaints. It is a guideline rather than legislation, but it is widely adopted and frequently referenced by regulators and ombudsman schemes.
What percentage of unhappy customers actually complain?
Published estimates vary widely and depend heavily on sector and method, so treat any single figure with caution. What is consistent across the research is the direction: formal complaints represent a minority of dissatisfaction, and the people who complain differ systematically from those who do not.
How can we find complaints that were never lodged?
They are usually mentioned somewhere, most often on a phone call that was recorded. Reading the content of calls rather than sampling them surfaces the customers who raised something and never entered a formal process.
See what a full review of your calls turns up
WiseSentry reads every recorded call and raises only the ones where your business let the customer down. Talk to us about a review of your own call history.