--- title: "Check-in" url: https://www.tallievents.com/docs/check-in updated: 2026-11-06 site: "Talli" --- ### All guides #### [Docs home](https://www.tallievents.com/docs) #### Getting started - [Getting started](https://www.tallievents.com/docs/getting-started) - [Organization settings and branding](https://www.tallievents.com/docs/branding) #### Venues and layouts - [Venues](https://www.tallievents.com/docs/venues) - [Floor plans and layouts](https://www.tallievents.com/docs/floor-plans-and-layouts) - [Venue map and signs](https://www.tallievents.com/docs/venue-map-and-signs) - [One layout across a series](https://www.tallievents.com/docs/series-layouts) #### Events - [Events](https://www.tallievents.com/docs/events) - [Agenda](https://www.tallievents.com/docs/agenda) - [Write with AI](https://www.tallievents.com/docs/write-with-ai) - [Cloning events](https://www.tallievents.com/docs/cloning) - [Languages and translation](https://www.tallievents.com/docs/languages) - [Registration form](https://www.tallievents.com/docs/registration-form) #### Team - [Team and roles](https://www.tallievents.com/docs/team-and-roles) - [Roles and activity log](https://www.tallievents.com/docs/roles-and-activity) #### Registration and attendees - [Public registration and tickets](https://www.tallievents.com/docs/registration) - [Attendees](https://www.tallievents.com/docs/attendees) - [Orders and group registration](https://www.tallievents.com/docs/orders-and-groups) - [Session sign-up and CE credits](https://www.tallievents.com/docs/sessions-and-credits) #### Communication - [Emails and contact lists](https://www.tallievents.com/docs/emails) - [Surveys](https://www.tallievents.com/docs/surveys) #### Planning and websites - [Tasks and checklists](https://www.tallievents.com/docs/tasks-and-checklists) - [Event website](https://www.tallievents.com/docs/event-website) #### Exhibitors - [Exhibitors](https://www.tallievents.com/docs/exhibitors) - [Brand portal and booth scanner](https://www.tallievents.com/docs/brand-portal) #### At the door - [Check-in](https://www.tallievents.com/docs/check-in) - [Devices and offline check-in](https://www.tallievents.com/docs/devices-and-offline) - [Talli for iPhone](https://www.tallievents.com/docs/mobile-app) #### Reports and AI - [Dashboard, overview and reports](https://www.tallievents.com/docs/dashboard-and-reports) - [AI assistants](https://www.tallievents.com/docs/ai-assistants) [Docs](https://www.tallievents.com/docs) / At the door # Check-in Check people in at the door from any phone browser: scan the QR code on their ticket with the camera, or find them by name. Each ticket counts once, and every scan shows a clear result: welcome, already checked in, not found, wrong event, waitlisted or cancelled. ## Open check-in on a phone 1. Sign in to Talli on the phone and open the event. 2. Choose **Check-in** in the event's section of the menu. 3. Under **Entry point**, choose where you are standing, for example Main entrance. The phone remembers this choice for the event, so the next time it opens at the same entry point. 4. Allow camera access when the browser asks. The top of the page shows the event, your entry point and your name, and how many confirmed attendees are checked in (for example 87/112). ## Scan a ticket 1. Stay on **Scan** and point the camera at the QR code on the attendee's ticket, on their phone or printed. 2. Read the result card: - **Welcome!** (green): they are checked in now. The card shows their name, organization, attendee type, language, and whether they asked for an interpreter or have accessibility needs. - **Already checked in** (amber): this ticket was checked in before. The card says when, at which entry point and by whom, and the second scan is not counted. - **Ticket not found** (red): the code matches no ticket. It may be a screenshot of another event or a mistyped code. - **Wrong event** (red): the ticket is for another of your organization's events, named on the card. Nobody is checked in. - **On the waitlist** (amber) or **Registration cancelled** (red): they have no seat, so they are not checked in. 3. Tap **Scan next** for the next person. The camera stays on between scans. A ticket held in front of the camera is read once; to scan the same ticket again, take it out of view for 3 seconds. ![Check-in on a phone browser after a scan: a green Welcome! card for Joshua Washington, checked in at 6:04 AM at Main doors, with Scan next and Undo check-in.](https://www.tallievents.com/api/media/a43d8045-8ad9-4ea2-9301-7875e273f8bf/talli-checkin-web-welcome.webp) ![The same screen after scanning the ticket again: an amber Already checked in card with the time, door and staff member, tagged Not counted twice.](https://www.tallievents.com/api/media/52328790-5295-40f8-a017-da8b180f971c/talli-checkin-web-already.webp) A scan, and the same ticket scanned twice. Shown with sample data. ## Type a ticket code 1. On **Scan**, tap **Or type a name, email or ticket code** under the camera. 2. Type the code printed under the QR code, for example 7KQ4-MX29-RD, and press Enter. Capitals and dashes do not matter, and the letter O is read as zero. Anything that is not a ticket code (a name, an email) opens the search instead. ## Find someone by name 1. Tap **Search**. 2. Type part of their name, email or organization, or their ticket code. 3. Tap the person to check them in. People already checked in show the time they arrived; tapping them shows the Already checked in card. Confirmed attendees are listed first, then waitlisted and cancelled ones. If nobody matches, owners and admins can **Add a walk-in** from the Attendees page. ![The check-in Search view on a phone, with a box to type a name, email, organization or ticket code.](https://www.tallievents.com/api/media/f5f9a316-b430-4c30-801f-9a25a2a0ef2a/talli-checkin-search.webp) Search on a phone. Shown with sample data. Ask your assistant ``` Is Nadia Haddad checked in at the Spring Safety Seminar? If not, check her in at the Main entrance. ``` Select the prompt and copy it into Claude or ChatGPT connected to Talli. Uses `search_attendees`, `list_entry_points`, `check_in_attendee`. [Connect an assistant](https://www.tallievents.com/docs/ai-assistants#connect-claude) ## Undo a check-in Owners and admins can tap **Undo check-in** under a Welcome card, for example when the wrong person was tapped. It is not offered after a scan at a session; take back the session's credits with `revoke_credits` instead. They count as not arrived again, and their next scan checks them in. ## Set up entry points Every event starts with one entry point, Main entrance. Owners and admins can change the list: 1. On the check-in page, tap **Edit** next to the entry point. 2. Rename an entry point, choose its kind (Door, Session room or Booth), add one with **Add entry point**, or remove one. 3. Tap **Save entry points**. Removing an entry point takes it off the list only: check-ins already made there keep its name. Ask your assistant ``` Set up two entry points for the Spring Safety Seminar: Main entrance and East doors. ``` Select the prompt and copy it into Claude or ChatGPT connected to Talli. Uses `list_entry_points`, `set_entry_points`. [Connect an assistant](https://www.tallievents.com/docs/ai-assistants#connect-claude) ## Check people in to a session Each session that takes sign-ups or awards CE credits has its own entry point, listed as **Session:** and the session's title, for example **Session: Workshop A: Online quoting tools**. The agenda keeps these up to date, so they are not in the **Edit** list. 1. Choose the session's entry point. 2. Scan tickets as at the door. The Welcome card says "Checked in to" the session and shows the credits awarded, for example "1 CE credit awarded". A person not yet checked in at the door is checked in to the event by the same scan. A second scan at the same session shows Already checked in and awards nothing. At a session that requires sign-up, someone without a seat in it gets an amber **Not signed up for this session** card: they are still checked in and credited, since they were there. See [Session sign-up and CE credits](https://www.tallievents.com/docs/sessions-and-credits). ## Check in without signal Check-in keeps working when the connection drops: scans are saved on the device and sync when it is back. Owners and admins see each device and the scans waiting on it under **Devices and sync**. See [Devices and offline check-in](https://www.tallievents.com/docs/devices-and-offline). ## Who can use it - Everyone in the organization (owners, admins and staff) can check people in, scan, search and see the scan history. - Staff assigned to some events or entry points see only those; see [Devices and offline check-in](https://www.tallievents.com/docs/devices-and-offline). - Owners and admins can also undo a check-in and change the entry points. ## Limits and edge cases - Each registration is checked in at most once, whichever phone or entry point scans it; two phones scanning the same ticket at the same moment still count it once. - Only confirmed registrations are checked in; waitlisted and cancelled ones are shown but never counted. - A ticket from another organization shows Ticket not found, the same as a code that does not exist, so nothing about other organizations is revealed. - Every scan and tap is kept in the scan history with its result, including duplicates and unknown codes. - An event can have up to 30 entry points, each name up to 60 characters and unique within the event (ignoring capitals). - The camera needs a secure (https) link; on a plain http link the page explains this and search still works. - If the browser blocks the camera, the page says so; search by name and typed codes keep working. - Search by name, typed codes and the result cards also work in a browser with JavaScript turned off; camera scanning needs JavaScript. ## See arrivals as they happen The event's [dashboard](https://www.tallievents.com/docs/dashboard-and-reports) shows check-ins live, with arrivals every 15 minutes. Ask your assistant ``` Show the last 20 scans at the Spring Safety Seminar and point out any that were for the wrong event or not found. ``` Select the prompt and copy it into Claude or ChatGPT connected to Talli. Uses `find_scans`. [Connect an assistant](https://www.tallievents.com/docs/ai-assistants#connect-claude) ## Coming soon - Printing a badge from the Welcome card. ## From an AI assistant - `list_entry_points` with `{ eventId }`: the event's entry points with their ids (creates Main entrance if the event has none); a session's entry point has its `sessionId`. - `check_in_attendee` with `{ eventId, entryPointId }` and exactly one of `code` (the ticket code, any case, dashes optional) or `registrationId`. The result `status` is `checked_in`, `already` (with `firstAt`, `firstEntryPoint` and `firstBy`), `wrong_event` (with `eventTitle`), `cancelled`, `waitlisted`, `pending_details` (a group ticket whose holder has not filled in their details yet) or `not_found`. At a session's entry point, `session` gives the session's `title` and `creditsAwarded` (null when nothing was awarded). - `search_attendees` with `{ eventId, q, limit? }`: matches by name, email, organization or ticket code, plus `checkedIn` and `expected` counts. - `undo_check_in` with `{ registrationId }` (owners and admins). - `set_entry_points` with `{ eventId, entryPoints }`, each `{ id?, name, kind? }` where `kind` is `door`, `session` or `booth` (owners and admins). Sessions' own entry points are not part of this list and stay as they are. - `find_scans` with `{ eventId, entryPointId?, entryPointKind?, result?, limit? }`: the scan history, newest first; `entryPointKind` is `door`, `session` or `booth`. Assistants never see attendees' accessibility needs unless an owner allows it; see [AI assistants](https://www.tallievents.com/docs/ai-assistants). [Back to all guides](https://www.tallievents.com/docs)