35% off all annual plans Lusha summer sale - limited time only

Claim discount

Find out why your deal went quiet

Built by: Lusha
Time to build: 2 min
Difficulty: Easy
Tools: Claude ▪ Gmail ▪ Lusha
Type: Prompt

Images on this page are for illustrative purposes only. Example outputs are based on Lusha data, with personal details masked or abbreviated for privacy.

This Claude prompt checks what changed at a prospect account after a deal goes dark — contact left, structural event, or a thread that simply dropped. Lusha scans the account for changes since your last touch. Gmail shows what was last said and who sent the final email. The output is a diagnosis and one prescribed next action — including a draft re-engagement email where relevant.

 

The prompt

Open in Claude Open in ChatGPT 
<context>
A deal I was progressing has gone quiet. I need to find out what changed (at the account or in the buying group) and decide whether to re-engage, escalate, or walk away.

My deal:
- Prospect company: [COMPANY NAME]
- Deal stage when it went quiet: [Discovery / Proposal / Negotiation]
- Last meaningful interaction: [DATE OR "CHECK GMAIL"]
- Who I was talking to: [NAME, TITLE]
- What we were selling: [PRODUCT / SOLUTION]
- Deal value: [DOLLAR AMOUNT]
</context>

<task>
1. Use Lusha to check what changed at the account since my last touch:
   - Has the contact I was talking to changed roles, left, or gone elsewhere?
   - Any executive changes in the buying function (new CRO, CFO, CTO, VP of the relevant department)?
   - Any M&A activity (acquisition, merger, or restructure)?
   - Any significant headcount changes in the team we were selling into?
   - Any funding event (positive: may unlock budget; or down round: may freeze it)?

2. Pull my last email thread with this contact from Gmail:
   - What was the last thing discussed?
   - Who sent the last email, me or them?
   - Is there an unanswered email on either side?
   - Did I make a commitment I haven't followed through on?
   - Was there any signal of hesitation, objection, or delay in the last exchange?

3. Based on what Lusha and Gmail return, diagnose why the deal went quiet:
   - CONTACT GONE: the person I was talking to left or changed roles
   - INTERNAL BLOCKER: a structural change at the account (M&A, reorg, budget freeze) stalled the deal
   - ENGAGEMENT DROP: no structural change, but the thread went cold. Likely a priority or interest shift.
   - MY DROP: the last unanswered email was mine and I haven't followed up

4. Based on the diagnosis, prescribe one clear next action:
   - CONTACT GONE: use Lusha to find the new owner and draft a re-entry email
   - INTERNAL BLOCKER: identify who now owns the decision and what the right re-entry timing is
   - ENGAGEMENT DROP: draft a direct re-engagement email that names the silence and asks a specific question
   - MY DROP: draft a short follow-up that picks up the thread without over-explaining the gap

5. If re-engagement is the right move, draft the email:
   - Under 100 words
   - Reference something specific from the last thread
   - One direct question or ask at the end
   - No "just checking in", no "hope you've been well", no "circling back"
</task>

<constraints>
- Base the diagnosis on what Lusha and Gmail actually return. Don't guess.
- If the contact is still at the company and there's no structural change, don't manufacture a reason the deal went quiet. Call it an engagement drop and treat it as such.
- The re-engagement email must reference something real from the Gmail thread. A generic email is not acceptable output.
- If the deal is genuinely dead (contact gone, no clear successor, M&A freeze, 90+ day silence), say so. Don't dress it up as re-engageable.
</constraints>

What you'll get back

The situation: An AE at a B2B SaaS company was at Proposal stage with a 250-person fintech. Last real exchange was 26 days ago — she sent a revised proposal after a pricing conversation, they acknowledged receipt, nothing since. Two follow-ups sent, no reply.

Output: Diagnosis: ENGAGEMENT DROP — contact still at the company, no structural change at the account, but the thread went cold after the proposal. One prescribed re-engagement email.

Diagnosis: ENGAGEMENT DROP

What Lusha found:

  • Ryan K., VP of Revenue Operations — still at the company, same title, no role change detected
  • No executive changes in Finance or Revenue Operations in the last 90 days
  • No M&A activity detected
  • Headcount in Revenue Operations stable — no significant growth or contraction
  • No funding event in the last 6 months

The account is structurally unchanged. Ryan hasn’t left. Nothing external stalled this deal.

What Gmail found:

  • Last meaningful exchange: 26 days ago
  • Last email: Ryan replied acknowledging receipt of the revised proposal — “Thanks, will review with the team and come back to you by end of week”
  • Last outbound from you: two follow-ups since, both unanswered
  • No commitment outstanding on your side
  • One signal in the thread: two exchanges before the proposal, Ryan mentioned “we’re moving faster than we expected on this” — the urgency language is gone in recent messages

The read: The revised proposal landed and the reply went quiet. The urgency language dropped out of the thread before the proposal was sent. This is an engagement drop — the deal slowed down internally and the follow-ups haven’t restarted it. Two unanswered follow-ups means a third generic one won’t either.

Prescribed next action

Don’t send another follow-up. Send a different kind of message — one that names the situation directly and asks a specific question that requires a real answer, not a polite non-reply.

Re-engagement email (draft)

To: r.k@[company].com Subject: The proposal — still worth pursuing?

Hi Ryan,

You mentioned a few weeks back that things were moving faster than expected. The proposal’s been sitting since then — I want to make sure I’m not holding something up on your end or missing a change in priorities.

Is this still something you’re looking to move on this quarter, or has the timeline shifted?

[Name]

Account signals pulled via Lusha connector, May 21. Gmail thread summary from live session. Contact details abbreviated for privacy.

Why use Lusha in Claude

A quiet deal has one of four causes: the contact left, something structural changed at the account, the prospect deprioritized it, or you dropped the thread. Each one has a different fix. Sending the same follow-up email regardless of which one it is is why most re-engagement attempts fail. Lusha in Claude checks the account for structural changes in the same pass that Gmail checks what was last said — the diagnosis comes from both signals together, not a guess. The prescribed email comes from the actual thread, not a template.

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

FAQ

  • What's the difference between ENGAGEMENT DROP and MY DROP?

    MY DROP means the last unanswered email in the thread was yours — you sent something and didn’t follow up, or you made a commitment and didn’t deliver it. That’s a different re-entry than an engagement drop where you followed up and they stopped replying. The fix for MY DROP is shorter and more direct — acknowledge the gap, don’t over-explain it.

  • What if the contact left and there's no obvious successor?

    The prompt flags it as CONTACT GONE and runs the same org-mapping logic as the champion left play — Lusha maps the current function and identifies the safest entry point. The two plays overlap deliberately for exactly this scenario.

  • What if Lusha finds a structural change but the contact is still there?

    That’s an INTERNAL BLOCKER — the contact may still be in the thread but the deal is stalled by something they can’t control. The prescribed action changes: instead of re-engaging on the proposal, the right move is a direct question about whether the blocker affects timeline. Don’t push the commercial conversation until the blocker is named.

  • Should I always re-engage after a quiet deal?

    No. If the output is CONTACT GONE with no successor found, M&A freeze as the acquired party, and 90+ days of silence — the prompt will say the deal is likely dead. That’s the correct output. Forcing re-engagement on a dead deal wastes time and damages the relationship for a future cycle.

  • How is this different from the buying group audit?

    The buying group audit is for an active deal — you’re in it and want to map coverage gaps. This play is for a deal that’s stopped moving — the question isn’t who else to contact, it’s why it went quiet and what to do about it. Run the audit first, this play when the deal goes dark.

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