Walk-ins

Walk-ins are people who show up to your event without a prior registration. Events gives you three ways to handle them, and the right one depends on who is doing the registering.

Here is when each path applies:

• Staff at the door registering someone on their behalf, use the check-in console walk-in dialog.
• Attendees registering themselves at an unattended station, use the kiosk walk-in flow.
• Walk-ins that need your review before a ticket is created, work them from the Walk-in Queue in Cockpit.

From the check-in console

The check-in console has a Walk-in button that opens a registration dialog. It opens with a contact search, so your staff member can link an existing contact instead of retyping. For someone new, they fill in first name, last name, phone, and an email address that is explicitly optional, leave it blank and there is no email on file. They pick a ticket type and a switch decides whether to check the attendee in immediately or register them ahead of arrival.

The check-in console is the only place operators register walk-ins; the same dialog was removed from the Attendees tab, which keeps a separate Add a registration action for back-office entries like comps.

This path skips Stripe entirely, no payment is collected through the dialog. If you need to charge the attendee, handle payment outside Events before completing the registration.

No confirmation email is sent. The ticket is created immediately on save and appears in your registrations list.

From the kiosk

The kiosk's walk-in flow behaves differently depending on whether your event is published. On a published event, attendees complete a full step-by-step wizard on the kiosk screen and their registration is confirmed immediately, no operator review needed. On a draft event, the kiosk falls back to a short form instead, and that submission waits in the Walk-in Queue for an operator to approve or reject it.

On a published event, the wizard walks the attendee through:

1. Path picker (for multi-path events)
2. Ticket selection
3. Personal details (email verification is optional, depending on your kiosk settings)
4. Additional info, any custom questions you have configured
5. Agreements, any attestations you require
6. Review and submit

On submit, the registration completes immediately, the badge is queued the same way a QR check-in is, and the kiosk returns to its home screen with the confirmation copy you configured under Kiosk mode.

From the Walk-in Queue in Cockpit

Draft-event submissions land in the Walk-in Queue module in Cockpit as pending rows. No ticket exists yet, the attendee is waiting for an operator to act. This module is reachable by signed-in operators and by door volunteers holding a Floor Lead cockpit invite, so someone working the door on a guest link can approve walk-ins directly, without needing a full Mercleo account.

To process a pending walk-in, select the appropriate ticket type for that attendee, then choose Approve or Reject.

Approving creates a confirmed ticket and increments the sold count for that ticket type. Rejecting removes the row without creating a ticket.

Capacity counting

For the kiosk's published-event wizard, the Allow overselling setting in your kiosk configuration controls what happens when a ticket type is at capacity.

With it off, the server rejects the walk-in submission when the ticket type is sold out. The attendee sees an error before they complete the wizard.

With it on, submissions are accepted even after the ticket type's quantity is exceeded. The sold count will exceed the capacity limit, and your dashboard surfaces the overage rather than hiding it.