Skip to main content
QR scanning is the primary check-in path in TalkValue Badge. Staff tap Scan Ticket, point the camera at the attendee’s QR code (printed on a ticket or shown on a phone), and confirm a single drawer to check the attendee in and queue a badge print at the selected print station. End-to-end, a clean scan takes a few seconds.
Before you start
  • You’re in Check-in mode on the staff station. See Open on mobile.
  • To print badges, pick a print station first. Tap the station chip in the header (it reads Select Station until you pick one) and choose a station. The status beside it reads Connected when that station’s printer is ready. You can scan and check in without a station, then print the badge later from a print station.
  • The device camera is granted browser permission. The first scan attempt prompts for it.

​
Scan an attendee

1

Tap Scan Ticket

The blue Scan Ticket bar is pinned to the bottom of the check-in screen. Tap it. A full-screen scanner opens with a viewfinder in the middle.
2

Grant camera permission (first time only)

The browser asks for camera access. Tap Allow. The viewfinder turns on and starts scanning. iOS Safari and Android Chrome remember the permission for the session.
3

Point the camera at the QR

Hold the device 10 – 30 cm from the QR. The scanner reads the code and the screen transitions to the attendee drawer within a second of a clean read. There’s no “snap” or shutter button; the scanner reads continuously.
4

Confirm the attendee

The drawer shows the attendee’s name, email, ticket type, VIP flag, and today’s check-in time if they already checked in today. Verify the details match the person in front of you, then tap the drawer’s primary action to confirm. The button is contextual: Print Badge & Check In for standard attendees, Reprint Badge if already checked in today, Force Check In if marked not attending, and Check In when no station is selected or its printer is disconnected. With a station, a toast confirms Checked in & printing badge and the badge job is queued there. Without one, the toast reads Checked in with a reminder to print the badge later from a print station. Spot a typo in the details? Fix what prints before confirming. See Edit what prints on the badge.
5

Close the scanner or scan the next attendee

The scanner stays open after confirming a check-in, ready for the next person. Tap Close Scanner to return to the check-in screen, or keep pointing at the next QR.
The scan delay between consecutive reads is 2 seconds, which keeps the scanner from double-firing on the same QR if it lingers in the viewfinder.

​
What the QR encodes

The QR on the printed ticket or in the attendee’s email encodes the barcode that uniquely identifies the attendee inside Badge. Depending on the provider, that value is a plain code or a full check-in URL — Luma tickets, for example, encode a https://luma.com/check-in/… link. The scanner sends whichever value it reads to the lookup, so both forms resolve to the attendee and open the drawer. Two practical consequences:
  • A wrong QR shows “Attendee not found.” If a guest hands over a ticket for a different event, or an old screenshot from a previous registration, the lookup fails. Fall back to Manual search check-in.
  • The same QR scans on every staff device. Multiple staff can scan the same event independently. There’s no device pairing, only the access code.

​
Re-prints and force check-ins

The same scan path covers two edge cases without leaving the scanner:
  • Re-print. If the attendee already checked in today, the drawer shows Already checked in with the time, and the action button reads Reprint Badge. Tapping it queues a new badge at the selected station without altering the check-in record. A toast confirms Reprint requested. Reprinting needs a selected station; without one you see Reprinting needs a print station.
  • Force check-in. If the ticket is marked as not attending, the drawer shows a Not attending warning and the action button reads Force Check In. Tapping it asks you to confirm. Use it when you’ve verified the person in front of you matches the record. The toast confirms Force checked in & printing badge.
  • Multi-day events. Check-in status resets each day in the event’s time zone. An attendee who checked in yesterday shows as not checked in today, and checking them in records today’s arrival.

​
Edit what prints on the badge

A misspelled name, a missing company, an outdated job title, a registration answer that changed since sign-up: fix any of it at the desk without touching the attendee record. The attendee drawer has an Edit Badge button above the details:
1

Tap Edit Badge

A drawer titled Edit Badge opens with an input for each value this attendee’s badge prints: first name, last name, company, job title, and any registration answer placed on the badge template. Each input holds the attendee’s current value. An input marked Prints in the contact QR only. changes the contact QR code, not the printed text.
2

Change any field

When First Name appears, it’s required; the rest are optional. Whatever you type here is what prints. Clearing a registration answer prints the badge with that field empty.
3

Print

Tap Print Badge & Check In, or Reprint Badge if the attendee already checked in today. The badge prints with your edits.
The edits apply to this print only. The attendee record keeps its original values, and later syncs from the provider are unaffected. Printing an edited badge needs a print station. Without one selected, TalkValue shows Printing an edited badge needs a print station and doesn’t check the attendee in.

​
Cancelling a mistaken check-in

To undo a wrong check-in, open the three-dot menu at the top of the attendee drawer and tap Cancel Check-in. It appears for attendees checked in today. A toast confirms Check-in cancelled, and the attendee returns to the pending list. Cancelling does not retract any printed badge; physically retrieve and discard the badge.

​
Troubleshooting

​
”Camera permission denied”

Browser blocked camera access. Open the device’s site settings for app.trytalkvalue.com, set Camera to Allow, then retry. On iOS Safari, the toggle is in Settings → Safari → Camera → Allow.

​
”No camera found”

The device doesn’t expose a usable camera to the browser, usually because another app holds the camera. Close any other camera-using apps (FaceTime, Zoom, Instagram), then retry.

​
”Camera is in use”

Another tab or app is using the camera. Close them and tap Retry in the scanner.

​
”Attendee not found” on a valid-looking QR

Three possibilities, in order of likelihood: the ticket is for a different event, the QR is from a cancelled or refunded registration that’s no longer in the attendee list, or the QR is unrelated to the ticket entirely (a website link, a Wi-Fi code). Fall back to Manual search check-in and look the attendee up by name or email.

​
”No barcode available” when tapping Check In

The attendee record exists but doesn’t carry a barcode, common for manually-added attendees and some Luma free events. Record them as a walk-in instead: tap Walk-in in the header. On a print station it opens Print New Badge and prints from the details you type. On a phone it opens Record Walk-in, which logs the walk-in without printing. See Walk-ins and missing records.

​
Scanner opens but won’t pick up the QR

Three quick fixes: improve lighting (a dim QR doesn’t scan), hold the camera further back so the full QR fits in the viewfinder, and clean the camera lens.

​
A “Print Failed” dialog appears

The check-in was recorded, but the badge didn’t print, usually because the station went offline. Tap Select Station to pick another station and reprint, or Not now to reprint later.

​
A banner says “Attendee sync is down”

The event’s integration stopped syncing, so registrations made since then may be missing from the list. Ask the event manager to reconnect it (see Recovering from disconnect). Meanwhile, record anyone you can’t find with Walk-in.

​
”Check-in failed”

A network or server error during the check-in call. Try again. If it persists, switch to a different device on the same access code, since the attendee record is shared across all staff devices.