Qualify an inbound lead in ChatGPT

Built by: Lusha
Time to build: 1 min
Difficulty: Easy
Tools: ChatGPT ▪ Lusha
Type: Prompt

Example outputs in this play are illustrative — they reflect the structure, fields, and format of real Lusha connector output, but were not pulled from a live session. Run the prompt with your own inbound lead details to see live results.

Inbound leads look simple from the outside. Someone filled out a form, downloaded a guide, registered for a webinar, or asked for a demo. But the form data rarely tells the full story.

The person may be a real buyer at a strong-fit account. They may also be a student, agency, competitor, consultant, tiny company, or someone outside the buying group. If every lead gets treated the same, sales wastes time and good leads wait too long.

This prompt uses Lusha in ChatGPT to verify the person, enrich the company, check for recent buying signals, and recommend the right next step. Instead of routing leads based on form fields alone, your team gets a clearer view of who the lead is, whether the account fits your ICP, and why now might be the right time to follow up.

How to start

Open in Claude Open in ChatGPT
1

Open Lusha in ChatGPT

Go to Lusha in ChatGPT and click “Start chat.” Every conversation started this way is automatically Lusha-enabled.

2

Or invoke Lusha in any existing conversation

Type @Lusha in the prompt bar and select Lusha from the dropdown. Unlike Claude, Lusha does not activate automatically in every ChatGPT conversation. You must invoke it every time.

3

Fill in the lead details and send

Copy the prompt below, fill in the inbound form data and ICP details, and send. Lusha verifies the lead, enriches the account, checks for signals, and recommends the right routing path.

The prompt

Start from Lusha in ChatGPT or type @Lusha before sending.

@Lusha Qualify this inbound lead before I route it to sales.

INBOUND FORM DATA:
Name: [full name]
Email: [email address]
Company: [company name or domain]
Submitted title: [title]
Message or form intent: [message]
Source: [demo request / contact sales / webinar /
content download / event / ad / other]

ICP:
Best-fit industries: [industries]
Best-fit company size: [employee range]
Best-fit regions: [regions]
Best-fit personas: [personas]
Disqualifiers: [students, agencies, competitors,
small companies, consultants, etc.]

MY PRODUCT:
[One sentence describing what you sell and the
problem it solves]

Using Lusha, do the following:

1. VERIFY THE PERSON
   Confirm whether the person is a real business contact.
   Return current title, company, department, seniority,
   location, and LinkedIn profile if available.

   Compare the submitted title and company with the
   verified profile. Flag any mismatch clearly.

2. CHECK FOR DATA ISSUES
   Flag:
   - Personal email
   - Title mismatch
   - Wrong company
   - Contact no longer at company
   - Contact outside the target persona
   - Company outside ICP
   - Contact could not be verified

3. ENRICH THE COMPANY
   Return:
   - Company name and domain
   - Industry
   - Employee count
   - HQ location
   - Revenue range if available
   - Company LinkedIn if available
   - Relevant company profile details

4. CHECK BUYING SIGNALS
   Check for recent company signals from the last 6 months.
   Prioritize:
   - Hiring surges
   - Hiring surges by relevant department
   - Headcount increases or decreases
   - IT spend changes
   - Website traffic changes
   - Commercial activity news
   - Corporate strategy news
   - Financial events news
   - People news
   - Product activity news
   - Risk news

   Pick the strongest signal and explain why it may
   make this lead more or less urgent.

5. GRADE THE LEAD
   Assign one lead grade:

   A: Strong ICP fit + verified buyer/persona +
      relevant signal or high-intent form action

   B: Good ICP fit + verified contact, but no strong
      recent signal

   C: Partial fit, unclear buyer, weak signal, or
      needs SDR qualification

   D: Poor fit, invalid data, wrong person, or
      clear disqualifier

6. ROUTING RECOMMENDATION
   Recommend one next step:
   - Route to AE now
   - Route to SDR for qualification
   - Add to nurture
   - Do not route

   Explain the recommendation in one sentence.

7. WRITE THE FIRST FOLLOW-UP
   If the lead is grade A or B, write one short reply
   for the sales team.

   Subject line:
   Under 7 words.

   Body:
   Under 100 words.
   Reference the form intent or strongest signal.
   Keep it direct and useful.
   End with one clear next step.

   If the lead is grade C or D, do not write a sales
   email. Instead, write the qualification question
   or nurture recommendation.

8. OUTPUT FORMAT
   Return:
   - Person verification
   - Data issues
   - Company enrichment
   - Strongest signal
   - Lead grade
   - Routing recommendation
   - First follow-up or qualification question
   - Reasoning

Do not over-score the lead if Lusha cannot verify the
person or company. Do not invent missing data.

What you’ll get back

 

A verified lead profile, account enrichment, buying signal check, and routing recommendation. Here’s what the output looks like:

Inbound lead qualification — Lusha

FieldValue
Person verification✓ Verified business contact · title matches form data
Company fitHigh fit · B2B SaaS · 500–1,000 employees · North America
Strongest signalHiring surge in Sales · detected in the last 30 days
Lead gradeA · verified buyer at high-fit account with relevant signal
Routing recommendationRoute to AE now
Follow-up includedYes · 87 words · references form intent and account signal

Example outputs in this play are illustrative — they reflect the structure, fields, and format of real Lusha connector output, but were not pulled from a live session. Run the prompt with your own inbound lead details to see live results.

 

Why use Lusha in ChatGPT for inbound lead qualification

 

Inbound leads are easy to over-trust. Someone filled out a form, so the instinct is to send them to sales. But form data alone rarely tells you whether the person is real, whether the company fits your ICP, or whether the timing is actually strong.

Lusha gives that decision a verified foundation. The prompt checks the person behind the form, enriches the company, and looks for recent account signals that may explain why the lead came in now. A demo request from a verified VP at a high-fit company with a recent hiring surge is not the same as a content download from someone outside your target persona.

The routing step matters because speed only helps when the lead is worth acting on. A strong lead should move fast. A weak or unclear lead should not distract the AE team. By combining verification, enrichment, and signals inside ChatGPT, teams can decide what to do next without jumping between CRM records, spreadsheets, enrichment tools, and Slack threads.

Lusha data is sourced and used in accordance with Lusha’s Privacy Policy and Terms of Use. Lusha is GDPR compliant and covers contacts across North America, EMEA, and APAC.

FAQ

  • Can I use this prompt for demo requests?

    Yes. Demo requests are one of the best use cases for this prompt. Use it to verify the person, enrich the account, check whether the company fits your ICP, and decide whether the lead should go straight to an AE or through SDR qualification first.

  • What if the lead used a personal email address?

    The prompt asks Lusha to verify the person and company behind the form submission. If the personal email cannot be matched to a real business contact, the lead should be reviewed before routing to sales.

  • What if Lusha finds no recent buying signals?

    A lead can still be worth routing without a recent signal, especially if the person and company are a strong ICP match. In that case, the prompt grades the lead based on fit, verified identity, form intent, and persona relevance.

  • Should every inbound lead go to sales?

    No. Some leads should go directly to an AE, some should go to SDR qualification, some belong in nurture, and some should not be routed at all. This prompt helps separate high-priority leads from poor-fit or unverified submissions.

  • Can marketing use this before sending leads to the sales team?

    Yes. Marketing and RevOps teams can use this prompt to validate and score inbound leads before routing. It helps reduce manual research and gives sales more context when a qualified lead is ready for follow-up.

Related Prompts

Ready to run this?

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

Get free access Read the Docs