Skip to content

Events & Tickets

From your event page to the door.

Workshop, customer event or online session: create your event page, collect registrations and keep track of tickets and guests.

Here’s what you can do.

Three examples show how you can use Events & Tickets.

01

Give guests a reason to join

Show what your event is about with an image, date and location. Add an agenda and speakers if needed. Review the preview before publishing your page.

A draft event page for Studio-Abend shows a workshop photo, date, location and the ticket-selection entry point.
Simplified product example · not a live product view
02

Put a name to every ticket

Even when someone books for the whole team, each ticket collects its own attendee details. Your list includes every registered guest, not just the buyer.

Two free example tickets collect separate details for Alex and Mia Beispiel; registration has not yet been completed.
Simplified product example · not a live product view
03

Scan at the door. Record the arrival.

For in-person events, your team scans the ticket QR code in the mobile app. If a ticket is missing, staff can check the guest in manually after verifying their identity. Registration and attendance stay separate.

An example ticket scan shows Alex as checked in; Mia has not arrived and is marked as pending.
Simplified product example · not a live product view

What this changes for your day-to-day work.

The practical benefits of Events & Tickets.

Register groups with less typing

Within one booking, reuse details already entered and adjust them for the next guest. Keep each person's name and email accurate.

Details in a group booking are reused and adapted for the next example guest.

Keep tickets on the phone

Guests at in-person events can save their ticket to Apple Wallet or Google Wallet. Each pass belongs to one ticket and contains its check-in code.

A fully visible phone shows an event ticket with an example check-in code and wallet action.

Refund the payment and keep the place

Refund eligible payments in full or in part. Decide separately whether to cancel the registration, then review which payment statuses are allowed at check-in.

A refund is reviewed separately from the retained registration and cancellation action.

Time reminders around your event

A configured workflow waits until your chosen interval before the event, then sends joining details. Set the channel, sender and intended recipients first.

A configured flow waits relative to the event date before sending joining details.

Follow up on the actual visit

Use a recorded check-in to trigger a workflow, such as sharing materials after the event. Registration alone does not mark a guest as having attended.

A recorded check-in starts a configured post-event materials flow, distinct from registration.

Simplified examples, not live account data.

What you need to get started.

We check access, costs, payment setup and the mobile app for your ONE LOOP account. Choose the event type, timezone and entry rules. Test registration and notifications before enabling publishing and live payments.

Registration and check-in are separate workflow triggers. Filter by event or ticket type, then send messages or create tasks. Configure and activate these workflows, and coordinate them with event notifications to avoid duplicate messages.

Availability and any add-on or usage costs are confirmed for your ONE LOOP account before implementation.

Your questions, answered.

Free registration or ticket sales?

Choose RSVP for a free confirmation without payment. A ticketed event can combine free and paid ticket types. You cannot switch between RSVP and ticketed after creation, so decide on the registration format first.

Can I use this for online events?

Yes, with an online attendee page and a meeting link whose visibility you control. QR check-in and wallet tickets are for in-person events, not proof of online attendance. The Events module does not replace a video-conferencing service.

Does canceling automatically issue a refund?

No. Cancellation and refund are separate actions that you can deliberately combine. Cancellation releases the seat and invalidates the QR pass. A refund alone does not remove the registration. Refund timing depends on the connected payment provider; it is not guaranteed to be instant.

What if a ticket is missing or scanned twice?

Staff can find the guest in the attendee list, verify their identity and check them in manually. A repeat scan shows that the ticket is already checked in. Tickets for a different event are flagged as invalid. Test app access and the entry process before event day.

See it with your own use case.

Let’s explore your use case and what the setup requires.

Book a demo