RIDE SERVICE REQUESTS · Workflow idea
For a passenger who has explicitly authorized an approved travel assistant, review ride types, cost estimates, pickup timing, and limited profile details, then prepare a requested trip operation. Protect location and account information, verify pickup and destination with the passenger, show price and cancellation implications, and require fresh confirmation before requesting, canceling, changing, rating, or tipping for a ride.
01 / The starting point
A verified passenger request and an authorized account connection
“Present accurate trip options without exposing profile data or taking an unapproved ride action.”
02 / The work
Helps a passenger review ride estimates, nearby driver information, trip details, and supported ride actions.
Confirm the account owner requested the specific lookup or ride action.
Check trip details and explain that price and arrival estimates may change.
Use only details needed for the selected trip and keep them private.
Show cancellation, destination, rating, or tip details before submission.
Require fresh confirmation for requests, cancellations, changes, ratings, or tips.
03 / The result
A verified ride estimate or action preview with passenger confirmation status.
Customer support · Example outcome
A verified ride estimate or action preview with passenger confirmation status.
Ride requests, cancellations, destination changes, ratings, and tips affect real people and may incur charges. Share location only when needed, verify the passenger and trip, explain current price and timing limits, and require explicit passenger approval for every consequential action.
04 / Make it yours
A few choices shape the work around your team.
Prevent other users or inferred requests from initiating travel actions.
Use precise trip data only for the active, authorized request.
Show relevant costs, pickup, destination, and estimate uncertainty.
Keep requests, cancellations, destination changes, ratings, and tips behind approval.