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

...

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

The price matrix is per seat with a price per seat above the matrix being optional

Gliffy
imageAttachmentIdatt821493762
macroId2e0a4801-25ce-456f-805f-3bfff19de760
baseUrlhttps://saasplications.atlassian.net/wiki
nameShuttle Pricing Flow
diagramAttachmentIdatt821428234
containerId821428227
timestamp1644216547353

Where a price cannot be calculated

Where a price cannot be calculated > “manual pricing” will tick on.

  1. The customer portal will save the booking and not allow online payment
    a) changes the "Pay Now" button to read "Create Booking"
    b) saves the booking but do not prompt for payment
    c) show the "Thank You" dialogue with customised text to indicate that the customer will be contacted regarding pricing

The customer will need to be contacted and a price entered manually by the back office