Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents

...

  1. Customers are individuals making bookings using an online website after authentication

    1. Referring organisations may provide a LOGO image to display to referred customers

  2. The booking screen may be a single page - or setup as a stepped wizard

  3. The customer may make a return booking and pay for it all at the same time

  4. The payment is online and the booking if not paid is not retained by the system

Booking screen

The fields can be arranged in any order or as a simpler stepped wizard easily

Phone number is setup on the host company > Contact Types > Key = CUSTOMERHOTLINE

...

The customer will then receive a booking confirmation email with an attached invoice

...

Ad-Hoc runs do not follow a schedule and bookings are commonly manually planned.

The run Bus Shift is made up of Legs Runs - TO or FROM destinations.

  1. Bookings can only be appended to legs that support the booking direction and destination

  2. Bus Shifts are offered with a right click on the booking

    1. The logic for finding viable Runs within a Bus Shift
      a) the Run is a matching booking type (inbound vs outbound) from the destination
      b) the Run has bookings attached
      c) the bookings pick up time <= the Run latest drop off time
      d) the bookings drop off time >= the Run earliest pick up
      e) the booking pick up time falls within the earliest pick up to latest drop off duration OR the booking drop off time falls within the earliest pick up to latest drop off duration

    2. if a Run is deemed viable but either the pick up OR drop off time is outside the earliest pick up to latest drop off duration, then highlight this fact to the user but still allow for the booking to be added to the Run

    3. do not allow a booking of incompatible booking type to be added to a Run

A view of the day and bookings shows

...