More Resources
Prompt

Qualify an inbound lead in under 60 seconds

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

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 lead data and connectors to see live results. Personal details in any live examples are masked or abbreviated for privacy.

An inbound lead submits a demo request. A rep has 90 seconds before calling back. This Claude prompt runs the qualification check in 60 of them — Lusha validates the contact, confirms ICP fit, and pulls a direct dial. Gmail checks for any prior contact with the account. The output is one screen: who the lead is, whether the company fits, what was said before, and one specific opening line. Read it. Dial.

The prompt

Open in Claude Open in ChatGPT 
<context>
An inbound lead just came in. I have 60 seconds before I call back. I want to know who this person is, whether the company is a real fit, whether we've spoken to anyone there before, and what to say when the call connects.

My inbound lead:
- Name: [NAME]
- Company: [COMPANY NAME OR DOMAIN]
- Email: [EMAIL IF AVAILABLE]
- What they submitted: [FORM TYPE — demo request, pricing inquiry, contact us, content download]
- What I sell: [PRODUCT / SOLUTION]
- My ICP: [COMPANY SIZE / INDUSTRY / FUNCTION]
</context>

<task>
1. Use Lusha to validate and enrich this lead in real time:
   - Current verified title — decision-maker, influencer, or end user?
   - Still at the company?
   - Company: headcount, industry, HQ — does it match ICP?
   - Any account signal in the last 30 days?

2. Check Gmail for any prior contact with this person or their company domain:
   - Has anyone from the team been in touch before?
   - If yes: what was discussed, did the conversation go anywhere?

3. Score the lead:
   - STRONG FIT: decision-maker, ICP match, verified — call immediately
   - GOOD FIT: influencer or partial ICP match — call, but qualify seniority on the call
   - WEAK FIT: outside ICP or unverified — research more before calling
   - DO NOT CALL: ICP mismatch confirmed — route to nurture, don't spend call time

4. Return a 60-second call brief:
   WHO I'M CALLING: verified name, title, tenure, seniority read
   COMPANY CHECK: ICP fit verdict, headcount, industry, signal if any
   PRIOR CONTACT: yes/no — if yes, what was discussed
   LEAD SCORE: STRONG / GOOD / WEAK / DO NOT CALL
   OPENING LINE: one specific sentence to open the call — references the form submission and one relevant detail

5. Direct dial: return the verified mobile number if available.
</task>

<constraints>
- This brief must be readable in 60 seconds. One screen, no headers, just the facts.
- The opening line must reference what the lead submitted — not a generic cold call opener.
- DO NOT CALL is a valid output — don't manufacture a reason to call if ICP clearly doesn't fit.
- Direct dial preferred over office line. Flag if only switchboard available.
</constraints>

What you'll get back

The situation: K.B. at Crestline Software submits a demo request at 2:14pm. A rep has 90 seconds before calling back. Running the brief now.

WHO I’M CALLING K.B., VP of Revenue Operations, Crestline Software ✓ 14 months in role · Decision-maker · Reports into CEO

COMPANY CHECK ICP fit: Strong · 340 employees · SaaS · San Francisco · Series A Signal: New CRO hired 12 days ago — active leadership change at the account

PRIOR CONTACT ⚠ Yes — T.K. (VP Sales at Crestline) was contacted by a colleague 8 weeks ago. Pricing discussion, no reply received. Different contact, same account.

LEAD SCORE: STRONG FIT — call now

OPENING LINE “Hi K.B. — thanks for requesting the demo. I saw you’re leading RevOps at Crestline. Given the CRO change that just happened, I imagine the timing of your request isn’t coincidental — is that fair?”

DIRECT DIAL: available (masked — returned on live run)

Illustrative example — fictional company names used. Run with your own lead data to see live results.

Why use Lusha in Claude

Two findings change what happens on this call. The prior contact flag — T.K. was contacted 8 weeks ago about pricing with no reply — means the rep can acknowledge the account relationship rather than treating Crestline as a cold account. The CRO signal — a new CRO 12 days in — gives the opening line its angle: “the timing of your request isn’t coincidental.” Without either finding, the opener is “thanks for your demo request, let me tell you about what we do.” With both, the opener is a specific observation that shows the rep was paying attention. That’s the difference between a call that books a next step and one that ends in 90 seconds.

Data drawn from 300M+ verified contacts under GDPR, CCPA, SOC 2, ISO 27701, ISO 31700, and TRUSTe.

FAQ

  • What if the lead form only captured an email and company name?

    Lusha finds the verified contact from the email domain and company name. The brief returns the most likely contact at that company in the relevant function — name, title, and direct dial — even if the form didn’t capture a name. If Lusha can’t match to a specific person, the brief flags it and recommends asking for the name when the call connects.

  • What does DO NOT CALL look like?

    The brief returns: “ICP mismatch — [specific reason]. Route to nurture. Don’t spend call time here.” The specific reason matters — “company is 12 employees, below your 200-employee floor” is actionable. The rep routes the lead and moves on rather than spending 10 minutes on a call that can’t convert.

  • How is this different from the inbound lead enrichment prompt?

    The inbound lead enrichment prompt enriches a lead and posts a Slack alert with routing instructions — it’s designed to run before the lead reaches a rep. This prompt is designed for the rep who already has the lead and needs a call brief in 60 seconds. Different moment in the workflow, different output format.

  • What if there's no direct dial available?

    The brief flags it — “office line only, no direct mobile available.” The rep can still call but should expect a gatekeeping scenario and have a message ready. For high-priority leads with no direct dial, the find a direct phone number prompt runs a deeper search.

  • Should I run this for every inbound lead?

    Run it for every lead where the callback window is short — demo requests, pricing inquiries, any form submission where speed-to-lead matters. For lower-urgency inbound like content downloads where a 24-hour response is acceptable, the enrich inbound leads prompt with Slack notification is a better fit.

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