Complaints handling process

When something goes wrong – a delivery doesn’t arrive, a bill is wrong or no one calls back when they promised to – what matters most is how you respond. Most people are reasonable if they can see you’ve understood the issue and are doing something about it. If they have to chase for updates or get inconsistent answers, even a small problem can drag on and become something much bigger.

This guide sets out a practical, repeatable workflow that frontline staff in UK organisations can follow under pressure. It focuses on the key steps in handling complaints and includes a small set of templates and timeframes to support consistent responses.

Complaints handling process steps

Frontline staff should not need to invent a complaints handling process while a frustrated customer waits on the phone. That will invariably make the customer even more disappointed in your business.

A complaint should trigger a predictable set of actions – a consistent workflow that makes handovers easy. This matters when you run a hybrid team, rely on shift patterns or juggle multiple roles in a small business.

Use this end-to-end process as your default. It works well across most UK organisations, whether you manage complaints in a ticketing system, a shared inbox or a simple CRM.

Step 1: Receive and capture

Capture the complaint as it comes in, whatever the channel. Record what the customer said (in their words where possible), what they want to happen and any key dates or references.

If you summarise too aggressively, you can accidentally change the customer’s meaning. Keep your summary short and factual.

Step 2: Confirm and acknowledge

Check it meets your definition of a complaint and acknowledge it quickly. This reduces the customer’s anxiety and stops repeat chasing.

Confirm that you have logged it, who is handling it and when the customer will hear from you next.

Step 3: Triage and assign

Assess urgency and risk. Identify anything that needs immediate escalation (e.g., safety, vulnerability, data issues), then assign the case with clear ownership and internal deadlines.

Step 3: Investigate

Build a clear picture of what happened. Review records, speak to staff and check timelines. Focus on evidence, not assumptions, and keep notes as you go.

Step 5: Update and manage expectations

If you can’t respond straight away, keep the customer informed. Explain what’s happening and why it may take time. Keep them in the loop so they know when to expect a full response.

Step 6: Decide, resolve, close

Explain your findings clearly, set out what you will do to put things right, and confirm when it will be completed. Only close the case once the agreed action has been delivered.

Step 7: Learn and improve

Tag root causes, review trends and feed learning into process, product, training and quality checks. Complaints are expensive feedback. Use them to stop the same failures from happening again.

To make this practical for frontline teams, create a one-page “complaint handling map” that includes:

• The first three actions staff must take in the first 10 minutes
• Severity levels and examples
• Approved acknowledgement and holding response wording
• Remedy authority limits (who can offer what)
• Escalation triggers (data breach, safety risk, vulnerability, discrimination allegations)
• Your internal timeframes and update frequency

If you want a recognised benchmark for your process design, ISO 10002 sets out guidance on complaints handling. It’s a paid standard, but its principles – fairness, accessibility, transparency and continual improvement – are widely used.

What counts as a complaint in the UK?

Many organisations miss complaints because they look for the word “complaint”. In real life, customers rarely announce it so neatly. They complain in everyday language, especially on the phone or in short messages. Therefore, your definition needs to be clear enough for staff to apply quickly and broad enough to catch dissatisfaction early.

A complaint is an expression of dissatisfaction about your product, service, staff or processes, where the customer expects a response or resolution.

That definition helps you capture complaints in any channel, including informal ones.

Common examples that count as complaints

• “This is unacceptable. I want this sorted today.”
• “I’ve been chasing for weeks. No one calls me back.”
• “You charged me twice.”
• “Your engineer didn’t turn up and I lost a day’s pay.”
• “Your staff member was rude and embarrassed me.”
• “I want to raise a complaint.”
• “If you don’t fix this, I’ll go to the ombudsman.”

Examples that may not be complaints, but still need action

• General enquiry – “What time do you open?”
• Neutral request – “Can you resend my invoice?”
• Suggestion – “It would be great if you offered weekend delivery.”

However, if the customer expresses dissatisfaction, frustration or a desire for compensation, what they are saying to you is often a complaint. When in doubt, log it. It’s easier to downgrade a logged complaint than to reconstruct a missing record after escalation.

UK considerations that affect how you classify and prioritise

