| Table of Contents | ||||
|---|---|---|---|---|
|
Summary
Experienced Drivers working as a team can plan their own runs and pass bookings they cannot do to others.
Bookings are either from or to the airport. Some are paid in advance (individuals) and some are on accounts (invoiced in arrears).
Drivers indicate the bookings they expect to pickup (Portal on IPad)
Others may assign bookings to a driver - normally contacting them
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
Driver is identified but does not have own separate log in
Device needs to know the driver so driver can easily add bookings to them as a driver
Bookings fall into two categories
From a destination (eg the airport) - regular services mean there is no need to schedule the bookings - simply mark them onboard when they present
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
...
There is a list of bookings
organised by time
Coloured in or out
Column for driver (initials)
Column for status (picked up or no show)
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 filter to see view only my bookings
Reducing list (hide marked done)
Select a booking
Tickbox assign to me
Text box for person initials (drop down of used today)
Buttons
Mark Onboard (mark done)
Mark Missed
...
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
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
Debtor to have the person who will login as a contact
The contact is to have “Allow Login” Ticked and roles of “Shuttle Greeter” and “Referrer or Delegate Bookings”
The contact will show with a green tick indicating they can login