More Resources
Prompt

Enrich inbound leads before routing to a rep

Built by: Unknown
Tools: Claude ▪ Gmail ▪ Lusha ▪ Slack

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.

A lead that arrives with just a name and email costs a rep time to research and qualify — and may not be worth pursuing at all. This Claude prompt enriches every inbound lead with verified title, direct phone, and company firmographics via Lusha, checks Gmail for prior contact history, scores the lead A through D, and posts an enriched alert to Slack with a specific recommended action before the lead hits a rep’s queue.

The prompt

Open in Claude Open in ChatGPT 
<context>
When an inbound lead comes in — from a form, demo request, or content download — I want to enrich it with verified contact and company data before it reaches a sales rep. The rep should receive a lead with a verified title, direct phone, company firmographics, ICP score, and a recommended action — not a name and email address.

My inbound lead:
- Lead details: [PASTE WHAT YOU HAVE — name, email, company, any form fields]
- What I sell: [PRODUCT / SOLUTION]
- ICP criteria: [COMPANY SIZE / INDUSTRY / FUNCTION]
- Where the lead came from: [FORM TYPE / SOURCE — e.g. demo request, pricing page, content download]
- Slack channel to notify: [CHANNEL NAME — or "skip Slack"]
</context>

<task>
1. Use Lusha to enrich the lead with verified data:
   - Confirm or find: current title, verified work email, direct phone
   - Company: current headcount, industry, HQ location, funding stage
   - Confirm the lead is still at the company — flag if contact details don't match

2. Score the lead against ICP criteria:
   - A: strong ICP fit, decision-maker, verified — route to AE immediately
   - B: ICP fit, influencer or partial data — route to SDR for qualification
   - C: partial ICP fit or unverified contact — nurture, don't route yet
   - D: outside ICP or contact can't be verified — do not route

3. Check Gmail for any prior contact with this person or company domain:
   - Has anyone from the team emailed this lead before?
   - If yes: who, when, and what was discussed — flag for the rep

4. Recommend a first action based on lead grade and source:
   - Grade A + demo request: call within 2 hours
   - Grade A + content download: personalized email within 4 hours
   - Grade B: SDR sequence within 24 hours
   - Grade C/D: nurture workflow — don't assign to rep

5. If Slack channel is specified: post an enriched lead alert with all verified fields, ICP grade, prior contact note, and recommended action. Tag the rep or SDR who should own it.
</task>

<constraints>
- Only route Grade A and B leads to reps. Grade C and D go to nurture — never to a rep queue.
- The recommended action must be specific: not "follow up" but exactly what to do and by when.
- If Gmail shows prior contact: the rep must know before reaching out — flag it in the Slack alert.
- Post to Slack only if a channel is specified.
</constraints>

What you'll get back

The situation: An inbound demo request arrives from K.B. at Crestline Software. The form captured name, company email, and company name only. Running the enrichment before routing to the AE.

Slack alert — posted to #inbound-leads

🔥 Grade A inbound — demo request · @sarah.ae

K.B., VP of Revenue Operations, Crestline Software Verified email: k.b@[crestline].com ✓ · Direct mobile: available Company: SaaS · 340 employees · Series A funded · San Francisco

ICP fit: Strong — decision-maker, right function, right size

Prior contact: ⚠ T.K. at Crestline was contacted by @james.ae 8 weeks ago — pricing discussion, no reply. Different contact, same account. Loop in @james.ae before Sarah reaches out.

Action: Call K.B. within 2 hours. Demo request at decision-maker level is the highest-intent signal. Reference the Crestline account relationship with James when connecting.

Illustrative example. Run with your own lead data to see live results.

Why use Lusha in Claude

A rep who receives “K.B., [email protected]” has to look up the title, check company size, verify ICP fit, and decide how to prioritize — 10–15 minutes of work before a single call is made. This prompt does all of that in 60 seconds and adds two things the rep would never find manually: the ICP grade that determines routing, and the prior contact flag that prevents Sarah from calling an account where a colleague already has an open pricing conversation. Both findings change what happens next. Without the prior contact flag, Sarah reaches out cold on a relationship James started 8 weeks ago.

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

FAQ

  • What if the lead source is unknown?

    Set the source to “unknown” — the enrichment and ICP scoring run the same way. The recommended action defaults to SDR sequence within 24 hours for unknown sources, since intent level can’t be inferred without a source signal.

  • Why does Grade D go to nurture rather than discard?

    Grade D means outside ICP or unverified — not worthless. A company below the size threshold today may grow into ICP in 12 months. A nurture track holds the record without routing to a rep queue. Discarding a Grade D lead permanently removes the relationship; nurturing keeps the option open.

  • Can I run this for every inbound lead automatically?

    The prompt runs on demand in Claude. For fully automated enrichment on every form submission without manual triggering, the Lusha + Zapier or n8n automation plays on the Campus handle that workflow. This prompt is for teams that want the enrichment run manually as leads come in.

  • What if there's no Slack channel to notify?

    Set “skip Slack” in the channel field — the prompt returns the enriched record as plain text instead of posting to Slack. Same output, different delivery.

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

    The research inbound lead prompt produces a deep research brief on a single lead — company background, recent news, talking points. This prompt is an enrichment and routing decision — ICP grade, verified fields, prior contact check, recommended action. Use this one to decide who gets the lead and when to act. Use the research prompt to prepare for the actual call.

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