Order Booking
Booking an ride and order lifecycles
Overview
A customer can book a ride using the Organization's Customer mobile app.
Consideration for support of Scheduled Ride
Driver Selection
When a Ride Order is confirmed, the driver selection process can be done in two ways - Manual or Automatic.
Manual Driver Selection
- When order is confirmed, a notification will be sent to an active
Admin - Admin selects a nearby driver from the available ones in the area
- When selecting a driver, a notification will be sent to the driver
- If the driver accepts, the order can be continued
- If the driver rejects, the
Adminneeds to select a new driver and try again
Automatic Driver Selection
- Any active Driver within a certain radius from the
Pick Uplocation of the ride will be searched - All active drivers found will be sent a notification for the Ride
- The first driver that accepts the ride will be selected
- When a driver is selected, other notification will be cancelled
- If no driver accepts, notifiy Organization's Admin and try again
Driver Status
| Status | Description |
|---|---|
| Offline | Driver is offline |
| Active | Driver is online and waiting for Order |
| In Order | Driver is currently in the middle of a ride |
| Lost Connection | Driver lost connection with Server (to check up on Driver and reassign ride to another driver if there are any issues) |
Order Status
| Status | Description |
|---|---|
| Accepted | Order is accepted and confirmed |
| Driver Assigned | A Driver has been assigned for the Order |
| Ride Enroute | The driver has currently enroute to the pick up location |
| Ride Started | Customer has been picked up and ride is started |
| Ride Ended | Destination reached and ride has been completed |
| Ride Cancelled | Ride has been cancelled |
Payment
Payment can be implemented in two ways:
| Mode | Description |
|---|---|
| Offline | Payment is done completely offline, where the customer pays the driver directly |
| Online | Payment is done from the Customer application |