WorkflowBranch, Cash & Contact Center

Vulnerable Customer Support

Vulnerable customer support that asks the customer first, records the need in their own words and follows it on every channel

Support needs recorded once, with consent, and followed on every channel.

See one case, screen by screen ↓
demo5channelschanged at once when the colleague saves Mrs Hollis's need, each marked “Updated 11:05”
demo61missesfound in 412,600 letters, calls, fees, sales and collections contacts checked against needs in 30 days; 54 put right
target100%of recorded needs carry the customer's consent, the date and who recorded it
target< 1%of customers have to tell the bank a need twice within 90 days, from 3.1% on the sample data
In short

What is Vulnerable Customer Support?

Vulnerable Customer Support is software for bank colleagues to spot customers who need extra care, record their support needs with consent and adapt service on every channel. Seven agents listen on the call, draft the need in the customer's own words, follow it through letters, fees, sales and collections, route specialist referrals and compare outcomes for customers with needs against everyone else. Colleagues ask and record, specialists check, and the Consumer Duty Manager signs.

AI use cases in banking: a buyer's guide to agentic AI for bank and credit union operations →

Updated

The problem

Why a customer in vulnerable circumstances has to say it twice

Vulnerable customer support starts on an ordinary call. A customer rings about a payment and mentions that her husband died last month, that she wears a hearing aid, or that she is struggling. Under the FCA's FG21/1 guidance and the Consumer Duty, the bank is expected to notice, ask, record the need with her agreement and serve her accordingly on every channel. On a busy call the sign passes, and needs typed into free-text branch notes are never read by the contact center.

Then the rest of the bank carries on as if nothing had been said: an 11 pt statement to a customer who asked for large print, a credit card upgrade call to someone who asked for no sales calls, overdraft charges caused by a payment for a person who has died. The FCA's April 2025 review of retail banks found staff who did not acknowledge customers who were noticeably distressed, and recorded needs that were not consistently used. Boards see service levels, not whether customers with needs fared as well as everyone else.

typical42%of customers in vulnerable circumstances had told their firm about their circumstances
typical44 vs 33%reported a negative experience: customers in vulnerable circumstances against everyone else
demo212customersbereaved, on the sample data, paid £7,480 of overdraft interest in one quarter after the bank knew
Where the minutes go on one disclosureestimated
By hand69 minutes
With the solution9 minutes
  • Noticing the sign and asking for consent3 → 1 min
  • Writing the need into the customer's record6 → 1 min
  • Telling letters, sales, fees and collections about the need15 → 1 min
  • Finding what the bank owes and proposing a refund20 → 2 min
  • Opening the specialist referral and booking the callback10 → 2 min
  • Evidence for file testing and the board report15 → 2 min

Estimated split of the people's working time on one disclosure, from the call to the evidence for the board, by hand and with the solution. Our arithmetic, kept modest.

How it works

How a need moves

Seven agents listen, draft, follow through and compare outcomes; colleagues record with consent, specialists check.

What comes in
Signs incalls, chats, branches · and the customer record
Agents at work
Listening agenthears it, prompts to ask
Then
Needs Record agentplain words, with consent
Then
Follow-through agentevery channel, checked
Referral agentspecialist, service level
Then
Outcomes agentneeds vs everyone
A person decides
Customer Service Colleagueasks, records with consent; a specialist checks
What comes out
Needs followed everywhere
Refunds checked by two
Board report, signed
One case, step by step

One call, from a payment question to a need followed everywhere

