Use this with your Lusha GTM Data Agent in Microsoft Copilot.
Use Lusha to enrich these inbound leads and recommend
the next-best action for each one.
INBOUND LEADS:
Paste leads in this format:
1. [Full name] | [Email] | [Company] | [Title] |
[Form source] | [Campaign] | [Form answer or note]
2. [Full name] | [Email] | [Company] | [Title] |
[Form source] | [Campaign] | [Form answer or note]
3. [Full name] | [Email] | [Company] | [Title] |
[Form source] | [Campaign] | [Form answer or note]
LEAD CONTEXT:
Source: [website form / webinar / demo request / content
download / event / partner / paid campaign / other]
Offer or conversion point: [demo / report / webinar /
trial / contact sales / consultation / other]
What the lead showed interest in: [one sentence]
ICP:
Best-fit industries: [industries]
Best-fit company size: [employee range]
Best-fit regions: [regions]
Target personas: [titles or personas]
Relevant departments: [Sales / Marketing / RevOps / IT /
Operations / Customer Success / Finance / HR / other]
Disqualifiers: [students, consultants, competitors, vendors,
existing customers, poor-fit segments, unsupported regions,
small companies, etc.]
MY PRODUCT:
[One sentence describing what you sell and the problem
it solves]
Using Lusha, do the following:
1. VERIFY EACH LEAD
For each lead, verify whether the person can be matched
to a real B2B contact profile.
Return:
- Name
- Current title
- Current company
- Department
- Seniority
- Location
- LinkedIn profile if available
- Whether the submitted title and company match the
verified profile
Flag:
- Personal email
- Company mismatch
- Title mismatch
- Contact no longer at company
- Contact outside target persona
- Contact could not be verified
2. ENRICH CONTACT DATA
For each verified lead, return:
- Verified business email availability
- Direct or mobile phone availability
- DNC status if available
- Last updated date if available
If contact data is unavailable or cannot be revealed,
say so clearly rather than guessing.
3. ENRICH COMPANY DATA
For each lead’s company, return:
- Company name
- Domain
- Industry
- Employee count
- HQ location
- Revenue range if available
- Tech stack if available
- Company LinkedIn if available
4. CHECK BUYER SIGNALS
Check recent buyer signals from the last 6 months,
if available.
Prioritize:
- Funding events
- Hiring growth
- Hiring growth by relevant department
- Hiring growth by location
- Leadership changes
- Role changes
- Company changes
- Headcount growth or reduction
- Technology changes
- Website traffic changes
- Commercial activity news
- Corporate strategy news
- Product activity news
- Risk news
- Intent topics related to my product, if available
5. SCORE AND PRIORITIZE
Create an explainable recommendation score from 1-100
using only the verified Lusha data returned and the ICP
context I provided.
Break the score into:
- Contact fit: 25 points
How well the person matches the target persona.
- Company fit: 30 points
How well the company matches the ICP.
- Timing: 25 points
Whether buyer signals make the lead more timely.
- Actionability: 20 points
Whether verified contact data is available and usable.
Do not present the score as a prediction that the lead
will convert or buy.
If there is not enough verified data to support a score,
mark the confidence as low and explain what is missing.
6. RECOMMEND ROUTING
Assign one next-best action:
Route to AE now:
Strong contact fit + strong company fit + strong signal
or high-intent form source.
Route to SDR:
Good fit, but needs qualification before AE handoff.
Add to nurture:
Partial fit, weak timing, junior title, or unclear urgency.
Review manually:
Data mismatch, personal email, unclear company, or
incomplete verification.
Exclude:
Competitor, vendor, student, poor fit, unverified, or
disqualified.
7. WRITE FOLLOW-UP COPY
For leads marked Route to AE now or Route to SDR, write
one short follow-up email.
Subject line:
Under 7 words.
Body:
Under 100 words.
Reference the conversion point or stated interest.
Connect the message to the strongest company or buyer
signal when available.
End with one clear, low-friction next step.
For nurture leads, write one nurture angle instead.
For review or exclude leads, do not write sales follow-up.
Do not:
Invent form answers, attendance, pain points, signals,
tools, vendors, internal projects, buying intent, emails,
phone numbers, or company context.
Say the lead is ready to buy.
Claim a signal proves intent.
Use the same generic follow-up for every lead.
8. OUTPUT FORMAT
Return:
- Lead enrichment table
- Verification status
- Contact data availability
- Company enrichment
- Buyer signals, if any
- Recommendation score and confidence
- Routing recommendation
- Follow-up email or nurture angle
- Review and exclusion reasons
If Lusha cannot verify a lead, company, contact detail, or
signal, mark it clearly rather than guessing.
