Ticketing best practices

Use Emma for the Full Ticketing Journey (Recommended)

We strongly recommend managing the entire ticketing lifecycle within Emma — from ticket sales through to guest check‑in.

Why this matters:

1. Seamless guest journey: Guests enjoy a single, consistent experience from purchase to entry.
2. Fewer errors: No manual data transfers or mismatched/duplicated guest lists.
3. Real‑time visibility: Live reporting on sales, registrations, and attendance.
4. Centralised guest data: One platform to manage tickets, guest data, registrations, communications, and check‑in.

Using Emma end‑to‑end ensures your team spends less time on admin and more time delivering a great event.

Selling Tickets Outside of Emma (Alternative Option)

If you choose to sell tickets through an external platform, Emma can still support the rest of the guest journey, but please try and adhere to the suggested process below to still ensure the 4 points above are realised.

Recommended process:

1. Sell your event tickets via your chosen external platform.
2. Bulk upload your lead guests/hosts into Emma using our bulk upload CSV template (bulk uploading guests help article).
3. Use Emma to:
   • Collect additional registration information (adding registration questions help article)
   • Collect additional guest names from hosts (for a table of 10 for example) (sending comms to hosts to collect registration information help article)
   • Send branded e‑tickets (e-ticket best practises help article – link TBC)
   • Manage communications
   • Handle on‑site check‑in (check-in best practises help article – link TBC)

This approach ensures that, even when sales happen elsewhere, guest management and event delivery remain streamlined within Emma.