Scan to connect, instead of swapping cards
QR networking in event67 is one attendee scanning another attendee's code to exchange profiles. The connection is saved in both people's apps with the context of where it happened, so the follow-up email a fortnight later does not begin with an apology for forgetting who they were.
What this looks like in the product
Both halves of a connection live in the same tab, so scanning and requesting are one habit rather than two.
- Personal QR code
- Every attendee carries a scannable code that identifies the person, not one door.
- In-app scanner
- The camera opens inside the app and shows the profile before anything is saved.
- Remote connection requests
- Browse the directory and request a connection when scanning is impossible.
- Attendee visibility switch
- One setting in the Me tab removes an attendee from the directory.
- Saved connections
- Both people keep the profile and the date the connection was made.
The Connect tab
- Your own code, full screen for scanning
- Scan someone else's
- Pending requests you have received
- Your connections, with the day you met
- Browse the directory and request remotely
How a connection is made
There are two paths into the same result, because the two situations are genuinely different. In a corridor with someone standing in front of you, scanning is faster than typing. Across a room, or after the fact when you remember a name and not a face, browsing is the only option that works.
One person opens their code
Every attendee has a personal QR code in the app. It identifies the person, not the event pass, so it works for the whole event rather than for one door.
The other scans it
The camera opens inside the app. A successful scan shows the other person's profile before anything is saved, so a mis-scan is visible rather than silent.
Both sides keep the connection
The profile, the links the person chose to publish, and the date land in both apps. Nobody has to type an email address that they will mistype.
Remote requests work the same way
From the attendee directory, send a connection request instead of scanning. The recipient accepts or ignores it. An unanswered request stays pending and does not leak the requester's details.
This is attendee to attendee, and the distinction is not pedantry
Search results for QR networking at events mix two products that share a shape and share nothing else. Getting them confused is how an organizer buys the wrong thing.
Lead retrieval is an exhibitor tool. A booth rep scans a visitor's badge, the visitor becomes a lead record, and the record syncs into a CRM so a sales team can work it. The person being scanned is the asset, and they usually do not get anything back.
Attendee networking is symmetric. Two people who both came to the event agree to swap details, both keep the result, and no CRM is involved because there is no seller and no lead.
event67 does the second one. It does not do the first one, at all, in any configuration. There is no badge scanner for booth staff, no lead export by exhibitor, and no CRM integration. If your bid needs lead retrieval, this is not the product, and no amount of QR in the feature list changes that.
| Attendee networking | Exhibitor lead retrieval | |
|---|---|---|
| Who scans | Any attendee | Booth staff |
| Who benefits | Both people | The exhibitor |
| Where it ends up | Both attendees' apps | The exhibitor's CRM |
| In event67 | Yes | No, and not on the roadmap |
What the attendee controls
A networking feature that publishes people without asking is a privacy incident waiting for a quiet week. The controls are in the app, in the Me tab, and they are the attendee's to set rather than the organizer's.
- What appears on your profile
- Name, title, company, a short bio, interests, links and a photo. Every field beyond your name is optional and editable at any point during the event.
- Whether you are listed at all
- A single switch removes you from the attendee directory. You can still scan and be scanned; you simply stop being browsable.
- Who gets your details
- Only people whose scan or request you accepted. A connection is a mutual state, not a follow.
- What the organizer sees
- Organizers see the roster they invited and aggregate engagement numbers. They do not get a readable graph of who met whom.
What this will not do
- No AI matchmaking and no suggested-people algorithm. The directory is searchable by name and company, and a person decides who to approach.
- No 1:1 meeting scheduler with calendar holds and meeting rooms.
- No lead retrieval, no badge scanning for exhibitors, no CRM sync, no lead scoring.
- No offline scanning. The scan writes to the backend, so a room with no signal will queue the interaction rather than complete it.
- No public connection graph, no follower counts, and nothing that turns a conference into a social network.
Where scan-to-connect earns its place
The feature is worth most where the reason people came is the other people. A sales kickoff where three regional teams meet in person once a year. An association annual meeting where the hallway is the product. A user conference where customers want to find the two other customers with the same problem.
It is worth least at an event with one room and forty people who already know each other, where a directory is a solution to a problem nobody has.
Last updated
What it costs
- Free up to 50
- activated attendees, on one live event
- $5
- per activated attendee beyond 50
- $4,750
- the most one event can ever cost, whatever happens past 1,000
Activated means the person claimed their invite and opened the app. Not when you import them, not when the invite is delivered, and not if they register and stay home.
Questions people actually ask
Does an attendee need to be online to scan someone?
Yes. The scan is written to the backend so that both people get the connection on their own device, which means a basement ballroom with no signal will hold the interaction rather than complete it. Venue wifi is the practical fix, and it is worth asking about before you commit to a room.
Can exhibitors use this to collect leads?
Not in the sense the phrase usually means. A booth rep who is an attendee can scan people and keep those connections in their own app, but there is no lead record, no per-exhibitor export and no CRM sync. If your exhibitors have been promised lead retrieval, they will not accept this as a substitute, and you should not present it as one.
What stops attendees being scanned by people they do not want to meet?
A scan shows the other person's profile before anything is saved, and the attendee's own visibility switch removes them from the directory entirely. Beyond that, a QR code only works if its owner chooses to display it, which is the same protection a paper business card has always had.
Do connections survive after the event ends?
The connection stays in the app with the event it came from, and the profile details came across at the moment of the scan, so they do not evaporate when the event closes. Profile and participation data is retained for the event plus one year, or until the attendee asks for deletion, whichever comes first.
What does QR networking cost on top of the app?
Nothing. Connections, the directory and the QR scanner are part of the event, not an add-on tier. You pay by activated attendee: the first 50 are free, each one after that is $5, and one event stops at $4,750.
Keep reading
Features that work with this
Event types that lean on this
See it in your own event
Your first 50 attendees are free on every event, so the smallest version of this costs nothing to try.