One journey, several handoffs
Imagine a visitor understands your service, sends a brief and then hears nothing. The page may have done its job, but the experience has stalled. Website design and the team’s response process need to connect.
For the research method behind fuller journey maps, read Nielsen Norman Group’s Journey Mapping 101.
THE JOURNEY CONTINUES AFTER THE CLICK
- 01UnderstandThe visitor finds a relevant service.
- 02EnquireThey know what they are requesting.
- 03RespondAn owner acknowledges the request.
- 04Next stepThe customer knows what happens next.
Ask for information you can use
An initial form should help the next conversation. Decide which information is necessary now and which can wait. Explain what the visitor is requesting. Do not present a request as a confirmed appointment, booking or order.
Agree who responds and what they need
For each contact route, identify an owner and a realistic response expectation. Decide how a request moves between people and how the team avoids asking the customer to repeat everything. Tools can support the process once the process itself is clear.
MAKE THE HANDOFF VISIBLE
- 01RouteWhere does the request arrive?
- 02OwnerWho takes responsibility?
- 03ContextWhat must move with the request?
Walk through your own enquiry
On a phone, try the journey from a service page to the contact route. Check labels, errors and what appears after the action. Then review the team handoff with a fictional enquiry. Record the point where responsibility or next steps become unclear.
Note These are illustrative situations and practical discussion prompts. Recommendations depend on your business context and available evidence.