ticket-checkin

Ticket check-in system, for events

Screenshots tour

• A check-in kiosk. Attendee can present a QR code at the kiosk or use their mobile phone to self-checkin using their ticket reference number.

  

• API for self-checkin. Instead of presenting a QR code, an attendee can go to the event website and check in using their ticket reference number..

  

• A staff panel. Event staff can manually check-in tickets for the attendees.

  

  Mobile version:

  

• QR code scanner webapp for event staff. In addition to the kiosk, event staff can scan attendee’s QR code using their mobile phone.

  

Features

• Multiple check-in modes:

  Check-in mode	Pros	Cons
  Self check-in Attendee checks in by entering ticket refCode + time-based OTP.	◆ No need to wait in line. ◆ Self-service. ◆ Attendee gets a personal greeting.	◆ Unfamiliar method. ◆ Requires attendee to have a mobile device to check in.
  Kiosk check-in Attendee presents ticket QR code to check in at the kiosk.	◆ Works with printed tickets. ◆ Self-service. ◆ Attendee gets a personal greeting.	◆ Have to wait in line to use the kiosk.
  Staff check-in Staff uses a mobile PWA to check attendees in using QR code.	◆ No need to wait in line. ◆ Works with printed tickets.	◆ Needs manual work by staff. ◆ Have to wait for an available staff. ◆ Attendees don’t get a personal greeting.
  Manual check-in A staff checks attendee in by searching manually. Used as a last resort.	◆ For when user has lost their ticket but can verify their identity.	◆ Needs manual work by staff. ◆ Takes the most time.

• Swag fulfillment:

  • We printed high-quality name tags with attendees’ name ahead of time. After an attendee checks in, we want them to see their name tag already placed on the table.

  • When an attendee checks in, their information will be placed on a queue. A fulfillment staff will rotate to take orders from the queue. This is kinda like how Starbucks.

Data model

Just read the bolt file.