LeadFuel
FeaturesPricingBlogDownloadROI Calculator
Sign InGet Started
Made forThe trade show floor

LeadFuel

Capture every booth conversation. Enrich every lead. Automate every follow-up. Stop leaving revenue on the trade show floor.

Get Started →Sign In
Product
  • Features
  • Pricing
  • Integrations
  • Demo
  • Download
  • Blog
  • ROI Calculator
Company
  • About
  • Security
  • Contact
  • Support
Legal
  • Terms of Service
  • Privacy Policy
Contact
  • hello@lead-fuel.com
© 2026 LeadFuel · All rights reserved
Built for operators who own event ROI
Back to Support

Set up a Known Attendee event

Upload your guest roster ahead of time, share a mobile attendee browser with your booth team, and let LeadFuel auto-match every conversation to the right attendee.

10 minutes6 steps

Before You Start

  • An event created in the dashboard (see the Events Management tutorial)
  • Your attendee roster as a spreadsheet — first name, last name, and company are required per row
  • Recommended: email, title, and LinkedIn URL for each attendee (better enrichment hit rate)
1

Switch the event to Known Attendee List mode

Open your event's detail page in the dashboard. At the top, find the Event Type card.

Click Known Attendee List. The card highlights to confirm the change, and two new sections appear below: the Upload Attendee List widget and the Attendee Browser Link card (the Attendee Browser Link appears once you've also generated a capture invite code for the event).

This mode tells LeadFuel two things: - Expect a pre-loaded roster of attendees — bulk-enrich them when uploaded - Auto-match incoming transcript chunks to attendees by name detection, no badge scan required

Both modes can coexist on the same event. Switching to Known Attendee List doesn't disable walk-in badge scans — surprise guests still get captured normally.

2

Download the Excel template

In the Upload Attendee List widget, click Download Excel template. This downloads attendee-list-template.xlsx.

The template has these columns:

  • first_name — [REQUIRED] — used for matching and display
  • last_name — [REQUIRED] — used for matching and display
  • email — [STRONGLY RECOMMENDED] — primary dedupe key; without it, enrichment falls back to name+company matching (lower hit rate)
  • company — [REQUIRED] — used for matching and enrichment
  • title — [RECOMMENDED] — improves enrichment results
  • linkedin_url — [RECOMMENDED] — surfaces directly in the mobile attendee browser
  • phone — [OPTIONAL] — pass-through

Header names are case-insensitive (e.g. "First Name" and "first_name" both work). CSV files are accepted too — save the template as .csv after editing if your team prefers CSV.

More complete rows produce richer enrichment and more accurate matching. If you have title and LinkedIn for most attendees, include them — it makes a real difference on the rep-facing bio pages.

3

Upload the spreadsheet

Fill in your attendee data, save the file, then click Choose Excel or CSV file in the upload widget.

LeadFuel: - Parses the file and validates required columns - Creates one lead per valid row with capture_type='attendee_upload' - Skips duplicate rows by email (per event) - Returns a summary: how many were uploaded, how many were duplicates, and any rows with errors

Each uploaded attendee uses 1 enrichment credit from your configured contact-data provider (Apollo, Clearbit, Cognism, FullEnrich, Hunter, Lusha, PDL, or ZoomInfo). If you haven't connected a provider, the LeadFuel platform-managed PDL fallback runs at no extra cost.

For large lists (200+ attendees), check your enrichment provider's usage dashboard before uploading — the upload consumes credits even on a dry run.

4

Wait for enrichment to finish

After the upload, the existing process-leads cron picks up the new leads automatically. Each attendee goes through:

  1. 1Contact enrichment (firmographic data, phone, LinkedIn)
  2. 2AI "About" bio generation
  3. 3Salesforce / HubSpot lookup (if your CRM is connected)

Status progresses from queued → processing → email_ready per attendee. Most leads enrich within ~2 minutes per row.

Open the Leads view filtered to your event to watch progress — you'll see the lead count grow and statuses transition automatically.

Run a test upload at least 1 day before the event to confirm enrichment is working end-to-end with your configured provider.

5

Share the Attendee Browser link with your booth team

Once your invite code is set and the attendees are uploaded, the Attendee Browser Link card on the event detail page shows a URL like lead-fuel.com/attendees?event=YOUR-CODE.

Copy the URL and share it with everyone working the booth — email, Slack, printed QR code, whatever works. Reps open the link on their phones to:

  • Browse the alphabetical attendee list with a search box
  • Tap any name to see the attendee's bio, company highlights, and LinkedIn link
  • Look up prospects before or during a conversation

The first time a rep opens it, a banner reminds them to use the attendee's name and company in conversation. This isn't just polite — it's how the AI auto-matches the conversation to the right attendee's lead. *"Hi Sarah, you're with Acme, right?"* is far better than *"Hey, how are you?"* both for matching accuracy and for the quality of the auto-generated follow-up email.

The Attendee Browser banner is dismissible per session. For events with a new booth team each day, the banner re-appears every event — reps see it freshly when they need it.

6

After the event — review conversations and follow up on no-shows

When the event ends, every engaged attendee's lead detail page shows an Auto-matched conversations timeline at the top. Each entry has:

  • Time range of the conversation
  • The rep's name (auto-detected from the channel)
  • Match confidence (high / medium) with the transcript phrase that triggered the link
  • Expandable transcript snippet

Analysis and follow-up emails reflect all matched conversations aggregated together — so if Sarah talked to three reps over the day, her email covers everything that was discussed, not just the latest snippet.

For the attendees who didn't appear in any transcript (status pending), filter the leads list to that engagement status and run a *"sorry we missed you at the event"* follow-up campaign. These are people who RSVP'd but either didn't show or didn't talk to a rep — still worth a courtesy email reference.

The walk-ins are separate: badge/business-card scans at a known-attendee event get `engagement_status='walk_in'` so you can distinguish them from your invited list when reporting.

Troubleshooting

My upload returned 'Missing required field' errors
Each row needs first_name, last_name, and company at minimum. Check that those columns have values in every row — the parser skips rows missing required fields and reports them in the response. Save your spreadsheet, fix the empty cells, and re-upload — the dedupe by email will skip rows that already imported successfully.
Some attendees aren't getting auto-matched even though they came to the booth
The matcher needs the attendee's name to be said out loud in the transcript. Common reasons for missed matches: (1) reps used only first names — train them to use first + last name in greetings; (2) the company name was abbreviated differently than uploaded — the matcher uses exact-ish company matching; (3) the conversation happened on a channel where the microphone wasn't capturing well — check audio levels in the desktop app.
Two attendees share the same first name — they're getting confused
By design, first-name-only mentions are low confidence and don't trigger engagement when there's ambiguity. The matcher requires first AND last name in the same transcript window for a high-confidence match. Coach reps to use full names: 'Hi Sarah Chen' or 'Welcome, Marcus Patel' resolves the ambiguity automatically.
I uploaded the same list twice by accident — did I double-charge enrichment credits?
No. The upload endpoint dedupes by email per event before creating leads, so duplicate rows are silently skipped. The response summary shows the count under 'skipped_duplicates'. Only the first upload consumes credits.
A conversation got matched to the wrong attendee
False-positive matches show in the conversation timeline with a confidence indicator. Self-service deletion of incorrect matches is on the roadmap — for now, contact support and we can remove the incorrect conversation entry from the lead. The aggregated analysis will re-run automatically once the bad entry is gone.

Need more help?

Check other tutorials or reach out to our team.

All TutorialsContact Us