Rules and compliance

Supporting Vulnerable Customers on the Phone: A Practical Guide

How to recognise and support customers who may be vulnerable on calls: signals, adjustments, careful questions, handoffs, record keeping and staff care.

Call editorial team · Published · 5 min read

A caller seems confused about a bill and keeps asking the same question. Another speaks quietly and mentions that their partner usually handles these things but has recently died. A third becomes distressed when asked to key numbers into a menu. None of them has announced that they are vulnerable. All of them need a good agent to notice.

A support agent with a headset listening attentively during a phone call
Illustrative image

This guide offers a practical approach for contact centers: what vulnerability means, the signals to listen for, how to adjust your approach, what to record, and how to design phone processes so they do not trip people up. It pairs well with De-escalating Difficult Calls and Empathy on Calls.

What vulnerability means

There is no single definition, but a common view is that a vulnerable customer is someone who, because of their personal circumstances, is especially susceptible to harm, particularly when a business does not act with appropriate care. It is a state that can be temporary or permanent, and it can change from one call to the next.

Four broad drivers of vulnerability

  • HealthPhysical or mental illness, disability, hearing or sight loss, cognitive difficulties, or a condition that makes phone calls hard.
  • Life eventsBereavement, relationship breakdown, job loss, caring responsibilities, or leaving a violent situation.
  • ResilienceLow financial resilience, or difficulty coping with unexpected costs and stress.
  • CapabilityLimited language skills, low confidence with technology or low understanding of the product.

Because anyone can be affected, treat vulnerability as a spectrum and build habits that help everybody, rather than a special track reserved for flagged people.

Signals to listen for

Callers rarely announce vulnerability. They show it through what they say and how they say it.

Adjust your approach

A simple pattern for a call with a struggling caller

  1. Slow downLower your pace, pause more and avoid jargon.
  2. Ask gently"Is now a good time? Would it help if I explained that another way?"
  3. Offer choicesOffer to call back, to send information in writing or to speak to a colleague.
  4. Check understandingAsk them to say in their own words what they will do next.
  5. Confirm what happens nextState the next step and when it will happen, and repeat it.

Adjustments that help many people

Asking, recording and sharing carefully

Details about someone's health or circumstances are sensitive. Ask only what you need to help, explain why you are asking and what you will do with the answer, and respect "I would rather not say". Record the adjustment that helps, such as "prefers callbacks in the morning", rather than the reason behind it.

Recording vulnerability information

Too muchJust enough
What is written"Customer is depressed after husband died, cannot cope.""Prefers morning callbacks; needs extra time."
Who can read itEveryone with CRM accessOnly those who handle the account
Customer knowsNot toldTold what is noted and why
Future callsAgents repeat the story to the customerAgents apply the adjustment without asking again

Where your organisation keeps a flag or note for future calls, say so, and let the customer see or change it where the rules allow. Limit who can read such notes. See Collecting Less Data in Customer Support and Access Controls for Contact Center Staff.

Design phone processes that do not trap people

Many problems come from the process, not the agent. A menu with many levels, a requirement to key long numbers, strict time limits to respond, and no route to a person all make life harder for some callers. Check your flows with that in mind.

An AI voice agent can take a request, but it can misread distress or confusion, so listen to real calls, not only test scripts. Build in an easy way to reach a person, and review calls where callers repeated themselves or gave up. See Phone AI and Older Callers.

When to escalate

Agree in advance what agents should do when a caller may be in danger, expresses thoughts of harming themselves or others, or discloses abuse. Provide a short escalation route, a trained person to speak with and the contact details for appropriate services. Agents should not have to improvise in those moments, and they should be able to take a break afterwards.

Looking after the people on the line

Staff also need permission to act. If an agent believes a caller needs more time but the schedule punishes long calls, the schedule will win. Say plainly that these calls may run over, and look at how targets for handle time treat them.

Supporting distressed customers is emotionally demanding. Give agents training with practice calls, a place to debrief, the freedom to take a short break after a hard call and managers who check in. See Preventing Agent Burnout. Review a sample of calls to praise good handling, not only to find faults.

Vulnerable customer readiness

  • Define vulnerability in plain words and share examples with staff
  • Train agents on signals, careful questions and adjustments
  • Give agents the freedom to slow down, call back and offer alternatives
  • Decide what is recorded, who can see it and for how long
  • Test menus and AI agents for people who need more time
  • Write an escalation route for urgent or risky situations
  • Support staff after difficult calls
  • Review calls and outcomes regularly and adjust

Doing it in Call

Several features in Call help you act on these ideas. Callbacks let a caller who cannot wait leave a request, and queues can offer a message and voicemail. A phone menu can include a clear route to a person, and an AI agent can hand a call over to a human; see Handing Calls from an AI Agent to a Person in Call. Appointments and callback entries let you note a preferred time. The CRM lets agents add short notes against a contact, and roles control who can see them. Call does not decide who is vulnerable; that judgment belongs to your people and your policy.

Frequently asked questions

Who counts as a vulnerable customer?

There is no single definition. It generally means someone who, because of personal circumstances, is especially susceptible to harm if a business does not act with appropriate care. It can be temporary and can affect anyone.

Should agents ask callers whether they are vulnerable?

Rarely in those words. It is better to listen for signals and offer help, such as more time or a callback, and to ask gently what would make the call easier.

What should we record about a customer's circumstances?

Record the adjustment that helps, such as a preferred callback time, rather than detailed reasons. Share it only with those who need it and explain how it will be used.

Can an AI voice agent handle vulnerable callers?

It can take requests, but it may misread distress or confusion. Provide an easy route to a person, review calls where callers struggled and never use it to pressure someone to continue.

What if a caller says they are in danger?

Follow the escalation process you have agreed in advance, including who to involve and which services to contact. Agents should not improvise; they need clear steps and support afterwards.

How can we measure whether we treat vulnerable customers well?

Review a sample of calls against your standards, look at repeat contacts and complaints, and ask customers and staff what gets in the way. Numbers alone will not tell you.

Set up callbacks and handoffs for callers who need extra time in Call

In the demo console you can try incoming calls in a simulation.

Related guides