SiteCheckin

How customers join the queue

What the customer sees, what they must provide, and what happens right after they check in.

A customer scans your QR code or opens your location link, taps Check in, and fills a short form. No app and no account are needed; it typically takes under 30 seconds.

What they're asked for

  • First name — required. Last name is optional (boards can show "John S." style names if you allow it).
  • Phone — required. It's also how duplicate check-ins are prevented.
  • Email — required by default, because it delivers their ticket number and live tracking link. You can make it optional in check-in settings.
  • Anything else you enabled: address, a service to pick, notes, or an age confirmation.

What happens next

  • They land on a confirmation page with their number (like #12), a reference code, live status, and how many people are ahead. Once your location has a few served visits today, the page (and the check-in form) also shows "Typical wait right now" — a rolling average of recent real waits, clearly labeled as a guide, and hidden when there isn't enough data to be honest.
  • They get an email with the same number and a link that re-opens their live status any time.
  • The page updates by itself as staff move their ticket — including on their phone's lock-screen return.
  • If they try to check in again with the same phone while still in line, they're shown their existing ticket instead of creating a second one.

Cancelling

While the ticket is still in the first stage (before staff engage), the customer can select Cancel my check-in on their status page. After that, the page tells them to ask the front desk.

Related articles