Back in April we introduced our first ever gradual rollout feature – a new way to assign drivers to tours. For each tour, drivers are ranked based on how suitable they are. The dispatch engine then gradually offers the tour to drivers, starting with the top-ranked drivers.

This month we're rolling out the updated gradual rollout focusing on performance and better Tour ↔ Driver matches. Learn more about the feature in this Help Center article.

Sequential rollout ensures tours go to the best suitable drivers while avoiding simultaneous requests. By offering tours one driver at a time in ranked order, we aim to improve acceptance rates and have more predictable dispatch outcomes. This means fewer reassignments and less wasted time.

The new sequential mode will be heavily tested with an eye on performance and match quality. We'll be gathering feedback to refine the logic before expanding the rollout more broadly.

We've streamlined the rules that control which bookings and tours org managers can see. Now there's one simple rule: org managers can see a booking or tour if their organization is listed as a managing organization. All previously existing exceptions have been removed in favour of this single transparent approach.

We've removed a restriction that prevented org managers from dispatching bookings into tours using the Dashboard. Org managers can now perform dispatching without limitations, unless they are in restricted mode.

The Operations page is undergoing significant technical refactoring to push its performance even further. As part of this update, we're removing three filters: Organizations, Stop status, and Capabilities. You can still use these filters on the Bookings and Tours pages.

We're continuing to improve platform performance and stability across multiple areas. Key operations now run faster, and the platform handles high volumes more reliably.