Notable logic changes in scheduled booking dispatching
Current approach
- When a driver claims the booking, they become a preferred driver of the booking.
- 60 minutes before the scheduled time, a preferred driver receives a booking request that they need to accept to start the booking.
New approach
- When a driver claims a scheduled booking, they become a driver of this booking.
- An admin can not add preferred drivers to the claimed booking.
- The driver will not receive a booking request 60 minutes before the scheduled time.
- The driver is expected to start the claimed booking manually X minutes before the scheduled time, where X is a configurable value.
- The timestamp of X marks the beginning of the time period within which a driver can start the booking. After this period expires the driver can no longer start the booking. The period length is configurable.
- The system extensively reminds the driver about the claimed booking they must start.
- The driver can start the booking regardless of their current location.
- When the driver starts the booking, the system makes sure the driver is online and has the right capabilities.
- If the driver fails to start the booking on time, the booking gets offered as an Instant booking to all eligible drivers.
- An admin can reject the booking on behalf of the driver via the dashboard.
- An admin can use the Preferred drivers feature to target certain drivers with the scheduled booking requests.
- Claimed scheduled bookings have Accepted label on the dashboard.
- The new booking claiming approach doesn't impact the customer experience. Customers won't be receiving any new push notifications or emails.
Notable changes in the app
All-new home screen