Event check-in software

Check people in by badge, by name, or at the door — with or without a signal.

Scan attendee QR codes from a phone browser or the WebMobi app. Check in by name when the badge is missing. Register walk-ins on the spot. In the app, check-in keeps working offline and syncs when the WiFi comes back.

iOS and Android · offline check-in in the app · every check-in on the record, with the staff member and the time at the desk

What it is

WebMobi check-in is the part of the platform your door staff hold on event day. Each registration carries an attendee QR code. Staff scan it, search for the person by name, or register a walk-in — on the web Check-In page in a phone browser, or in the WebMobi Events app on iOS and Android. Check-ins can be pointed at the whole event or at one session, and every one of them is recorded with who did it, on which device, and whether it was made offline.

Who it is for: conference and association teams running a registration desk, organizers whose venue WiFi cannot be trusted, and anyone who has to report afterwards on who actually turned up — per session, not just a total at the door.

WebMobi Event App Builder · Build and launch your event app yourself.

WebMobi Event App Builder is a self-service event app builder that helps conference organizers, associations, agencies and event teams create and launch branded event apps — with registration, check-in (including offline check-in and walk-ins), session attendance, agenda, speakers and exhibitors in one platform.

Four people arrive. Here is what the desk does.

Every row works today, on production. The right-hand column is what happens when the venue has no signal.

The personConnectedNo connection
Has their QR badgeScan it in the app, or on the web Check-In pageScan it in the app
Registered, no badgeManual Check-In — search their name, email or registration numberApp Manual Check-In — search the list saved on that phone
Not registered (walk-in)Walk-in form in the app or on the web — register and check in togetherApp Walk-in — email required, so the phones can merge them later
Walk-in added at another desk, now at a sessionManual Check-In — search their nameAdd as a walk-in with the same email; the server merges them on sync

The WebMobi app is on iPhone and Android. Offline QR scanning works on both. Checking people in by name while offline, and adding walk-ins in the app, are on iPhone today and reach Android with the next Google Play update of the app. On iPhone the scanner also plays a sound for every scan, reads only the badge inside the square (two badges in view check in nobody), and can use the front or back camera.

Offline check-in is in the mobile app only — the web Check-In page needs a connection. Full steps: Check-in with or without a QR code, walk-ins, and working offline.

What the desk can actually do

Not adjectives — the eight things a member of your team will do on the day.

Scan QR badges from any phone

Every registration carries an attendee QR code. Scan it with the camera in the WebMobi app, or on the web Check-In page with a phone camera or a USB badge scanner.

Check in by name

The badge is at the hotel, the phone is dead, the email never arrived. Search by name, email or registration number and check the person in without a code.

Walk-ins at the door

Register someone who never signed up and check them in in the same step, on the web or in the app. If their email is already registered you are offered that person instead of a duplicate.

Offline check-in that syncs

In the app, scanning keeps working with no signal on iPhone and Android, and checking in by name and adding walk-ins do too on iPhone. Each check-in is written to the phone before the screen answers, and uploaded when the connection returns.

Sessions, not just the front door

Point a device at a single session or at the whole event. A session check-in counts toward that session only — it does not mark the person as having arrived at the event.

A check-in audit you can read

Every check-in is listed: who it was, the time at the desk, the session, QR or by name, which staff member, which device, and whether it was made offline.

Who attended each session

The Analytics page lists each session with its attendees and their in and out times — names, not just a number — and exports the whole thing as a CSV.

iOS and Android

The WebMobi Events app is in the App Store and on Google Play. Door staff use the app they already have; nothing is installed from a file.

Offline check-in, and what it guarantees

“Works offline” is easy to say. These are the rules the product actually holds to, including the awkward ones.

The arrival time is the time at the desk

Not the time the WiFi came back. A queue that syncs at 6pm still reports the 9:04am arrival.

Nothing at the desk is thrown away

A scan, a by-name check-in or a walk-in is written to the phone before the screen says anything — and a retried upload is treated as the same check-in, not a second one.

One person, one registration — across phones

The same walk-in added on two phones with the same email becomes one registration with two check-ins. Email is the merge key, which is why an offline walk-in has to have one.

A repeat scan is recorded, not counted twice

Scanning someone who is already inside is logged as “Already inside (not counted again)”. Your attendance number does not move.

Check-ins cannot be deleted

The History view is read-only. Nothing in it can be edited or removed from the dashboard.

One thing to do before the doors open

Each phone keeps its own copy of the attendee and session lists, so every phone has to open a check-in screen once while it still has a connection. The scanner then reads Online · N cached. A phone that never did this has no list, and offline name search will find nobody on it. People who register after that download are not on that phone until it refreshes. Rehearse it with the event-day dry run.

The whole event, or one session

Before scanning, the operator picks the target: Whole event or a named session. The web page does it with a dropdown above the scanner; the app does it with a “Scanning into” button that is always visible, so the screen and the data can never disagree about which room a scan counted for.

  • ·A session check-in counts toward that session only. It does not mark the person as having arrived at the event — which is what you want when the keynote door and the front door are different people.
  • ·Someone who leaves and comes back is a second visit, not a second attendee. Session attendance counts people; visits are reported alongside.
  • ·A badge from a different event is refused and records nothing.

Afterwards: who checked in whom, and who attended what

Two separate questions, two places to answer them.

