More Resources
Prompt

Find every inbound lead that came from a target account

Built by: Lusha
Time to build: 1 min
Difficulty: Easy
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, Gmail, and Slack connector output, but were not pulled from a live session. Run the prompt with your own inbound leads and connectors to see live results. Personal details in any live examples are masked or abbreviated for privacy.

An inbound lead from a target account is a buying signal regardless of the submitter’s seniority — a junior analyst filling in a pricing form at a Tier 1 ABM account means someone at that company is actively researching. This Claude prompt checks every inbound form fill against the ABM target list via Lusha, identifies the account owner, checks Gmail for any active deal at the account, surfaces the most senior verified contact in the buying function, and posts an ABM inbound alert to Slack before the lead gets routed as standard MQL. The signal reaches the right rep in minutes, not days.

The prompt

Open in Claude Open in ChatGPT 
<context>
Someone just filled in a form. Before I route it as a standard inbound lead, I want to check whether the company is on our ABM target account list. A junior contact from a Tier 1 account is not a standard MQL — it's a buying signal that the account owner needs to know about immediately.

My check:
- Inbound lead: [PASTE NAME, EMAIL, COMPANY, TITLE, FORM TYPE — or "check Gmail for today's inbound"]
- ABM target account list: [PASTE COMPANY NAMES OR DOMAINS — or "use the list in [Drive folder / Slack channel]"]
- What we sell: [PRODUCT / SOLUTION]
- Account owner mapping: [PASTE REP NAME PER ACCOUNT — or "auto-assign by territory"]
- Slack channel for alerts: [CHANNEL NAME OR "skip"]
</context>

<task>
1. For each inbound lead, use Lusha to validate and enrich:
   - Verified current title and seniority level
   - Still at the company?
   - Company: headcount, industry, funding stage
   - Is this company on the ABM target account list? Match by domain or company name.

2. If the company IS on the ABM target list:
   - Flag immediately as ABM INBOUND — regardless of the lead's seniority
   - Identify the assigned account owner for this account
   - Check Gmail for any prior contact between the sales team and this company
   - Check whether there is an active deal at this account
   - Find the most senior verified contact in the buying function via Lusha

3. If the company is NOT on the ABM target list:
   - Route as standard inbound MQL — apply normal scoring and routing rules

4. For every ABM INBOUND lead, build an account signal brief:
   - Who submitted the form: name, verified title, form type
   - Company: ABM tier, account owner, active deal status
   - Most senior contact in the buying function (may differ from who submitted)
   - Recommended action: engage the form submitter, route to account owner,
     or use as a signal to accelerate existing outreach
   - One suggested message for the account owner referencing the inbound activity

5. If Slack channel specified: post ABM inbound alert immediately — tag the account owner.

6. Return:
   - ABM INBOUND leads with full account signal brief
   - Standard MQL leads — routed normally
   - Summary: X ABM inbound signals, X standard MQLs
</task>

<constraints>
- ABM INBOUND flagged regardless of the lead's seniority.
- Account owner must be notified before any outreach.
- Active deal at the account: flag to deal owner, don't route as a new lead.
- Recommended action must be specific — not "follow up" but exactly what to do and who does it.
</constraints>

What you'll get back

The situation: Three form fills came in this morning. Marketing ops runs the check against the ABM target list before routing.

ABM INBOUND — 🔥 Flag to account owner immediately

C.A. · Dunmore Analytics · content download

Slack alert posted to #abm-alerts · @sarah.ae

🔥 ABM INBOUND — Dunmore Analytics · @sarah.ae

C.A., Revenue Operations Analyst, Dunmore Analytics ✓ Downloaded: “The RevOps Data Quality Playbook”

Account context: Dunmore is Tier 1 ABM · Series B closed 18 days ago · Sarah is the assigned AE Active deal: No active deal — account has been prospected, no response to date Most senior contact in buying function: T.K., VP of Sales ✓ · t.k@[dunmore].com

Recommended action: C.A. is an analyst — don’t engage directly. Use the content download as the signal to re-open the T.K. conversation. Series B + an analyst researching data quality = active internal evaluation.

Suggested message to T.K.: “Someone from your team just downloaded our RevOps data quality playbook — with the Series B just closed, it sounds like data quality is on the Q3 list. Worth a conversation?”

Standard MQL — route normally

P.L. · Waverly Digital · demo request · behaviour score 71 Waverly Digital is not on the ABM target list. Route as standard MQL per normal scoring rules.

K.J. · Meridian Analytics · content download · behaviour score 44 Meridian Analytics is not on the ABM target list. Route to nurture — below score threshold.

Summary: 1 ABM inbound signal · 2 standard MQLs

Illustrative example — fictional company names used. Run with your own leads and account list to see live results.

Why use Lusha in Claude

Lusha in Claude connects the inbound form fill to the ABM account list in real time — a connection that most marketing automation platforms don’t make at the contact level. The C.A. finding is the core insight: an analyst downloading a playbook at a Tier 1 account is not a junior MQL to route to an SDR sequence. It’s evidence that someone at Dunmore is actively researching the problem the product solves. Lusha confirms the company is on the ABM list, Gmail confirms no active deal exists, and Lusha surfaces T.K. as the right person for Sarah to reach out to — not C.A. The recommended action and the suggested message give Sarah exactly what to do with the signal before the buying window closes.

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

FAQ

  • Why flag a junior contact from a target account — why not just route normally?

    A junior contact from a Tier 1 account signals active internal research — someone at that company assigned the analyst to look into the product. The person who fills in the form is rarely the buyer. Routing the analyst to an SDR sequence wastes the signal and potentially alerts the wrong person at the account before the AE can engage the decision-maker correctly.

  • What if there's already an active deal at the account?

    The inbound is flagged to the deal owner, not routed as a new lead. A form fill during an active deal means someone else at the account is researching independently — which is either a good sign (broader interest) or a risk (evaluating alternatives). The deal owner needs to know either way and decides how to use it.

  • How does the ABM account list get maintained?

    Paste the current list into the prompt each time, or reference a Drive folder or Slack-pinned list. For teams that want automatic matching without manual list pasting, the prompt can search a Drive folder for the most recent ABM list file and use that as the reference.

  • What if the same company appears on the list but under a different name?

    Lusha matches by domain as well as company name — so “Dunmore Analytics” and “dunmore.com” both match. If the company uses multiple trading names, include both in the ABM list to ensure matching works correctly.

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

    The inbound lead enrichment play scores every inbound lead for ICP fit and routes each one to the right rep. This play checks specifically whether the inbound company is on the ABM target list — a different question with a different output. Use the enrichment play for all inbound. Use this play as an additional ABM filter layer to catch target account signals before disappearing into the standard MQL queue.

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