Amazon SGT detailed user flows ← Back to the Amazon case study
DETAILED USER FLOW
Work through the decisions before refining the interface. Request creation, approval routing and the changes that follow.
Screen or action Decision Outcome Design note
Open each flow to follow its branches. On a phone, use landscape or scroll across the diagram.
01 Create the request Coverage, city stops, traveller details, drafts and review Create an SGT request: detailed user flow Enter SGT from Concur or Trail, understand the service, check destination availability, add cities and travel details, provide contact and co-traveller details, add notes, review and submit. Unavailable destinations lead to TRM guidance. Additional cities loop back to itinerary entry. A saved draft resumes at the saved step. Review edits return to the relevant step. 01 / REQUEST CREATION ALTERNATE PATHS + GUIDANCE Yes No Yes No Yes No Submit Edit Relevant step Open SGT in Trail Concur email link or direct entry Choose destination country Read service and coverage guidance Destination available in the booking tool? Read destination guidance Contact TRM for help. Do not complete an unsupported intake. Select destination cities Review city-level recommendations Enter travel details for the city Arrival, pickup and accommodation Service, vehicle and departure Another city in the itinerary? Add the next city Keep each stop’s details together Confirm traveller details Name, work email and phone Same or different WhatsApp number Colleagues travelling together? Include co-traveller details Names and travel needs supplied through notes or an attachment Add attachments and notes Include supporting trip information Review the complete request Check itinerary and cancellation guidance Return to the relevant step Correct details, then review again Submit request Continue to approval routing below Save and exit Available throughout the intake. Resume the draft at the saved step. Keep the entered details. Separate the meanings A city recommendation is guidance. It is not an approval decision. Approval follows agreed request rules. 02 Approval and provider handoff Automatic approval, TRM review and service communication Approval routing and provider handoff The submitted request is created through the lifecycle APIs and evaluated against agreed destination and request criteria. Eligible requests follow automatic approval. Other requests notify TRM for review and an approval or rejection decision. Approved requests notify both traveller and provider. Provider confirmation is separate from approval; the provider is expected to make contact within two business days. 02 / APPROVAL + SERVICE HANDOFF Meets criteria Needs review Approved Declined Create the submitted request Request Lifecycle Management APIs Which approval route does the request require? Automatic approval Agreed destination and request criteria Notify TRM for review Email prompts a human decision TRM decision Request declined Do not proceed to provider booking Approved request Proceed to the provider handoff Notify the traveller Request summary, provider contact and next steps Send itinerary to the provider Group details by city. Copy the traveller into the conversation. Provider confirms arrangements Contact expected within two business days Approval is not confirmation TRM decides whether the request can proceed. The provider then confirms the transport arrangements. 03 Change or cancel a request Edit boundaries, city removal, confirmations and cancellation View, edit and cancel: detailed user flow From booking details the traveller chooses to edit or cancel. Editing is available at least 72 hours before arrival, otherwise the traveller contacts the provider. Country changes require cancellation and a new request. City removal requires confirmation. Submitted changes update the provider. Cancellation requires a reason and explains the possible fee, with a keep-request path and a cancelled state. 03 / CHANGES + CANCELLATION Edit Cancel No Yes Yes No Confirm removal Keep city Submit Back No Yes Open booking details Review itinerary, status and provider Choose a trip action At least 72 hours before arrival? Contact the provider Self-service editing is unavailable. Discuss changes directly. Edit the itinerary Country remains locked. A new country requires a new request. Update city and traveller details Review travel needs, notes and group details Remove a city? Confirm city removal Explain that the city’s travel details will be removed from the request. Review the updated itinerary Remaining stops and supporting details Submit changes to the provider? Keep editing Do not send changes yet Changes submitted Provider receives the update. Booking details show the modification. Review cancellation consequences A fee may apply within 72 hours. Choose a cancellation reason: pricing, change of plans or other. Confirm cancellation? Keep the request Return to booking details Request cancelled Show the cancelled status. Remove edit and cancel actions. Provider follows up if a fee applies. Cancel and exit while editing Discard unsubmitted edits. Return to the last saved request. Leave the existing itinerary intact. Detailed interaction flows adapted for confidentiality. They connect the exploration questions to the request lifecycle, with the traveller’s actions, business decisions and return paths shown explicitly.