• Vulnerability – a customer might have additional needs due to health, disability, bereavement, financial distress or low confidence. If you suspect the customer is vulnerable, treat the case as high-priority and adapt how you communicate (slower pace, clearer steps, choice of channel).
• Safety and safeguarding – if the complaint involves safety risks, potential harm or safeguarding concerns, escalate it immediately to a senior owner.
• Protected characteristics and harassment – if the complaint involves discrimination or harassment, your organisation may have duties beyond customer service. This can also shift how you investigate and record the issue.
• Consumer rights – many outcomes link back to consumer protection expectations, including whether goods are faulty or services meet reasonable standards. The Consumer Rights Act 2015 provides useful background information on this.

Complaints procedure policy template

Your policy does two jobs at once. First, it tells customers how to raise concerns and what they can expect. Second, it gives staff a fixed workflow, enabling them to act consistently under pressure. A good policy also protects you if a complaint escalates, because you can show you followed a fair process.

You don’t need pages of legal language. Aim for clear, plain English that a customer or new starter can understand.

Use this structure as a practical template.

• Purpose – why you handle complaints and the outcomes you aim for (fair resolution, consistency, learning)
• Scope – what the policy covers (products, services, staff, partners, digital journeys) and what it does not (employee grievances, issues in court)
• Definition of a complaint – your definition, with examples, and confirmation that you accept complaints through any channel
• How to complain – channels available and the key information needed (contact details, reference, what happened, what the customer wants)
• Accessibility and adjustments – how you support different needs (alternative formats, verbal complaints, call-backs, translation where possible)
• Timeframes and updates – when customers can expect acknowledgement, updates and a full response (with a note that regulated sectors may differ)
• Triage and escalation – how you assess severity, who owns complaints and what triggers urgent escalation (safety, fraud, data issues)
• Investigation approach – confirm you use evidence, keep records and assess cases fairly
• Remedies and outcomes – types of resolution you may offer (refund, repair, rework, goodwill), depending on the facts
• Final response and escalation routes – what your final response includes and how customers can take things further
• Record keeping and privacy – what you store, why, how long for, and how customers can request their data
• Learning and review – how you use complaint data to improve, and how often the policy is reviewed

Acknowledging a complaint – wording

Acknowledging a complaint is often the first point where things either settle down or start to escalate. If the customer doesn’t hear back from you, they will assume they are being ignored. A quick, clear acknowledgement shows the issue has been taken seriously and that something is happening.

Aim to acknowledge the complaint within one to two working days – or sooner when complaints arrive via social channels. Even if you can’t actually investigate it yet, you can still respond.

A strong acknowledgement includes:

• A simple thank you for raising the issue
• A brief apology for the inconvenience (without jumping to conclusions)
• A summary of the issue in plain language
• The case reference and owner
• What happens next and by when
• How the customer can share more info

Acknowledgement template (email or letter)

Hello [Name],

Thank you for getting in touch. I’m sorry you’ve had to contact us about this.

I understand you’re unhappy about [brief summary in plain language]. I’ve logged your complaint under reference [ID] and I will look into what happened.

I will update you by [day, date] with either a full response or a progress update if we need more time. If you have any additional information that could help, please reply to this message or call us on [number] quoting your reference.

Kind regards,
[Name]
[Role]

Acknowledgement phone script (short and calm)

• “Thank you for explaining that. I’m sorry for the inconvenience.”
• “I’m going to log this as a complaint so we can investigate properly.”
• “Your reference is [ID]. I’ll update you by [date].”
• “Is there anything else you’d like us to take into account while we look into it?”

Keep your tone steady, even if the customer is angry and combative. If you sound like you’re rushing the call or like following a script, customers often escalate because they think you’re not taking it seriously.

Complaint triage and severity levels

Triage prevents two costly mistakes: teams treating every complaint as equally urgent, which burns out staff and creates delays, or treating everything as low urgency until a serious case escalates into a reputational or legal problem.

A simple severity model helps you prioritise properly. Use a three-level model that staff can apply quickly.

Level	Risk and description	Typical examples
Level 1 – standard	Low risk and low impact. The customer wants information, a correction or a straightforward fix.	Minor billing error, single late delivery without loss, confusing communication Minor product fault with easy replacement
Level 2 – priority	Medium risk or higher impact. The customer reports repeated failures, significant inconvenience, financial loss, vulnerability or escalation risk.	Multiple missed call-backs, repeat delivery failure Service disruption causing business impact, mentions of chargeback, solicitor, regulator or social media
Level 3 – critical	High risk. Immediate escalation required.	Minor billing error, single late delivery without loss, confusing communication, minor product fault with easy replacement

Attach actions and deadlines to each level. For example:

