Consumer Duty Pattern Library
22

The Human Moment

Support That Enables
Engagement

All Sectors

  • Digital channel design has steadily optimised human contact out of customer journeys. For most low-stakes interactions this is a service improvement: customers prefer a working app to a phone queue. But there are points in every customer journey where the absence of a human is the harm itself — bereavement, claims under stress, financial difficulty disclosure, retirement income decisions, accessibility breakdown. Most firms manage deflection metrics on a portfolio basis, and the numbers improve because the average interaction is well served. The numbers conceal the cohort of interactions that should never have been deflected — the customer at a defining moment who reaches a chatbot, a form, or a hold queue and concludes that the firm cannot help them.

  • The structural move is to treat human availability as a designed feature of specific journey moments rather than an output of staffing optimisation. The pattern identifies those moments, designs them for human contact, and instruments them so deflection metrics cannot quietly erode them:

    Map the human-required moments

    Each customer journey has a defined set of moments where stakes, complexity, vulnerability, or emotional load mean that human contact materially changes the outcome. Bereavement notification. Claims under stress. Financial difficulty disclosure. A request to surrender, drawdown, or crystallise. Suspected fraud. A vulnerability disclosure across any channel. Loss of capacity or activation of a power of attorney. The first task is to enumerate these moments per product and journey, evidence why each is human-required, and review the list as journeys change. The design test: can the firm name, for each material customer journey, the moments at which a human must be available, and the evidence base for that judgement?

    Engineer human availability into the design

    At each named moment, human contact must be designed in — not left to the customer to find. That means proactive routing where signals are detectable (a chatbot keyword, a form abandonment pattern, a search-term cluster), an offered callback when the journey reaches a high-stakes step, a defined handover protocol from digital to human with the customer's context preserved, and a specialist queue with sufficient skilled capacity to handle the moment without rerouting. Where the customer must initiate, the path to a human must be visible and direct — not buried under self-service options that the customer has to bypass. The design test: at each named human moment, what is the path from the customer's first signal to a trained human, and how long does it take?

    Measure for harmful deflection, not contact volume

    The standard metric set — call volumes, average handling time, chatbot containment, self-service rates — is calibrated against the average interaction and is insensitive to the cases that should not have been deflected. The pattern requires a measurement layer that distinguishes legitimate digital deflection (the customer wanted self-service and got what they needed) from harmful deflection (the customer needed a human and was prevented from reaching one). Channel-mismatch complaints, post-interaction outcome surveys focused on customers in distress, repeat-contact analysis, abandoned-and-not-recontacted cohorts, and outcomes for cohorts crossing the named moments are the relevant data. The design test: does the firm's measurement set reliably surface the human moment that was missed, or does it reward the firm for missing it?

    • The firm has a current and reviewed list of human-required moments per product and journey, with evidence supporting each entry and named owners for the design and operational delivery of those moments

    • At each named human moment, the customer's path to a trained human is documented end-to-end — including detection signals, routing logic, handover protocol, specialist queue capacity, and target time-to-human — and tested against representative cases

    • Outcomes monitoring distinguishes legitimate from harmful deflection: channel-mismatch complaints, repeat-contact rates, abandoned-and-not-recontacted cohorts, and customer-distress indicators are reported alongside contact-volume and containment metrics

    • Cross-channel context propagation prevents customers having to re-disclose at the human moment — the bereavement, financial difficulty, or vulnerability disclosure made on one channel is visible to the human handler on the next, without the customer being asked to repeat the information

    • A retail bank reviewed customer journeys involving bereavement and power of attorney following the FCA's multi-firm review of vulnerable customer treatment. The review had found common failures: bereaved customers having to repeat sensitive information across multiple staff members, cases dropped or lost in fragmented CRM systems, and limited availability of online or app channels for attorneys, with access constrained by historical investment decisions rather than technical limits. The bank rebuilt the journey around two human-required moments: first contact after a death, and the operational handover when an attorney first acts on the account. A single specialist team was given end-to-end ownership of each case, the customer's context was preserved across all interactions through a unified case record, and the chatbot was reprogrammed to detect bereavement keywords and route immediately to a named handler with the conversation transcript already attached. App-based access was extended to attorneys, removing the differential channel access the review had flagged. Within a year, repeat-information complaints from bereaved customers fell substantially, average days to defund accounts shortened, and senior MI began to track outcome measures — distress reduction, customer satisfaction at completion — alongside SLA performance, which the review had warned could otherwise dominate the picture.

    • A wealth platform analysed digital engagement on its drawdown decision tool and found that customers who spent more than three times the average session duration without progressing were significantly more likely to complain about retirement decisions in the months that followed. The platform treated drawdown initiation as a named human-required moment under the pattern. Real-time behavioural monitoring was introduced: when a customer crossed the duration threshold without progression, the journey paused and offered a callback from a retirement specialist within a stated window, with the option to continue digitally if preferred. The flag persisted in the customer record so the next quarterly review, the next withdrawal request, and the next adviser meeting were all aware that the customer had previously hesitated at a defining decision. The platform also reviewed its outcome MI to add channel-mismatch indicators alongside the existing self-service success metrics, so the case where a customer self-served a high-stakes decision under stress would surface in monitoring rather than register as containment success. Complaint rates from the cohort fell, take-up of structured retirement guidance rose, and the FCA's research on digital engagement practices in investment outcomes provided supporting evidence that proactive design at high-stakes moments materially changes outcomes.

  • Common failure modes

    The most common failure mode is treating the pattern as a defence of voice channels in general. It is not. Most journeys benefit from digital optimisation; the pattern is precise about which specific moments must be human, and why. A second is using human availability as compensation for poor digital design — a callback offer when the customer has hit a confusing form is fixing the symptom, not the cause. A third is the channel-mismatch deflection: the customer who reaches the firm via chat about a bereavement, and the bot's natural-language detection misses the disclosure, so the message is queued for a routine response. The FCA's Consumer Support Outcome review specifically called out as good practice the firm whose chatbot automatically routed bereavement queries to a customer support representative — most journeys do not yet do this. A fourth is human-availability that is human-in-name-only: a script-bound agent at an outsourced service provider who cannot deviate from a flow is not a human moment in any operative sense. A fifth is conflating cost with capability — human moments are not unlimited and the Duty does not ask for unlimited human contact, but the firm that cannot evidence which moments warrant the cost has failed the design test that the pattern asks of it.

Related Patterns