The Events area is the organizer's console. This is where an event is set up and run; EventOxygen is the attendee-facing side of the same data.
What lives here
| Screen | What it holds |
|---|---|
| Events | The events themselves and their lifecycle |
| Sessions | Multi-track agenda — talks, workshops, rooms |
| Ticket Types | What can be bought, at what price, with what limits |
| Tickets | Issued tickets and their state |
| Bookings | Purchases, which may cover several tickets |
| Badge Templates | Printed badge layouts |
| Speakers | Speaker profiles attached to sessions |
| Exhibitors | Exhibiting organizations and their staff |
| Check-ins | Arrivals, by zone and over time |
| Leads | Leads captured from badge scans |
Setting an event up
1. Create the event and describe it — dates, venue, description, imagery.
2. Define ticket types — what is on sale, at what price, with what capacity.
3. Build the agenda — sessions across tracks and rooms, with speakers attached.
4. Publish it, which makes it discoverable and opens sales.
5. Go live when the event starts, which turns on the door-side features.
Bookings and tickets
A booking is a purchase; tickets are what it contains. Cancelling a four-ticket booking is one action rather than four, while individual tickets can still be transferred or refunded on their own.
Tickets can also be comped without payment, or pre-generated in a batch and activated later — which is how physical stock is produced before you know who buys it.
Check-in
Check-ins are recorded per zone, with check-out as well as check-in, so occupancy is a live count rather than a cumulative one.
Staff scan using Appmint Mobile.
Leads
Badge scans capture leads. They land in the same pipeline as every other lead in CRM, rather than in an event-only list that has to be exported afterwards.