Customer Complaints Charter: What It Is, Why It Matters & How to Build One That Works
A customer complaints charter is a public-facing statement that explains how your organisation will receive, assess and resolve customer complaints — clearly, fairly and within defined timeframes.
It is your organisation's complaints promise, made in plain English where customers can see it.
But a charter is only ever worth the delivery behind it. The industry too often treats it as a website page to satisfy a compliance checklist — a set of confident timeframes nobody actually measures.
ACXPA's position is blunt: a promise you cannot keep does more damage than no promise at all. A charter works only when a real process, clear escalation, and trained people sit behind every line of it.
This guide covers what a customer complaints charter is, what to include, a copy-and-paste template, the pitfalls that quietly undermine trust, and how to make sure yours is backed by something real.
What it is
A short, public statement of how you handle complaints — the channels, the timeframes, how customers are kept informed, and how to escalate.
Why it matters
It sets expectations and creates accountability at the exact moment trust is under pressure — when a customer has already been let down.
What this guide covers
The definition, what to include, a ready-to-use template, common mistakes, how to measure it, and how to back it with a real process.
What is a Customer Complaints Charter?
A customer complaints charter is a short, plain-English document — usually published on your website — that tells a customer exactly what will happen if they complain.
It typically covers how to lodge a complaint, what happens after it is received, how long each stage should take, how outcomes are communicated, and what to do if the customer is still not satisfied.
In a mature complaint system, the charter is the public "front door". Behind it sit the parts customers never see: a complaint log, a decision framework, response templates, escalation rules and trained staff.
The charter makes the promise; everything behind it keeps the promise.
In plain English
A complaints charter answers one question for an upset customer: "If I complain, what will you actually do, and by when?"
If your charter can't answer that clearly — or your team can't deliver on the answer — you don't have a charter, you have marketing.
✓ What a charter IS
- A public, plain-English promise to customers
- A set of commitments on channels, timeframes and escalation
- The visible "front door" to your complaints process
- A trust and governance artefact you stand behind
✗ What a charter is NOT
- A complaints policy — that's the internal procedure staff follow
- A complaints handling framework — that's the end-to-end process and decision logic
- A legal disclaimer or terms page
- A one-time page you publish and never revisit
Why a Complaints Charter Matters
A complaint is a moment of maximum risk and maximum opportunity. The customer is already frustrated — but research consistently shows that a complaint handled well can leave a customer more loyal than if nothing had gone wrong.
A charter is how you stack the odds in your favour before the complaint even arrives, because everyone knows what is supposed to happen.
For your customers
It removes the "where do I go now?" anxiety. A clear charter reassures an upset customer they'll be heard, treated fairly and given a defined path — without having to fight for it.
For frontline & contact centre teams
It gives staff a shared standard to work to. When the timeframes, escalation points and tone are agreed in advance, complaints are handled consistently instead of being improvised under pressure.
For governance & leadership
It evidences a documented, defensible approach. Many sectors expect this, and a charter backed by a framework and a complaint log is far easier to stand behind when a decision is challenged.
The editorial point
A charter is not a customer-service nicety — it is a commitment device. Publishing your timeframes publicly forces internal honesty about whether you can actually meet them.
That discomfort is the point: it's what turns a vague intention to "handle complaints well" into a measurable operational standard.
What to Include in a Complaints Charter
To work in the real world — not just look good on a webpage — a charter should mirror the process your team actually runs. These are the eight elements every effective charter covers.
Channels & accessibility
Every way a customer can complain — phone, email, web form, in person — plus any accessibility support, so no one is locked out of being heard.
What counts as a complaint
A shared, plain definition so customers and staff work from the same baseline and genuine complaints aren't quietly logged as "feedback".
Acknowledgement time
When the complaint is confirmed as received, how the customer is told, and what they can expect to happen next.
Investigation & resolution timeframes
Realistic targets you can genuinely hit, plus honest guidance on how complex matters are handled when they take longer.
Updates & communication
How customers are kept informed during the process and what they will receive in writing at each key point.
Outcomes & remedies
What resolution can look like — an explanation, a fix, a refund, a goodwill gesture, and the action taken to prevent a repeat.
Escalation & review
Clear, named options if the customer is unhappy with the response — internal review first, then any external avenue available to them.
Continuous improvement
How complaint themes and root causes feed back into your systems, processes and training — closing the loop instead of just closing the ticket.
💡 Match the charter to your size
For a small organisation, a charter plus a simple complaint-capture method may be all you need.
For larger teams, consistency improves dramatically when the charter is backed by structured tools and a decision framework — exactly what the ACXPA Complaints Handling Hub is built around.
Customer Complaints Charter Template
The template below shows the typical structure of a customer complaints charter.
Use it as a starting point and replace the placeholders in <angle brackets> with your own details. The seven clauses below map directly to the elements above.
Our commitment
We are committed to handling complaints fairly, respectfully and in a timely way. We treat every complaint as an opportunity to put things right and improve our service.
How to make a complaint
Phone: <insert number> · Email: <insert email> · Website: <insert form or page> · In person: <insert process>. We can provide support if you need help making your complaint.
What happens next
We acknowledge your complaint and assess it using a consistent internal process, so that every customer receives a fair and considered response.
Our timeframes
We aim to acknowledge complaints within <X> business days and resolve them within <Y> business days. Complex matters may take longer, and we will keep you informed if they do.
Communication & outcomes
We communicate clearly, explain our decisions, and confirm the outcome of your complaint in writing.
Escalation
If you are unhappy with our response, you can request a review by contacting <insert role>. We will also tell you about any external review options available to you.
Continuous improvement
We analyse complaint themes and root causes to improve our services, systems and training, so the same issues don't keep recurring.
Inside the ACXPA Complaints Handling Hub
The in-page text above is yours to adapt freely.
ACXPA members can also access ready-built versions inside the Complaints Handling Hub — an editable charter template for internal sign-off, website-ready complaints page copy, a developer implementation guide, a complaints handling framework, and a print-ready customer commitment sign for your point of service.
The complaints logging tool and escalation decision tool are included with ACXPA Business Membership.
How to Build & Publish a Complaints Charter
Writing the words is the easy part.
A charter earns its keep only when it reflects what really happens and is backed by people who can deliver it. Here's the order that works.
Map your real process first
Before you write a single promise, document how a complaint actually moves through your organisation today — who touches it, where it stalls, and how it gets resolved.
The charter should describe reality, then raise the bar. A charter that describes a process you don't have is a promise you can't keep.
Set timeframes you can actually hit
Pick acknowledgement and resolution targets from evidence — your own data on how long complaints really take — not from what sounds impressive.
A modest timeframe you meet 95% of the time builds far more trust than an ambitious one you miss half the time.
Write it in plain English
Strip out legalese and internal jargon. An upset customer should understand every line on first read.
If a sentence needs a second reading, rewrite it.
Publish it where customers actually look
A charter buried three clicks deep helps no one. Link it from your contact page, your footer, and any "make a complaint" journey.
Consider point-of-service signage so the commitment is visible before a problem arises.
Train the team behind it
The people who receive complaints need to know the charter exists, what it commits to, and how to deliver on it — including how to de-escalate and when to escalate.
A charter the frontline hasn't been briefed on is a promise made on their behalf without their knowledge.
Review it against real data
Set a schedule — at least annually — to check the charter against what your complaint data shows.
Are you meeting your timeframes? Are the same themes recurring?
Update the charter and the process behind it accordingly.
The Benefits of a Complaints Charter
Done properly, a charter pays off well beyond the individual complaint. Here's what a well-built, well-backed charter delivers.
Builds trust under pressure
It reassures customers at the exact moment trust is most fragile — giving them a fair, defined path instead of a fight.
Reduces repeat contact
Clear next steps stop the "where do I go now?" chasing across channels — cutting avoidable contacts and frustration.
Drives consistency
It gives every team member the same standard to work to, so outcomes don't depend on who happens to pick up the complaint.
Supports governance
A documented, public commitment backed by a framework helps evidence a robust and defensible approach when decisions are challenged.
Turns complaints into intelligence
The charter's improvement commitment forces complaint themes to be captured and acted on — converting gripes into operational insight.
Protects reputation
Customers who feel fairly handled are far less likely to escalate publicly — a quiet, resolved complaint rarely becomes a review or a regulator's file.
Common Complaints Charter Mistakes
Most charter failures aren't failures of intent — they're failures of follow-through. These are the mistakes that quietly turn a charter into a liability.
❌ Promising timeframes you can't meet
An ambitious "resolved within 5 days" that you hit 50% of the time creates more anger than no number at all.
Every missed promise is a second complaint in the making. Set targets from your real data.
❌ A charter with nothing behind it
The most common and most damaging mistake: a polished public page with no framework, no log, no escalation rules and no trained staff.
The charter is the promise — the process is the delivery. Don't publish the promise until the delivery exists.
❌ Copying a generic template verbatim
A charter that doesn't match your actual channels, roles and timeframes reads as boilerplate and falls apart on first contact with a real customer. Use a template as scaffolding, then make every line true for your organisation.
❌ Treating it as a compliance tick-box
Writing a charter purely to satisfy an auditor produces a document customers never see and staff never use. The value is operational, not ceremonial — build it to be used, not filed.
❌ No clear escalation path
If the charter doesn't tell a dissatisfied customer exactly who to go to next, you've simply moved the dead end. Name the internal review point and any external options.
❌ Set it and forget it
A charter that's never reviewed against complaint data slowly drifts from reality.
Roles change, channels change, timeframes slip. Schedule a review at least annually and update both the charter and the process.
The one that matters most: a complaints charter is a promise made in public.
An unbacked or unmet promise erodes trust faster than having no charter at all — because the customer now has documented evidence you didn't do what you said.
Never publish a commitment your process and people can't actually deliver.
How to Know Your Complaints Charter is Working
A charter isn't a "publish and done" exercise. These are the signals that tell you whether yours is delivering — or just decorating a webpage.
Acknowledgement-time adherence
Track the percentage of complaints acknowledged within your published timeframe. This is the easiest commitment to keep and the first one to monitor — if you're missing it, the rest of the charter is in trouble.
Resolution-time adherence
Measure how often complaints are resolved within your stated timeframe, and analyse the ones that aren't. Consistent misses mean your timeframe is wrong, your process is broken, or you're under-resourced — all worth knowing.
Escalation rate
What proportion of complaints get escalated or reopened? A rising escalation rate suggests first responses aren't resolving the issue — a signal to look at quality and root cause, not just speed.
Repeat-contact rate
How often does a customer have to chase you about the same complaint? Low repeat contact means your communication commitments are working; high repeat contact means customers are filling a silence you promised not to leave.
Theme & root-cause tracking
Are the same complaint causes recurring quarter after quarter? The continuous-improvement clause is only real if themes are captured and acted on.
Falling repeat-themes is the clearest proof the charter is driving change.
Post-resolution feedback
Ask customers how the complaint felt to go through, not just whether it was resolved. A fair, well-communicated process can leave a customer more loyal than before — that recovery is the ultimate test of the charter.
The rule
If you publish a timeframe, you must measure it. A commitment you don't track is a commitment you can't keep — and one you'll only discover you've broken when a customer points it out.
Frequently Asked Questions About Complaints Charters
What is a customer complaints charter?
It's a short, public statement of how your organisation receives, assesses and resolves complaints — including the channels customers can use, the timeframes you commit to, how you'll keep them informed, and how to escalate if they're unhappy.
In plain terms, it answers the question: "If I complain, what will you do, and by when?"
Is a complaints charter legally required?
It depends on your industry and jurisdiction. Many regulated sectors expect documented complaint-handling processes, and a charter is a clear way to evidence one — but even where it isn't mandated, it's strong practice.
Treat the charter as the public face of a complaint process that meets whatever obligations apply to you; this is general information, not legal advice, so check the specific requirements for your sector.
What's the difference between a complaints charter and a complaints policy?
A charter is customer-facing and public — it tells customers what to expect. A policy is internal — it tells staff the rules and procedures to follow.
They should align, but they're written for different audiences and do different jobs. A third document, the complaints handling framework, sets out the end-to-end process and decision logic that sits behind both.
What timeframes should we put in our charter?
Use timeframes drawn from your own data on how long complaints actually take, not from what sounds impressive.
Common patterns are acknowledgement within a small number of business days and resolution within a longer window, with an explicit note that complex matters may take more time.
The right number is the one you can consistently meet — a target you hit 95% of the time beats an ambitious one you regularly miss.
Where should we publish our complaints charter?
Somewhere customers can find it without hunting — typically a dedicated complaints or contact page, linked from your site footer and from any "make a complaint" journey.
Many organisations also use point-of-service signage so the commitment is visible before a problem arises. A charter no one can find delivers none of its benefits.
Should we promise a resolution timeframe we can't always meet?
No. This is the single most damaging charter mistake. A public timeframe you miss half the time creates documented evidence that you didn't keep your word, which fuels escalation and erodes trust.
Set a realistic target you can consistently hit, and be explicit that complex matters may take longer with regular updates. Under-promise and over-deliver — never the reverse.
How is a charter different from a complaints handling framework?
The charter is the public promise; the framework is the private machinery that keeps it. The framework defines what counts as a complaint, how each one is assessed and escalated, who decides what, and how outcomes are recorded.
You need both: a charter without a framework is a promise with nothing behind it, and a framework without a charter is a process customers can't see.
Do small businesses really need a complaints charter?
Yes — though it can be lighter-touch. Even a one-page charter plus a simple way to log and track complaints brings the same core benefits: clearer customer expectations, more consistent handling, and a record you can learn from.
As you grow, you add structure behind it. The promise matters at any size; only the machinery behind it scales.
Where to Next
Summary: Customer Complaints Charter
A customer complaints charter is your public promise on how you receive, assess and resolve complaints — clearly, fairly and within defined timeframes.
It sets expectations for customers, creates a shared standard for staff, and gives leadership a documented, defensible approach.
Done well, it can turn one of the riskiest moments in the customer relationship into one of the most loyalty-building.
But the charter is only the promise. Its real value depends on the framework, the complaint log, the escalation rules and the trained people behind it.
A charter with nothing behind it — or one that promises timeframes you can't meet — does more harm than no charter at all, because it hands the customer documented proof you didn't keep your word.
So build the process first, set timeframes you can genuinely hit, publish it where customers will find it, train the team who deliver it, and measure it against real complaint data. Make the promise, then keep it — every time.
