More Resources
Prompt

Validate direct dials before a calling block

Built by: Lusha
Time to build: 1 min
Difficulty: Easy
Tools: Claude ▪ Lusha

A Claude prompt that takes an existing list of named contacts — from a CRM export, a conference roster, a webinar registration — and re-validates each contact’s direct dial and email before you start calling. Do Not Call flags surface inline, so the list is compliant and callable in the same pass. Once Lusha is connected in Claude, the connector runs in the background — no special syntax needed. Just paste the prompt 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

Open in Claude Open in ChatGPT 
<context>
Validate dials and emails on a named contact list before a calling block.
</context>

<task>
1. Contact list (paste with name and company):
   [PASTE LIST]
2. For each contact, confirm via Lusha:
   validated email (with confidence grade),
   mobile and office phone (with DNC status),
   current title and company.
3. Output a callable table sorted by phone availability and DNC:
   Name | Company | Title | Email (confidence) | Phone | DNC | Action.
4. For each row, suggest an action:
   Call (validated phone, DNC=no),
   Email only (validated email, no callable phone),
   Re-research (no current match),
   Skip (DNC=yes).
5. Summary at the top: total validated, callable, DNC, no-match.
</task>

<constraints>
- No-match returns no charge. Flag for re-research, don't drop silently.
- Treat DNC=yes as a hard skip. Surface those rows separately so they're not lost.
- Email confidence below A is worth flagging for follow-up validation.
</constraints>

What you'll get back

Input: 5-contact named list across enterprise SaaS — data, productivity, customer messaging, analytics, and developer tools companies.

Output: 3 of 5 validated, 2 flagged for re-research (no current match), 2 marked Do Not Call on the mobile, 1 callable office line. Below is the real result table from running the prompt against the live Lusha connector.

ContactTitleEmailPhoneDNCAction
Brian R.CFO, [Cloud data platform]✓ A+MobileYesEmail only
Tori M.Global Head of RevOps, [Productivity SaaS]✓ A+Office + mobileMobile DNC, office OKCall (office)
Tyler W.VP RevOps, [Customer messaging SaaS]–––Re-research
Saad S.VP RevOps, [Cloud analytics SaaS]–––Re-research
Laura F.Head of RevOps, [Dev workflow SaaS]✓ A+MobileNoCall

Names and company identifiers abbreviated for privacy. Full records — including emails and direct dials — are returned inside your Claude session.

A no-match (Tyler W., Saad S.) does not consume a Lusha credit. Re-research candidates surface separately so you can either re-confirm spelling or remove the row from the calling block.

Why it works

Calling blocks fail when a third of the list is wrong. Three things change when validation runs inside the same Claude session as the call prep.

The list compresses to its callable subset. From the demo above, 5 contacts became 2 callable rows in one pass. The other 3 didn’t get dropped — they got categorized (1 email-only, 2 for re-research). The rep walks into the calling block knowing exactly what to dial.

Do Not Call flags are inline. Lusha surfaces DNC status per phone number, sourced through the verified contact base under GDPR, CCPA, SOC 2, ISO 27701, ISO 31700, and TRUSTe. The prompt routes DNC rows out of the calling block automatically, which is a compliance win and a time-saver in the same step.

Email confidence is graded. Each work email comes back with a confidence grade (A+ through D). A+ means recently verified through multiple signals. The prompt flags anything below A for a second pass before the email goes out.

FAQ

  • What's a "no-match" result?

    The Lusha contact lookup returned no current record for that name and company. Three common causes — the contact left the company, the spelling is off, or the company name needs disambiguation. The prompt flags these for re-research and does not consume a Lusha credit.

  • How current is the dial data?

    Phone records carry an updateDate. Most are refreshed within the last 90 days. The prompt surfaces the update date so the rep knows whether the dial was validated last week or last quarter.

  • What does "Do Not Call" mean on a Lusha record?

    The phone number has been flagged in the DNC compliance feed. Calling DNC-flagged numbers carries legal risk in most jurisdictions. The prompt routes those rows out of the calling block by default. You can still email or use other channels.

  • Will this prompt re-validate dials I already have in my CRM?

    Yes. That’s the primary use case. Paste the CRM export, run the prompt, and Claude returns a re-validated table you can copy back. Direct CRM push runs through Lusha’s standard integrations.

  • Can I run this before an event or conference?

    Yes. Paste the attendee list, run the prompt, and walk into the event with a callable subset and a DNC-clean follow-up list.

Related Prompts

Ready to run this?

One data connection. Works in Claude, ChatGPT, your CRM, or any agent you build.

Start for free Read the Docs