> ## Documentation Index
> Fetch the complete documentation index at: https://docs.boothrev.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Importing leads

# Importing Leads

BoothRev supports two kinds of CSV import: a pre-event **pre-registered attendee list**, and a post-event **badge scanner file**. This is the **inbound** CSV channel — for the conversational alternative (pulling a registration platform's attendee list straight through Claude, no file needed), see [Connecting Claude → Import attendees from another tool](/integrations/connecting-claude#import-attendees-from-another-tool).

***

## Pre-registered attendee import

If the event organizer gives you a list of registered attendees before the event starts, import it as a **pre-registered** list. This gets your reps a head start: they can review who's coming, and any rep can add notes or record a meeting on a pre-reg lead without needing to "claim" it first.

Pre-registered leads:

* Are created with no owner — every rep assigned to the event sees them in their mobile sync.
* Get ICP-scored automatically on import, for any row that has an email address.
* Have no separate "claim" step. The first rep to confirm the lead's email address automatically becomes its owner.
* Are skipped on re-upload if they already exist — importing the same file twice never creates duplicates.

If a rep captures the same person manually (scan, voice note, or manual entry) before the pre-reg lead is claimed, BoothRev merges the manual capture's details into the pre-reg lead rather than creating a second record.

If your attendee list includes a **notes** column — background on the attendee from the organizer, LinkedIn research, whatever your team has ahead of the event — map it during import. It's added to the lead's activity timeline as research context any rep can read before they even start the conversation, giving them a head start on rapport and qualification.

***

## Badge scanner import (post-event)

Most trade show organizers also provide a CSV file of everyone who scanned your badge or visited your booth after the event. Import that the same way, selecting the badge scanner import type.

Import it as soon as the organizer sends it — ideally on the day of the event or the morning after. The sooner the imported leads land in the inbox, the sooner your team can confirm emails and follow up.

***

## What the import does

When you import a CSV, BoothRev reads each row and adds it as a lead. Each imported lead starts in your Leads queue labeled **Email needed**. An email address in the CSV does not count as a confirmation. A rep or event owner still needs to confirm it.

This is intentional. Badge scanners collect a lot of data, and not every scanned badge represents a strong conversation. The confirmation step keeps the inbox clean.

***

## Auto-enrichment: when CSV data fills in existing leads

If a badge scanner lead matches someone a rep already captured manually, BoothRev does something smart: it doesn't create a duplicate. Instead, it fills in any missing fields on the existing lead from the CSV data.

For example: a rep captured a lead with a name and note but no email. The badge scanner file has their email. BoothRev adds the email to the existing lead and notes the enrichment in the activity timeline. The rep's notes and context stay intact.

This happens automatically. You don't need to merge them manually.

***

## How to import

1. Go to your event inbox.
2. Click **Import CSV** (in the inbox header or the Leads queue empty state).
3. Upload the CSV file from the organizer.
4. BoothRev processes the file and shows you a summary.

***

## Reading the import results

After import, you'll see a breakdown:

| Result | What it means |
| - | - |
| **Drafts** | Leads added to your Leads queue, waiting for email confirmation |
| **Enriched** | Existing leads that had missing fields filled in from the CSV |
| **Duplicates** | Leads flagged for your review — two CSV rows that may be the same person |
| **Errors** | Rows that couldn't be processed (missing required fields, formatting issues) |

Review any Errors to see what went wrong. Fix the rows in a spreadsheet and re-import them if needed.

***

## After the import

Work through the Leads queue and confirm email addresses for the leads worth following up. Use the search and filter tools to prioritize by company, title, or ICP fit.

***

## Related

* [Integrations](/integrations/index)
* [Integrations → Connecting Claude](/integrations/connecting-claude) — the conversational alternative for registration-platform imports
* [Your inbox](/for-event-owners/your-inbox)
* [Managing leads](/for-event-owners/managing-leads)
* [Integrations → Exporting leads](/integrations/exporting-leads)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.