Start with one representative exception
Choose one consented or safely simulated cancellation request. Identify the original message or call record, the authoritative service record, the person allowed to decide the exception, and the people or commitments that can be affected. Do not let a form submission silently become the cancellation decision.
A service blueprint is one way to show relationships among people, artifacts, and process steps. The map here is a representative scenario; it does not show how another service's policy, payment, or customer relationship works.
Separate receipt from authority
The person who receives a request may be allowed to record it without being allowed to cancel a commitment, grant a credit, or reassign work. Name the request-recording owner, authoritative record owner, exception decision owner, notification owner, and recovery owner independently. If policy or a financial decision is unresolved, keep the request in a visible hold state. A generic "cancelled" label hides the decision a later operator needs to make.
Walk the map before choosing an automation
Use this map with a second operator. Fill each stage from the original request through confirmation or recovery. The smallest useful improvement may be a shared handoff and acknowledgement rather than a new portal feature.
| Stage | Original artifact | Authoritative record | Decision owner | Affected commitments | Hold | Confirmation or recovery |
|---|---|---|---|---|---|---|
| Receive request | __________ |
__________ |
__________ |
__________ |
__________ |
__________ |
| Identify request | __________ |
__________ |
__________ |
__________ |
__________ |
__________ |
| Decide and record | __________ |
__________ |
__________ |
__________ |
__________ |
__________ |
| Notify and reallocate | __________ |
__________ |
__________ |
__________ |
__________ |
__________ |
| Confirm or recover | __________ |
__________ |
__________ |
__________ |
__________ |
__________ |
Stop the automation discussion if the team cannot identify the authoritative record, decision owner, affected commitment, policy or financial hold, or recovery confirmation. A button cannot supply missing authority.
For a request that begins in text, see Map a Client Request That Begins in a Text Message. For a cross-team handoff, see Map the Field-to-Office Service Handoff.
Should every cancellation follow the same workflow?
Not necessarily. The accountable service owner should define which differences change authority, commitments, or recovery. The map reveals those branches before a tool turns them into invisible rules.