
Journey Mapping
Part of Accessible customer experiences
Testing alternatives to a phone-only service process
Compare a phone task with another route from entry to verified outcome, including access, protection, ownership and follow-up.
undefined
Test a web form, monitored email or message route, or in-person service as an alternative to a phone-only process. Give participants the same customer goal through each route, then check whether it reaches the same usable result.
An email address or form counts as an alternative only if it accepts the request, passes it to a team that can act and returns an answer the customer can use.
Map the phone-only service process
Choose a specific task, such as disputing a charge or changing an appointment. Map the call: how the person finds the number, what information is requested, how identity is checked, what decision is made and how the result is confirmed.
Before designing another route, record which steps staff currently handle in conversation and why.
A web form can suit a structured request; a monitored email or message route can handle an exception; an in-person service route can suit a task needing staff involvement. Test each against the same customer goal.
Each option needs clear availability, a workable response process and a way to follow up.
Compare every route against the same task and outcome, while allowing different channels to meet different needs. Keep the journey map focused on what the customer must do and what the organisation must complete.
Compare a phone route with a web form
Worked example: test changing an appointment by phone and through a web form. Record the phone route as the baseline, then check whether the form lets a participant provide the needed details, correct an error and send the request to the team that can act. Follow both routes through to the outcome, not just submission.
Example test record (hypothetical): Phone route—appointment changed in the relevant record and accurate confirmation received: pass. Web form—request submitted, but no accurate confirmation received: fail. This comparison makes the outcome gap visible; the form passes only when it completes the same task and returns a usable result.
Set the success condition before testing and apply it to every route: the appointment is changed in the relevant record and the customer receives accurate confirmation. Track submission separately from completion, and record errors, recovery and whether staff intervention was needed.
In a safe test, check the simulated service outcome; verify a live outcome only through an authorised process.
Phone vs Web Form: Changing an Appointment
- Task Outcome
- Appointment changed in record and accurate confirmation received
- Phone Route Result
- Pass
- Web Form Result
- Fail (no accurate confirmation received)
Test ordinary and difficult cases
Invite people who have relevant access needs to use a safe test version of the route. Include a routine request, missing information, an incorrect entry and a case that needs staff judgement.
For a web form, use WCAG 2.2 as the accessibility reference and check keyboard and assistive-technology use. W3C's Forms Tutorial covers labels, instructions, input validation, correction options and notifications of completion or errors. W3C's Easy Checks provide a first review of web accessibility; a few checks can indicate overall accessibility.
Then trace the request beyond the interface. Did it reach the right team? Could staff act without making the customer restart by phone? Was the promised update sent, and was the outcome correct?
Keep unsuccessful and unknown cases visible. Consider replacing a mandatory phone step only when the alternative can carry that task through to its outcome with appropriate controls.
Testing Alternative Service Routes
- Define the customer goalChange an appointment
- Map the phone-only processRecord steps including identity check, decision-making and confirmation
- Design alternative route(s)Web form, monitored email or in-person service
- Test with real users including those with access needsInclude routine, missing data, incorrect entry and complex cases
- Verify end-to-end outcomeRequest reaches right team, staff act without restart, correct update sent



