Learning centre

Training

Learn more about features and system basic.

Event Guides

Setting up a Basic Event

Setting up a Registration Event

Setting up a Tabled Event

Setting up to Sell Merchandise


Functions

Welcome to the learning centre

Extending the Booking Time

Cloning an Event

Recycling an Event

Promotional Codes Overview    

Different Levels of Access   

Tracking Overview   

Locking Your Bank Account

Data Collection Fields Overview   

Gatekeeper Scanning   

Seating Plans Overview   

Sample Buttons

Finding the Event URL

Follow up Emails   

Working with Tickets   

Creating a Tax Invoice

Terms and Conditions

Introducing TryBooking to your Community

Gift Certificates Overview   

Waitlists

Donations

Event Homepage

Session Times Overview   

Using Headers

Changing to Daylight Savings Time

Finding a Booking

Refund Overview   

Sections Overview   

Data Collection Once per Booking

When creating data forms, it's important to consider the information that may apply to multiple people on a booking.  This ensures your form is easy and quick to complete, such as:

  • Dinners - There's a strong chance that everyone on that booking will want to be seated together.  So you may wish to ask, once for that booking, data collection questions relating to seat placement  ie, Please seat me with, year level, Alumni year, table captain name etc.
  • Registrations - Emergency contact information, parent / gaurdian details, permission for photographs, acceptance of your organisation's code of conduct etc.
  • Conferences - Business name, main contact for the booking etc
  • Merchandise - Team name for pick up, parental contact etc.

Information such as the participant / attendee name is best handled via Attendee data collection.  You can use both Once per Booking and Attendee information all within the one event. 

When adding data, the following fields are provided:

  • Label - Are the words that your patrons will see on booking that define what you'd like them to enter into this field
  • Manadatory - You can determine if this question is a must completed or if you're happy for them to skip if not applicable (such in the case of special dietary requirements).
  • Field Type - Can be text, yes/no, a drop down list, or dates.
  • Field Name - Is an optional field, only needed when you will be flowing this information onto your ticket.


Check your work

A common mistake is that people put data collection under Attendee, where it is more beneficial to be added in Once per Booking to keep your form concise.  Do click on Make a Booking, selecting more than 1 ticket to confirm your data is forming correctly. 

TIP:  One per Booking data collection will appear at the top of any form, whereas Attendee information will appear under a ticket name as shown below.
 

undefined

< PREVIOUS      NEXT >