History — the check-in audit

The event’s History tile lists every check-in, repeats included: the attendee, the time at the desk, the session or Whole event, QR scan or by name, the staff member, the device, and an Offline label with the time it synced. Walk-ins are listed with who added them. A repeat scan appears as Already inside (not counted again).

History is read-only — nothing in it can be edited or deleted. It is visible to the event’s creator, organization owners and admins, and event admins who can edit the event. Check-ins made before 17 September 2026 show the staff member as “Not recorded”.

Guide: History — content changes and check-ins →

Analytics — attendance and export

The Analytics page shows registrations, checked in, check-in rate and a breakdown by ticket type, then Session Attendance: each session with its attendee count, expandable to every attendee’s name with their in and out times. Someone who re-entered appears once per visit.

Export writes a CSV with the summary, the ticket breakdown, session attendance and one row per session visit. Every time is in the event’s own time zone, which is named in the file, in 24-hour YYYY-MM-DD HH:MM:SS form — so two people exporting the same event get the same report.

What it does not do

Written down here so you find out now, not at 8am on event day.

No badge printing

There is no badge designer and no supported on-site printer. Attendees carry a QR code on their phone. If you need printed badges, produce them from your own template with the attendee QR on them.

No lead-retrieval scanning app for exhibitors

Exhibitors get a directory listing and a booth page. There is no scan-a-badge-to-capture-a-lead app, and no lead export for sponsors.

Offline is the mobile app only

The web Check-In page shows an Offline Mode badge but queues nothing — it is an online tool for watching the desk, not for running it without a signal.

An offline walk-in must have an email address

Email is the only key the server can use to merge the same person added on two phones. Offline, the walk-in form requires it. A mistyped email creates a second registration, and there is no automatic merge afterwards.

Phones do not talk to each other

Each phone has its own copy of the list and its own queue; the server reconciles them. A walk-in added on phone A is not searchable on phone B until A has synced and B has refreshed. If you expect to be offline, run one walk-in desk.

The app walk-in form has no ticket picker

Walk-ins added in the app are ticketless; the web walk-in form does let you pick a ticket. Walk-ins are recorded as free either way — no payment is taken, even against a paid ticket.

A confirmation email for an offline walk-in arrives late

It is sent when the phone syncs, not at the desk — and only if the event is set to send emails at all.

The live Check-in Console is an Enterprise feature

Live counts, recent arrivals and the active-device list on one screen are part of our Enterprise offering. Scanning, by-name check-in, walk-ins and the History audit do not depend on it.

Manual search is capped at the 500 most recent registrations

On the web Manual Check-In tab. At a larger event, scan the badge rather than searching for the person.

No hybrid or streaming check-in

This is an on-site product. There is no virtual-attendance tracking, and no streaming platform behind it.

FAQ

Does check-in work with no internet at the venue?

In the mobile app, yes. Scanning a badge works offline on iPhone and Android; checking someone in by name and registering a walk-in work offline on iPhone today, and reach Android with the next Google Play update of the app. Everything syncs when the connection returns. The web Check-In page needs a connection — it shows live counts but queues nothing. Each phone must open a check-in screen once while connected, so it can download the attendee and session lists before the doors open.

What happens if someone arrives without their QR code?

Use Manual Check-In and search for them, then check them in. On the web you can search by name, email or registration number; in the app, by name or email. Online it works on the web and in the app; offline it works in the app on iPhone today, reading the attendee list that phone downloaded before the doors opened.

Can we register someone at the door who never signed up?

Yes — that is a walk-in. Enter their name, pick a ticket if the event has them, and register and check in together. If the email you type is already registered for that event you are told, and offered the existing person to check in instead of creating a second registration. Ticket, event and plan limits still apply.

Two of our phones added the same walk-in. Do we get a duplicate?

Not if both desks typed the same email. The first phone to sync creates the registration; the second gets told it already exists and its check-in is attached to that same person. Two different emails for one human do create two registrations — email is the only key the server can enforce, so the desk rule is to capture it exactly.

Can we track attendance per session, not just at the front door?

Yes. Before scanning, choose the whole event or a specific session — on the web page with the Session dropdown, in the app with the “Scanning into” button. A session check-in counts toward that session only and does not mark the person as having arrived at the event. Re-entry is recorded as a second visit, not a second attendee.

Who checked that person in?

Open the event’s History tile and choose Check-ins. Every check-in is listed with the attendee, the time at the desk, the session or Whole event, whether it was a QR scan or by name, the staff member, the device, and an Offline label with the time it synced. Check-ins made before 17 September 2026 show the staff member as “Not recorded”.

Can we get a list of who attended each session?

Yes. The Analytics page lists each session with every attendee and their in and out times, and exports the report as a CSV with times in the event’s own time zone, named on the file, in 24-hour format.

Who on our team can run the check-in desk?

The person who created the event, owners and admins of your organization, and teammates you invite to that event with the Manage registrations permission. Permissions are per event and set with tick boxes on the event’s Team page, not by the role name.

Do you print badges?

No. WebMobi issues each attendee a QR code they carry on their phone. There is no badge-design or badge-printing product, and no supported on-site printer. If you print badges, print them from your own template and put the attendee QR on them.

Run your next door on it.

Set up an event, issue attendee QR codes, and rehearse the desk with the dry run before anyone is standing in front of you.