Journey Mapping
Part of Omnichannel customer experience
Preserving context when customers change channels
Learn what to carry into a new service channel, how to handle corrections and verification, and how to check whether the handover works.
Give the next authorised team a short, accurate record of the customer's goal, what has happened and what remains to be done. A case number alone is not enough if the person opening it must reconstruct the story. The customer should be able to continue the task and correct a mistaken summary.
Define the minimum useful record
Start with one common switch, such as a customer leaving webchat to call about an order change. Follow representative cases and note what the receiving agent needs to act. A handover record may contain:
- the customer's requested outcome and preferred contact route;
- the relevant order or case reference;
- what the customer has supplied and which checks were completed;
- the current blocker, next action, owner and any promised update;
- the source and time of information that may change, such as order status.
Record the customer's account separately from a staff diagnosis. “Customer says the replacement has not arrived” differs from “courier lost the parcel”. Mark uncertainty until it has been checked. A concise summary may be easier to use than an entire chat transcript, with authorised detail available if needed.
Make the switch dependable
Tell the customer what information will carry over before asking them to change channel. Give them a reference to use if the systems fail to match the contact. At the receiving end, show the summary at the start of the interaction and allow the agent to update it. Record a customer correction so the next person sees it.
Distinguish a new contact about the same task from a new task by the same person. Otherwise, an earlier answer may be attached to the wrong issue. Check delayed switches too: a customer may email after a chat closes or call after submitting a form but before another team has acted.
Control access and explain verification
Context sharing involves personal information. Limit the record to what is needed, control which teams can see it and apply an appropriate retention rule. A receiving agent may still need to verify identity before discussing protected account details. Explain that safeguard without asking the customer to repeat unrelated facts.
For organisations subject to the Australian Privacy Principles, collection and security requirements depend on the information and circumstances. Sharing between teams may raise further questions about permitted use or disclosure. Have the relevant privacy and security owners review the proposed flow before implementation.
Check the receiving view
Check a routine case, a mistaken summary and a case where the customer cannot use the original channel again. Can the receiving person identify the goal, avoid unnecessary re-entry and take the promised next action? Record any facts the customer still has to repeat, why and who owns the gap. Continuity of the task matters more than whether two systems exchanged data.
