Validate emails before a campaign
A Claude prompt that runs pre-flight validation on a campaign list before you press send. Confidence grades, domain match against current employer, multi-email selection where a contact has more than one address, and bounce risk surfaced inline. Built for marketers and SDR managers running QA before the sequence loads.
Once Lusha is connected in Claude, the connector runs in the background — no special syntax needed. Just paste the campaign list and run.
Images on this webpage are for illustrative purposes only. Any named individuals shown in live demo outputs are real, with last names abbreviated for privacy.
The prompt
<context>
I am about to send a campaign to a contact list. Before launch, I want to validate every email — confidence grade, domain match to current employer, recommended send address where a contact has more than one — so I do not burn sender reputation on bounces or send to the wrong inbox.
</context>
<task>
1. Take this campaign list (paste with name, company, and the email on file):
[PASTE LIST]
2. For each contact, use Lusha to validate:
- Current employer (does it match the email's domain?)
- All work emails on file (with confidence grades and updateDate)
- Recommended send address: pick the email whose domain matches the contact's current company
- Flag any contact whose employer changed since the email on file was captured
3. Output a pre-flight table:
Name | Current company | Email on file | Lusha-verified email | Confidence | Domain match | Bounce risk | Send decision
4. Assign one of these send decisions per row:
- SEND — email matches current employer, A or A+ confidence
- SWITCH — Lusha has a better verified email for this contact; recommend the new one
- HOLD — contact changed employer; the email on file will bounce; needs the new address
- SKIP — no current record (likely bounce, do not send)
5. Summarize at the top: total to send, total to switch, total to hold, total to skip.
</task>
<constraints>
- A no-match result returns no credit charge — flag as SKIP, don't send.
- Domain match is the key signal: if the email's domain is from a previous employer, that email will bounce.
- When a contact has multiple verified emails, recommend the one whose domain matches their current company. Surface the alternative addresses but don't recommend them.
- Email confidence below A is worth flagging in the bounce-risk column even when the domain matches.
- Do not invent or guess emails. If Lusha returns no email, the row goes to SKIP.
</constraints>What you'll get back
Input: 4-row pre-campaign list — three contacts with emails on file (one matches current employer, one is a multi-email contact, one was captured before a job change) and one designed to fail.
Output: 2 SEND, 1 SWITCH, 1 SKIP. Below is the real result from running the prompt against the live Lusha connector.
| Contact | Current company | Email on file | Confidence | Domain match | Send decision |
|---|---|---|---|---|---|
| Brian R. | Snowflake | b.r.****@snowflake.com | A+ | ✓ | SEND |
| Tori M. | Notion | t.m.****@notion.com.br | A+ | ✓ | SEND |
| Brian R. (multi-email) | Snowflake | b.****@brightonparkcap.com | A | ✗ → switch to @snowflake.com | SWITCH |
| Tyler W. | Intercom | t.w.****@intercom.com | — | No match | SKIP |
Names and emails abbreviated for privacy. Full records — including complete email addresses and direct dials — are returned inside your Claude session.
The SWITCH row is the most important pattern to surface. The email on file is a real verified work email, but the domain doesn’t match the contact’s current employer. Sending there will reach a different mailbox than intended. The prompt recommends the address at the current company instead.
Three credits consumed for three filled rows. The SKIP row charged nothing.
Why use Lusha
Email validation before a campaign is not a vanity check. Bounce rates above 2 percent damage sender reputation across every recipient on the list — not just the bouncing addresses. Three patterns repeat across every pre-campaign QA pass.
Domain match is the single highest-signal check. A verified email whose domain does not match the contact’s current employer will bounce. The contact has moved. Their old mailbox is closed or forwarded. The prompt does this check on every row before recommending a send decision, drawing on Lusha’s verified company and employment records.
Multi-email contacts need a recommendation, not a coin flip. A senior contact often has a primary work email at their current employer plus secondary addresses at adjacent boards, advisory roles, or previous companies. The prompt recommends the address whose domain matches the contact’s current company and surfaces the alternatives so the user can confirm.
No-charge no-match is a trust signal. A contact Lusha cannot match returns nothing — no email guess, no fabricated confidence grade, no credit. The user routes that row to SKIP and protects sender reputation. Data is drawn from 300M+ verified contacts under GDPR, CCPA, SOC 2, ISO 27701, ISO 31700, and TRUSTe.
FAQ
What email confidence grade is safe to send?
A+ emails were recently verified through multiple signals — safe to send. A grade is the next tier and still safe in most cases. B grade and below carry meaningful bounce risk and are worth a second pass before a campaign goes out.
What does "domain match" mean?
The email’s domain should match the contact’s current employer’s domain. If the email on file is at acme.com but the contact’s current company is widgets.com, the email will bounce. The prompt flags this mismatch as HOLD or SWITCH depending on whether Lusha has the new address.
Why does a contact have more than one work email?
Senior contacts often serve on boards, hold advisory roles, or maintain emails from past employers. Lusha returns every verified work email it has on file. The prompt recommends the address whose domain matches the contact’s current employer for the campaign.
Will this catch every potential bounce?
The prompt catches structural bounce risks — wrong employer, no current match, low confidence grade. It does not test live delivery. For belt-and-suspenders, pair this prompt with a dedicated SMTP-level email validator before a high-volume send.
How is this different from cleaning a CRM export?
The CRM cleanup prompt is general hygiene. This prompt is a focused pre-flight check before a known campaign load. The output is narrower — one decision per row, SEND or SWITCH or HOLD or SKIP — so the campaign loads with confidence.
How often should I run this?
Before every campaign launch. Email accuracy decays continuously. Even a list cleaned 30 days ago will have a few rows where the contact moved. Five minutes of validation prevents a deliverability dip that can take weeks to recover from.
Ready to build this?
Get started with Lusha and set up this play in minutes.
