FCA complaint reporting is changing — here’s what small UK businesses can copy to reduce escalation

Practical takeaway: you don’t need to be FCA-regulated to benefit from FCA-style complaint discipline. Clear categories, consistent language, and a simple record can make complaints easier to handle and less likely to escalate.

Why this matters (even if you’re not a regulated firm)

In December 2025, the Financial Conduct Authority (FCA) published PS25/19: Improving the Complaints Reporting process. The policy statement is aimed at financial services firms, but the themes are universal: better comparability of data, clearer definitions, less duplication, and more consistent reporting.

For small UK businesses, complaints can feel like one-off fires to put out. The FCA’s direction is a reminder that complaints are also information—and the way you record and respond to them influences what happens next: whether the customer feels heard, whether your team stays consistent, and whether you can spot patterns before they become expensive.

This article translates the FCA’s changes into a lightweight approach: clear categories, a steady acknowledgement, realistic timelines, and a simple record.

Note: This is general information and operational good practice, not legal advice.

What the FCA is changing (plain English summary)

The FCA’s PS25/19 describes changes intended to make complaints data more useful and more comparable, while reducing unnecessary burden where possible. Key themes include:

A single consolidated complaints return replacing multiple existing returns, aiming for consistency and less duplication.
Permission-based reporting so firms only complete sections relevant to their regulated activities.
A simpler “nil return” option for firms with no complaints to report.
Removal of group reporting in favour of reporting at individual legal entity level for clearer oversight.
An updated complaints taxonomy to improve categorisation and understanding.
More explicit treatment of vulnerability (with reference to the FCA’s four drivers: health, life events, resilience, capability) when recording complaint data.

You’ll notice a pattern: consistent definitions + consistent categorisation + consistent reporting. That’s not just a regulatory concern; it’s how you reduce confusion in customer-facing communication.

Five lessons small UK businesses can borrow immediately

1) Build a complaint taxonomy (a simple list of “what kind of issue is this?”)

The FCA’s updated taxonomy is about making complaint types comparable across firms. Your version doesn’t need to be complex. The goal is to help your team categorise issues the same way every time, so you can:

route the complaint to the right person faster,
use the right tone and wording consistently,
spot repeat causes (and prevent future complaints),
avoid arguing about definitions mid-way through a stressful exchange.

Start with 8–12 categories max, then refine quarterly. Example categories for a small business might include: delivery/timing, quality/fit for purpose, billing/refund, communication, staff conduct, website/booking issues, accessibility, data/privacy queries, and “other (needs review)”.

2) Keep records like you’ll need to explain your thinking later

One reason regulators want clearer reporting is so decisions can be understood and compared. For you, a basic complaint record keeps everyone aligned and reduces “he said / she said” spirals.

A good record is not a novel. It’s a short timeline: what happened, what the customer says happened, what you checked, what you offered, and what you told them next. If you ever need to hand over to a colleague (or respond to a follow-up), you’ll be glad it’s there.

3) Acknowledge promptly, but don’t overpromise

Customers often escalate when they feel ignored or when expectations are vague. A short acknowledgement message does two things: it signals you’re taking it seriously, and it sets the next step.

The key is to confirm what you understand the issue to be, what information you will review, and when they’ll hear from you—without promising an outcome.

4) Use consistent language (definitions matter)

The FCA is improving guidance and definitions because inconsistent interpretation creates messy data. In customer complaints, inconsistent wording creates something worse: inconsistent experiences.

Pick a few standard phrases your team can rely on (for acknowledgement, requesting evidence, explaining timelines, confirming next steps). This reduces accidental admissions, avoids conflicting messages, and lowers emotional temperature.

5) Treat vulnerability as a practical lens, not a label

The FCA’s approach to vulnerability is detailed: firms should have regard to guidance and record relevant data points. Small businesses don’t need to mirror that reporting structure, but you can adopt the mindset: some customers have circumstances that make complaint handling harder—stress, health, life events, limited time, or reduced ability to navigate complex processes.

Practically, this means offering clear options, avoiding jargon, and confirming what will happen next in plain English. It also means keeping your process flexible enough to reduce friction (for example, accepting a phone summary followed by an email confirmation if that helps the customer).

A simple 7-step complaint process you can run with a small team

This is designed for busy teams. It borrows the FCA’s emphasis on clarity, consistency, and records, without adding unnecessary admin.

Step 1: Capture the complaint in a single place

