Attendees get their ticket, schedule and networking directory in one place. Staff get scanning, accreditation and a live view of who is actually in the room. It is a standalone brand — attendees see EventOxygen, not Appmint — running on the same backend, so leads captured from badge scans land straight in your CRM.

Ticketing and QR check-in, multi-day tracks and zones, attendee networking, meetings and a live feed — a real app your attendees install, running on the same platform as everything else you own. Your data, your agents, your API, on day one.






Most event apps do one of these and integrate the other two badly. This is one product on one backend, so a badge scanned at the door becomes a lead in your CRM without anybody exporting anything.

Sold through Stripe or issued free, transferable to someone else, refundable, and carrying perks the holder can claim on the day.
Most systems count check-ins and call that attendance. Scanning here records the way out as well as the way in, so what you see is live occupancy per zone — the only number that means anything when a room has a capacity and a fire officer.
Not a separate events tool with its own login and its own customer list. It sits in Studio Manager beside your CRM, your orders and your inbox.

Scanning records check-in and check-out, so occupancy is a live count per zone rather than a cumulative total. That is the number that matters when you have a capacity limit.
No. EventOxygen is a standalone brand — attendees download EventOxygen and that is what they see. It runs on the same backend as the rest of the platform, which is how badge scans reach your CRM, but none of that is visible to them.