• Level 1 – acknowledge within 2 working days, respond within 10 working days.
• Level 2 – acknowledge on the same day or the next working day, update every 3–5 working days, and respond within 15–20 working days.
• Level 3 – acknowledge on the same day, escalate within 1 hour, provide daily updates and assign a senior owner.

Quick triage checklist

• Has the customer suffered financial loss?
• Is there vulnerability or distress?
• Is there a safety concern?
• Is personal data involved?
• Has it happened before?
• Does it affect multiple customers?
• Is the customer threatening escalation?

Train staff with real examples and give them confidence to escalate complaints early. It’s better to over-escalate a few cases than to under-escalate one critical case.

Best practices for investigating complaints

A fair investigation depends on slowing things down and checking the facts properly. Problems usually occur when teams jump to conclusions, defend earlier decisions, or rush to close the complaint before they fully understand what happened. A clear process helps you stay focused on evidence and keep decisions consistent.

Use this practical investigation approach.

1) Restate the issue and desired outcome

Write one sentence on what the customer says happened and what they want. This keeps the work focused and prevents scope creep.

2) Build a timeline

List key events with dates and times:

• When the issue first happened
• When the customer contacted you
• What actions were taken, and when
• What responses or updates were given
• Any delays, missed steps or repeat contacts

3) Gather evidence

Pull what you need depending on the case:

• Order records, invoices, payment logs
• Delivery tracking and scans
• Call recordings and chat transcripts
• Emails, notes, internal messages
• System logs and outage records
• Photos, engineer notes, inspection reports
• Supplier and contractor updates

4) Speak to the people involved

Ask staff for their account while they can still remember the details clearly. Keep your questions neutral:

• “Talk me through what happened.”
• “What information did you have at the time?”
• “In hindsight, would you have done anything differently?”

If staff think they will be blamed immediately, they may leave details out or become defensive. Make it clear that the goal is to understand what happened properly, while still addressing mistakes where needed.

5) Clarify with the customer when needed

If facts conflict, ask for clarity without making any accusations. For example: “I want to check that I have understood. You said the delivery arrived at 2pm. Our system shows 4pm. Do you have a message time stamp we can compare?”

6) Identify the root cause

The root cause of a complaint can never be “human error”. That’s a label, not an explanation. Ask “why” until you reach a process, system or decision that you can change to prevent similar issues from happening in the future.

Below are some examples.

• Why did the engineer not attend? Because the job did not appear on the route.
• Why did it not appear? Because a booking change did not sync.
• Why did it not sync? Because the system requires a manual confirmation step that no one completed.

Now you can fix something real.

7) Decide what’s fair

Once you understand what happened, decide what outcome makes sense based on the impact and the evidence available. Consider:

• Whether the complaint is fully, partly or not upheld
• What the customer actually experienced or lost
• Whether your team followed the correct process
• What you have done in similar situations before

If you offer goodwill, record why. If you refuse part of the request, explain the reason clearly and refer back to the evidence where needed.

8) Write an outcome summary

Summarise:

• What happened
• Why it happened
• What you will do now
• What you will change to prevent repeats

It also helps to separate the mistake from the impact and remedy. That makes explanations clearer and allows you to acknowledge the customer’s experience even if some details are disputed.

Holding response template and timescales

It’s not always possible to resolve a complaint quickly. You may be waiting for information from a supplier, reviewing records or speaking to the staff involved. In those situations, a “holding response” reassures the customer that the complaint is still being dealt with, which stops them from feeling like they need to keep chasing you.

Send a holding response as soon as you realise you will miss your promised deadline. Don’t wait until the deadline passes. Customers often escalate because they feel ignored, not because the investigation is taking time.

Good holding response habits

• Explain why you need more time to investigate the complaint in clear, plain English.
• Give a clear next update date – not “as soon as possible”.
• Offer an easy way for the customer to share additional evidence.
• Increase update frequency for higher severity complaints.

Holding response template

Hello [Name],

Thank you for your patience while we look into your complaint about [brief summary].

I’m writing to let you know that we are still investigating. We need a little more time because [brief reason, for example: we are waiting for information from our delivery partner and reviewing call recordings from the day].

I will update you again by [day, date]. If I can provide a full response sooner, I will do so. In the meantime, if you have any additional information, such as photos, receipts or reference numbers, please reply to this message.

Kind regards,
[Name]
[Role]

Short holding response phone script

• “We’re still investigating. We take complaints very seriously, so we don’t want to get this wrong.”
• “We will share the next update by [date].”
• “If you have any extra information, I can add it to the case now.”

