Consumer Duty complaints emails: a practical acknowledgement & next-steps flow (with less escalation)

Audience: UK firms handling customer complaints and support, especially where a regulator might reasonably expect you to know what you’re doing.

The FCA’s Consumer Duty implementation: good practice and areas for improvement is (quietly) a communications document. Yes, it talks about governance, vulnerable customers, products, value, understanding, and support. But the bit your customers experience is the bit you write.

This post turns “good practice” into a straightforward complaint email flow you can actually run: acknowledgement, next steps, evidence, updates, and decision—without overpromising or sounding like you’re hiding behind policy.

Disclaimer: This is general guidance and not legal advice. Always align to your own policies, the FCA rules and guidance relevant to your sector, and any ombudsman expectations.

Why escalation often starts with your first email

Most escalations don’t begin with the substantive issue. They begin with uncertainty: “Do they understand what I’m saying?”, “Is anyone accountable?”, “How long will this take?”, “Do I need to chase?”, “Are they going to ask me for the same thing three times?”

Under the Consumer Duty, firms should act to deliver good outcomes and address issues that risk causing harm. In complaints land, that translates to predictable, accessible support; communications customers can understand; and processes that are governed and monitored rather than left to chance.

Your acknowledgement is the moment to reduce uncertainty. Not with grand promises—just with clarity.

The email flow (ReplyRight): five messages that do the heavy lifting

ReplyRight is a simple way to structure complaint communications so they’re consistent, fair, and easy to audit. Think of it as a sequence, not a single “perfect” email.

Acknowledge (same day where possible): confirm receipt, summarise the issue, give ownership, give the next update point.
Clarify (if needed): request evidence once, explain why, offer alternatives, and set a reply date.
Update (on schedule): even if there’s no new outcome, keep the promise you made about the next touchpoint.
Decision: explain what you found, what you will do next, and how to challenge or escalate.
Aftercare: short check-in, learning loop, and (internally) theme capture for monitoring.

The FCA’s publication stresses monitoring and continuous improvement. A consistent email flow makes that realistic: you can measure timeliness, clarity, vulnerability flags, and repeat contact.

Message 1: Acknowledgement that actually acknowledges

A good acknowledgement is not “we’ve logged your complaint”. It’s a mini-brief that makes the customer feel heard and tells them what happens next.

Include these seven elements

Human receipt: confirm you’ve received it, with date/time and reference.
Your summary: one or two lines describing what you believe the complaint is about.
Ownership: a named person or team, and how to contact them.
Timeline in plain English: what happens by when (use dates or business days).
What you need next: only if required; avoid shopping lists.
Support needs: invite disclosure of accessibility or vulnerability needs without prying.
Escalation/signposting basics: what formal complaint process you’re using and what the next formal stage is (aligned to your sector’s rules).

Example snippet: acknowledgement paragraph (realistic, not robotic)

Thanks for getting in touch on 23 February. I’m sorry to hear about the issues you’ve had with the refund and the follow-up calls. To check I’ve understood: you’re saying the refund was applied to the wrong account, and you’ve since had conflicting updates from our support team. I’ll be your point of contact and I’ll review the account notes, call recordings and payment trail. I’ll send you an update by Thursday 26 February, and if we need anything from you I’ll explain exactly what and why.

Notice what’s not there: sweeping promises. Customers don’t need theatre; they need a calendar.

Message 2: Asking for evidence without making the customer do your job

Many “areas for improvement” in Consumer Duty boil down to friction: customers being bounced between channels, repeating themselves, or being asked for documents that don’t seem relevant. Evidence requests are often where that friction peaks.

Good practice for evidence requests

Ask once, ask well: explain the specific decision you’re trying to make and what the document helps you confirm.
Offer alternatives: if someone can’t upload a file, offer post, branch, secure message, or a call-back to capture details.
Be proportionate: request the minimum needed. “Everything you have” is convenient for you, not fair to the customer.
Set a reply date and a plan B: what happens if they can’t respond by then (especially for vulnerable customers).
Protect data: remind customers not to send unnecessary sensitive information, and direct them to the right channel.

Example snippet: follow-up requesting information

To confirm the payment route, could you send either (a) a screenshot of the transaction showing the date, amount and last 4 digits of the destination account, or (b) the bank statement line with those details. If sharing a screenshot is difficult, we can take the details by phone instead. If you can send this by Monday 1 March, we’ll be able to keep to the update date we agreed. If that timing doesn’t work for you, tell me what does and we’ll plan around it.

