Risk · R-117 · Conduct & Customer Outcomes
Failure to recognise vulnerable customers
An automated interaction does not detect or respond to signs of vulnerability that a trained person would notice and act on.
- Severity
- High
- Audience
- Heads-of · Practitioner
- Frameworks
- Section 20 · PRIN 2A.2 · PRIN 2A.6
- Responsible AI domain
- Lifecycle stage
- Reviewed
- 2026-11-11
What it is
A customer in vulnerable circumstances is one who, because of health, a life event, low resilience or limited capability, is especially open to harm when an organisation does not take appropriate care. Trained staff pick up the signs: a mention of bereavement, confusion, distress, a third party prompting answers. They slow down, check understanding and change what they offer. An automated channel that has not been designed for this continues with its script. The risk concerns failure to notice and adapt. Deliberate targeting of vulnerability is a prohibited practice, covered in exploitation of vulnerable groups by AI.
How it happens
- The system was built to complete transactions and has no concept of vulnerability.
- Disclosures made in free text are not recognised or recorded.
- A flag on the customer's record is not passed to the AI channel.
- Detection exists, and nothing different happens when it fires.
Why it matters
Harm to vulnerable customers is the harm conduct regulators treat most seriously. A sale completed, a debt pursued or a claim closed with someone who did not understand can be unfair even if every step was correct in form.
Warning signs
- The design documents do not mention vulnerability.
- Conversations containing clear disclosures end with no referral.
- Outcomes for customers flagged as vulnerable are not reported separately.
- Staff say they would have handled a case differently.
Who owns it
The business owner of the journey is accountable. The vulnerability lead sets the standard. Engineering builds detection and referral. Operations receive those referred.
In practice
A customer tells a collections chatbot that their husband has just died and they cannot think about money. The bot acknowledges the message and repeats the payment options. The same pattern generalises to any automated channel that hears what a customer says only as input to its own task.
Mitigating controls
Primary controls
- Escalation to a human Preventive
- Gives the customer a route to a person. Automated channels offer a prompt, unobstructed route to a person, available on request and triggered automatically by defined signals, with the conversation handed over.
- Vulnerable customer safeguards Preventive
- Detects indicators of vulnerability and routes the customer to support. Automated journeys detect indicators of vulnerability, adapt what they do, and route the customer to appropriate human support, with the disclosure recorded.
Supporting controls
- Customer outcome monitoring Detective
- Shows whether vulnerable customers fare worse. The outcomes customers receive from AI-driven journeys are measured, broken down by customer group and compared with other channels, and poor outcomes are investigated and acted on.
- Evaluation suite and regression testing Detective
- Tests detection against realistic conversations. A maintained set of test cases with expected results is run on every change to model, prompt, data or tools, and the results are compared with the approved baseline.
Framework and clause references
| Framework | Clause | Title |
|---|---|---|
| Equality Act 2010 | Section 20 | Duty to make adjustments Adjustments for disabled customers. |
| FCA Consumer Duty (PRIN 2A) | PRIN 2A.2 | Cross-cutting obligations Foreseeable harm to customers with vulnerability. |
| FCA Consumer Duty (PRIN 2A) | PRIN 2A.6 | Consumer support outcome Support that meets customers' needs. |
Related terms
How to cite
Axiom Verity (2026). Failure to recognise vulnerable customers. Reference Library, R-117. https://axiom-verity.com/risks/failure-to-recognise-vulnerable-customers. Reviewed 2026-11-11.
Found an error or a better source? Report a correction.