Even when you can’t yet deliver a full outcome, you can usually reduce stress by confirming what you have already done:

• “We’ve pulled your account notes and requested a report from our courier.”
• “We’ve reviewed the booking history and spoken to the engineer’s manager.”

Apology wording that doesn’t admit liability

Many teams avoid apologising because they fear it admits liability. In practice, a well-worded apology is often the fastest way to create a good impression and make the customer feel calm. You can apologise for the customer’s experience and the impact without making inaccurate statements about fault.

A safe, effective apology usually includes a clear “sorry”, what you’re sorry for (impact or experience), and what you will do next.

Example apology wording

• “I’m sorry for the inconvenience this delay has caused.”
• “I’m sorry you had to chase us for an update.”
• “I’m sorry we didn’t explain that clearly.”
• “I’m sorry for the frustration caused by the conflicting information.”

When your investigation confirms an error, be direct:

• “We got this wrong. I’m sorry.”
• “We made an error on your account. I’m sorry for the impact.”

Avoid non-apologies that inflame customers:

• “I’m sorry if you feel…”
• “I’m sorry you took it that way…”
• “I’m sorry, but…”

A simple rule helps: apologise for the impact straight away, confirm the facts once you have them and explain the next step. That keeps the response calm, clear and accurate.

Remedies – refunds, goodwill and fixes

A remedy should be appropriate for what actually went wrong and how it affected the customer. Most people are reasonable about the outcome when you act quickly and explain things clearly.

Think of remedies in three layers.

1) Put it right

Fix the underlying problem:

• Repair or replace a faulty item.
• Re-perform the service.
• Correct an account error.
• Deliver missing items.
• Provide the promised information.
• Rebook a missed appointment quickly.

2) Pay the customer back

If the customer has paid for something they did not receive, or suffered direct loss due to your failure, consider reimbursement where appropriate. Keep it evidence-led and proportionate.

• Refund for undelivered goods or services
• Refund of charges applied in error
• Reimbursement of direct costs with proof, where appropriate

For consumer disputes, outcomes often connect to the Consumer Rights Act 2015, so it helps to train staff on the basics of refunds, repairs and reasonable service standards.

3) Recognise the customer’s experience

Goodwill means recognising the customer’s inconvenience and frustration, especially when they have had to chase you or when the business has failed them repeatedly.

Here are some examples:

• A partial refund
• A goodwill voucher
• A service credit
• A delivery upgrade
• A free month of service

To stay consistent, create a remedy banding guide linked to impact:

• Minor inconvenience – waived fee or small credit
• Significant inconvenience – partial refund plus priority fix
• Repeat failure – larger credit plus management review and process fix
• Serious impact – senior owner, urgent fix and proportionate financial remedy

Make sure staff know what they can approve. For example:

• Frontline can approve up to £X.
• Team leaders can approve up to £Y.
• Senior managers approve above £Y or any case involving alleged injury, discrimination, or legal threats.

This avoids delays and the usual “let me check with my manager” loop that frustrates customers.

If you need to refuse what the customer has asked for, be clear and straightforward about it. Explain the reason and offer the closest fair alternative. For example: “I can’t refund the full annual amount because the service has been provided. However, I can refund the unused portion from today and waive the cancellation fee.”

Customers accept refusal more easily when you show you considered their request fairly and properly.

Final response letter template

The final response should leave the customer feeling clear on what you investigated, what you found and what happens next.

It also becomes your audit trail. If the customer escalates, your final response may be reviewed by senior leadership, an alternative dispute resolution (ADR) scheme, an ombudsman, a bank or legal advisers.

A good final response should cover:

• What the customer raised
• What you investigated
• What you found
• What you will do next
• How the customer can escalate if they remain unhappy

Final response template (email or letter)

Hello [Name],

Thank you for your patience while we investigated your complaint (reference [ID]) about [summary].

I’ve reviewed [records/tracking/account notes/conversations] and spoken to the relevant teams to understand what happened.

Our investigation found that [finding]. This happened because [plain-language explanation]. I’m sorry for the inconvenience and frustration this caused.

To put things right, we will [remedy]. We expect this to be completed by [date]. If this involves a payment, it should appear within [timeframe].

We have also [process change/supplier escalation/additional check] to reduce the risk of this happening again.

If you would like us to review any part of this outcome, please reply with any additional information you would like us to consider. If you remain unhappy after our internal review, you can contact [ombudsman/ADR provider/regulator] using the details below.

