Check-in Without Signal: Amber, Red and Confirming Scans
In this article
Check-in Without Signal: Amber, Red and Confirming Scans
4 min read · Check-in
Check-in Without Signal: Amber, Red and Confirming Scans
The scanner keeps working when the signal drops, on every plan. It checks each QR code against the guest list saved on the phone and sends the scans to our servers when the phone reconnects. A guest let in this way is not confirmed until the server agrees, so the scanner shows amber until then.
Open the scanner while online at least once first, so the guest list and the signing key are saved. A phone that has never opened this scanner online says "No guest list on this phone yet. Connect to load it, then scan again."
What the colours mean
- Amber, "Saved on this phone, not yet confirmed.": this guest was let in using the list saved on the phone and the scan is waiting to reach our servers. Let them in. The row also reads "Offline: not confirmed yet". It turns green ("Confirmed with the server.") when the phone reconnects and the server agrees. If the server refuses it, the row turns red with the reason and the guest appears in the needs-attention list.
- Amber, "Not on this phone's list. We check it when you reconnect. Let them in if your manager agrees.": the QR is genuine but the ticket is not on the saved list, for example because it was bought after the list was saved. The phone cannot decide, so your manager does. The ticket is checked when the scan syncs.
- Amber, "This phone's guest list is out of date. We check it when you reconnect. Let them in if your manager agrees.": the saved list is more than 6 hours old. Same decision, same check on reconnect.
- Red after reconnecting: the server disagreed with the phone. For example "Server says this ticket is not valid (refunded or cancelled). The guest may already be inside. Tell your manager." or "This ticket was already used on another phone. The guest may have a shared QR. Tell your manager." Check the guest in person.
The needs-attention list
If the server refuses a guest the phone let in, or a scan cannot be sent, an amber banner reads "N guests were let in on this phone and the server did not confirm. Check them by hand." It lists each guest. It stays after you reload the scanner or close the app, and it appears the next time any scanner is opened on that phone. Tap Got it once you have checked them.
What the phone refuses offline
- A ticket refunded or cancelled before the phone last synced: "This ticket was refunded and can't be used. The guest was not checked in. Ask your manager." (or "cancelled").
- Any scan once the event is cancelled or archived: "This event was cancelled. Check-in is closed." (or "archived"). A paused or ended event is refused offline only while the saved list was updated in the last 6 hours.
- A typed ticket code with no signal: "Can't check a typed code without signal. Scan the QR code, or connect and try again." Search by name works offline for guests on the saved list.
- A scan the phone could not store: "Not saved. This phone could not keep this scan. Check this guest in by hand." If the phone is out of space: "Not saved. This phone is out of space. Reconnect before scanning more, or check in by hand." Nothing about that guest reaches our servers.
- A phone with no signal that cannot check on its own: "No signal. Connect to check in this guest."
Refusals are not saved to sync later.
Syncing
- Scans send automatically when the phone reconnects, or tap Send now. The banner shows "N check-ins waiting to send."
- If our servers are briefly unavailable, the phone keeps the scans and tries again. A scan still unsent 24 hours after it was made is dropped with "Couldn't confirm this check-in. Check the guest by hand."
- Switching to another event, time slot or series scanner on the same phone leaves earlier scans queued for the scanner they belong to: "N scans from another scanner are waiting. Sign in to that scanner to send them." Sign back in to that scanner while online and they send.
- Scanning a guest again before the first scan is confirmed reads "Already scanned on this phone. Not confirmed yet." After a scan gets no answer: "Couldn't reach the server. We don't know if this guest is already in. Scan again when you have signal."
- Two phones that are both offline can each let the same ticket in. The second to sync turns red.
Closing or reloading offline
A phone that signed in to this event while online reopens the scanner still signed in until its sign-in expires. If you have since opened another scanner on that phone, reconnect and sign in again.
For refusals on screen, see Check-in Troubleshooting. For the scanner itself, see Event Day Mode.
Still need help?
If this article didn't answer your question, our support team is here.
Contact Support