| Admin System | Admin Users will have back-end access to the Admin System for the purpose of managing bookings and maintaining data. Users are assigned into groups which have set permissions. |
|---|
| Booking forms | Booking forms control the data collected from the end user (customer) when making the booking. Booking forms are created as part of the initial setup. Every product requires a booking form. |
|---|
| Booking views | Booking views include the List, Calendar, Seven Day, Seven Day Season, Rooms & Venues and Session. Events will be displayed on these views. |
|---|
| Childcare Vouchers | If enabled, Childcare Vouchers can be accepted as a method of payment for admin users and customers. |
|---|
| Data migration | If included, BookingLive will ensure customer and booking data is migrated into booking system. |
|---|
| Deposits and payment timeline | If enabled, products can be configured to capture full payment or part payment at the point of booking. |
|---|
| Electronic Point of Sale (EPOS) | If included, the EPOS is a point of sale till system that supports the booking system. It enables walk-ins to be booked onto events and checked-in with ease. |
|---|
| Events | An event is the date and time that a product is available to be used or booked. |
|---|
| Frequently Asked Questions | If enabled, FAQs are available to the customer during the booking process and can be specific to the products being booked. |
|---|
| Google Analytics | If enabled, the Google Analytics add-on allows you to track and report on traffic to your booking system and any web pages added to your website. |
|---|
| JSON feed | If enabled, a JSON feed provides all product and event availability in XML format. BookingLive are responsible for providing the feed only. |
|---|
| Locations | Events are setup to take place at locations. Locations can also be used to allow the user to filter and find products and events at specific locations. |
|---|
| Look & feel - branding | The front-end of the booking system will be accessible to the public via the internet. The header, footer and CSS can be modified to match the look and feel of and existing website. |
|---|
| MailChimp | If enabled, the MailChimp add-on allows customers to sign up to a single MailChimp mailing list via the booking process. |
|---|
| Membership Products | If enabled, membership products can be set up to allow customers to purchase annual memberships for a fixed fee. Once active, the customer can login and book products at a different cost. |
|---|
| Minimum Attendance Level | A minimum attendance figure can be added to an event which will display on the Admin Calendar. The event colour will be red (for admins) should the number of bookings be above this figure. This gives the admin a quick reference to see which events are below the minimum level. No automated processes occur and the event will still go ahead even if the minimum attendance level is not met. |
|---|
| MyAccount | Customers (purchasers) can optionally login to a customer MyAccount. Within here they will have the option to view and edit bookings, complete outstanding payments and download documents and vouchers (if applicable). |
|---|
| Notifications | Email and SMS notifications can be sent from the booking system as per the specified timeline. Typically this includes booking confirmations and reminders. |
|---|
| Organisations | If enabled, the Organisations module allows for user to be set up within organisations. Organisation Admins can manage bookings and users on behalf of that organisation. |
|---|
| Payment gateway | If enabled, BookingLive can be integrated with a variety of payment service providers. It is the Client’s responsibility to choose a payment gateway, register for an account and manage all communications with the gateway provider. |
|---|
| Prerequisites | If enabled and similar to the Terms and Conditions, additional prerequisites can be set up which the customer must accept before completing the booking. |
|---|
| Pricing schemes | If enabled, pricing schemes allow a product to have multiple prices without having to create duplicate products, such as off peak/peak pricing or adult/child pricing. Prices can be altered based upon the date of the event or the location. |
|---|
| Privacy Policy | A privacy policy must be provided to customers. It is advised that a reference to BookingLive’s Privacy Policy is included within this policy. BookingLive’s use of cookies is covered as part of the Privacy Policy. |
|---|
| Products | Products are the items available to book on the system. Individual product descriptions and images can be displayed alongside the product name. |
|---|
| Resources | A resource is an item that will be used during the event and helps manage event capacity. Resources can be shared across events and locations. |
|---|
| Single Sign On (SSO): Customers | If enabled, SSO gives the ability for customers to login to BookingLive My Account from a third party account using the BookingLive API. |
|---|
| Single Sign On (SSO): Admin users | If enabled, SSO gives the ability for admin users to login to BookingLive Admin System from a third party account using the BookingLive API. This is achieved using OAUTH2 or OpenID Connect. |
|---|
| Sub sites | If enabled, the subsites module allows Clients to create departments or service areas within the admin system. Staff users are allocated to a sub site which restricts them to viewing system and customer data that exist within that sub site. Customers are also restricted to booking 1 product type per transaction. If subsites are used, they should be included within the products import. |
|---|
| Tax (VAT) | Products can be inclusive or exclusive of Tax (VAT). If exclusive, the price advertised for the end user will be the cost before VAT. |
|---|
| Terms and Conditions | A link to the Terms and Conditions must be included which customers must accept as part of the booking journey. BookingLive are not responsible for the contents of the Terms and Conditions. |
|---|
| Upsells | If enabled, upsells are optional extras for users to buy alongside the product being booked. |
|---|
| Users | A user is a person who will have access to the booking system. Typically this is an administrator or customer. |
|---|
| Vouchers | If enabled, vouchers can be sold for a monetary value or a specific item. The recipient can then redeem vouchers online. |
|---|
| Waiting lists | If enabled, waiting lists allow events that are fully booked to display a "Join Waiting List" link. The customer will complete a form that adds their information to a waiting list for the event. No payment will be taken and administrators will use this information to communicate to those customers. Waiting lists are available for the list and calendar views on single/multi product types only. |
|---|
| Webhooks | If enabled, webhooks sends booking and customer data in JSON format and in real-time to an external URL. The external system will receive the data and import it correctly. Webhooks are sent upon a booking confirmation or update. |
|---|
| Zapier | If enabled, Zapier is an online service used to integrate data between different applications. BookingLive supports the use of Zapier and can send data to any apps available in the Zapier app store. It is the Client’s responsibility to organise the setup of Zapier. |
|---|