Kind regards,

[Name]

[Role]

[Contact details]

Internal note for teams

Keep the section about preventing the issue from happening again specific. Customers can usually tell when a response includes vague promises rather than real action.

For example:

• “We have added an extra check before dispatch.”
• “We have updated the script so customers get clearer appointment windows.”
• “We have changed how booking changes are confirmed with our supplier.”

Escalation routes and ombudsman options

Customers should have clear escalation routes if they remain unhappy with the outcome or how the complaint has been handled. Most organisations manage this in layers, starting with frontline resolution and moving to more senior review where needed.

• Layer 1: Frontline resolution – frontline staff aim to resolve the issue quickly within their authority and standard timeframes.
• Layer 2: Supervisor review – a team leader reviews the case and considers whether the outcome and proposed remedy are reasonable. This often resolves complaints where the customer wants a second opinion.
• Layer 3: Senior or specialist review – complex, high-risk or high-value complaints are reviewed by a senior manager, complaints specialist, compliance team or legal adviser, depending on the organisation.
• Layer 4: External escalation – if the customer remains unhappy, they may escalate to an ombudsman, ADR provider, regulator, trade association scheme or court, depending on the sector and complaint type

Because external arrangements vary, maintain an internal directory that staff can search quickly. Common UK examples include:

• Financial Ombudsman Service for many financial services disputes
• Ombudsman Services for some energy and communications disputes
• The Property Ombudsman for many estate agency and property complaints, if the business belongs to the scheme
• Local Government and Social Care Ombudsman for councils and some care services
• Parliamentary and Health Service Ombudsman for many NHS and UK government department complaints, usually after internal routes

Further guidance: Consumer rights, GOV.UK 

Chargebacks and card disputes

If you take card payments, customers may bypass your process and raise a chargeback through their bank. A clear, timely complaints process reduces chargebacks because customers feel they can get a fair outcome directly from you.

Your audit trail can help if you need to challenge an unfair dispute.

Court as a last resort

Some complaints may still end up in the small claims process. Most businesses would rather resolve issues earlier and maintain a good customer relationship. Clear communication, fair outcomes and good records make that much more likely.

Complaint record keeping and GDPR

Complaint records often contain personal or sensitive information, so they need to be accurate, relevant and stored securely.

Follow these practical principles.

Keep records necessary and relevant

Record what you need to investigate and resolve, always avoiding unnecessary personal commentary.

Use a consistent case record

A strong complaint record typically includes:

• Complaint reference number
• Customer details and preferred contact method
• Date received and channel
• Complaint summary and desired outcome
• Severity level and case owner
• Evidence reviewed
• Investigation notes and decision rationale
• Remedy offered and completion date
• Final response issued date
• Escalation details
• Root cause tags and learning actions

Control access

Complaints can include health details, protected characteristics and distressing content, so you should limit access to those who need it.

Store securely

Use secure systems, not personal inboxes, as the long-term archive for complaints. Create a central log, even if you receive complaints via email.

Set retention periods

Only keep complaint records for as long as they are needed for operational, legal or regulatory reasons. Document your logic, and train staff to follow it.

Prepare for subject access requests

Customers can ask for copies of their personal data, including complaint records and internal notes. This underpins the importance of writing records clearly and professionally, avoiding unnecessary comments or personal opinions.

Share data carefully

If you share data with suppliers or ADR bodies, share the minimum necessary, and use secure channels.

Further guidance: UK GDPR guidance and resources, ICO

Complaint trends and root cause analysis

A single complaint can usually be resolved and closed. Repeated complaints about the same issue are a sign that something in the process is not working properly.

Looking at complaint patterns helps you spot where problems are being created, which issues are generating the most avoidable contact, and where changes would have the biggest impact. You do not need a complex system to start. Consistent tagging and regular review are usually enough.

Start with simple categories

Choose categories that reflect your operation:

• Product or service quality
• Delivery or fulfilment
• Billing and payments
• Communication and information
• Staff conduct
• Systems and technology
• Third-party suppliers
• Policy and contract misunderstandings

Then add cause codes within each category. For example, within delivery:

• Late delivery
• Missed delivery
• Damaged item
• Wrong item
• No tracking updates

This makes it easier to spot recurring issues quickly.

Track metrics that drive action

Useful metrics include:

