Client site (public pages)

• The “Book Now” page on the public site collect a basic booking (One-way or Return to the same routes -  ie only 1 or 2 journeys, same combinations).   
  • The backend can be used for more complex ones.
  • Unlike a backend booking, we should sequence the collection of data….  ie the client wants to know prices and options first, before typing in their details and payment details. 
• This site does it brilliantly:  https://www.mountaindropoffs.com.  
  • Please try making a fake booking (don't save anything, just click out before payment - they are nice people) their site.  
  • It is amazing and super well thought out site. Best in the business. 
• This is what you will see.  All on one page but with tabs to make it quick 
  • Step 1 is picking the dates and destinations
    • Number of pax
    • Destination list
      • Nice details: Return date can't be before Outbound date
      • Second journey defaults to the reverse of First journey
        • Dates remembered if you unclick Return and back again
  • Step 2 is flight data or address and then the service type/price
    • If airport: flight
    • if non airport:  Address
      • Then picking the Shared/Private/Private+ with price 
  • Step 3 is collecting contact details, names/emails/telephone/babies etc and luggage
    • Nice way to get international codes
    • Look at the extras (babies, luggage)
  • Step 4 payment
• The design of this is 100% optimal (the owner is very experienced and logical) and we did exactly the same, but my old site has been changed so I can't show you that

Now all of this is the same as the booking entity and the (1 or 2) transfers in that booking.  Make senses?