Score and prioritize post-event leads before handoff to sales
Images on this page are for illustrative purposes only. Example outputs in this play are illustrative — the structure, fields, and format reflect real Lusha, Gmail, and Slack connector output, but were not pulled from a live session. Run the prompt with your own attendee list and connectors to see live results. Personal details in any live examples are masked or abbreviated for privacy.
Scoring post-event leads before sales handoff means validating every attendee against verified firmographic and contact data, checking for prior sales conversations, and routing each lead to the right person with the right context — not sending a raw badge scan list to sales and hoping for the best. This Claude prompt runs every attendee through Lusha for ICP scoring and signal detection, checks Gmail for prior sales contact at each company, assigns a P1–P4 priority, drafts a handoff note per lead, and posts priority alerts to Slack — so sales reaches out warm, not cold.
The prompt
This prompt may contain placeholders — look for [BRACKETS] and fill them in.
<context>
An event just ended. I have an attendee or badge scan list and I need to score every lead, prioritize for sales handoff, and make sure the right contacts go to the right people with the right context — before sales reaches out cold to someone marketing already spoke to.
My post-event list:
- Event name: [EVENT NAME]
- Attendee list: [PASTE NAME, EMAIL, COMPANY, TITLE (if known) — one per line]
- What we sell: [PRODUCT / SOLUTION]
- ICP criteria: [COMPANY SIZE / INDUSTRY / FUNCTION / SENIORITY]
- Did anyone from our team meet specific attendees? [YES — LIST WHO / NO]
- Sales team Slack channel: [CHANNEL NAME OR "skip"]
- AE or SDR to route to: [NAME OR "auto-assign by territory"]
</context>
<task>
1. For each attendee, use Lusha to enrich and validate:
- Current verified title — flag mismatches with badge or form data
- Still at the company? Flag departed contacts.
- Company: headcount, industry, HQ, funding stage, tech stack
- ICP fit score: A (strong fit, decision-maker), B (ICP fit, influencer),
C (partial fit), D (outside ICP)
- Any account signal in the last 30 days
2. Check for any prior sales contact with each attendee or company domain via Gmail:
- Has anyone from the sales team been in touch before?
- If yes: who, when, what was discussed — flag as warm, not cold
3. Score and prioritize the full list:
- P1 — ROUTE TO AE TODAY: Grade A ICP + met in person OR prior sales contact + strong signal
- P2 — SDR SEQUENCE THIS WEEK: Grade A or B ICP + no prior contact + signal present
- P3 — NURTURE: Grade B or C + no signal + no prior contact
- P4 — DO NOT ROUTE: Grade D, outside ICP — nurture list only
4. For every P1 and P2 lead, draft a one-line handoff note for the sales rep:
- Role, company context, signal if any, prior contact if any
- One specific suggested opening referencing the event
5. Return:
- Full scored and prioritized lead table
- P1 leads with handoff notes — route immediately
- P2 leads with handoff notes — SDR sequence this week
- P3 and P4 summary — nurture, no sales action needed
- Slack alert if channel specified: P1 contacts tagged to assigned rep
- Summary: X P1, X P2, X P3, X P4
</task>
<constraints>
- Prior sales contact flagged on every P1 and P2 lead — the rep must know before reaching out.
- Departed contacts are not routed under any circumstances.
- P1 requires Grade A ICP AND either a signal or in-person meeting — don't inflate P1.
- Handoff note must be specific — not "follow up from event" but the exact context the rep needs.
</constraints>What you'll get back
The situation: RevOps Summit just ended. A field marketing manager has 6 attendees from the badge scan. Sales team is in #sales-leads on Slack. Two attendees were met in person.
Scored lead table — RevOps Summit
| Attendee | Verified title | Company | Size | ICP | Signal | Prior contact | Priority |
|---|---|---|---|---|---|---|---|
| R.V. | VP Revenue Operations | Crestline Software | 340 | A | Hiring +22% | None | P1 |
| T.K. | VP of Sales | Dunmore Analytics | 580 | A | Series B · 18d | ⚠ Yes — pricing thread | P1 |
| M.L. | Head of Sales Operations | Ashford Platforms | 420 | B | None | None | P2 |
| P.O. | VP of Sales | Briarway SaaS | 290 | A | None | None | P2 |
| C.N. | Director of RevOps | Elmont Systems | 610 | B | None | None | P3 |
| [Badge: J.S.] | Marketing Coordinator | Waverly Digital | 180 | D | None | None | P4 |
P1 — Route to AE today
R.V. · Crestline Software · @james.ae VP RevOps, 340-person SaaS, hiring surge 22% in the last 30 days. Met in person at RevOps Summit. Handoff note: “R.V. runs RevOps at a company actively scaling. No prior contact — fresh start. Open with: ‘We met at RevOps Summit — given how fast you’re hiring, the data quality conversation is probably timely.'”
T.K. · Dunmore Analytics · @sarah.ae VP Sales, 580-person SaaS, Series B closed 18 days ago. No in-person meeting. ⚠ Prior contact: colleague emailed T.K. 54 days ago about pricing — no reply received. Handoff note: “Warm account — pricing discussion already started by James. Don’t cold-open. Reference the prior thread: ‘With the Series B just closed, the conversation James started is probably more relevant now.'”
P2 — SDR sequence this week
M.L. · Ashford Platforms Head of Sales Operations, 420-person SaaS. Attended but no in-person meeting. No prior contact. No active signal. Sequence opening: “You attended RevOps Summit — data quality for ops teams at your scale is usually front of mind. Worth a quick call?”
P.O. · Briarway SaaS VP Sales, 290-person SaaS. No prior contact. No active signal. Grade A ICP. Sequence opening: “We were both at RevOps Summit. SDR data quality at your headcount is the thing that usually comes up first — happy to show you what that looks like.”
P3 — Nurture: C.N. at Elmont Systems — Director level, below VP floor. Add to nurture sequence, revisit in 60 days.
P4 — Do not route: J.S. at Waverly Digital — Marketing Coordinator, outside ICP. Add to event nurture only.
Slack alert posted to #sales-leads
🔥 2 P1 leads from RevOps Summit · @james.ae @sarah.ae — handoff notes above. Route today.
Summary: 2 P1 · 2 P2 · 1 P3 · 1 P4
Illustrative example — fictional company names used. Run with your own attendee list to see live results.
Why use Lusha in Claude
Lusha in Claude connects three inputs that marketing and sales typically handle separately — the badge scan, the sales CRM thread history, and the live account signals. The T.K. finding is the critical one: Sarah is about to cold-open a company that James already has a pricing thread with. Without the Gmail check, the Dunmore account gets two uncoordinated touches in the same week from different reps. With the prior contact flag, Sarah references James’s conversation instead of starting over. The P1 requirement — Grade A ICP plus either a signal or an in-person meeting — stops every attendee from being routed to sales as a hot lead, which is the pattern that erodes sales trust in marketing’s event lists over time.
Data drawn from 300M+ verified contacts under GDPR, CCPA, SOC 2, ISO 27701, ISO 31700, and TRUSTe.
FAQ
What makes a lead P1 rather than P2?
P1 requires Grade A ICP fit — decision-maker at an ICP-matching company — plus either an in-person meeting at the event or a live buying signal from the last 30 days. A Grade A lead with no signal and no in-person meeting is P2, not P1. The distinction matters because P1 leads go directly to AEs, while P2 leads go to SDR sequences. Inflating P1 wastes AE time on leads that aren’t ready.
What if the entire list comes back as P3 or P4?
That’s accurate data, not a problem with the play. A P3-heavy post-event list means the event attracted an audience that doesn’t match the ICP — which is useful information for the field marketing team’s next event selection decision. Don’t force P1 or P2 routing on leads that don’t qualify.
How quickly should P1 leads be routed after the event?
Within 24–48 hours. Event context fades fast — a “great to meet you at RevOps Summit” message sent a week later lands cold. P1 leads should be in the rep’s hands the same day the event ends. That’s why the play posts a Slack alert immediately rather than returning a static list.
How is this different from the conference attendee list to leads play?
The conference attendee list to leads play is built for individual reps — it enriches a list, drafts first-touch emails, and returns a personal outreach brief. This play is built for marketing operations — it scores the full list, routes leads to the right rep with handoff context, and posts Slack alerts. Different user, different output, different workflow.
Can I use this for webinar attendees as well as in-person events?
Yes — the workflow is identical. Set “Did anyone meet specific attendees?” to “No” for a virtual event. The scoring, enrichment, and handoff notes work the same way. For webinar registrant enrichment before the event, use the enrich event registrant list play first, then run this play after the event ends.
Ready to build this?
Get started with Lusha and set up this play in minutes.
