Check-in Experience for In Person Events

Check-in allows event organizers to mark attendees as arrived at their venue using the mobile app. It works for in-person events only—both ticketed and RSVP'd. For online events, you can view the attendee list, but check-in is not available.

There are two ways to check in an attendee: scanning their QR code or doing it manually.

Every attendee who purchases a ticket or registers via RSVP receives a ticket with a QR code. To check them in, open the mobile app and scan the QR code when they arrive.

If QR scanning isn't working, or the attendee has lost their ticket, you can check them in manually. Verify their identity, then:

FAQs

1. 1What happens if I scan the same ticket twice? The app will show that the attendee has already been checked in
2. 2What happens if I scan a ticket meant for a different event? The app will show that the ticket is not valid.

Before you begin

“Check-in Experience for In Person Events” is part of the Calendars → Calendar Views area in Adaptive AI. Use month, week, day, and agenda views. Calendar changes affect availability, assignment, reminders, and conflict checking. Validate the complete booking experience rather than relying only on the administrator preview. The objective is not merely to save a setting; it is to confirm the result works for the staff member or customer who will depend on it.

• Confirm the business time zone, user time zone, appointment duration, buffers, minimum notice, and booking window.
• Review each assigned team member and verify that the correct personal or external calendars are connected and authorized.
• Identify which calendars should write new appointments and which calendars should only be checked for conflicts.
• Use a test contact and an email address or phone number that can receive confirmations without contacting a real customer.
• Note any group, room, equipment, service, or round-robin rules that may affect which time slots are offered.

Verify the result

After completing the instructions in this guide, use a controlled test before treating the setup as finished. A saved screen or success message confirms configuration, but only an end-to-end test confirms the business outcome.

1. 1Open the public booking link in a private browser window and confirm the correct calendar, service, team, and time zone appear.
2. 2Book a controlled test appointment and verify it appears in Adaptive AI and on the intended connected calendar.
3. 3Confirm blocked or conflicting times are unavailable while genuinely open times remain bookable.
4. 4Check the confirmation, reminder, reschedule, and cancellation experience using the same links a customer receives.
5. 5Cancel the test appointment and verify availability, status, notifications, and connected-calendar events update as expected.

Troubleshooting checklist

If the result differs from what you expected, preserve the current state and isolate one variable at a time. Start with the checks below before deleting the configuration or rebuilding it from scratch.

• Compare account, user, and external-calendar time zones when times appear shifted or unavailable.
• Check linked and conflict calendars for duplicate connections, all-day events, recurring events, or stale authorization.
• Review availability, buffers, minimum notice, date range, capacity, and assignment rules before assuming the calendar is malfunctioning.
• Confirm the selected user is active, belongs to the calendar, and has permission to receive or manage appointments.
• Test in a private window to separate a saved configuration issue from browser cache or an authenticated preview.

Best practices

• Keep one documented source of truth for business hours and define exceptions for holidays, events, and planned absences.
• Use clear calendar names that identify the service, location, duration, or assigned team instead of generic labels.
• Test booking, rescheduling, cancellation, reminders, and conflict behavior after every material calendar or integration change.
• Avoid connecting the same external calendar through multiple users unless the conflict behavior is intentional and tested.
• Review upcoming availability from the customer view regularly, especially after daylight-saving or staffing changes.