Omni Core · Customer Journey Mapping · Module

Channel handovers

What happens when a customer moves between channels or functions — where context is lost and where the experience most often fails.

The idea

How it works

Within a function the experience is usually competent. Between functions the customer explains themselves again, and repeated explanation is the single most reliably cited source of frustration in service research.

Handovers follow organisational boundaries, which means the fix is usually organisational rather than technical. A system that passes context is useless if the receiving team does not read it.

Working with it

In practice

  1. 01

    Count the handovers

    Every point where the customer moves between people, teams or channels. The count predicts the effort they experience.

  2. 02

    Record what is lost at each

    Context, history, commitments made. What the receiving side does not know is what the customer has to repeat.

  3. 03

    Check whether context is actually read

    Passing information and using it are different. Ask the receiving side what they saw.

  4. 04

    Remove handovers before improving them

    A handover that does not happen cannot fail. Removing one is usually cheaper than making it work.

One level in

The components of channel handovers

A component is something that exists afterwards which did not exist before — a deliverable or a mechanism, not an intention.

  1. The handovers

    Every point where the customer moves between people, teams or channels.

    Learn
  2. The context loss

    What the receiving side does not know, and what the customer therefore repeats.

    Learn
  3. The removals

    Handovers that were eliminated rather than improved.

    Learn

A handover that does not happen cannot fail. Removing one is usually cheaper than making it work.