Best-Practice Complaint Handling: Building Team Capability Beyond the Policy Document
Updated: Oct 27
Best-practice complaint handling means a team can acknowledge a complaint quickly, listen well, keep the person informed, explain decisions fairly and choose the right resolution pathway for each matter. A written policy supports this, but the outcome depends on the skill and confidence of staff in real conversations.
Most organisations I work with already have a complaints policy, and many have a complaint management framework aligned to recognised standards. The policy is rarely the problem. The problem is the distance between what the document says and what a tired officer says on the phone to an upset person at 4.45pm on a Friday.
This article is written for heads of complaints, HR directors and L&D leads who are reviewing performance or weighing up in-house training. It covers where complaints actually go wrong, what good looks like at each stage, and how to build complaints team capability that holds up under pressure.
Key Takeaways
A policy describes a process. Capability is what staff do and say in the first conversation, and that is what decides whether a complaint stays small.
Complaints rarely escalate because of the original issue. They escalate because of silence, delay and perceived unfairness in how the matter was handled.
Early resolution works best when acknowledgement, listening and a clear next step happen before positions harden.
Fairness has to be visible. People need to see who is deciding, on what basis and why, in plain language.
Not every matter needs the same pathway. Some need conciliation, some coaching, some investigation and some simply a clear management decision.
Multi-day, in-house training tailored to your legislation and case patterns outlasts one-off sessions because the whole team practises together.
Summary Table
Stage 1: First contact
What goes wrong: Rushed intake, scripted empathy, no clear next step
What best practice looks like: Prompt acknowledgement, genuine listening, clear expectations
Capability needed: Active listening, clarifying questions
Stage 2: Early resolution
What goes wrong: Positions harden while the matter waits in a queue
What best practice looks like: Early conversation about what matters to the person
Capability needed: Early-resolution structure, confidence to act
Stage 3: Progress
What goes wrong: Silence, then a late and defensive response
What best practice looks like: Regular, honest updates even when there is no news
Capability needed: Plain-language communication
Stage 4: Decision
What goes wrong: Outcome delivered without reasons
What best practice looks like: Transparent reasoning and an explained outcome
Capability needed: Procedural fairness, writing and speaking clearly
Stage 5: Pathway choice
What goes wrong: Defaulting to the familiar process
What best practice looks like: Matching the process to the matter
Capability needed: Process-fit judgement
Stage 6: Team capability
What goes wrong: One-off workshop, little retained
What best practice looks like: Shared language, practised in context, embedded follow-up
Capability needed: Tailored in-house training
Why Policy Alone Does Not Deliver Best-Practice Complaint Handling
A complaints policy sets out what should happen. Best practice depends on what actually happens in the first phone call, the first email and the first meeting. The gap between written process and frontline conversation is where most avoidable escalation starts, and it is a capability gap, not a documentation gap.
In Australia, the reference points are well established. AS 10002:2022 provides guidance on complaint management, and ombudsman offices at Commonwealth and state level publish better-practice guidance for agencies. I treat these as essential context. They tell you what a sound complaint management framework should contain: commitment, accessibility, responsiveness, objectivity, remedies, and review.
What they cannot do is hand a staff member the words to use when a person is angry, distressed, or convinced nobody is listening. A framework says to acknowledge complaints promptly. It does not tell an officer how to acknowledge a complaint from someone who has already called three times.
In my experience, organisations often respond to a weak complaints result by rewriting the policy. The new version is clearer and better formatted. Frontline behaviour stays the same, because the behaviour was never driven by the document. It was driven by habit, workload, fear of saying the wrong thing and uncertainty about how much an officer is allowed to say.
That is why I start with a different question when I review a complaints function: not "is the process documented?" but "what do your people do in the first five minutes of a difficult contact, and do they all do the same thing?"
Conflict is not a failure. A complaint is a signal that something important has not yet been properly understood. The task of the team is to understand it early and respond in a way that keeps the person and the system in view.
The First Contact Sets the Trajectory
The first contact sets the trajectory because it is when a person decides whether they are being heard. Prompt acknowledgement, genuine listening and a clear statement of what happens next calm most complaints before positions harden. Early resolution is far easier at this point than after weeks of uncertainty.
The issue is rarely just the thing the person first raised. By the time someone lodges a formal complaint, they have usually tried to raise it informally, been passed around, or waited for a response that did not arrive. They are bringing that history into the conversation, whether or not your officer knows it.
Good first contact has three parts.
1. Acknowledge without defending
Acknowledgement is not agreement. It is a clear statement that the concern has been received, understood in outline, and will be handled. Many staff avoid acknowledging a concern because they fear it will be read as an admission. Training should separate empathy from agreement so officers can say "I can see why this has been frustrating" without implying the organisation was at fault.
2. Listen for what matters
People often lead with the grievance that is easiest to state. What matters to them may be different: an apology, a correction to a record, an assurance that it will not happen to someone else, or simply a decision. Good listening uses open questions, reflects back what was said and checks understanding before moving to process.
3. Create a clear next step
Every first contact should end with the person knowing who has their matter, what will happen next and when they will hear from you. That sounds basic. It is also the step most often skipped when the queue is long.
This is where The Early Resolution Sequence is useful. It moves a vague tension into a manageable process through six steps: clarify the issue, understand what matters, choose the right process, create structure, support the conversation and document the next step. Used at intake, it gives officers a shared structure for early resolution of complaints, rather than leaving each person to improvise.
I have delivered in-house communication and early-resolution training for an ombudsman office whose complaints teams handle emotionally charged contacts. The program was built on the office's real case patterns, so the practice scenarios were the conversations staff actually have. The result was shared language and structure for their hardest calls, delivered without anyone leaving the building. That shared language matters as much as any individual technique.
Managing Silence and Delay
Silence and delay compound the original concern. When people hear nothing, they assume nobody is looking at their matter, or that someone is avoiding it. Regular, honest progress updates, even when there is no news, keep frustration from becoming a second complaint layered over the first.
A common belief in complaints teams is that careful means slow. I disagree. Delay is not the same as care. By the time a thorough, measured response arrives, the person is reacting to the silence as much as to the original issue. Clarity is kind.
Consider a composite illustration, not a real case. A member of the public complains that a notice they received was confusing and they cannot tell what they are required to do. It is a small matter. The officer acknowledges it, plans to confirm the wording with a colleague, and the colleague is on leave. The officer is busy and does not want to send an update that says nothing. Weeks pass.
The person follows up. The reply is polite but generic. They follow up again and are told the matter is with another area. By now they are no longer asking about the notice. They are asking why nobody will tell them anything. When a substantive answer finally arrives, it is correct, and it is also too late. The complaint now includes allegations of being ignored, a request for the officer's name and a threat to go to the oversight body.
Nothing in that story is dramatic. The substance was minor and the answer was available. What escalated the matter was an absence of communication, and no policy clause would have prevented it, because the policy probably said to respond within a set timeframe. What would have helped was an officer comfortable sending a short, honest message: "I haven't got the answer yet, here is what I'm waiting on, and I will update you by Thursday."
What a good progress update contains
What has been done so far
What is still outstanding and why
When the person will next hear from you
Who to contact if something changes
This takes minutes to write. Teams skip it because it feels uncomfortable to report no progress. Training should make it routine, so that a holding update is treated as part of the work, not an apology for not having finished it.
Managers have a role too. Complaint workloads, handover practices and leave cover are system issues. If a matter stalls whenever one person is away, that is information about the system, not a personal failing.
Fairness People Can See
Procedural fairness is visible when a person knows who is deciding, what information is relied on, and why the outcome was reached. They can disagree with a decision and still accept the process. Transparent reasoning, delivered in plain language, is what makes an adverse outcome defensible and respectful.
Many agencies are good at being fair and poor at showing it. The decision was reasonable, the evidence was considered, the officer was impartial. But the person receives a letter with a conclusion and no reasoning, and concludes the process was a formality.
Visible fairness has a few practical elements.
Tell people what to expect. Explain the steps, who is involved and what will not be covered.
Let people respond. Where an adverse view may be reached, give the person a genuine opportunity to put their position.
Explain the reasoning. Link the outcome to the issues the person raised, not only to the policy.
Be clear about what can change. If review rights exist, say so plainly, and say what the review can and cannot do.
Be honest when the answer is no. A clear no with reasons is more respectful than a vague response that leaves hope alive.
There is a distinction I raise often: neutrality is not the same as fairness. An officer can be scrupulously neutral and still run a process that feels unfair, because the person cannot follow it, cannot be heard, or cannot understand the outcome. Fairness is about the experience of the process as well as its design.
The skill that holds this together is the ability to explain an outcome well. That includes delivering a difficult decision calmly, without defensiveness, and staying with the conversation when the person is upset. Difficult conversations in complaint handling are not an add-on. They are the point at which procedural fairness is either felt or lost.
This matters further as AI-generated complaints and submissions enter the picture. Fairness, evidence integrity and workload realities all become harder to manage. I built a dedicated program, Navigating AI in Complaints and Dispute Resolution, because public-sector and business teams asked for practical guidance on exactly this.
It now runs as public sessions and as tailored in-house delivery for regulators and complaints teams. Related guidance on building an AI complaints handling policy that staff actually use is worth reading alongside your framework.
Not Every Complaint Needs the Same Pathway
No. Not every complaint needs the same pathway. Some matters need conciliation or facilitation, some need coaching, some need an investigation, and some need a clear management decision. Best practice means choosing the process that fits the matter rather than defaulting to the one your organisation knows best.
This is the point where I part company with the common advice that serious disputes should go to mediation. Mediation is a valuable process. It is also not always the right one. The hardest decision in complaint handling is often not the outcome but which process to use to get there.
Two parties with a relationship to repair or an issue to negotiate
Often fits: Conciliation or mediation
Why: A facilitated conversation can resolve what a decision cannot
A group or team with competing views and unclear roles
Often fits: Facilitation
Why: Structure helps people reach shared understanding
One person struggling with how to raise or respond to a concern
Often fits: Coaching
Why: Builds capability and confidence for the conversation
Allegations of misconduct or a breach that must be established
Often fits: Investigation
Why: Facts need to be found and findings made
A question the organisation has authority to decide
Often fits: Clear management decision
Why: Rapid clarity is the respectful response
The Process-Fit Distinctions I use with teams help organisations avoid reaching for a familiar tool:
Mediation vs investigation. One explores interests and options. The other establishes facts and makes findings.
Conflict vs misconduct. A disagreement about priorities is not the same as a breach of a code of conduct.
Early resolution vs avoidance. Resolving a matter early is not the same as hoping it goes away.
Neutrality vs fairness. Impartiality alone does not make a process feel fair.
Empathy vs agreement. Understanding a concern does not commit you to the outcome the person wants.
Psychological safety vs comfort. Good process creates safety. That is not the same as avoiding hard topics.
A mistake I see regularly is sending a matter to mediation when what the person needs is a decision. The organisation has the authority to decide, the facts are not in dispute, and yet the matter is referred for a facilitated conversation because it feels gentler. The person experiences it as more delay. Equally, an investigation launched for what is really a communication breakdown can harden positions that a calm conversation would have softened.
Choosing well requires judgement, and judgement is built through practice on realistic scenarios. Where a matter does suit a facilitated resolution, conciliation can be an effective option, particularly where the parties need to keep working together or dealing with each other afterwards.
Building Complaints Team Capability That Lasts
Capability lasts when a whole team learns together, in their own legislative and operational context, using their own case patterns, with follow-up after the training. Multi-day, in-house programs outlast one-off sessions because staff practise the language and structure, not just hear about it.
I have more than 15 years of dispute resolution practice and have worked with more than 50 government and business organisations. A pattern is clear. Generic external courses give individuals useful ideas, but those ideas rarely survive the return to a team with different habits. One person tries a new approach, nobody else does, and the old pattern reasserts itself.
Training should never be abstract. It should give people language, structure and confidence they can use in the next difficult conversation they have at work. That is why I design and deliver the work myself, in-house, around a specific team's legislation, context and real conversations.
For a federal government department, I designed and delivered a five-day accredited mediation training program for tribunal-facing staff, tailored to the department's statutory context. The whole cohort was trained together inside their own regulatory frame, rather than attending generic external courses. The same principle applies to complaint handling training for government: the cohort shares a vocabulary, so the practice carries into daily work.
What effective in-house training includes
Your legislation and context. Scenarios reflect the powers, limits and review pathways your staff actually work within.
Your real case patterns. De-identified contact types are used for practice, so staff rehearse the conversations they will have.
Practice, not presentation. Participants role-play, receive feedback and repeat, because confidence comes from doing.
Whole-team participation. Managers and frontline staff learn the same language, which makes coaching on the job possible.
Embedding after delivery. Follow-up keeps the practice alive when workloads rise.
The feedback I value most comes from clients, and I am grateful for more than 40 five-star Google reviews. But the measure that matters to a head of complaints is simpler: do the team handle the next hard contact more calmly, clearly and fairly than the last one? Calm, clear and fair is the standard. It is built through repetition inside the team, not through a policy refresh.
If you are considering this for your own team, the first step is a conversation about your complaint-handling challenges. A confidential training consultation lets us look at your context before anything is designed.
What Reviewing Your Complaints Function Should Start With
Start by listening to real contacts, not auditing documents. A sample of calls, emails and meeting notes will show you more about your complaint handling than any policy review. It reveals whether acknowledgement, updates and explanations actually happen, and where staff avoid the difficult parts of the conversation.
Here is a position I hold that may be uncomfortable. Many complaints reviews measure what is easy to count: timeframes met, acknowledgements issued, matters closed. Those measures matter. But a team can meet every timeframe and still leave people feeling unheard, because the acknowledgement was a template and the closing letter gave no reasons.
What helps is reviewing the quality of the conversation alongside the speed of the process. Ask a few direct questions of a sample of closed matters:
Did the person know what would happen next after the first contact?
Were there periods of silence, and did anyone explain them?
Could the person understand why the outcome was reached?
Was the pathway the right fit, or the familiar one?
Did the officer feel equipped to handle the hardest moment?
That last question is the one organisations skip. Staff who feel unequipped avoid, delay and defer. The delay then looks like a process problem, when it is really a confidence problem. Fixing it means giving people structure and practice, and removing the idea that a difficult conversation is a sign something has gone wrong.
Treating complaints as information, rather than as a threat, changes how a team works. People raise problems earlier. Managers respond proportionately. And the person who complained is more likely to feel that the system was calm, clear and fair, even when the answer was not the one they wanted.
This is the kind of work we do inside organisations, over one, two or three days, built for your team's context. Book a confidential discussion about in-house training and team workshops.
FAQs
What is best-practice complaint handling?
Best-practice complaint handling is a consistent approach in which complaints are acknowledged promptly, listened to properly, progressed with regular updates, decided fairly and explained clearly. It is supported by a written framework, but it is delivered through the skills of staff in real conversations, and it matches each matter to the right resolution pathway.
What should a complaint management framework in Australia include?
A complaint management framework in Australia should reflect recognised guidance such as AS 10002:2022 and the better-practice material published by ombudsman offices. In general terms that means leadership commitment, accessible channels, timely responses, objective handling, appropriate remedies and review. The framework only works if staff are trained to apply it in conversation.
How do you achieve early resolution of complaints?
Early resolution depends on acting before positions harden. Acknowledge the complaint quickly, listen for what matters to the person, clarify the issue, choose the right process, agree a clear next step and document it. Frontline staff need the confidence and authority to have that early conversation, not just refer the matter on.
How do you handle difficult conversations in complaint handling?
Stay calm, acknowledge the person's experience without defending or conceding, ask open questions, and explain clearly what you can and cannot do. Separate empathy from agreement so you can show understanding without promising an outcome. Practising these conversations in realistic scenarios builds the confidence to do it under pressure.
Is in-house complaint handling training better than external courses?
For teams, usually yes. In-house training can be built around your legislation, your case patterns and your real conversations, and the whole team learns the same language together. External courses can suit individuals, but ideas often fade when one person returns to a team that has not changed its habits.
If you are reviewing how your complaints team works in practice, send me an enquiry and we can talk through what would help.
References
Newsletter and blog
A monthly note from Shiv on conflict, complaints handling, leadership and dispute resolution practice. Reflective, practical, and written for people who work in and around conflict. No hype and no hard selling.
Subscribe to the monthly newsletter: Subscribe here
Shiv also writes regularly on workplace conflict, complaints, facilitated conversations and the changing landscape of dispute resolution.
Get new articles as they are published: Subscribe to the blog
How Shiv Martin Consulting Supports Teams
We provide:
Conflict resolution skills training in Brisbane, Australia and New Zealand wide and online to a range of global clients
Workplace mediation for early or unresolved conflict or tension
Leadership coaching to build communication and resolution skills
Team building and facilitation for groups that want to reconnect and move forward, without necessarily labelling the situation as conflict.
Whether your team is facing signs of friction or entrenched issues, we help you take a practical, people-smart approach to strengthening your culture.
.png)
