Reading the Room

All Sectors

• The Problem

  Most insurance journeys are designed around a standard customer in a standard situation. The digital flow assumes literacy, stability, and sufficient cognitive bandwidth to complete a transaction. The customer who is grieving, financially stressed, or cognitively impaired moves through the same journey and either completes it poorly, abandons it, or reaches a human who has no context for their circumstances. The signals were present in the journey data. The design was not built to use them.

• The Pattern

  The structural move is to design every customer touchpoint to detect circumstance signals and propagate them across the entire service delivery chain, so that every subsequent interaction responds consistently:

  Behavioural signals

  Present in the journey itself without requiring disclosure: extended session times, repeated form abandonment, unusual navigation patterns, accessibility feature usage, requests for callbacks, multiple failed attempts at the same task. These are observable in existing journey data and should trigger adapted responses automatically

  Contextual signals

  Arising from the nature of the interaction: a bereavement claim, a policy change following a job loss, a query about payment difficulty. These should automatically trigger a different response posture — not just a flag in the record but a change in how the next interaction is handled

  Cross-chain propagation

  Detected signals must travel with the customer across channels, functions, and time. A vulnerability flag set on a call must be visible in digital, at renewal, and during claims. The propagation mechanism must be systematic — embedded in the customer record and surfaced to every touchpoint — not dependent on individual agents remembering to check notes

• Indicators It's Working
  • Vulnerability identification rates increase toward population-representative levels as designed disclosure pathways and behavioural detection take effect

  • The gap between internally reported vulnerability volumes and statistically expected population rates closes over time

  • Context flags persist accurately across channels without requiring customer re-disclosure — measurable by testing whether a flag set in one channel is visible in another

  • Post-interaction surveys show vulnerable customers feel their circumstances were understood and responded to, not just recorded

• In Practice

  • A life insurer discovered that customers who disclosed bereavement during a death claim were subsequently contacted by the retention team about lapsed direct debits on the deceased’s policy — because the bereavement context was recorded in the claims system but not propagated to billing. They built a context propagation layer that flags all accounts associated with a bereavement event, suppressing automated collections and routing any contact through the specialist bereavement team. The technical change was modest; the experience change was transformative. Complaints from bereaved families fell by 70%.

  • A motor insurer analysed its digital journey data and identified that customers who spent more than three times the average session duration on the claims notification form had a 4x higher rate of subsequent complaints about the process. They introduced real-time behavioural monitoring: when session duration exceeds a threshold, the journey offers a callback option and flags the case for a trained handler. The flag persists through the claims lifecycle, ensuring that every subsequent touchpoint — assessment, settlement, repair — is handled with awareness of the customer’s likely circumstances.

• Watch-Outs
  Common failure modes

  The most common failure mode is building detection capability that identifies vulnerability but does not change what happens next. Detection without response erodes trust faster than no detection at all — the customer disclosed something personal and nothing visibly changed. A second is over-engineering identification to the point where it feels intrusive: customers who feel surveilled rather than supported will disengage and disclose less. A third is propagating the flag without propagating the response: knowing a customer is vulnerable means nothing if every touchpoint still follows the standard process.