Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Customer Experience, Retention & Loyalty › Service and Support

Supporting Customers in Vulnerable Circumstances

How a support team recognises and helps customers in difficult circumstances such as illness or bereavement: adapting the process and recording needs.
Guideintermediate11 min readUpdated

What vulnerable circumstances mean for a support team

For a support team, a customer in vulnerable circumstances is someone whose situation makes the normal process harder to use or more likely to cause them harm. The situation might be lasting, such as a disability or a long illness, or temporary, such as a bereavement, a hospital stay or a sudden drop in income. It might affect how the customer communicates, how quickly they can respond, whether they can deal with the business at all, or what a standard step such as a reminder or a charge does to them.

Two points shape everything that follows. First, the circumstances belong to the situation, not the person: anyone can be in them, and most people pass through them at some point. Second, the business usually does not know. Customers rarely announce their circumstances, and the support team has to notice, ask and adapt within the conversation.

The support channels and self-service guide covers this in a paragraph: staff need guidance on recognising these situations and the authority to adapt the process, for example by pausing collections or accepting a different form of identification. This guide takes that paragraph through. It is written as general practice for any business, not as a description of any regulator's rules.

Some sectors, such as financial services, energy and telecoms, have their own rules on customers in vulnerable circumstances, set by their regulators. No source this site cites documents them, and this guide does not summarise them. A business in a regulated sector should take its approach from those rules and from qualified advice; the practice below can sit alongside them but does not replace them. Nothing here is legal advice.

Recognising the signs without labelling people

Agents recognise vulnerable circumstances from what the customer says and how the conversation goes, not from a checklist of personal characteristics. Common signs include:

  • What the customer tells you. A mention of a death, a diagnosis, a hospital stay, caring for someone, losing a job or a difficult situation at home.
  • How the conversation goes. Difficulty following the steps, repeated questions, distress, long pauses or a customer who seems overwhelmed by a routine request.
  • Who is contacting. A relative, friend or carer contacting on the customer's behalf, or a request to deal with the account of someone who has died.
  • What the account shows. A sudden change in behaviour, such as missed payments from a customer who has always paid, or a series of contacts about the same simple task.

None of these signs proves anything, and agents should not try to diagnose. The right response is a simple, open question about what would help, asked in the team's normal tone: "Is there anything that would make this easier for you?" Avoid asking customers to describe their condition, and avoid the word "vulnerable" in conversation, which many people find patronising. The customer decides what to share.

Automated channels need the same care. The AI in customer service guide keeps customers in vulnerable situations with people and routes signals of such situations straight to trained staff; the same rule applies to any bot or automated flow. Mapping where these contacts arrive along the journey, with the customer journey mapping framework, shows the moments where a standard message or process is most likely to reach someone at a bad time, such as a renewal reminder or a payment chase.

Adapting the process: what agents can change

Recognising a situation helps only if the agent can do something about it. Decide in advance what agents may change, so they can act in the conversation without seeking approval each time, and what needs a named person.

What can be adaptedExamplesUsually decided by
TimeLonger to respond, pay, return or provide documents; pausing reminders and chasersAgent, within set limits
ChannelMoving to phone, email, letter or a written summary; a call-back at a time that suitsAgent
Who speaksDealing with a relative, carer or representative the customer namesAgent, with the customer's agreement
Communication formatPlain language, larger print, written confirmation after a call, a slower paceAgent
Proof and paperworkAccepting a different form of identification or fewer documentsAgent within limits, or team lead
Charges and collectionsPausing collections, waiving a fee, adjusting a payment dateTeam lead or named owner
Point of contactOne named person for the rest of the case, so the customer does not repeat their storyTeam lead

Accessible channels are part of this. The support channels guide sets out that the Web Content Accessibility Guidelines, organised around content being perceivable, operable, understandable and robust, apply to the help centre, contact forms and chat, and that offering more than one route to a person removes barriers no single channel can. This guide does not repeat that section; read it alongside the guide to accessibility as conversion work, which covers finding and fixing barriers on pages. WCAG covers digital content; the adaptations above cover the conversation.

