Use Sidebar LHS to navigate
For global help click here

Drivers Planning runs

Owned by Paul Sawkins
Last updated: 03, Jul, 2023
3 min read

Summary

All drivers can see all bookings and can mark themselves as driver to any they commit to doing

Buses have a device (eg iPad) the driver logs into

  1. Driver is identified but does not have own separate log in

  2. Device needs to know the driver so driver can easily add bookings to them as a driver

Bookings fall into two categories

  1. From a destination (eg the airport) - regular services mean there is no need to schedule the bookings - simply mark them onboard when they present

  2. To a destination - especially if not a regular stop - need to be linked to a driver so they know to pick them up

Experienced Drivers working as a team can plan their own runs by choosing bookings to pickup and are in constant contact with other drivers

Bookings are marked as picked up or no show by the driver

Booking times may change and this may impact on drivers

Portal view > can see all bookings

Manager Portal

Cannot pickup bookings but can assign them and can see all the bookings

  • Can enter a driver code - or overwrite a driver code

  • Can enter a new pickup time (changes sequence in the grid)

Driver Portal

Drivers logs the bus in

Driver Identifies

Some companies have the driver login as the bus (username / password)

To identify the driver - the driver then logs in using their 3 letter code and password

Driver drives and updates bookings

The drivers 3 letter code (AKA) becomes their identification in the grid

Can assign bookings to themselves (Tick Me) or others (by entering the drivers AKA)

Can view only their bookings (on by default) can view completed (off by default)

  • Normal use the grid shows only incomplete bookings assigned to them

Completed also includes missed bookings (no show flag)

Customer Greeters Portal

Where a customer wants a view of the portal showing the bookings they are the booking entity

Login as a Shuttle Greeter

Shuttle Greeter View

The portal view provides where the booking is being dropped off and the name and contact details for the booking.

The greeters can then meet customers as the are due to arrive using the status of “on board” to indicate the driver has picked up the passenger. Passengers may not go directly to the shuttle and so the status is considered the most accurate.

If a passenger is under age that will be indicated in the view

How to Setup Shuttle Greeter Logins

Where a debtor has multiple drop off points - example a university. Define each drop off point as an address on the Debtor as a “Shuttle Stop” so the booking will show this as the end destination

  1. Debtor to have “Allow Login” ticked and default roles of “Shuttle Greeter” and “Referrer or Delegate Bookings” - this allows persons to be given login roles

  2. Debtor to have the person who will login as a contact

  3. The contact is to have “Allow Login” Ticked and roles of “Shuttle Greeter” and “Referrer or Delegate Bookings”

  4. The contact will show with a green tick indicating they can login

 

For information about SaaSplications go to http://saasplications.com.au