Booking Support
Use this when a live or upcoming ride needs action, clarification, or a fast answer before pickup.
Contact
Talk to the Right Team Before the Journey Starts
Use the route that fits the job. Urgent booking support should move faster than a corporate setup request, and a new coverage request should not get buried inside a generic inbox.
Corporate Enquiries
For company-wide travel programs, recurring executive transfers, events, and billing workflows.
Coverage Requests
If your required city, airport, or route is not visible yet, send the market and expected usage.
Partner Onboarding
Supply-side partners should use the onboarding portal so approvals, documents, and dispatch readiness stay auditable.
Fast Routing
Use the shortest path to resolution
For most public users, the fastest route is still the booking flow itself. Start with the ride request so pickup, destination, vehicle class, and timing are already structured before a human needs to step in.
For corporate teams, send the cities, expected monthly volume, booking ownership model, and billing expectations. That gives operations enough context to propose a workable setup instead of another discovery loop.
- Live ride or urgent support: include booking ID and pickup time
- Corporate setup: include expected cities, traveller profile, and monthly volume
- Coverage request: include route, expected timing, and cabin class expectations
- Partner enquiries: use the partner portal where possible
Prefer a structured workflow?
If the request is already clear, start with the booking flow or partner onboarding so your details land in the right queue.