FCA vulnerable customer guidance for collections teams

Collections teams often speak with customers at difficult moments.

Someone may have lost income, experienced bereavement, developed a health condition, taken on caring responsibilities, or reached a point where managing everyday financial decisions has become harder. In other cases, a customer may simply need more time, clearer information, or a different way to communicate.

These circumstances affect what appropriate collections treatment looks like.

The FCA expects firms to understand the needs of customers in vulnerable circumstances and provide support that meets those needs. Under Consumer Duty, the FCA’s Consumer Support outcome includes an expectation that firms design and deliver support for retail customers, including customers with characteristics of vulnerability, and monitor whether customers are receiving the support they need.

For collections teams, this means vulnerability can't sit in a policy document or an agent note. When a customer’s circumstances are relevant, the collections process needs to respond.

This article provides general information only and isn’t legal advice. FCA requirements can depend on the firm, product, customer, and facts of a particular case. Firms should review their obligations with qualified legal, compliance, and operational advisors.

What does vulnerability mean in collections?

Vulnerability isn't a fixed label.

A customer may be more likely to experience harm because of personal circumstances, a life event, health, financial resilience, capability, or their ability to engage with the firm. These circumstances can be temporary, long term, or change over time.

In collections, vulnerability may become visible when a customer:

• Explains that they have lost income or are struggling to meet essential costs
• Discloses a health condition, disability, or communication need
• Reports a bereavement, relationship breakdown, or another major life event
• Says they don't understand the information they have received
• Repeatedly misses payments or breaks arrangements
• Asks for more time, a different communication method, or help from a third party
• Is working with a debt adviser, carer, or authorized representative
• Shows signs that the standard collections process isn't working for them

None of these signals automatically tells a firm what the outcome should be. But they may indicate that the account needs a closer look and that the standard workflow may not be appropriate.

What FCA guidance means for collections teams

The FCA’s approach isn't about creating a separate process for every customer.

It's about making sure firms can identify when a customer may need different support, respond appropriately, and monitor whether that support is working.

For collections teams, this usually means having clear answers to a few practical questions:

• How can a customer tell us they need help?
• How do agents record relevant information?
• Who reviews the account when a customer’s circumstances change?
• What happens to planned calls, messages, or escalation activity?
• Can the customer use a different channel or get more time to engage?
• Is there a route to a specialist team, debt adviser, or authorized representative?
• How do we make sure the customer does not have to repeat difficult information?
• How do we know whether the support process is actually helping?

The FCA’s Consumer Support outcome isn't measured by whether a firm has a vulnerability flag in its system. It's about whether customers can access support that meets their needs.

Identify signals without making assumptions

Collections teams need to be ready to recognize relevant signals. They also need to avoid assuming they know what a customer needs based on limited information.

The best starting point is usually the conversation itself.

A customer may tell an agent they're dealing with a health issue, a change in income, bereavement, caring responsibilities, or another event affecting their ability to pay or communicate. They may ask for more time, explain that they don't understand their options, or ask to deal with the account through someone else.

Other signals may come from the account history, such as repeated missed payments, broken arrangements, or a pattern of contact suggesting the customer is struggling to engage.

These signals should prompt an appropriate review. They shouldn't be treated as an automatic diagnosis or a reason to make assumptions about the customer.

Teams need clear guidance on:

• What information to record
• How to record it sensitively and proportionately
• When to seek more information
• When to escalate the case
• What support routes are available
• How to protect customer privacy

Turn information into appropriate support

Recording a vulnerability disclosure is only the first step.

The important question is what changes after the information is recorded.

Depending on the customer’s circumstances, firm policy, and the account, appropriate support may include:

• Giving the customer more time to consider their options
• Adjusting the communication channel, format, pace, or timing
• Routing the account to a specialist or trained support team
• Pausing or reviewing standard collections activity
• Providing clearer explanations of the balance, options, or next steps
• Working with an authorized representative or debt adviser
• Reviewing whether an existing payment arrangement is still appropriate
• Making a reasonable adjustment to support the customer’s access to the process
• Recording the outcome and setting a clear review point

The right response will not be the same for every customer. A short term change in circumstances may need a different approach from a complex, long term support need.

What matters is that the process gives teams a way to respond with care and consistency, rather than leaving the outcome to chance.

Make sure the workflow changes

A customer shouldn't have to repeat difficult information every time they make contact.