When a customer agrees that an adjustment should continue, such as written confirmation after every call or a named relative who may speak for them, the team needs to record it so the next agent does not ask again. Recording it well is a data protection question as well as a service one, and the site's guides set out the relevant points.

The GDPR is the EU framework for processing Personal Data. As the healthcare industry guide states, it treats data concerning health as a special category of personal data, which may be processed only under specific conditions in addition to an ordinary Lawful Basis. A note that a customer has a particular illness is health data. The guide to minimising data before prompting records that the GDPR lists data minimisation among its principles: personal data should be adequate, relevant and limited to what is necessary for the purpose.

In practice that leads to a few rules a support team can follow:

  • Record the support, not the condition. "Prefers written confirmation after calls" or "daughter may speak on the account" is usually enough. A description of the customer's health or circumstances rarely is needed.
  • Ask first. Tell the customer what you would like to note, why and who will see it, and record it only if they agree. Where consent is the basis, the GDPR, as the participant information and consent guide summarises it, describes consent as freely given, specific, informed and unambiguous, and as easy to withdraw as to give.
  • Limit who can see it. Put the note where the agents who need it will see it, and nowhere else. It should not reach marketing lists, segments or exports.
  • Keep it current. Ask the customer, when it makes sense, whether the arrangement is still needed, and remove notes that no longer apply.
  • Check the basis with someone qualified. Before building the process, agree the lawful basis, any condition for special category data and how long notes are kept with whoever is responsible for data protection, or a qualified adviser. This guide does not set retention periods.

The same care applies when cases are used for training or review. Remove anything that identifies the customer before a case is shared beyond the people handling it, in the same spirit as the extra care that guide gives research participants who need it.

Bereavement and other common situations: a table

Some situations recur often enough to plan for. A short route for each saves the customer from explaining themselves several times and saves the agent from improvising.

SituationWhat usually helpsWhat to avoid
A customer has died and a relative contacts the businessOne route and one contact person; stop marketing and reminders; ask once for the minimum proof needed; close or transfer the account simplySending reminders, renewal notices or promotions to the person who died; asking for the story again at each step
Serious illness or a hospital stayExtra time; pausing reminders and charges where possible; dealing with a named representativeChasing for responses the customer cannot give; insisting on the usual channel
Disability affecting communicationThe customer's preferred channel and format; more time; written summariesAssuming what the customer needs; routing to a channel they cannot use
Sudden money difficultyPausing collections where the business can; a clear, calm explanation of optionsPressure to pay or upgrade; offers framed as urgent
Distress or crisis during a contactSlowing down; offering a call-back or a pause; escalating to a named personPushing through the standard script
Someone acting for the customerChecking the customer's agreement where they can give it; a clear record of who may actRefusing all help because the account holder cannot speak

The table describes general practice. Where a situation involves a risk to someone's safety, the team should have a separate, simple instruction on who to tell and what to do, written with qualified advice.

Escalation, staff support and reviewing cases

Escalation. Name the people agents can pass a case to when the adaptation needed is beyond their authority or the situation is serious, and say how to reach them. The service recovery and complaints guide already lists customers in vulnerable circumstances among the reasons to escalate; this guide adds that the route should be named, quick and staffed whenever the channels are open. A complaint from a customer in difficult circumstances should be handled with the same adaptations as the original contact. A written complaints procedure is the place to record that rule, and the tutorial on setting remedies and goodwill limits is where the approval levels for adaptations such as waived fees belong.

Looking after staff. These conversations are hard. Agents who take a call from a bereaved relative, or from someone in distress, need permission to take a few minutes afterwards, someone to talk to, and the confidence that the business will back a reasonable adaptation. Training should cover the signs, the open question, the adaptations agents may make and where to escalate, using real situations with details removed. Agents should never be measured in a way that pushes them to rush these contacts.

