Ride requests
Publish your travel need when no trip fits — how requests work, what they do, and what they honestly do not.
A ride request flips the marketplace around: instead of searching for a trip, you publish where and when you need to travel, and drivers planning that corridor see real demand. This guide covers when to post, what happens next, and the one thing a request is not — a reservation.
Posting a request
- Search first — A request is the fallback, not the first move: check the trips page (including the All mode and wider dates) before posting. If a suitable trip already exists, booking it directly is always faster.
- Post your need from your account — Describe the route, the date or window, seats, and your flexibility. The clearer the corridor and timing, the easier it is for a driver to recognize your request as matching a trip they could publish.
- Know what happens next — Your request becomes visible to drivers planning similar routes. When a matching trip is published, you are notified — and you book it through the normal secure checkout, like any other trip. Nothing is charged for posting, and nothing books automatically.
Tracking and booking
Follow your request in your passenger space
Active requests show their status and expiry. Requests expire on their travel date if unmatched — you can post a new one, ideally with more flexibility, or keep searching in parallel.
When a matching trip appears
You receive a notification; open the trip page and review it like any other — route, schedule, driver profile, amounts. If it fits, reserve through checkout. The request brought the trip to you, but the booking decision and flow stay entirely normal.
What a request is not
Not a dispatch order, not a guaranteed seat, not a negotiation channel. It is a demand signal — honest and useful, but a driver may never publish a matching trip. Keep searching while a request is open; the two work together.