top of page
Library - Portrait.png

Customers Experiencing Vulnerability Need Responsive Service, Not Just a System Flag

Nov 12
6 min read
BlindSpot Insights Customer Experience branded article cover.

Customers experiencing vulnerability need responsive service, not just a system flag. A flag can be useful, but it does not answer the customer's question, change an inaccessible document, pause an automated collection process or help a frontline employee decide what to do next. Too often, organisations become better at recording vulnerability than responding to it. The field is populated, the workflow continues, and the customer receives the same process with slightly more sympathetic notes. This is administration wearing the name of support.


Customers experiencing vulnerability are not one customer segment


Vulnerability is not a fixed identity or a small category of people who can be separated neatly from everyone else. It can arise from disability, illness, bereavement, financial pressure, family violence, language barriers, digital exclusion, a natural disaster, caring responsibilities or a sudden change in circumstances. Several factors may interact, and they may be temporary, recurring or long term. The same person can move in and out of vulnerable circumstances while using the same service.


That makes the familiar segmentation approach unreliable. A customer may not use the organisation's preferred label, may not disclose their circumstances directly or may not realise that support exists. Another may explain the situation repeatedly but encounter a process that recognises only one approved type of need. ASIC's review of financial hardship practices found that an overly limited view of vulnerability could cause lenders to miss individual circumstances and the extra care people required.


The design question is therefore not simply how to identify the right people. It is how to make services safe and usable when the organisation has incomplete information. If support depends on a customer presenting the correct phrase to the correct employee during the correct contact, the system has confused a help pathway with a password challenge.


Inclusive service design should reduce the need to disclose


Inclusive service design starts by removing barriers that affect many customers before individual support is needed. Clear information, accessible documents, flexible communication channels, plain language, reasonable timeframes and an easy route to a person can prevent ordinary complexity from becoming harm. These features help customers experiencing vulnerability, but they also help anyone who is tired, stressed, unfamiliar with the process or attempting to complete it while life is being unhelpfully realistic.


The Australian Energy Regulator's Customer Engagement Toolkit makes this connection explicit. It notes that the way services are designed and delivered can either mitigate or contribute to vulnerability and harm. Its better practice principles include designing for all consumers, engaging effectively with vulnerability, collaborating with other organisations, using data to improve outcomes and committing to continuous improvement.


This shifts the conversation from exceptions to service quality. Instead of building a standard process and adding a specialist escape route at the end, organisations can design common journeys with more than one workable option. Customers should be able to use digital and human channels, appoint a representative, request accessible information, explain circumstances without unnecessary repetition and move into support before the situation becomes a crisis.


Customer support must turn information into action


When a customer discloses difficult circumstances, the employee needs more than permission to sound caring. They need practical options, decision authority, specialist support and clear safety guidance. A well-intentioned conversation followed by an inflexible process can leave the customer carrying both the original problem and the organisation's empathy. The words may be warm, but the direct debit remains impressively punctual.


ASIC's hardship review found cases where customers' vulnerability was not identified early, despite information being provided multiple times. It also highlighted problems where case management was absent and the significance of a customer's circumstances became visible only across repeated contacts. The lesson is not that employees should diagnose people. It is that systems should help staff notice relevant signals, ask respectful questions and connect the information to an appropriate response.


Responses may include adapting communication, allowing more time, involving an authorised representative, arranging an interpreter, offering a suitable payment or support option, changing contact preferences, escalating safety risks or coordinating with a specialist team. Not every organisation can provide every form of assistance, but every organisation can make the next step clear, respectful and proportionate.


Continuity matters more than the quality of one conversation


A strong interaction can be undone by the next contact if context is lost. Customers experiencing vulnerability may already be managing distress, fatigue, cognitive load or safety concerns. Repeating a painful history to several employees is not a neutral administrative requirement. It can discourage further engagement and, in some circumstances, create additional risk.


Continuity requires careful information handling. Record only what is necessary, make consent and access visible, respect communication preferences, recognise authorised representatives and ensure that relevant instructions follow the customer across channels. A flag without meaningful guidance can alert every employee while helping none of them. A useful record tells the next person what support has been agreed and what the customer should not have to repeat.


The Australian Financial Complaints Authority encourages early identification of financial difficulty and a flexible approach to communication, interpreters and authorised representatives. ACMA's Financial Hardship Standard similarly emphasises proactive identification, accessible information and assistance suited to the customer's circumstances. These expectations point to a consistent principle: support should continue through the journey, not expire when the first helpful employee ends the call.


Safety and privacy need deliberate design


Some circumstances require additional care because ordinary contact practices can expose a customer to harm. Family violence is the clearest example. Contacting the wrong number, revealing account information, sending correspondence to a shared address or insisting that a customer negotiate with another account holder can create safety and privacy risks. The safest process is rarely produced by adding a warning banner after the standard workflow has already made its decisions.


Organisations should identify where identity checks, joint accounts, collections, correspondence, representatives and channel switching can create risk. Employees need clear instructions about safe contact, authentication, escalation and information sharing. Customers should be able to update preferences without being forced through a path that exposes the very circumstances the controls are meant to protect.


Good governance also protects against over-recording. A detailed narrative may feel thorough but can spread highly sensitive information far beyond the people who need it. Record the support requirement and agreed actions, limit access appropriately and retain information only for a legitimate purpose. The organisation needs enough context to help, not an internal biography assembled during a difficult afternoon.


Use data to improve outcomes, not just count flags


Vulnerability data is often reported as the number of customers identified or referred. Those figures describe activity, but they do not show whether the service helped. A rising count might indicate better identification, worsening customer circumstances or a process creating more hardship. Like many dashboard measures, it becomes more useful once someone asks what decision it is meant to support.


Track outcomes such as time to reach support, repeat contacts, abandoned journeys, successful use of representatives, accessible format delivery, complaints, missed commitments and the stability of agreed arrangements. Review where customers disclose needs, where those needs are lost and which policies generate repeated exceptions. Combine quantitative patterns with customer and frontline insight, because a clean average can conceal a very difficult journey.


Use the findings to change the service. If customers repeatedly need a specialist team because the standard form is inaccessible, improve the form. If employees request approvals that are routinely granted, reconsider the authority level. If a support pathway begins only after arrears, complaints or disconnection risk, move the intervention earlier. Continuous improvement is more convincing when it eventually reduces the need for heroic case handling.


What leaders should check now


Leaders should walk through the service as a customer whose circumstances do not fit the standard path. Can the person find support without using a stigmatising label? Can they choose a safe channel, appoint someone to help, receive accessible information and keep their context across contacts? Can employees pause automation, change a process or escalate a risk? If the answer depends on finding one unusually resourceful staff member, the capability belongs to that person, not yet to the organisation.


  • Design for variation first. Remove common barriers so customers do not need to disclose personal circumstances simply to use the service.

  • Connect identification with action. Give employees clear options, authority and specialist support when a customer's needs become apparent.

  • Protect continuity and consent. Record agreed support carefully so customers do not have to repeat sensitive information across channels.

  • Build safety into workflows. Review contact, authentication, joint account, collections and correspondence processes for foreseeable harm.

  • Measure customer outcomes. Use repeat contact, access, resolution and harm indicators to improve the service, not merely the number of flags recorded.


Customers experiencing vulnerability do not need an organisation to predict every circumstance. They need a service that can notice variation, respond safely and adapt without turning support into another obstacle. A system flag may help start that response, but it is not the response itself. The real measure is whether the customer experiences less effort, less risk and a clearer path forward. That is where compassionate intent becomes service capability.


References

bottom of page