Start with the outcome, not the inboxes
Choose a safely simulated or consented, redacted scenario. Name the outcome a client seeks and capture each message separately with its channel and received time. Record the first follow-up separately too: who sent it, when, and its observed result or unresolved state. Do not merge messages merely because the sender, words, or timing look similar.
Nielsen Norman Group's service-blueprint definition is used only to make people, actions, and support processes visible. This representative map does not describe a client, contract, or observed result.
Make matching a visible review step
Use the accompanying repeated-request map to record the matching inputs and the named authority who may call a later message the same request, a distinct request, or unresolved. Then name who instructs staff and who communicates the current state to the client.
| Hidden assumption | Question to make visible |
|---|---|
| Same sender means same request | Which matching inputs and exceptions are approved? |
| A retry means nothing happened | What record shows the first follow-up and its observed outcome? |
| Automation can merge work | Who owns an ambiguous match before work begins? |
| The client only needs a confirmation | Who corrects an unclear or repeated message? |
Stop where matching has no owner
Pause automation if the intended outcome, intake channels, matching rule, decision authority, record owner, contact owner, staff instruction, or escalation path is unknown. A shared manual record can be a smaller and more useful improvement than an automatic deduplication rule.
For another intake exception, see Map a Client Cancellation Exception Before Automation. For uncertain payment and appointment records, see Map Payment Captured While an Appointment Remains Unconfirmed. For work after acceptance, see Map a Client Request After Accepted Work Before Automation.
Does this map decide that two client requests are the same?
No. It makes the inputs, decision, people, and recovery route inspectable. An authorised service owner must complete and review the map before treating it as operating policy.