Friday, August 22, 2025
A practical guide for complaint case handlers. Dealing with vulnerable customers
In this article, we're going to discuss:
Introduction
If you’ve worked in complaints for more than a week, you know that no two customers are the same, and some need more than the standard process to get to a fair outcome.
This guide is written for complaint case handlers and frontline teams managing real cases day-to-day.
Vulnerability isn’t rare. It’s part of complaint handling, and the responsibility sits with you, not the customer, to identify whether additional support is needed.
A vulnerable customer is someone who, due to their personal circumstances, is especially susceptible to harm, particularly when a firm is not acting with appropriate levels of care. (FCA)
This can relate to a long-term illness, sudden bereavement, fluctuating mental health, or even retirement. The point is that you will not always be told. Often, it’s down to you, as the person speaking to the customer, to spot the signs, record them accurately, and adapt how you handle the case.
Under the FCA’s Consumer Duty, your actions need to result in outcomes for vulnerable customers that are as good as those for everyone else.
🎗️ Some customers may object to being labelled as ‘vulnerable’, and we've found that phrases such as ‘requiring additional support’ are much more appreciated.
How can complaint handlers recognise vulnerable customers in real cases?
Complaint handlers can often spot support needs by listening carefully to what the customer says, how they communicate, what they struggle to understand, or any change in tone, urgency or circumstances.
The FCA describes four drivers of vulnerability and some of the characteristics that may sit under each one:
Health: includes physical disability, severe or long-term illness, mental health condition, addiction, or low mental capacity.
Life events: includes bereavement, relationship breakdown, domestic abuse, caring responsibilities, and migration.
Resilience: includes low emotional resilience, erratic income, and over-indebtedness.
Capability: includes low knowledge of managing finances, poor literacy or numeracy skills, and poor English language skills.
Some cases are obvious. A customer may tell you they’ve been diagnosed with a long-term illness, or you may hear that English isn't their first language. But many cases need to be identified through active listening.
Examples:
A customer struggling to keep track of what you’ve said may be experiencing cognitive difficulties
Someone who avoids phone calls might have anxiety or hearing impairments
A change in tone or urgency could indicate sudden life changes such as job loss, caring responsibilities, or another major life event
💡 Tip: Don’t automatically dismiss an unpleasant or unusually mannered customer. If something doesn't seem right, there may be more going on. If you’re unsure, flag it for review with your team leader.
What are the 4 R’s for supporting vulnerable customers in complaint handling?
The 4 R’s for supporting vulnerable customers in complaint handling are Recognise, Record, Respond and Review. They give handlers a simple structure for spotting support needs, recording them clearly, making proportionate adjustments and checking whether those adjustments remain appropriate.
Recognise: Identify vulnerability markers through active listening, questioning, and observation.
Record: Capture details clearly in the system so that the customer doesn’t have to repeat their circumstances to multiple people.
Respond: Make reasonable, proportionate adjustments that meet the customer’s needs without causing unnecessary delay.
Review: Reassess regularly, especially for transient or intermittent vulnerabilities, to make sure adjustments remain appropriate.
Following the 4 R’s will help you act consistently, build an evidence trail, and support good outcomes, no matter who picks up the case next.
What complaint management software helps teams manage vulnerability, customer updates and evidence trails?
Complaint management software built for regulated complaint handling, such as Complyr, helps teams manage vulnerability, customer updates and evidence trails by keeping support needs, case notes, communication, evidence and actions connected to the complaint record.
For vulnerable customers, this is especially important because the customer shouldn’t have to repeat sensitive information every time they speak to someone new. The record should help the team understand the customer’s needs, communicate in the right way and review whether the support offered is still appropriate.
The right system should help complaint teams:
record vulnerability indicators and support needs clearly
keep customer updates, evidence and actions attached to the case
set review points where support needs may change
make agreed adjustments visible to the people handling the complaint
keep a clear audit trail of what was offered, agreed and done
support consistent handovers if the case moves between handlers or teams
Configurable workflows can also help teams build vulnerability prompts, review points and agreed adjustments into the complaint process, so support needs are less likely to be missed when cases move between handlers or teams.
The software doesn’t replace judgement, empathy or good conversations. It helps make sure the important details are captured, visible and acted on throughout the complaint journey.
Which vulnerability frameworks help complaint handlers support customers consistently?
Frameworks and conversation techniques such as TEXAS, IDEA, BRUCE, TED and The Listening Wheel can help complaint handlers support customers more consistently by giving structure to difficult conversations, disclosures, capacity concerns and communication needs.
Frameworks aren’t just for training courses. They’re a safety net for when you’re working under pressure. Here are some useful frameworks and techniques used across vulnerability guidance and complaint handling practice:
TEXAS: Thank, Explain, eXplicit consent, Ask, Signpost: used to manage disclosure and record details lawfully.
IDEA: Identify, Design, Evaluate, Adjust: works well with the FCA's MALD (monitor, analyse, learn and develop) strategy to build an organisation-wide approach.
Another approach referenced across UK vulnerability guidance and good practice is BRUCE.
BRUCE: Behaviour, Remembering, Understanding, Communicating, Evaluation: useful when you need to assess capacity and resilience.
Other practical conversation techniques can also help complaint case handlers identify vulnerability more effectively in live conversations.
TED: Tell, Explain, Describe: helps customers speak in their own words, giving you a clearer picture of what they are experiencing without leading them towards a yes or no answer.
Silence also matters and shouldn’t be seen as an awkward part of the conversation. Some customers need extra time to process information, remember details, or feel comfortable enough to explain what’s really going on. A short pause can give them the space they need, and will often help you more than rushing to get the answer to the next question.
The Listening Wheel: helps you listen for more than the headline issue, including emotional cues, what may be left unsaid, and whether the customer may need communication or process adjustments.
For a fuller explanation of The Listening Wheel, Samaritans provides a short handout on practical listening techniques, including open questions, summarising, reflecting, clarifying, encouragement, and reacting.
When your system prompts you to run through TEXAS or BRUCE, follow it step by step. Use TED questions, active listening, and short pauses to give the customer space to explain what they need. These checks help you record and respond consistently, and show clearly why the support offered was appropriate when the case is reviewed later.
How can complaint handlers make reasonable adjustments without delaying the complaint?
Complaint handlers can make reasonable adjustments without delaying the complaint by making small, proportionate changes that help the customer engage with the process. Once vulnerability has been identified, the aim is to act quickly and thoughtfully, not to make the complaint slower or more complicated.
This may mean offering a different communication channel, using plain language instead of technical terms, or breaking the next steps into manageable parts. In some cases, it may help to provide a short written summary after a phone call, offer information in a more accessible format, or arrange support from a trusted third party where appropriate.
Where customers or trusted third parties need to share updates or documents, a secure case portal can help keep communication and evidence connected to the complaint record, rather than spread across separate inbox threads.
It’s also worth checking understanding before moving on. Asking the customer to explain the next step in their own words can highlight where something is still unclear and give you the chance to put it right early. These are often small adjustments, but they can make the complaints process feel far more manageable for someone who’s already under pressure.
Record these adjustments clearly, along with any review or expiry dates if the need for additional support may be temporary.
Why is evidence important when supporting vulnerable customers in complaints?
Evidence is important when supporting vulnerable customers because it shows what the handler identified, what the customer disclosed, what adjustments were offered and why those adjustments were appropriate. Without clear notes, the case can be much harder to evidence later.
The Financial Ombudsman Service (FOS) often looks closely at the quality of reasoning, records and evidence. A written summary after the event isn’t enough if the case file doesn’t show what happened at the time.
This is why your notes, emails and decisions need to show the:
the vulnerability markers you identified
the adjustments you made
why the adjustments were proportionate
whether any review or follow-up was needed
If you want to see how this evidence fits into a firm’s systems, data, and compliance controls, read Embedding vulnerability in complaint handling. It gives a bigger picture of how these individual actions will help your firm meet compliance and governance objectives.
What can complaint teams learn from real vulnerability cases?
Real vulnerability cases show complaint teams why it’s important to spot support needs early, record what was considered and act when there are signs of potential harm.
For example, in a case study shared by the FOS, a consumer complained that their bank acted irresponsibly after they made a high volume of gambling transactions. The ombudsman found that the bank had not identified or acted on clear signs of potential vulnerability and financial harm and upheld the complaint.
Missing vulnerability indicators can directly affect the customer’s wellbeing and the quality of the complaint outcome.
Handling vulnerability well isn’t about doing more work; it’s about supporting your customers and following the right steps, every time. Recognise. Record. Respond. Review. This is how you protect your customer, your decision-making, and your firm’s regulatory risk.
How can teams identify root causes of vulnerability issues in complaints?
Where the same vulnerability issues keep showing up in complaints, using the Fishbone diagram and 5 Whys can help teams identify root causes and reduce repeat harm.
This helps teams move beyond the individual case and ask whether repeat vulnerability issues are being caused by unclear communication, poor handovers, inaccessible processes, weak staff prompts or gaps in how support needs are recorded.
Frequently asked questions about supporting vulnerable customers in complaint handling
These FAQs cover common questions complaint case handlers ask when managing complaints involving customers who may need additional support in FCA-regulated firms.