Tuesday October 20, 2026, the Corvane Bank UK contact center in Leeds. Mrs Ann Hollis, 74, a customer since 1988, calls about a £1,250 payment that left her overdrawn. Here is what happens next, screen by screen, in the working solution.

  1. 0111:04

    A bereavement heard, and one prompt to ask

    Listening agent

    Mrs Hollis explains that the £1,250 standing order to Westmere Lodge Care Home was her husband David's, and that he died last month. Her record already holds the needs she shared in the Harrogate branch on Mar 3, 2025: a hearing aid, large print at 16 pt and no app. The Listening agent hears a possible bereavement at 0.96 confidence and possible distress at 0.81, and prompts Ellie Marsh once, with three choices: she agreed, she declined, or ask at the end of the call.

    You could say: “I’m so sorry about David. Would it help if I made a note of this on your record, so you don’t have to explain it again, and we can give you more time? You can ask us to remove it at any time.”

  2. 0211:05:02

    She agrees, and the need is drafted in her own words

    Ellie Marsh · Customer Service Colleague

    Ellie asks, and Mrs Hollis answers: “Yes, please do. I don't want to go through it all again.” Only then does the Needs Record agent draft a temporary bereavement need under life events, at 0.94 confidence, with a review on Apr 20, 2027, six months on. The consent passage is stored with the need. Ellie can edit the words, and an edit is logged as an override.

    “Mrs Hollis’s husband, David, died on Sep 14, 2026. She would like one team to deal with his accounts, and more time on calls.”

  3. 0311:05

    Five channels changed at once, and what the bank owes her

    Follow-through agent

    Ellie saves the need. Calls now go to the Bereavement Support Team with extra time, nothing is addressed to Mr Hollis, there is no sales or marketing contact until Apr 20, 2027, overdraft charges are reviewed for refund until Dec 20, 2026, and no collections contact happens without a specialist. The agent proposes a £35.00 refund of overdraft charges, a Bereavement Support Team callback on Thursday Oct 22 at 10:00, and a pause of the £1,250.00 standing order due Nov 1, only if she asks.

    The Follow-through agent proposes and never acts: money and account changes need a checker.

  4. 0411:05:44

    The refund opens its source

    Ellie Marsh · Customer Service Colleague

    Ellie clicks “overdraft charges Oct 1–19” and reads the passage from the core banking customer record. On Oct 1 standing order SO-88213 took −£1,250.00 and left a balance of −£637.60 against an arranged overdraft limit of £1,000; on Oct 19 charges of −£35.00 took it to −£672.60. The proposal also cites the bank's Bereavement standard BS-3 §2 and the team diary.

  5. 0511:06

    She approves; a second person will check

    Ellie Marsh · Customer Service Colleague

    The £35.00 refund, reason RF-02, is within Ellie's £50 mandate, so she approves it and it waits for a specialist's check. She books the callback, and a large-print confirmation letter is queued because of the need Mrs Hollis shared in her branch. On Mrs Hollis's instruction, the standing-order pause goes for a check too.

    “Approved by Ellie Marsh · waiting for Priya Raman's check”

  6. 06The queue

    Referrals with service levels and named owners

    Priya Raman · Customer Support Specialist

    The specialist teams have 418 open referrals: 37 due today, 5 overdue and escalated, 3 checks waiting and 1 day 6 h on average to first contact. Bereavement, power of attorney, carers, financial difficulty and specialist support each have a team, a service-level chip and an owner; Mark Okonjo's mental health crisis call is urgent, due by 11:30. A suspected financial abuse referral shows only “Held by Specialist Support”.

  7. 0711:11

    Checked and posted: maker Ellie, checker Priya

    Priya Raman · Customer Support Specialist

    Priya opens referral R-10418, opened Oct 20 at 11:06, first contact due Oct 22 at 17:00. She checks the £35.00 refund and posts it to core banking. The referral shows 3 of 6 steps done, the standing-order pause until Nov 30 waiting for a check, and the death certificate and the large-print statement reprint still to do.

    An overdue referral goes to the team manager at the due time, then to the Consumer Duty Manager after 1 working day.

  8. 08After the call

    One support needs record for the whole bank

    Review agent

    Mrs Hollis's row now shows her bereavement, recorded on a call on Oct 20 at 11:05:02 by Ellie Marsh, review Apr 20, 2027. The register holds 96,141 customers with a recorded need, 3,214 new disclosures in 30 days, 2,860 temporary needs due for review in 30 days, and 0 needs recorded without consent. Each row says how to help in plain words; health details stay with the specialists.

    The Review agent asks the customer at the next natural contact. It never closes a need: a maker and a checker do.

  9. 09Last 30 days

    Every letter, call and fee checked against the need

    Follow-through agent

    The agent checked 412,600 contacts against recorded needs and found 61 not respected: 54 put right, 7 open, 3 h 40 min on average to put right. One is Mrs Hollis's own: her Sep 26 savings statement was printed at 11 pt. Others are a credit card upgrade call to a customer who asked for no sales calls, and an £8.00 returned payment fee on a late husband's direct debit, which waits for a specialist.

    When the collections system stopped answering at 09:12, the screen said so, and queued letters were held until it was back.

  10. 1011:13

    Customers with needs against everyone: a gap agreed

    Thomas Achebe · Consumer Duty Manager

    For Quarter 3 the Outcomes agent compares 96,140 customers with a recorded need with all 1,412,300 customers on 9 measures. First-contact resolution is 71.2% against 78.1%, and complaints 14.2 per 1,000 against 9.6. Gap G-1: 212 bereaved customers paid £7,480 of overdraft interest in the 30 days after a bereavement was recorded. Thomas agrees the action with an owner and a date: Craig Nolan, Current Accounts Product Owner, by Dec 15, 2026.

    The agents suggest stopping overdraft interest for 60 days once a bereavement is recorded, and refunding all 212; Thomas Achebe decides.

