Frequently Asked Questions

Yes. Where supported by the browser or application, YAVA can use voice input to help enter your pickup and destination. You can still search manually whenever you prefer.

Yes. YAVA is designed to show the actual pickup point associated with a ride. Nearby ride matches should not be presented as though they start exactly from the location you entered.

YAVA can match journeys using pickup, destination, timing and configurable nearby-location rules. The platform is designed so these matching rules can evolve as the service expands.

Yes. When seat selection is enabled for a vehicle, available passenger seats can be displayed using the seating layout configured for that specific vehicle model.

Yes. Vehicle seating is tied to the configured vehicle model. A sedan, MPV or other vehicle type can therefore display a different number and arrangement of passenger-selectable seats.

The platform is designed to show the relevant vehicle model and seating information for the ride, so passengers can understand the type of vehicle being offered before booking.

Basic ride discovery may be available without login depending on the active platform configuration. Account verification or login can be required before confirming a booking.

YAVA can use OTP verification for mobile-based authentication. The exact verification flow may depend on the application and account configuration currently in use.

No. Uploading documents and receiving verified status are separate steps. Verification should depend on completion and approval of the required checks.

Yes. Logged-in passengers can access relevant upcoming, active and historical ride information through their account or mobile application.

Cancelled rides are handled separately from completed rides. Any related booking, payment, refund or reward treatment depends on the applicable ride and payment rules.

Yes. The driver application is designed to support trip management, passenger information, seat availability and other relevant journey activity.

YAVA Family is designed to allow eligible users to join a family group while keeping their own individual YAVA accounts. Completed eligible rides can contribute toward family ride progress.

A YAVA Family Group is designed to support between 2 and 6 members, subject to the active platform rules.

No. Family ride progress is intended to count successfully completed eligible rides. Cancelled, rejected or no-show bookings should not be counted.

No. Reward targets, reward types and eligibility rules can be configured by the platform rather than permanently hardcoded into the application.

YAVA is designed as a shared-mobility platform and can support suitable local or intercity use cases depending on the routes and services available in your area.

You can use the Contact Us page for general enquiries. For booking-specific or account-specific concerns, provide the relevant account or booking information when requested.