01
Define exactly what admission includes
Publish the date, venue, reception opening time and programme start and finish. Explain whether a ticket covers the full day, a particular date or a separate activity. Say explicitly whether lunch or a networking reception is included. A ticket type does not automatically reserve a parallel session; only promise that choice when you have arranged session capacity through a separate process.
- Distinguish admission from programme preferences.
- Publish travel information and a contact for accessibility questions.
02
Keep pricing and business questions manageable
Early-bird and regular tickets can each have their own sales period. Choose names that make sense outside your organisation and check the combined quantity you are offering. Business participants may ask about billing names or payment documents. Decide which information is required and how your team handles requests; do not promise automatic support for every invoicing requirement without checking it first.
- Test ticket prices, sales windows and quantities with a sample order.
- Make change and cancellation conditions visible before purchase.
03
Connect registration to your conference website
Use the ticket link or place the available sales embed on your conference website. Keep the programme and practical details current, with a clear registration action rather than competing links. Test the journey on a phone, including the return after online payment. Then inspect the ticket email: check delivery, the event date and whether the QR ticket opens from the order as expected.
- Check the participant journey and the contact for booking questions.
- Budget separately for platform fees and payment-provider charges.
04
Plan QR check-in separately from badges and sessions
At arrival, your team verifies the admission ticket. Test the camera, connection and an example ticket before participants arrive. If you hand out badges after scanning, organise that as a separate step; ticket checking is not an automatic badge-printing system. Give helpers only the permissions they need and agree who handles missing tickets, duplicate scans and booking questions during the reception.
- Brief helpers on the correct event and the exception process.
- Use arrival records to evaluate reception, not as proof of attendance at individual sessions.