UX Patterns Guide
My learning 0 of 20 lessons complete
Start lesson 1 →

Unit 5 · Lesson 18 of 20

Coordinate the service across channels

Align kiosk, reception, phone messages, and backstage events around one patient status.

Ready to learnLearn the method, study the case, make a decision, and build your case file.
YOUR LEARNING PATH
18 / 20

01 / Learn

Learn the method

Fictional case

Mira can check in at the kiosk, ask reception, and receive an appointment update on her phone.

Terms for this lesson

Channel
A route through which a person interacts with a service.
Service blueprint
A map connecting visible experience with staff and system work.
Channel handoff
A move between routes that carries status, context, or responsibility.

A service crosses channels whenever a person moves between interfaces, messages, and people. A patient may read a kiosk receipt, ask a receptionist, then receive a delay notice by phone. These touchpoints should describe the same underlying appointment state and offer a fitting next action in each setting.

A service blueprint adds the work behind the patient journey. Put patient actions on the top row, visible staff and interface actions below, and backstage systems beneath them. Connect each patient message to the event and owner that supports it. The receipt, queue refresh, and delay update then occupy distinct places in the blueprint.

Channel consistency comes from shared meaning. A kiosk can give a short receipt and waiting instruction. A phone message can carry a changed appointment time. Reception can explain a queue delay and resolve a mismatch. Their wording can differ while the appointment status and promise remain aligned.

Trace one interruption across every channel. During an appointment delay, identify the source of the new time, when each channel updates, and how a patient gets help. Test the full route with a patient and a staff member so the blueprint reflects actual work.

Use the method

  1. Put patient actions, visible channels, staff work, and systems on aligned rows.
  2. Connect each message to the event and owner that supports it.
  3. Trace one interruption across the channels a patient may use.
Key distinction

Connected channels share a source of truth and give people a useful next action for their setting.

Read alongside this lesson
See the idea in action →

02 / See the reasoning

Worked example

A receptionist changes Mira's appointment to 10:30. The appointment service stores the new time and triggers a phone message. The kiosk status page reads from that record, while reception sees it after the next queue refresh. The team marks this interval in the blueprint and gives staff a direct lookup route. Mira receives the same 10:30 expectation wherever she asks.

Try a decision →

03 / Decide

Guided decision

The appointment service stores a new time at 09:40, the phone message sends at 09:41, and the staff queue refreshes at 09:42. Which blueprint detail most helps the team coordinate the interval?

Choose the option you would try first

04 / Build the case

Your case file

Fictional case update

A patient has changed phone numbers since registration and asks reception for an appointment update.

Evidence and constraints

  • Fictional service fact: the appointment service is the source for current appointment time.
  • Fictional channel detail: phone messages send after the appointment record changes.
  • Fictional operations detail: the staff queue refreshes separately; reception can query the record directly.

Add this route to the blueprint. Show how reception verifies the current time, communicates it, and updates the patient's contact preference.

Create: A service blueprint fragment with patient, channel, staff, system, and recovery rows.

Review your work against these criteria

The blueprint connects every patient promise to a current service event and an owner across channels.

  • Patient-visible messages have named sources.
  • Update timing appears for each channel.
  • A patient with a changed contact route can still learn the current appointment state.
Where this leads

The blueprint shows the complete service choice. The next lesson records why the team chose it.

05 / Keep working

Related patterns

sync statenotification centererror state

Apply this skill: Design decision memo and state model →

Saved items