Turn a conference attendee list into verified leads
Images on this page are for illustrative purposes only. Example outputs in this play are illustrative — the structure, fields, and format reflect real Lusha connector and Gmail output, but were not pulled from a live session. Run the prompt with your own event list and connectors to see live results. Personal details in any live examples are masked or abbreviated for privacy.
A badge scan list is raw data — names, companies, and inconsistent titles that arrive in a PDF three days after the event. This Claude prompt enriches every attendee via Lusha, scores each against ICP criteria, checks Gmail for any prior contact, and drafts a specific first-touch email for every Grade A and B attendee — referencing the event honestly, whether the rep met the person in person or not.
The prompt
This prompt may contain placeholders — look for [BRACKETS] and fill them in.
<context>
I have a list of attendees from a conference or event. Before I reach out to any of them, I want to enrich the list with verified contact data, score each attendee against my ICP, and have a personalized first-touch email ready for the best ones — referencing the event specifically.
My event list:
- Event name: [EVENT NAME]
- Attendee list: [PASTE NAME, COMPANY, TITLE (if known), EMAIL (if known) — one per line]
- What I sell: [PRODUCT / SOLUTION]
- ICP criteria: [SIZE / INDUSTRY / FUNCTION / SENIORITY]
- Did I meet any of these people at the event? [YES — LIST WHO / NO]
</context>
<task>
1. For each attendee, use Lusha to enrich and validate:
- Current verified title — does it match the badge scan?
- Verified work email and direct phone
- Company: headcount, industry, HQ location
- ICP fit: does the company and role match my stated criteria?
2. Score each attendee:
- A: strong ICP fit, decision-maker, all fields verified
- B: ICP fit, influencer level or partial fields
- C: partial ICP fit or unverified
- D: outside ICP — don't route to outreach
3. Check Gmail for any prior contact with each attendee or their company domain.
4. For every Grade A and B attendee, draft a first-touch email:
- Subject: references the event by name — not "Following up"
- Opening: one sentence that places the event context honestly
- If we met in person: reference the specific conversation
- If we didn't meet: acknowledge the shared event without pretending otherwise
- Body: one specific reason this conversation is relevant given their role and company
- Closing: one low-friction ask
- Under 80 words
5. Return:
- Enriched attendee table with ICP grade and verification status
- First-touch drafts for Grade A and B attendees
- Prior Gmail thread flags per attendee
- Summary: X Grade A, X Grade B, X to skip
</task>
<constraints>
- Never pretend we met if we didn't. The opening must be honest about the event context.
- Grade D gets no draft and no outreach recommendation.
- Under 80 words per email. Count them.
- Flag title mismatches between badge data and Lusha — badge scans are frequently inaccurate.
</constraints>What you'll get back
The situation: An SDR returns from RevOps Summit with a badge scan list of 6 attendees. Selling sales intelligence software into RevOps and Sales Operations, VP level and above. Met 2 people at the event; the rest are names from the badge scan PDF.
Enriched attendee table
| Attendee | Company | Badge title | Verified title | Grade | Note |
|---|---|---|---|---|---|
| R.V. | Crestline Software | Head of Operations | VP Revenue Operations | A | ⚠ Title mismatch — badge was generic |
| T.K. | Dunmore Analytics | VP Sales | VP of Sales ✓ | A | Met in person ✓ |
| M.L. | Ashford Platforms | Operations | Head of Sales Operations | B | ⚠ Prior Gmail thread — flagged below |
| P.O. | Briarwood SaaS | VP | VP of Sales ✓ | B | — |
| C.N. | Elmont Systems | Director | Director of RevOps | C | Below VP threshold |
| [Badge: “John S.”] | Unknown | — | — | — | NOT FOUND — name doesn’t resolve |
Summary: 2 Grade A · 2 Grade B · 1 Grade C · 1 unresolvable
Prior contact flag
M.L. at Ashford Platforms: Gmail shows a thread from 6 months ago — a colleague sent pricing information, no reply was received. Flag to the rep before sending. The email should reference the prior contact rather than treating this as a cold intro from the event.
First-touch drafts
R.V. — Crestline Software · Grade A · Didn’t meet
To: r.v@[crestline].com Subject: RevOps Summit — we were both there but didn’t connect
Hi R.V.,
We were both at RevOps Summit but didn’t get a chance to meet. As VP RevOps at Crestline, the data quality conversation is probably a recurring theme. Worth 15 minutes to see if it’s relevant?
[Name]
T.K. — Dunmore Analytics · Grade A · Met in person
To: t.k@[dunmore].com Subject: Good to meet you at RevOps Summit
Hi T.K.,
Enjoyed the conversation at the Summit. You mentioned the SDR data layer was on the Q3 list — happy to show you what that looks like in practice.
15 minutes this week?
[Name]
P.O. — Briarwood SaaS · Grade B · Didn’t meet
To: p.o@[briarwood].com Subject: RevOps Summit — a belated introduction
Hi P.O.,
We didn’t cross paths at RevOps Summit, but we were both there. Selling into Sales leadership at companies your size is our focus — curious whether the data quality side of the stack is on your radar.
Quick call?
[Name]
Illustrative example — fictional company names used. Run with your own event list to see live results.
Why use Lusha in Claude
The R.V. badge scan shows “Head of Operations” — a title so generic it tells the rep nothing about seniority or function. Lusha returns “VP Revenue Operations” — a title that changes the entire email and confirms the attendee is a Grade A decision-maker. Without the Lusha check, R.V. looks like a vague operations contact. With it, the rep knows to prioritize the call. The M.L. prior contact flag is the other finding that changes behavior: without it, the rep sends a “nice to meet you at RevOps Summit” email to a company where a colleague already sent pricing information 6 months ago. The event framing masks the prior relationship. Lusha + Gmail surfaces it before the send.
Data drawn from 300M+ verified contacts under GDPR, CCPA, SOC 2, ISO 27701, ISO 31700, and TRUSTe.
FAQ
How long do I have before the event context loses its warmth?
Send within 5 business days of the event. Beyond 2 weeks, “we were both at RevOps Summit” loses its relevance and the email should shift to a direct cold outreach framing rather than an event reference. The event context is strongest in the first week — use the window.
What if the badge scan has company names only and no attendee names?
The prompt searches for the most relevant verified contact at each company in Lusha. The opening line shifts from “we were both at [Event]” to “I saw your company was represented at [Event].” Less personal but still grounded in the event context.
What if I have 50+ badge scans?
Run in batches of 15–20. The enrichment and scoring logic is consistent across batches and the output format stays the same, so combining results from multiple runs is straightforward.
Why does the prompt require honesty about whether we met?
Sending “great to meet you at the Summit” to someone you didn’t actually speak to is easy to detect — and the recipient notices. A rep who opens with “we were both at the Summit but didn’t connect” is more memorable than one who pretends a conversation happened. The honest opener works because it’s specific without being presumptuous.
How is this different from the lead list enrichment prompt?
The enrich lead list before import prompt is designed for CRM import — it fills fields and ICP-scores before data enters the system. This prompt is designed for outreach — it enriches, scores, checks prior contact, and drafts the first email in one pass. Use the import prompt when the goal is clean CRM data; use this one when the goal is pipeline from the event list.
Ready to build this?
Get started with Lusha and set up this play in minutes.
