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 actionDecisionOutcomeDesign note

Open each flow to follow its branches. On a phone, use landscape or scroll across the diagram.

01Create the request Coverage, city stops, traveller details, drafts and review
Create an SGT request: detailed user flowEnter 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 CREATIONALTERNATE PATHS + GUIDANCEYesNoYesNoYesNoSubmitEditRelevant stepOpen SGT in TrailConcur email link or direct entryChoose destination countryRead service and coverage guidanceDestination availablein the booking tool?Read destination guidanceContact TRM for help.Do not complete an unsupported intake.Select destination citiesReview city-level recommendationsEnter travel details for the cityArrival, pickup and accommodationService, vehicle and departureAnother cityin the itinerary?Add the next cityKeep each stop’s details togetherConfirm traveller detailsName, work email and phoneSame or different WhatsApp numberColleaguestravelling together?Include co-traveller detailsNames and travel needs suppliedthrough notes or an attachmentAdd attachments and notesInclude supporting trip informationReview the complete requestCheck itinerary and cancellation guidanceReturn to the relevant stepCorrect details, then review againSubmit requestContinue to approval routing belowSave and exitAvailable throughout the intake.Resume the draft at the saved step.Keep the entered details.Separate the meaningsA city recommendation is guidance.It is not an approval decision.Approval follows agreed request rules.Solid arrows: task sequence. Dashed arrows: return or resume. Destination rules and identifying details are simplified.
02Approval and provider handoff Automatic approval, TRM review and service communication
Approval routing and provider handoffThe 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 HANDOFFMeets criteriaNeeds reviewApprovedDeclinedCreate the submitted requestRequest Lifecycle Management APIsWhich approval routedoes the request require?Automatic approvalAgreed destination and request criteriaNotify TRM for reviewEmail prompts a human decisionTRM decisionRequest declinedDo not proceed to provider bookingApproved requestProceed to the provider handoffNotify the travellerRequest summary, provider contactand next stepsSend itinerary to the providerGroup details by city.Copy the traveller into the conversation.Provider confirms arrangementsContact expected within two business daysApproval is not confirmationTRM decides whether the requestcan proceed. The provider thenconfirms the transport arrangements.
03Change or cancel a request Edit boundaries, city removal, confirmations and cancellation
View, edit and cancel: detailed user flowFrom 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 + CANCELLATIONEditCancelNoYesYesNoConfirm removalKeep citySubmitBackNoYesOpen booking detailsReview itinerary, status and providerChoose a trip actionAt least 72 hoursbefore arrival?Contact the providerSelf-service editing is unavailable.Discuss changes directly.Edit the itineraryCountry remains locked.A new country requires a new request.Update city and traveller detailsReview travel needs, notes and group detailsRemove a city?Confirm city removalExplain that the city’s travel detailswill be removed from the request.Review the updated itineraryRemaining stops and supporting detailsSubmit changesto the provider?Keep editingDo not send changes yetChanges submittedProvider receives the update.Booking details show the modification.Review cancellation consequencesA fee may apply within 72 hours.Choose a cancellation reason:pricing, change of plans or other.Confirm cancellation?Keep the requestReturn to booking detailsRequest cancelledShow the cancelled status.Remove edit and cancel actions.Provider follows up if a fee applies.Cancel and exit while editingDiscard unsubmitted edits.Return to the last saved request.Leave the existing itinerary intact.Request states are supported by Engineering’s lifecycle APIs. These flows retain the operational boundaries of the MVP.
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.