Account & access · Everyone

The app lost connection during booking or a trip

Recover the current request before trying again.

What you can do

  1. Move to a safe place before checking the phone. Confirm data or Wi-Fi and reopen the app without clearing app data.
  2. Refresh the current trip or request status first. A delayed reply does not prove a booking or payment failed.
  3. Use the existing retry action for the same request. Do not repeatedly submit a new booking, collection or payout while the outcome is unknown.
  4. Keep the draft or displayed reference and describe the time and action that failed. Do not post screenshots containing access tokens or private contact details.
  5. For immediate danger, use your phone’s emergency-call options rather than waiting for the laptop or app connection.
Availability & policy

Local testing needs the laptop service and phone connection. Cross-network production recovery still needs acceptance testing.

When to contact support

If the issue remains unresolved, continue one support case under Account & access. Include the relevant reference if available and explain the outcome you need.

Support library v2.0 · reconciled local workflows · Global core · approved Country Pack rules apply
Article v2.0 · Operational guidance draft · local capability checked · Reviewed 2026-11-10 · English

Get help with Account & access

A journey reference is helpful but optional. Use sample details only: this form saves on your computer and does not email a team.

For immediate danger, seek appropriate local emergency assistance. Do not wait for a form, email or reply.