Run the door on the platform that already holds your leads
Issue tiered tickets, send them with wallet passes, and scan people in with the Lynqu app — with every check-in landing on the lead record you already work.
- Apple & Google Wallet
- Works offline at the door
- Re-entry counted, not blocked
Lynqu turns the leads you already hold into event tickets. Pick who's attending, give them a tier, and Lynqu issues each person a unique entry QR. The ticket email carries the QR plus Add to Apple Wallet and Google Wallet buttons, and it reaches every attendee — it's transactional, so it isn't suppressed by marketing opt-outs. At the door, your team scans with the Lynqu app: the screen floods in the attendee's tier colour with their name, so a VIP is obvious at a glance. Re-entry is allowed and counted rather than blocked. Check-in lands on the same lead record your pipeline already reads, so you can see who actually showed up.
How does event check-in work in Lynqu?
Lynqu turns the leads you already hold into event tickets. Pick who's attending, give them a tier, and Lynqu issues each person a unique entry QR. The ticket email carries the QR plus Add to Apple Wallet and Google Wallet buttons, and it reaches every attendee — it's transactional, so it isn't suppressed by marketing opt-outs. At the door, your team scans with the Lynqu app: the screen floods in the attendee's tier colour with their name, so a VIP is obvious at a glance. Re-entry is allowed and counted rather than blocked. Check-in lands on the same lead record your pipeline already reads, so you can see who actually showed up.
The ticket starts as a lead and comes back as one
Four steps from an attendee list you already have to a check-in your pipeline can read.
Issue from your leads
Pick who's attending from the leads you already hold, give them a tier, and each person gets their own entry QR. No import, no separate attendee list to keep in sync.
Send it with a wallet pass
The ticket email carries the QR as a real attachment plus Add to Apple Wallet and Google Wallet buttons. It's transactional, so a marketing opt-out never blocks someone's ticket.
Scan at the door
Any team member scans with the Lynqu app. The screen floods in the attendee's tier colour with their name, so a VIP is obvious at a glance. Re-entry is counted, not blocked.
It lands on the lead
Who actually showed up is a field on the lead record your pipeline already reads — so follow-up, scoring and reporting see attendance without an export.
The same event, end to end: Badge & card scanningWallet passesMeeting booking
The Queue Doesn't Care That the Wifi Died
Basement venues, packed halls and shared event wifi all fail at the same moment: when everyone arrives at once. Turn on offline scanning for an event and your team's phones keep the door moving without a connection at all.
A signed list, not a copy of your database
Before the doors open, staff phones pull a signed manifest for that event. It holds hashed ticket references — never the ticket codes themselves — and it expires on the window you set, so a lost phone after the event is a lost phone, not a lost guest list.
The same answer, with or without bars
Scanning offline gives the same verdict and the same tier colour as scanning online, and re-entry is still counted rather than refused. If a scan genuinely can't be judged, the app says exactly that — it never guesses "invalid" at someone holding a valid ticket.
The queue empties itself
Every check-in taken offline is held on the device and sent the moment signal returns — no export, no reconciliation, nobody re-typing names. Attendance lands on the same lead records your pipeline already reads.
The ticketing tool knows who came. The CRM knows who they are. Neither knows both, so the follow-up starts from a spreadsheet.
The ticket is issued from the lead, so the check-in writes straight back to it — who showed up is a field on the record, not an export.
From lead list to open door
Three parts, all on rails Lynqu already runs.
Issue in bulk, by tier
Select the leads attending, choose a tier, and every one of them gets a permanent entry QR. Re-issuing only changes the tier — a ticket already printed or saved to a wallet keeps working.
Tickets that actually arrive
The ticket email is transactional, so it reaches attendees who opted out of your marketing and never counts against your follow-up limits. The QR rides as a real attachment as well as an image, so it works with images turned off, and Apple Wallet and Google Wallet buttons are right there.
A door that reads at arm's length
Scanning happens in the Lynqu app your team already has. The result fills the whole screen in the attendee's tier colour with their name, backed by a distinct icon and haptic so it reads in a loud room and without relying on colour alone. Re-entry shows the first entry time and a scan count instead of blocking anyone, and staff can keep scanning offline from a downloaded list that expires on a window you set.
Where Lynqu Runs the Door
Three ways organizers use Lynqu to run entry on the same platform that holds the relationship.
Conference Organizer
Tiered entry without a second system
A summit issues VIP, speaker and general tickets from its existing lead list, each tier in its own colour. Door staff see the tier fill the screen before they read a name, so the VIP lane moves without anyone checking a printed list.
10
Tiers per event
1
QR per attendee
0
Extra systems
Venue & Ops Lead
A door that survives bad wifi
Basement venues lose signal exactly when the queue is longest. With offline scanning enabled, staff phones hold a signed attendee list and keep validating locally, then sync every check-in the moment they reconnect.
Offline
Validation
Signed
Attendee list
Auto
Sync on return
Field Marketing Team
Attendance that reaches the pipeline
Because the ticket was issued from a lead, checking someone in writes straight back to that record. The team segments no-shows from attendees the next morning without exporting anything, and automations can react to a check-in the moment it happens.
Same
Lead record
0
CSV exports
Live
Automation trigger
Event Check-in Questions, Answered
Do attendees need the Lynqu app?
No. Attendees get an email with their QR code attached, a link to their own ticket page, and buttons to add the ticket to Apple Wallet or Google Wallet. Only your door staff use the Lynqu app, to scan.
What happens if someone leaves and comes back?
They get back in. Re-entry is allowed by design — lunch breaks are normal at a conference. The second scan still shows green, with the original entry time and the scan count, so door staff see the full picture instead of being stopped by a warning.
Can we scan without an internet connection?
Yes, if you enable offline scanning for the event. Staff devices download a signed attendee list that stores hashed ticket codes, never the raw ones, and validate against it locally. You set how long that list stays valid, and every offline check-in syncs automatically once the device is back online.
What if we need to cancel someone's ticket?
Revoke it, and the QR stops working immediately. Any wallet pass already saved to that person's phone is voided too. If it was a mistake, restoring the ticket keeps the same code, so a QR that was already printed or saved to a wallet keeps working.
Don't take our word for it
Ask any AI about Lynqu
Get an unbiased breakdown from the AI you already trust. One click — your question is pre-filled.
Opens a new tab with your question pre-filled.
Need this for your team?
Get a Demo
Meeting Booking
Turn a shared link or card tap into booked meetings with availability rules, calendar invites, and a shared request inbox.