Is there a standard template for the e-Ticket and e-Ticket email?

For your e-Ticket email, we recommend using our standard template. The template will be provided to you via the Client Blueprint.

We encourage the use of the e-Ticket template we provide free of charge. If you wish to use custom developed html we require 3 weeks notice and it will incur an additional charge of $450.

Please also note, any amendments to the e-Ticket template must be sent to us no later than 3 weeks prior to the event commencement date.

Can I customise the email and SMS send name?

For all events within Australia, communications will be sent from an appropriate email domain i.e. <event-name> Likewise, SMS send names will be event specific (note; there is an 11 character limit for SMS name). Special characters e.g. #%$! cannot be supported within the email and SMS names.

How does print routing work?

When a person has their e-Ticket scanned, our system assigns that person's Smart Badge to print at one of the printers within a group e.g. If there are 6 printers at 'Main Event Check-in', that person's Badge will print at 1 of the 6 printers. Our system intelligently load-balances the printing across all available printers - eliminating build-ups/queues forming. Additionally, where large arrival volumes are expected requiring many printers, we are able to assign particular e-Ticket scanners to specific print groups, allowing us to better split the arrival flow. This improves the traffic flow and prevents people crossing paths etc. We will always ensure smooth, fast arrival processes through careful planning of check-in layout, number of printers, and peak arrival density well in advance of your event.

Our experience with traffic flow and management has helped us to determine the optimum distance for an attendee to walk between having their e-ticket scanned, and their badge handed to them. By maintaining a minimum distance of 6m between the badge distribution plinths and the e-ticket scanning staff, we ensure that attendee flow is maintained even at peak arrival times.

Did this answer your question?