Standard Ride Lifecycle
Request or schedule → validate booking → dispatch → accept → pickup → required verification → started → completed/paid → post-trip rating.
Read more →Request or schedule → validate booking → dispatch → accept → pickup → required verification → started → completed/paid → post-trip rating.
Read more →Rider receives PIN; driver verifies it before starting; if verification fails, do not start the trip and use support escalation as needed.
Read more →Prioritize immediate safety, contact emergency services when necessary, preserve records, document the incident and apply appropriate account controls during review.
Read more →Rider records needs when possible; driver reviews accommodations before acceptance; support/reassignment should be used when a legitimate capability issue exists.
Read more →Confirm return plan, track wait/return state and use the supported release/reassignment workflow if the original driver cannot complete the return.
Read more →Confirm days, dates, departure and optional return time; save same-driver preference when requested; allow pause/resume of future schedule generation.
Read more →Verify package and recipient details, capture required pickup proof, contact recipient only as needed, capture final proof and complete secure delivery confirmation.
Read more →Rider and driver ratings are recorded independently; allegations involving safety or policy violations should route to support review.
Read more →Validate organization, rider eligibility, department/program, policy and funding before creating or scheduling a managed ride.
Read more →Validate eligibility, apply expiration/limits/stacking, record redemption and sponsor impact, and record reward events idempotently.
Read more →Report with trip details, protect user contact information, arrange safe return and prohibit misuse of found property.
Read more →