If a customer has disclosed a relevant circumstance, the people handling the account need to see enough information to provide appropriate support. Future communications and workflow steps may also need to change.

This can include:

• Suppressing a planned communication while the account is reviewed
• Routing the account to a different queue
• Making relevant agent guidance available at the next interaction
• Updating the customer’s communication preference or support needs
• Creating a task for a specialist team
• Setting a review date for a payment arrangement or support plan
• Making sure authorized teams and relevant third parties receive the necessary information

This doesn't mean every employee should see every detail about a customer’s personal circumstances. Access should be appropriate to the person’s role and the support they need to provide.

The goal is to keep relevant context connected to the next action without compromising privacy or dignity.

Communications should support, not add pressure

The language, timing, and channel of a collections communication can make a real difference.

A standard reminder may be appropriate for one customer. It may be unhelpful or confusing for another customer who's already disclosed financial difficulty, asked for help, or agreed to a different arrangement.

Collections communications should help customers understand:

• What the message relates to
• What they need to do next
• What options may be available
• How to ask a question or get support
• How to raise a dispute or explain a change in circumstances
• Where to find independent help, where appropriate

They shouldn't create unnecessary pressure, assume that every customer can respond in the same way, or ignore information the firm already holds.

For more on this topic, read Consumer Duty and collections communications.

Monitor outcomes, not just activity

It's easy to count how many accounts were flagged, how many cases were sent to a specialist team, or how many agents completed training.

Those measures are useful. They don't tell the whole story.

Firms also need to consider what happened to the customer after they asked for help.

Useful questions include:

• Did the customer reach the right support route?
• Did they need to repeat their circumstances?
• Did standard communications continue when they should have been reviewed?
• Did the customer understand the options available?
• Was a payment arrangement or support plan reviewed at the right time?
• Are complaints or repeat contacts showing a problem with the process?
• Are some customer groups finding it harder to access support?
• Are third party agencies identifying and handling vulnerable customers appropriately?

The FCA expects firms to monitor whether customers are receiving the support they need. This requires more than a dashboard. Teams need to look at the evidence, identify patterns, and change the process when it isn't working.

Train people and oversee partners

Technology can help teams record information, route work, and keep account history connected. But a collections process still depends on people.

Agents need the confidence to have sensitive conversations, recognize when a customer may need help, and know when to escalate. Managers need to review quality and support their teams. Third party agencies need to work to the same standards as internal teams.

A practical approach includes:

• Clear training on vulnerability and support processes
• Simple, usable guidance for frontline teams
• Defined escalation routes
• Specialist support where needed
• Quality assurance that looks at customer outcomes, not just call handling
• Clear expectations for third party agencies
• Regular review of complaints, repeat contacts, and exceptions
• Feedback loops that improve scripts, workflows, and support routes

The aim isn't to turn every collection call into a specialist assessment. It's to make sure teams know what to do when a customer needs more support than the standard process can provide.

Vulnerability support is part of fair treatment

Treating vulnerable customers fairly isn't separate from the rest of collections.

It affects communications, payment discussions, escalation, complaints, data handling, and third party oversight. It also connects directly to Consumer Duty, FCA conduct expectations, and the overall customer experience.

A strong process gives customers a clear way to ask for help. It gives teams the information and authority to respond. And it helps the firm learn from the outcomes, rather than assuming that a policy on paper is enough.

For a broader view of FCA collections conduct, read FCA debt collection rules and fair treatment. For an overview of Consumer Duty in collections, read Consumer Duty in collections and recovery.

Ready to turn compliance into a competitive advantage?

Treating vulnerable customers fairly and supporting them thoroughly is a business imperative in the UK and beyond. With the FCA moving from principles to proactive enforcement, collections teams need more than good intentions. Real time insights, personalized strategies, and clear, provable outcomes are what make a real difference.

That’s exactly what FitLogic and Debt Manager were built for.

Debt Manager is the industry’s leading system for end-to-end collections and recovery, trusted globally for its power, flexibility, and ability to adapt quickly to changing regulations. Paired with FitLogic, our advanced decisioning solution, you gain real-time decision automation, seamless segmentation, and the ability to respond to customer needs with precision and care.

If you're navigating the demands of Consumer Duty or anticipating similar regulatory shifts in other regions, now’s the time to invest in technology that’s already built for it. Contact us at inquiries@crsoftware.com to find out more.