We’re making the ride experience more efficient for both drivers and riders.
Drivers can now accept a new trip request before completing their current one.
This means less downtime for drivers and shorter wait times for riders.
Here’s how it works:
The system compares the total distance from an idle driver to a pick up point and an active driver’s future drop-off point to the rider’s pickup location.
If a driver who’s finishing a trip will be closer in distance to the next pickup than an idle driver, they’ll receive the request.
Riders will see a note in the app: “Driver is finishing another trip nearby.”
In the driver app, the incoming request appears as an overlay, showing the distance from the current drop-off to the next pickup.
Once the first trip ends, the new one begins automatically.
This update helps maximize driver productivity and ensures riders get matched faster — creating a smoother, more connected ride experience for everyone.
Note that there is also a multiplier for the ride sequence, so the driver with no active rides gets prioritized compared to a driver dropping off a customer, in case the distance is more or less the same for both of them to pick up the new customer.
The distance to the next customer for the driver with the active ride gets updated with a multiplier extending the distance to the next pick-up when compared to a driver without a current ride. By default, the multiplier in the system is 1,3.
For example, a driver without any rides currently is 5km away from the customer pick-up location, while the second driver has an active ride, he is 1km away from the current customer drop-off location and has another 3km to the pick-up location of the new customer. In this case the first driver without an active ride gets the new customer's ride request first, because his 5km are closer compared to the other driver's 4km (1+3km) multiplied by 1,3.
NB! Please note that any ride request is sent to drivers within the defined radius. However, in trip stacking, the system takes into account the radius from the drop-off point of the active driver, instead of his current location. In the idle driver's case, the system will calculate the radius from the driver's active location.
Preview from Driver app:
NB! The 'Trip stacking' feature can be enabled or disabled for the platform in the dashboard's System preferences (this is disabled by default).
