Table of Contents:

• Rideshare v3
• HopDrive Lite Ride
• Admin v5 Updates

Rideshare v3

The rideshare system has been upgraded. Most of the upgrades are backend improvements.

• What does this mean?
  • Better visibility into why rides are failing.
  • Auto-retry if rides fail
  • Uber rides should fail much less often than they used to.
  • Time estimates for rideshares are visible in the driver app
  • Faster & easier implementation of potential future rideshare partners.

Other notable rideshare updates:

• Ridehailing has been added for HopDrive Lite users.
• New UI for HopDrive Lite users to help manage & track their rides.

Automatic Ridehail Retry and Ridehail Attempt History

Below, you can see an automatic retry of a failed attempt to call an Uber, as well as the ridehail attempt history that shows the failure reason.

Ridehail Arrival Estimates in the Driver App

On the ridehail screen, drivers will now see an estimate of the ride's arrival time to better time their trips.

HopDrive Lite Rides

Hopdrive Lite customers can now call rides (controlled by customer settings).

Key Features:

• Option to call rides for drives when dispatching moves to drivers
• Rideshare can be called from Portal or in the driver app
• Rideshare Details page with all the information from rideshare provider about ride Details
• Rideshare Index page to track past, future, and active rideshare

Demo

Admin v5 Updates

Steps have been taken to get Admin v5 closer to being our main platform for day to day operations.

• The unassigned moves screen has now become "scenario"-based.

  • Scenarios are a combination of drive moves and ride moves that make up a real-world scenario.
  • You can filter down and select which scenarios you want to plan in admin v4 or v5.

• Planning in admin v5 has been added. This new type of planning presents a few core changes to how planning works.

  • Planning will now create "bundles" of moves, instead of an ever-changing driver plan.
  • Bundles are structured chunks of moves that must be accepted by a driver.
  • Bundles can be assigned to a specific driver, similar to an old-fashioned plan. Or they can be broadcasted to a number of drivers until the driver accepts.

• NOTE: There is still work to be done on Admin v5 planning. It is usable, but may not have all of the tools needed for day-to-day operations.

Unassigned Demo

Planning Demo