Loading…
What is in the code, how it reaches the attendee, and exactly what the scanner does with it — on the web, in the app, and with no signal.
Every registration in WebMobi gets its own QR code when it is created. The code holds a short identifier — no name or email — which the scanner looks up in that event's registrations. Attendees receive it in their registration confirmation email when emails are on for the event. Staff scan it on the web Event Check-In page (camera or USB scanner) or in the WebMobi app, which also works offline.
WebMobi does not design or print badges. For choosing QR check-in for your event, see QR code check-in.
An attendee QR code encodes the text WEBMOBI:ATTENDEE: followed by a short code — for example WEBMOBI:ATTENDEE:7E4C3A93. The short code is random. It is not the registration number and it carries no personal details, so a photo of it reveals nothing about the person by itself.
When the code is scanned, WebMobi looks it up among the registrations of the event being scanned. Badges issued with older WebMobi links (addresses containing /check-in/) are still read.
| How the person was registered | Code |
|---|---|
| Registered on your event page | Created with the registration. |
| Imported from a spreadsheet | Created with each imported registration. |
| Added by hand on the dashboard | Created with the registration. |
| Walk-in added on the web or in the app | Created when the registration reaches WebMobi — for an offline walk-in, when the phone syncs. |
A code does not change when you edit the person's name or details. There is no screen to issue a new code.
The registration confirmation email carries the QR code as an image, with the attendee's ticket and registration number. WebMobi sends it only when emails are switched on for the event:
| Situation | Result |
|---|---|
| Registered for this event, not yet inside | Checked in — to the event or to the session selected — and the name is shown. |
| Already inside (same event or session) | In In only mode: recorded as a repeat, not counted again. In In / Out mode: checked out. |
| A badge from another event | Refused. Nothing is recorded. |
| Not a WebMobi attendee code | Refused as an invalid code. |
On the web: open the event → Check-in, then the QR Scanner tab to use the camera, or plug in a USB barcode scanner while USB Badge Scanner Ready is shown — each scan checks in automatically. In the app: Admin Panel → Scan QR Code. In both, set the scanning mode and the session first; see Session attendance and reports.
In the app, badge scanning works offline on iPhone and Android. The phone matches the code against the attendee list it saved while connected, and queues the check-in with the time it happened.
| The phone shows | Meaning |
|---|---|
| Checked in · queued | Matched on the phone; sent when connected. |
| Already inside · queued | This phone already checked them in. Not counted twice. |
| Not in local list · queued for sync | The code is not in this phone's list — for example someone who registered after the phone downloaded. It is kept and matched when connected. |
A phone that never saved the list reads NO ROSTER — offline scans cannot match. Preparing each phone: Preparing staff phones.
Anyone holding a copy of a code can be checked in as that person, and check-in cannot tell a screenshot from the original. Ask attendees not to share their confirmation email. At the door, the name shown after a scan is your cue to compare it with the person in front of you.
Every scan, including repeats, is kept in the event's History with the staff member and time, so a code used twice is visible afterwards.
Yes. Every registration gets its own code when it is created — whether the person registered on your event page, was imported from a spreadsheet, added by hand or registered as a walk-in.
The text WEBMOBI:ATTENDEE: followed by a short code of letters and numbers. It contains no name, email or other personal details; the code is looked up in your event’s registrations when it is scanned.
In the registration confirmation email, which WebMobi sends only when “Send emails for this event” is on in the event’s settings. It is off for every new event until you turn it on.
No. WebMobi does not offer badge design or badge printing. Attendees show the QR code from their confirmation email on their phone or on a printout.
No. A code belongs to one event. Scanned at another event, it is refused and nothing is recorded.
The person is counted once. The second scan is recorded as a repeat — “Already inside” — or, in “In / Out” mode, checks the person out.
In the WebMobi app, yes: the phone matches the code against the attendee list it saved, records the check-in and sends it when connected. The web check-in page needs a connection.
Each imported registration has a code, but the import does not email anyone, so imported attendees are not sent their code by the import. Check them in by name at the desk.