Clean a contact list before a campaign goes out
Images on this page are for illustrative purposes only. Example outputs are based on Lusha data, with personal details masked or abbreviated for privacy.
One bad send damages deliverability for every send that follows. This Claude prompt validates every contact on a list before the campaign launches — Lusha checks who’s still at their company, whose email will bounce, and whose title breaks the {{title}} personalization token. Returns a per-contact send decision and a deliverability risk rating before a single email goes out.
The prompt
This prompt may contain placeholders — look for [BRACKETS] and fill them in.
<context>
I'm about to launch an outbound campaign. Before the first email goes out, I want to validate every contact on the send list — so we don't burn deliverability on bounces, send wrong personalization to people who've been promoted, or reach out to contacts who left months ago.
My list:
- Contact list: [PASTE NAME, TITLE, COMPANY, EMAIL — one per line]
- Campaign type: [COLD OUTREACH / RE-ENGAGEMENT / PRODUCT UPDATE / EVENT INVITE]
- Personalization tokens used: [e.g. {{title}}, {{company}}, {{first_name}}]
- Last time this list was validated: [DATE OR "NEVER"]
- Estimated send date: [DATE]
</context>
<task>
1. For each contact, use Lusha to validate:
- Still at the company?
- Verified work email — does it match what we have?
- Current title — does it match the personalization token we're using?
2. Flag each contact with a send decision:
- SEND: confirmed at company, email verified, title current — safe to include
- UPDATE FIRST: still there but title changed enough to break personalization — fix the token before sending
- DO NOT SEND: departed or email undeliverable — remove from this send
- UNVERIFIED: Lusha can't confirm — manual check before including
3. For DO NOT SEND contacts, suggest whether to find a replacement contact at the same company or remove entirely.
4. Return:
- Cleaned list with status and corrected fields where needed
- Summary: X SEND, X UPDATE FIRST, X DO NOT SEND, X UNVERIFIED
- Estimated bounce rate if sent as-is (% of DO NOT SEND)
- Deliverability risk rating: LOW / MEDIUM / HIGH based on list quality
5. Flag any company where multiple contacts on the list are DO NOT SEND — may signal a larger org change worth investigating before outreach.
</task>
<constraints>
- DO NOT SEND is a hard call — don't soften it to "check before sending."
- Title changes matter when they break personalization tokens — a VP who became SVP breaks {{title}} unless updated.
- If 20%+ of the list is DO NOT SEND, flag the whole campaign as HIGH deliverability risk.
</constraints>What you'll get back
The situation: A demand gen manager is sending a re-engagement campaign to 8 Zendesk and Salesforce Sales and RevOps contacts. List hasn’t been validated in 9 months. Using {{title}} personalization. Running the clean before scheduling the send.
Output from live Lusha run, May 25, 2026:
| Contact | CRM title | Current status | Send decision | Note |
|---|---|---|---|---|
| E.L. | VP of Sales | SVP of Sales | UPDATE FIRST | {{title}} will render “VP” — update to SVP before send |
| A.L. | VP Global Sales | SVP of Global Sales | UPDATE FIRST | Same — promoted, token will break |
| G.L. | VP of Sales | VP of Sales ✓ | SEND | Title confirmed current |
| J.P. | VP Sales Ops | VP Worldwide Sales Ops | UPDATE FIRST | Title changed — update token |
| R.C. | Area VP Sales | Area VP Sales ✓ | SEND | Confirmed |
| S.T. | Sr Director, SDR | Sr Director, SDR ✓ | SEND | Confirmed |
| K.C. | Regional VP Sales | Regional VP Sales ✓ | SEND | Confirmed |
| M.C. | VP RevOps | SVP, AR & RevOps | UPDATE FIRST | Significant promotion — update before send |
Summary: 8 contacts · 4 SEND · 4 UPDATE FIRST · 0 DO NOT SEND · 0 UNVERIFIED
Estimated bounce rate if sent as-is: 0% — no departures detected. Deliverability risk: LOW — all contacts still at their companies. Personalization risk: MEDIUM — 4 of 8 contacts will receive wrong {{title}} token if sent without updating. Fix before scheduling.
Company flag: Both Salesforce and Zendesk contacts show multiple title changes — consistent with org restructures at both companies over the past 9 months. Worth checking for additional contacts before the send if the list is larger.
Contacts verified live via Lusha connector, May 25, 2026. Names masked to initials.
Why use Lusha in Claude
A personalization token that renders wrong — “Dear VP of Sales” sent to someone who’s been SVP for 8 months — is not a minor issue. It signals to the recipient that you’re working from stale data, which is exactly the opposite of the impression a data intelligence company should make. The deliverability risk rating and bounce rate estimate give the campaign manager a single number to act on. The company-level flag — “multiple contacts at Salesforce show title changes” — is the output that prompts a broader CRM audit rather than a one-off fix.
Data drawn from 300M+ verified contacts under GDPR, CCPA, SOC 2, ISO 27701, ISO 31700, and TRUSTe.
FAQ
Does UPDATE FIRST mean I have to delay the campaign?
Not necessarily. If you’re using a sequencer like Outreach or Salesloft, updating four personalization tokens takes under 5 minutes. The delay is worth it — sending wrong titles at launch means every contact on the list receives the wrong message.
What if 20%+ of my list is DO NOT SEND?
The prompt flags the whole campaign as HIGH deliverability risk and recommends pausing the send. A 20%+ bounce rate on a single campaign can damage your sending domain’s reputation — which affects every future campaign, not just this one.
What counts as a title change that breaks personalization?
A change that affects what the token renders. VP → SVP breaks
{{title}}. Director of Sales → Sr Director of Sales breaks it. A minor spelling variation at the same seniority level is worth updating but isn’t a campaign risk. The prompt distinguishes between the two.Should I run this for every campaign, or just large ones?
Every campaign where the list is more than a month old. For a list of 10 contacts built this week from fresh Lusha searches, skip it. For any imported list, re-engagement sequence, or campaign built from CRM contacts, run it before every send.
How is this different from the lead list enrichment prompt?
The lead list enrichment prompt runs before CRM import — it fills missing fields and ICP-scores. This prompt runs before a campaign send — it validates existing CRM records for deliverability and personalization accuracy. Run enrichment at import time, run this before every send.
Ready to build this?
Get started with Lusha and set up this play in minutes.