• Complaint volume by category and channel
• Time to first response and time to resolution
• Contacts per complaint (how many times the customer chased)
• Repeat complaints from the same customer
• Escalation rate to managers and external bodies
• Refund and goodwill spend by category
• Complaint rate per 1,000 orders or customers
• Failure demand (contacts created by avoidable issues)

Run a monthly complaints review

Keep it short and practical. Here’s a simple agenda:

• What were the main complaint drivers this month?
• Which issues created the most repeat contact or escalation?
• Which problem cost the most in refunds or staff time?
• What change would reduce the most complaints?
• Who owns the action, and when will it be reviewed?

Use the “5 Whys”

The “5 Whys” approach helps teams move past surface-level explanations. Instead of stopping at “human error”, keep asking why the problem happened until you reach something you can realistically change.

For example:

1. Why was the delivery missed? Because the route update failed.
2. Why did the route update fail? Because the booking change was not confirmed in the system.
3. Why was the booking change not confirmed? Because the process relied on a manual step.
4. Why did the manual step get missed? Because staff were handling multiple systems at once.
5. Why were staff handling multiple systems? Because the booking platform does not sync automatically with dispatch.

By this point, you have identified a process problem that can actually be fixed.

Staff training for complaint handling

A process is only as strong as the people using it. That’s why staff need skills, confidence and permission to act.

Under pressure, even experienced staff can sound defensive or robotic, which frustrates customers. Therefore, training should focus on real behaviours and decision-making, not get sidetracked on policy alone.

Below are training topics that have the biggest impact.

1) Listening and empathy

Teach staff to reflect the customer’s concern without agreeing with them prematurely:

• “I can see why that’s frustrating.”
• “Thank you for explaining. I’m going to look into this.”
• “I’m sorry for the inconvenience. Let’s get this sorted.”

2) De-escalation

Give staff a simple structure:

• Slow down.
• Ask clarifying questions.
• Summarise what you heard.
• Offer the next step and timeline.

Useful lines include:

• “I want to help. Let’s take this step by step.”
• “I’m going to ask a couple of questions so I can resolve this properly.”

3) Clear writing

Teach staff to write short, structured responses that explain the issue, what will happen next and when the customer will hear back. Long explanations often sound defensive, even when the information is accurate.

4) Evidence-led investigation

Train staff to avoid assumptions and confirm facts before deciding outcomes.

5) Remedy authority

Make sure staff know:

• What they can approve
• What needs manager approval
• What triggers immediate escalation

6) Accurate record keeping

Teach staff to write notes that support a defensible audit trail and respect privacy.

7) Vulnerability awareness

Help staff recognise vulnerability and adjust how they communicate, including offering options and extra clarity.

8) Handling aggressive behaviour

Staff need clear guidance on how to handle aggressive or abusive behaviour, including what language to use and when it’s appropriate to end a call or pause contact. This helps people respond consistently in difficult situations and gives staff confidence that they will be supported.

You can reinforce training with practical tools:

• A one-page “first response checklist”
• Approved apology and holding response wording
• A remedy decision tree and authority matrix
• Short role-play scenarios based on real cases
• Weekly coaching using a small sample of complaint cases

Turning complaints into improvements

Complaints offer one of the clearest windows into your customer experience. People rarely complain when everything works, so each and every complaint highlights areas where there is friction, ambiguity or failure in your customer journey, offering you valuable opportunities for improvement.

Focus on three habits.

Habit 1 – make learning visible

Share a short monthly “what we learned” update:

• What the top drivers of complaints were
• One case study with a clear timeline
• What you changed
• What early impact you can see

This helps nurture a strong work culture where teams talk about problems proactively instead of hiding them.

Habit 2 – fix upstream, not just tone

Better apologies help, but prevention saves the most time and money. Upstream is usually the best place to start looking. For instance:

• Can you stop the failure earlier?
• Can you automate proactive updates?
• Can you simplify steps that cause errors?
• Can you improve supplier controls?
• Can you redesign forms, confirmation emails or handover steps?

Habit 3 – close the loop with customers

When you make a meaningful change, tell customers who raised that issue: “Based on feedback like yours, we’ve changed X.” This increases trust and often turns a frustrated customer into a supporter.

Final thoughts

A good complaints process should make life easier for everyone involved. Customers should not have to chase for updates or repeat themselves, and staff should not be left guessing what to do next under pressure.

The details will vary between organisations, but the basics stay the same: respond clearly, investigate properly and fix problems early where you can. Over time, that usually saves far more time and stress than it creates.