--- title: "KYC scanning lessons for event lead capture" description: "Five practical lessons from identity-document capture for badge scanning, uncertain fields, offline use and CRM handoffs." canonical: https://www.luminik.io/blog/2026/kyc-lessons-booth-capture/ source: html generated_at: 2026-10-05T09:21:23.778Z --- 1. [Home](/) 2. [Blog](/blog/) 3. [2026](/blog/2026/) 4. What KYC-grade document scanning taught us ab… AI in Marketing # What KYC-grade document scanning taught us about booth capture Five practical lessons from identity-document capture for badge scanning, uncertain fields, offline use and CRM handoffs. ![Prasad Subrahmanya avatar](/founders/prasad-192.webp) Prasad Subrahmanya Founder & CEO, Luminik, August 8, 2026, 3 min read > **TL;DR:** Five 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 own badge scans. A misread company name could send follow-up toward the wrong account. These five 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 ninety 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 | Attach account fit, booth notes, an owner and the next step to the captured CRM record. ## 4\. Validate fields during capture In identity flows, a birthdate that parses as next year is rejected at the point of capture, not discovered in an audit. 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](/case-studies/cybersecurity-automation-rsa-blackhat/), 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, not building the scanning technology. When evaluating capture tools, check each of these five areas: correction during capture, uncertain fields, venue conditions, validation and the CRM handoff. The [during-event capture](/product/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](/blog/2026/trade-show-lead-retrieval-costs-and-options/) and the [badge OCR field guide](/blog/2026/badge-ocr-field-guide/). ![Prasad Subrahmanya avatar](/founders/prasad-192.webp) About the author Prasad Subrahmanya Founder & CEO, Luminik Founder of Luminik. Previously Venture CTO at Bain & Company and cofounder at Mainteny. Writes about how mid-market B2B teams build predictable pipeline from events. [Connect on LinkedIn](https://linkedin.com/in/prasadus) Keep reading ## More on AI in Marketing [All posts](/blog/) [![The field guide to badge OCR: why confidence beats accuracy claims cover image](/blog-thumbnails/badge-ocr-field-guide.png)AI in MarketingThe field guide to badge OCR: why confidence beats accuracy claimsGlare, lanyards and handwritten name tags decide what reaches your CRM. How to read badge scanning and OCR accuracy claims, and what to test before buying.](/blog/2026/badge-ocr-field-guide/)[![Why badge scans do not become pipeline (and how to fix it) cover image](/blog-thumbnails/ai-event-lead-capture.png)AI in MarketingWhy badge scans do not become pipeline (and how to fix it)Badge scans become pipeline only when ICP fit, conversation context, owner, next step and CRM attribution travel with the record. How to capture all five.](/blog/2025/ai-event-lead-capture/)[![Cvent LeadCapture and iCapture leads into Salesforce or HubSpot cover image](/blog-thumbnails/cvent-lead-capture-icapture-salesforce-hubspot.png)Lead CaptureCvent LeadCapture and iCapture leads into Salesforce or HubSpotHow Cvent LeadCapture and iCapture leads reach Salesforce or HubSpot, from Cvent's own docs: exports, sync, field mapping, campaign status and dedupe.](/blog/2026/cvent-lead-capture-icapture-salesforce-hubspot/) ## See how Luminik would approach your next event A 20-minute walkthrough, tailored to the events on your calendar. [Book a 20-min walkthrough](/demo/) ![Prasad Subrahmanya](/founders/prasad-192.webp) > I take every walkthrough myself. Bring the next event on your calendar. Prasad Subrahmanya, founder