Who it’s for

Built for everyone who looks after a customer with a need.

The same call, seen by the people who take it, check it, test it and answer for it: what their day looked like, and what it looks like now.

EM
Ellie MarshCustomer Service Colleague · contact center, Leeds · refunds to £50
Customer Service Colleague
Before
Takes 60 calls a day and hears a bereavement or distress between security questions and a payment query; what she writes up is free text the next team may never read.
Now
Gets one prompt with the words to ask, saves the need in the customer's words when she agrees, and approves the agents' proposals within her £50 mandate.
PR
Priya RamanBereavement Support Team · checks refunds and account changes
Customer Support Specialist
Before
Wants the case ready before she calls, and nothing posted that she has not seen.
Now
Opens R-10418 with its steps, service-level clock and the agent's plan, and checks and posts every refund and account change a colleague makes.
TA
Thomas AchebeConsumer Duty Manager · signs the outcomes report for the board
Consumer Duty Manager
Before
Has to show the board where customers with needs fare worse, and what it costs to fix, from figures that measure service levels.
Now
Sees 9 measures for customers with recorded needs against everyone, agrees each gap's action with an owner and a date, and signs only a report Compliance has verified.
FL
Fiona ListerCompliance Monitoring Analyst · tests 60 files a month
Compliance Monitoring Analyst
Before
Tests files against FG21/1 and the bank's policy, and wants to re-listen before she agrees that an agent heard distress.
Now
Re-reads 16 of 16 numbers in the board report against source before it can be signed, and sees the Listening agent's accuracy measured each month.
OP
Owen PryceVulnerability Program Administrator · settings and agents
Vulnerability Program Administrator
Before
Keeps the consent wording, review periods, refund mandates and channel adaptations the whole bank relies on.
Now
Proposes each change with a written reason; it takes effect only when the Consumer Duty Manager approves, and every agent's version and threshold is listed.
Built on the engine

7 agents. Each with one job, and hard limits.

Seven agents listen, draft, follow through and compare outcomes; colleagues record with consent, specialists check.

Listening agent

Hears possible signs of vulnerability on calls and chats under the four drivers (a bereavement, confusion, distress, a carer speaking), quotes the passage with its confidence, checks the customer's record and prompts the colleague once, with suggested words.

  • Never records a need and never speaks to the customer
  • Prompts only above 0.70, once per sign per contact
Needs Record agent

Drafts the need in plain words from the conversation, with its driver, kind and review date, for the colleague to edit and save.

  • Never saves: a person saves, with the customer's consent
  • No diagnosis words unless the customer used them
Follow-through agent

Applies a saved need to seven channels, looks back 30 days for what the bank owes, proposes refunds and callbacks, then checks every letter, call, fee, sales and collections contact against recorded needs.

  • Proposes, never acts
  • Money and account changes need a checker
Referral agent

Routes needs that need a specialist to the right team, sets the service-level clock and prepares the callback.

  • Restricted referrals are visible to their team only
Review agent

Finds temporary needs due for review and asks the customer at the next natural contact.

  • Never closes a need: a maker and a checker do
Outcomes agent

Compares nine outcome measures for customers with recorded needs against all customers and by driver, raises gaps over the 5-point tolerance with the evidence and an estimated cost of the fix, and drafts the quarterly report.

  • Never reports a group under 50
  • Every number cited to its source
Evidence Pack agent

Builds evidence packs for FCA supervision, internal audit and the Consumer Duty Manager from the audit trail.

  • Redacts health details by default
  • Never includes reports made outside the bank
Customer Service Colleague

Records with consent; a specialist checks. The agents propose; a named person decides.

Ask in plain words

Ask about any customer, referral or gap

Colleagues, specialists and managers ask in plain words. Every answer points to its source and opens the screen it is about.

Which bereaved customers paid overdraft interest after we knew?

212 customers in Q3, £7,480 in total, in the 30 days after a bereavement was recorded. 61 of them, like Mrs Hollis, still had a payment for the person who died running. The agents suggest stopping overdraft interest for 60 days once a bereavement is recorded, and refunding all 212; Thomas Achebe decides.

Has anything we sent Mrs Hollis ignored her needs?

One thing: her annual savings statement on Sep 26 was printed at 11 pt, though she asked for large print in March 2025. The template carried no large-print setting. The fix is to reprint in 16 pt with an apology and correct the template.