Message 3: The scheduled update (the underrated escalation blocker)

“No update” reads as “no progress”, even when your team is working flat out. A scheduled update is a small operational commitment with a big trust impact.

Your update email can be short. It just needs to do three things:

Confirm what you’ve done: e.g., reviewed call recordings, checked system notes, contacted a third party.
Confirm what’s next: the remaining checks and who owns them.
Confirm the next touchpoint: the next update date (even if it’s “by end of day Friday”).

If you can’t meet a previously stated date, say so early, explain why in plain English, and propose the new date. Customers can cope with delay; they struggle with silence.

Message 4: The decision email — clear, fair, and readable

Consumer Duty emphasises consumer understanding. Complaint outcomes often fail not because the decision is unreasonable, but because the explanation is written like a policy manual had a bad day.

A simple structure that works

Outcome up front: what you’ve decided (accepted in full/part/not accepted) using plain language.
What you looked at: bullet list of evidence sources and dates.
What happened (your finding): a short timeline in customer-friendly terms.
What happens next: actions you will take and actions the customer needs to take (if any), with timeframes.
How to challenge: internal escalation route and any external signposting appropriate to your regime.

Keep jargon for the footnotes. If you must reference rules, do it sparingly and link to them. A customer should be able to understand the decision without opening six PDFs.

Message 5: Aftercare and the internal learning loop

The FCA’s publication points firms to culture, governance and monitoring. Complaints are one of the best “live feeds” you have for where customers are experiencing harm, confusion, or friction.

Aftercare can be a short note: “If anything in our explanation wasn’t clear, tell us.” It’s also internal: capture the theme (fees, delays, product complexity, channel friction), and record whether vulnerability considerations affected the approach.

If your monitoring shows repeat complaints about the same journey step, that’s a Consumer Duty signal. Your emails won’t compensate for a broken process forever—but they will buy you time and reduce unnecessary escalation while you improve.

Vulnerability: make it easier to say “I need help”

The FCA highlights consumers in vulnerable circumstances as a core focus. In complaints communications, good practice is less about labelling and more about options.

Practical adjustments you can offer in every flow

Alternative formats (large print, audio, plain-English summary).
Choice of channel (email, phone, post) and time of day for calls.
Third-party support (permission to speak to a trusted person).
More time to provide documents where reasonable, without penalty language.
Clear signposting to free support services where relevant (sector-dependent).

Include one gentle line in the acknowledgement: “If there’s anything we can do to make this easier—such as a different format or extra time—please let us know.” It’s a small sentence with a big compliance footprint.

Avoiding the five classic overpromises

Overpromising drives escalation because customers remember your promise, not your intent. Here are five common traps and safer alternatives.

Trap: “We’ll get back to you shortly.” Better: “I’ll email you by Wednesday 4pm.”
Trap: “We’ve escalated this.” Better: “I’ve asked our Payments Team to confirm the transfer reference; I’ll update you by Friday.”
Trap: “This is urgent.” Better: “I understand the impact. Here’s what we can do today, and what needs more checks.”
Trap: “We can’t do that.” Better: “We’re not able to do X because of Y. We can do A or B. Which suits you?”
Trap: “It’s with our back office.” Better: “It’s with [team name]. I’m still accountable for updates.”

Operationalising it: a one-page checklist for your complaints mailbox

You don’t need a perfect rewrite of every template. Start with a checklist your team can use today.

Acknowledgement checklist (copy into your CRM notes)

Did we restate the issue in one sentence?
Did we give one owner and one contact route?
Did we give the next update date (not a vague promise)?
Did we ask only for necessary evidence, with alternatives?
Did we include a vulnerability/support line?
Did we set expectations about what we will review (notes, calls, letters)?
Did we avoid defensive language and policy wall-text?

Over time, you can add monitoring: average time to first acknowledgement, missed update commitments, repeat contact before decision, and the percentage of cases where the customer says “you didn’t understand my complaint” (a brutally honest KPI).

Closing thought

The FCA’s Consumer Duty good practice is not an abstract principle. It’s visible in the everyday moments where a customer asks for help and you answer. A calm acknowledgement, a sensible evidence request, and a predictable update rhythm won’t make every complaint painless—but it will reduce avoidable friction and lower the odds of escalation driven by uncertainty.

If you want a simple starting point, use the ReplyRight flow above as your internal standard: acknowledge, clarify, update, decide, aftercare. Then measure it.

Not legal advice.