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

If the customer logs in again and has an existing booking they will see it at the top of the screen - see the green line

...

The booking will then be ready for adding to a Bus Run

Booking confirmation email template

  • Email Template for the booking confirmation

    • Usage context = Booking

    • System Usage = Order/Booking Payment Receipt

    • Recipients Role = Customer

...

Booking Time calculations

Bookings use the following logic to calculate times

  1. The

...

  1. destination must be on the booking

  2. The address must be on the booking with a suburb/postcode

  3. The date must be entered

  4. A time is required

    1. Flight or ship time

Booking changes

The customer has not been allowed to make changes to their bookings - they will need to make a phone call.

If a booking has already been paid for it cannot be changed

  1. it can be cancelled and a replacement booking entered

Bus Runs that are a number of Routes

Bus runs have Legs and each Leg can be a route.

Bookings will attach to routes based on time

Bus runs that are Ad-hoc

Bus Runs have Legs and each leg is TO or FROM a destination (or group of destinations where they are linked using a TAG).

...

  1. View their runs today and in the future

  2. Confirm they have done a vehicle check

  3. Start their run

  4. Be shown the next address to go to

  5. Mark passengers on-board / missed / or end of leg

  6. Back to 4 until day is finished

...

End to End flow of a shuttle booking

The system include full financials (GL/AP/AR etc)

Gliffy
imageAttachmentIdatt821329925
bordertrue
macroIdf0da9f56-7c90-4a7c-bb89-a5b2160d26dc
baseUrlhttps://saasplications.atlassian.net/wiki
nameShuttle Bus Booking Flows
diagramAttachmentIdatt821035013
containerId821428227
timestamp16442164832881644808005119

...

Pricing logic

Each customer may use a different pricing logic - below is an example

...