Decide where complaints “live” (a shared inbox, a CRM, a spreadsheet, or a ticket system). What matters is one source of truth. Record:

customer name and contact details
date received and channel (email, phone, in person)
order/booking reference
a one-sentence summary in the customer’s words

Step 2: Categorise using your complaint taxonomy

Select one primary category (and an optional secondary category). If you can’t confidently categorise it, use “other” but add a note explaining why—this will guide improvements to your taxonomy later.

Step 3: Acknowledge receipt and set expectations

Send a short acknowledgement that confirms you’ve received the complaint, summarises the issue, and gives a clear timeline for the next update.

Sample acknowledgement email (short and calm)

Subject: Thanks for your message — complaint received

Hi [Name],

Thank you for getting in touch. I’m sorry to hear about the issue with [brief description].

I’ve logged your complaint under reference [REF]. I’m now reviewing [what you’ll check: order details / messages / delivery tracking / staff notes].

You’ll receive an update from me by [day, date]. If you have any additional information (for example photos, screenshots, or dates/times), please reply to this email and I’ll add it to the record.

Kind regards,
[Name]
[Role]
[Business name]
[Contact details]

Step 4: Check the facts and build a short timeline

Pull together what you can verify: receipts, tracking, internal notes, policies you shared at the point of sale, and prior messages. Write a brief timeline with timestamps where possible. This helps you communicate clearly and prevents “moving target” explanations.

Step 5: Decide your position and options

Separately from writing the customer response, decide internally:

what happened (as you understand it),
what you can offer (if anything),
what you cannot offer (and why),
what decision-maker approval is needed.

Keeping this step explicit avoids inconsistent outcomes depending on who replies.

Step 6: Respond with consistent language and a clear next step

Aim for: empathy, clarity, brevity, and structure. A helpful pattern is:

What we understand (one paragraph)
What we checked (bullet points)
Our outcome / options (plain English)
Next step (what the customer can do, and when you’ll respond)

Step 7: Close, learn, and improve the taxonomy

When the complaint is closed, record the closure date and outcome type (for example: explanation provided, goodwill gesture, partial refund, refund, replacement, policy exception, declined). Then do a short monthly review:

Top 3 complaint categories
Top 3 root causes (process, product, communication)
One change to reduce repeat issues

Common pitfalls that lead to escalation (and what to do instead)

Most escalations aren’t caused by a single “wrong” sentence. They happen when the customer experiences uncertainty, inconsistency, or silence. These four pitfalls cover the majority of avoidable problems:

Pitfall 1: Minimising the experience

If a customer senses you’re dismissing them, they’ll often repeat themselves louder—or take the conversation elsewhere. Acknowledge the impact and confirm the next step.

Pitfall 2: Vague timelines

“We’ll look into it” creates uncertainty. Give a specific update date, even if that update is simply progress and what you still need.

Pitfall 3: Inconsistent language across the team

When one person calls it a “refund request” and another calls it a “warranty issue”, the customer hears confusion. Use your taxonomy and keep standard phrasing for key moments: acknowledgement, evidence request, decision, and closure.

Pitfall 4: Apologising in a way that sounds like a conclusion

You can apologise for the customer’s experience without making factual claims you haven’t checked. Keep empathy separate from conclusions: “I’m sorry this has been frustrating” is different from “We failed to do X”.

Where ReplyRight fits: templates and checklists for consistency

The FCA is moving toward clearer definitions and more consistent reporting. For a small business, the equivalent is having a consistent set of words and a consistent set of fields to record.

ReplyRight can help you maintain that consistency through practical templates and checklists—so your team doesn’t have to reinvent the structure of a good response each time. For example:

Acknowledgement template (receipt + reference + what you’ll review + next update date)
Information request template (what you need, why you need it, how to send it)
Decision template (what you checked, outcome, options, next step)
Complaint log checklist (minimum fields so records stay usable)
Taxonomy starter list (a simple set of categories you can adapt)

The aim isn’t to sound scripted; it’s to sound steady. Consistency reduces misunderstandings, helps customers know what to expect, and supports better internal decision-making.

Bottom line: fewer surprises, fewer escalations

The FCA’s PS25/19 is about improving the usefulness and comparability of complaints information. For small businesses, the same idea applies: when you categorise complaints clearly, keep a simple record, acknowledge promptly, and use consistent language, you reduce uncertainty.

Disclaimer: This article is for general information only and does not constitute legal, regulatory, or professional advice.