Which referrals are overdue?

5 of 418 are overdue and escalated to the team manager; 37 are due today. Peter Lyons (financial difficulty, overdue 2 days, unassigned) and Hazel Brookes (bereavement, waiting for the grant of probate copy). Mark Okonjo's urgent call is due by 11:30.

How do I ask a customer about recording a need?

Use script C-4: “Would it help if I made a note of this, so you don’t have to explain it again? You can ask us to remove it at any time.” If they say no, nothing is recorded and the decline is kept with the call.

Every screen

The working solution, as it ships.

13 screens from the working solution, on its sample data. Pick one to see it large.

The live callThe call transcript, the customer's support needs record under the four drivers with consent, recorder, review date and source, how each of 7 channels serves her, and the Listening agent's one prompt with the words to ask.
Consent, then the needConsent recorded as the customer's own words at 11:05:02, and a temporary bereavement need drafted in plain words, editable, with its review date.
Every channel adaptedFive channels updated at 11:05, and three proposals, a £35.00 refund, a specialist callback and a standing-order pause, each with its sources.
A cited sourceThe core banking passage behind the refund: the standing order, the balance against the arranged overdraft and the charges for Oct 1–19.
The colleague approvesApprove, change or reject with a reason code; the refund waits for a specialist's check, and the callback is booked with a large-print letter.
The specialist's checkReferral R-10418 with its steps, service-level clock and the agent's plan; the refund checked and posted, with maker and checker on the record.
Specialist referrals418 open referrals by team with service levels, owners and escalations; filter, search, and assign or escalate several at once.
Support needs registerEvery customer with a recorded need, how to help in plain words, reviews due and declines; health details stay with the specialists.
Follow-through checks412,600 letters, calls, fees, sales and collections contacts checked against needs in 30 days: 61 misses, each with the passage and a proposed fix.
Consumer Duty outcomesNine measures for customers with recorded needs against everyone, by driver, and gap G-1 agreed with an owner and a due date.
The board reportThe Q3 outcomes report with every number cited, verified 16 of 16 by Compliance before the Consumer Duty Manager can sign.
Audit trail and evidence packWho did what, when, why and on which evidence, and a redacted evidence pack for FCA supervision and internal audit.
Settings and agentsAgent versions, thresholds and limits beside consent wording, review periods, refund mandates and retention; every change approved by a second person.
Governance

Vulnerable customer support that is consented, checked and on the record.

Nothing recorded without consentThe agents prompt, a person asks and the customer decides. The consent passage is stored with the need, a decline is kept and never asked again on that contact, and customers can see, change or remove any need.
The maker never checksEvery refund, account change and closed need goes to a second person. A colleague approves within a £50 mandate and a Customer Support Specialist checks and posts; the person who approved cannot check.
Health details on a need-to-know basisColleagues see how to help in plain words; health details stay with specialists, compliance and internal audit. A restricted referral shows only “Held by Specialist Support”, and anything reported outside the bank about a customer never appears on a colleague or customer view.
Agents propose, people decideEvery agent is versioned with its threshold and limits. A new version runs beside the old one on last month's calls before the Consumer Duty Manager approves it, and any person can override an agent with reason OV-01.
The board report is verified, then signedThe Outcomes agent drafts it with every number cited; a Compliance Monitoring Analyst re-reads each number against source; only then can the Consumer Duty Manager sign. The person who signs cannot verify.
An audit trail and an evidence packWho did what, when, why and on which evidence, with reason codes. The evidence pack redacts health details and masks account numbers to the last four digits, the export itself is logged, and the trail is kept six years after the relationship ends.
Configuration

Your vulnerable customer policy, as settings

Consent wording, review periods, refund mandates, agents and retention are settings. Every change needs a written reason and the Consumer Duty Manager's approval; the old setting stays in force until then.

SettingDefaultChoose from
Consent wording on callsScript C-4: “Would it help if I made a note of this, so you don’t have to explain it again? You can ask us to remove it at any time.”Your own words for calls, and for branches and the app
Lawful basisExplicit consent, UK GDPR Article 9(2)(a)Where consent cannot be given, the specialist records the legal basis
Review periodsBereavement: 6 months, then ask the customerFinancial difficulty at the end of the breathing space or 3 months · temporary health 12 months · permanent every 24 months, at a natural contact
Refund mandatesColleague up to £50 per customer in 90 days; a specialist checksSpecialist up to £250, a second specialist checks · above £250 the team manager approves
Account changesAlways maker and checker, with the customer's instruction recordedStanding orders, attorneys and names
Listening agentv3.2 · prompt threshold 0.70 · never recordsA new version runs beside the old one on last month's calls before approval
Outcomes agentv1.8 · gap tolerance 5 pointsNever reports a group under 50
RetentionExpired temporary needs deleted 90 days after the review date; consent records and the audit trail kept 6 years after the relationship endsCall transcripts kept 12 months, with card and account numbers redacted at capture
Connections