Reviewing cases. Review a sample of cases regularly with the team: what helped, what the process got in the way of, where agents lacked authority, which standard messages or charges caused harm. The changes that come out of the review, such as a reminder that should stop automatically after a bereavement notice, are often the most valuable part of the work. On the marketing side, the tutorial on pausing marketing to customers with an open issue builds the hold that stops promotion as soon as a bereavement is recorded, passing a flag to the marketing tools rather than the note itself. The service and support hub places this alongside the team's other standards and the route from support insight to product and marketing.

A mobility aids supplier writes its approach (illustrative)

Illustrative example — not a real result

Plenvaro Mobility Aids writes guidance for difficult contacts

Plenvaro Mobility Aids, an invented online supplier of wheelchairs, walking aids and bathroom equipment, has 5 support agents. In one month they log 23 calls from relatives returning equipment after the customer has died. Agents report that the returns process asks for an order number, a reason code and photos, and that 4 of the relatives received a payment reminder or a promotional email after their first call.

The support lead writes a two-page guide with the agents. It adds a bereavement route: the agent records the death on the account, which stops reminders and marketing at once; collection is arranged without the returns form or photos; and one named agent handles the case to the end. Agents may extend any return or payment deadline by up to 60 days without approval and refer anything further to the support lead.

The team agrees that notes record only the support agreed, such as "son handling account, wants email updates", visible to support agents and not to marketing, and checks the approach with the firm's data protection adviser. Each month the lead reviews the cases with the agents. In the next 3 months the team handles 61 bereavement returns, none receives a reminder or promotion after the first contact, and the agents add a second route for customers in hospital who cannot accept a delivery.

Common mistakes

  • Waiting for customers to announce it. Most customers do not. Train agents to notice signs and ask what would help.
  • Labelling people. Asking a customer whether they are vulnerable, or describing them that way in notes, feels intrusive. Ask about needs instead.
  • Sympathy without authority. Agents who recognise a situation but cannot change anything leave the customer where they started. Set what agents may adapt.
  • Recording too much. A description of a customer's health is special category data and rarely needed. Record the support agreed, with the customer's agreement, and limit access.
  • Letting automation carry on. Reminders, renewals and promotions sent after a bereavement notice do real harm. Make the route stop them.
  • Treating regulated rules as covered. Businesses in regulated sectors have their own rules. Take qualified advice rather than relying on general practice.
  • Forgetting the staff. Agents who take hard calls need time, support and backing, not targets that rush them.

Frequently asked questions

What counts as a customer in vulnerable circumstances?

In general practice, a customer whose personal circumstances make it harder for them to deal with the business or more likely that they will be harmed by a standard process. Bereavement, serious illness, a disability, a mental health crisis, a sudden change in income or a difficult situation at home are common examples. The circumstances can be temporary or lasting, and they are about the situation rather than the person. Some regulated sectors define the term in their own rules, and businesses in those sectors should follow them with qualified advice.

Should support agents ask customers whether they are vulnerable?

Not in those words. Labelling someone as vulnerable can feel intrusive or patronising. Agents do better to notice signs, such as a customer mentioning a death in the family or struggling to follow the conversation, and then ask a simple question about what would help: more time, a different channel, someone else to speak for them, or a pause. The customer decides what they share and what happens next.

Can a support team record information about a customer's health or circumstances?

Only what it needs to help, and with care. Under the GDPR, information about a person's health is special category data, which may be processed only under specific conditions in addition to an ordinary lawful basis. In practice a team should record a short note of the support the customer has agreed to, not a description of their condition, limit who can see it, and check the lawful basis and the conditions with whoever is responsible for data protection or a qualified adviser before building the process.

Terms used on this page

Frameworks

Where this page is used

Also related

Sources

  1. Regulation (EU) 2016/679 (GDPR) — EUR-Lex
  2. Web Content Accessibility Guidelines (WCAG) — W3C

Related