Passenger: set the waiting request.
Highway Wait captures the pickup location, destination and seats needed. Keep the request current, and stop waiting in the app when the plan changes.
All services
Highway ride matching
Highway Wait & Radar
Highway matching is a ride workflow, not just a route map. A waiting passenger shares their destination; a driver broadcasts an active route and seats, reviews matches, confirms boarding with an OTP and completes the journey.
A CLOSER LOOK
A highway pickup needs a route match, not just two pins.
Driver: broadcast the route.
Radar uses the active route and available seats to surface relevant waiting passengers. Review the pickup details before accepting; a nearby person is not automatically a suitable route match.
Both: confirm the handover.
The match has a boarding OTP and completion action. Use the trip's confirmation flow instead of assuming an accepted request means someone has boarded.
AN EVERYDAY EXAMPLE
A passenger waiting along the highway.
A passenger enters a pickup location, destination and required seats. A driver travelling along a compatible route starts Radar and reviews the waiting request.
Accept a suitable match, use boarding OTP and close the trip when it is complete.
APP UTILITIES
Tools in this part of BIDUAGO.
Rides: passenger Highway Wait and driver Highway Radar.
Passenger: I am waiting
Share a highway pickup location, destination and seat requirement.
Driver: Radar Mode
Publish an active route and available seats to discover relevant waiting passengers.
Route-based matching
Review a potential match along the route before accepting the pickup.
Boarding OTP
Confirm boarding through the match's OTP workflow.
Complete or stop the journey
Mark a matched trip complete or stop broadcasting the active route.
App workflow means the flow is implemented in the app source, not that the app is publicly released or every dependency is live. Check the app guide and the actual listing or provider status.
App access & release detailsACCESS & RELEASE
Choose the right app workflow.
Use the app guide to find the relevant tab or role. Account access, local coverage and external service configuration are separate requirements; a website description does not activate a service.
App tabs & rolesYOUR NEXT STEPS
How it works.
- 01
Passenger sets a waiting location, destination and seat requirement.
- 02
Driver starts Radar for an active route and reviews a relevant match.
- 03
Accept the pickup, confirm boarding by OTP and complete the matched trip.
LOCAL COVERAGE
Know what to expect.
Matching needs participating users, location access and an active route. It is not guaranteed pickup, scheduled public transit or emergency assistance.
Join as a local partnerTHE DETAILS THAT MATTER
Your questions, answered.
Is Radar just a navigation map?
No. It is a route-based driver/passenger matching workflow.
Does waiting guarantee a pickup?
No. A participating driver must review and accept a suitable match.