Table of Contents:

• Shuttle Planning v2
• Offer Based Dispatching
• Portal Move Form Time Changes

Shuttle Planning v2

Version 2 of shuttle planning is here! Users now have more control over the way plans are created and can even edit them after creation. Here are some notable features:

• Adding/removing/swapping moves in the group plan
• Adding/removing shuttle moves (shuttle drivers will no longer have 40+ moves showing up in their plan if the group plan is edited)
• Autofill button that acts identical to how shuttle planning v1 would plan moves
• Adding/removing drivers from a group plan
• Showing move statuses in the plan
• Correctly reassign move workflows so the shuttle drivers no longer have to take pictures except for the first and last move of a group plan
• Better handling of back-end data to integrate with dispatch automation

Overall, the system should be much better suited to all of our shuttle usecases. We do plan on a v3 in the future to cover anything that was missed in this release.

Demonstrations

Offer Based Dispatching

In preparation for dispatch automation, we are transistioning dispatching to an offer based system. This should be a smooth transistion, with few visible differences. But here are some changes you will notice:

Driver App

• Notifications and the Inbox will show groups of moves instead of individual moves.
• These move goups are offers. The offers are created when the dispatcher syncs the plan to the app.
• Drivers will no longer need to accept/decline each move individually.

Admin

• Saving a plan will now generate offers.
• Because generating offers takes time, there may be a short delay between saving a plan and showing the sync button.
• There is a new section in Move Details with bundle and offer information.

Click here if the image is not showing above.

Portal Move Form Time Changes

The 90 minute "buffer" requirement for setting a move's ready_by time has been removed for all move types except concierge pickup and concierge-loaner pickup. This will allow the "ready by" time on these moves to represent the actual time the vehicle is ready to move on the Customer side. It will also allow quicker response time in planning, especially once the automated dispatching of concierge return moves begins. Becuase of this change we have also updated the language around times entry in the form and adjusted how the SLA delivery time is calculated for both concierge return and operational moves.

Click here if the image is not showing above.

HopDrive API

The 90 minute buffer requirement has also been removed for move requests (except concierge pickup moves). This will allow users to set the ready by to anytime not in the past.