Works with the systems your contact center and branches already run on

Contact center platformlive call audio and chat for the Listening agent, team diaries, contact outcomes
Core banking customer recordcustomers, accounts, standing orders and charges; refunds and account changes written after a check
Correspondence systemevery letter before it prints, checked for format and addressee against needs
Collections systemcollections contacts and holds, for follow-through checks
Complaints systemcomplaints and their outcomes, for the outcomes comparison
Branch appointmentsappointments, interpreters and accessible rooms
What it changes

The difference, in numbers.

Every figure is labelled: a target the solution is built to, an estimate, a typical published result, or a proven one.

target
<1%
of customers have to tell us a need twice within 90 days, from 3.1% today
Today3.1%
With agents< 1%
target
100%
of recorded needs carry the customer's consent, the date and who recorded it
Every need
consent on the record
estimated
£7,480a quarter
back to 212 bereaved customers charged overdraft interest after the bank knew

“demo” = seen in the working solution, on its sample data · “target” = the design goal, measured in the live solution · “estimated” = our estimate, kept modest · “typical” = published figures (FCA review of firms' treatment of customers in vulnerable circumstances, March 2025: 42% of customers in vulnerable circumstances had told their firm, and 44% reported a negative experience against 33% of others; FCA multi-firm review of retail banks' treatment of customers in vulnerable circumstances, April 2025; FCA FG21/1 and the Consumer Duty, PRIN 2A). Corvane Bank UK, Westmere Lodge Care Home and the customers, people, accounts and references named on this page are fictional: characters and sample data in the working solution.

Questions

Vulnerable customer support: what banks ask us.

What is Vulnerable Customer Support?

Vulnerable Customer Support is software for bank colleagues to spot customers who need extra care, record their support needs with consent and adapt service on every channel. Seven agents listen on the call, draft the need in the customer's own words, follow it through letters, fees, sales and collections, route specialist referrals and compare outcomes for customers with needs against everyone else. Colleagues ask and record, specialists check, and the Consumer Duty Manager signs.

How does it identify a vulnerable customer on a call?

The Listening agent hears possible signs on calls and chats under the FCA's four drivers of vulnerability: health, life events, resilience and capability. Above a 0.70 confidence threshold it prompts the colleague once, with the quoted passage, its confidence and suggested words. It never records a need and never speaks to the customer, and Compliance measures its accuracy every month.

Does it record a support need without the customer's consent?

No. Nothing is recorded until the customer agrees, and the consent passage itself is stored with the need as evidence. A decline is kept, and the prompt never repeats on that contact. Customers can see, change or remove any need.

How does one recorded need change letters, fees and sales calls?

When the colleague saves a need, the Follow-through agent applies the bank's channel adaptations to calls, letters, branch, app, sales, fees and collections. It then checks every contact against recorded needs, before a letter prints where it can and after a call or fee where it cannot, and proposes a fix for each miss. Money fixes wait for a specialist.

How does it help with the Consumer Duty for customers in vulnerable circumstances?

The Outcomes agent compares customers with recorded needs against all customers on nine measures and by driver, raises gaps above the 5-point tolerance with the evidence and an estimated cost of the fix, and drafts the quarterly report. A Compliance Monitoring Analyst verifies every number against source before the Consumer Duty Manager can sign it for the board.

Who can see a customer's health details?

Customer Support Specialists, compliance and internal audit. Colleagues see how to help, in plain words. Evidence packs redact health details by default, and call transcripts have card and account numbers redacted at capture.

Do people stay in control?

Yes. The agents may not record a need, speak to the customer, move money, change an account, close a need, decide an outcome action or sign anything. A colleague approves, a specialist checks every refund and account change, and every decision carries a named person and a reason code on the audit trail.

How long does it take to go live?

The Agentic Solution Engine builds and deploys it from your requirements and documents, such as your consent script, bereavement standard, review periods and channel adaptations, and it goes live once every quality gate has passed. We will walk you through it on a sample of your own calls first.

See it on
your own calls.

We'll run Vulnerable Customer Support on a sample of your own recorded calls and branch notes.