What KYC-grade document scanning taught us about booth capture
5 practical lessons from identity-document capture for badge scanning, uncertain fields, offline use and CRM handoffs.
TL;DR: 5 checks for booth capture: let reps correct errors during the conversation, report confidence for each field, test venue conditions, validate fields during capture and send the context to the CRM.
Before Luminik, I worked with the marketing team at an identity-document AI company on booths, target lists, follow-up and pipeline reporting. At the booth, we were demonstrating capture technology while dealing with errors in our badge scans. A misread company name could send follow-up toward the wrong account. These 5 checks focus on correcting those errors while the attendee is present and passing a usable record to sales.
1. Let the rep correct errors during the conversation
If a prospect leaves the booth in 90 seconds, the rep has a short window to check the record. Design for one-handed operation, instant feedback on what was read, and a manual path that takes seconds when the automatic one struggles. A later correction may require contacting the attendee again.
2. Report confidence for each field
A capture record is easier to review when it includes confidence for each field. A confident name can auto-fill; an uncertain one can be flagged for review. Apply that approach to booth capture:
- Confident fields write to the CRM untouched.
- Uncertain fields surface for a one-tap fix while the person is still there.
- Flag uncertain fields rather than silently guessing. A misread company name can pull in the wrong firmographic data, route the contact to the wrong account owner and attach follow-up to the wrong record.
3. Test venue conditions
Lighting, screen condition and device age can affect document capture. At a conference or trade show, include these conditions in the test:
| KYC condition | Booth condition | Design consequence |
|---|---|---|
| Kitchen-table glare | Expo hall downlights on laminate | Read across multiple frames, not one shot |
| Old device cameras | Reps’ personal phones | On-device processing that degrades gracefully |
| No connectivity mid-flow | Convention-center Wi-Fi | Offline-first queue, sync when the network returns |
| Unfamiliar document layouts | Every organizer’s new badge design | Layout-agnostic reading, not per-event templates |
4. Validate fields during capture
In identity flows, a birthdate that parses as next year is rejected at the point of capture. Booth capture has the same class of cheap, decisive checks: a company field that reads as a country name, a title that is the event’s tagline, an email domain that does not exist. Catching an error at the booth lets the rep ask the attendee for the correct company or title. After the attendee leaves, marketing ops may have to search for a match and ask the rep to reconstruct the conversation before routing the lead.
5. Send a usable record to the CRM
For sales to act on a badge scan, the CRM record needs the ICP score, account match, owner and agreed next step. Keep the event attribution fields with that record so RevOps can trace a later opportunity to the event conversation. Check that those fields arrive with the contact details and booth notes. In the Series C cybersecurity program, the case study reports 1,840 ICP-matched accounts in its RSA pass. Its roughly 43,000 attendee figure is event context, not an account-to-contact conversion denominator. Across RSA, Black Hat and a regional summit, the program recorded 85+ qualified meetings and $2.4M in attributed pipeline, and the badge scan was exactly one stage of that.
Checklist
My role was event marketing. I did not build the scanning technology. When evaluating capture tools, check each of these 5 areas: correction during capture, uncertain fields, venue conditions, validation and the CRM handoff. The during-event capture page shows how Luminik answers the five, and where the stage hands off to attribution. For the organizer side of the same question, see trade show lead retrieval costs and options and the badge OCR field guide.
