Find contacts you haven’t emailed in 90+ days in active accounts
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 thread output, but were not pulled from a live session. Run the prompt with your own data and connectors to see live results. Personal details in any live examples are masked or abbreviated for privacy.
Active accounts go cold one neglected contact at a time. This Claude prompt searches Gmail for the last outbound email to every contact on a list, validates each contact is still in place via Lusha, and drafts a specific re-engagement email for every contact not touched in 90 or more days. Run it monthly. The relationships it surfaces are worth keeping.
The prompt
This prompt may contain placeholders — look for [BRACKETS] and fill them in.
<context>
I want to find contacts in my active accounts who I haven't emailed in 90 or more days — but who are still at the company and still relevant to the relationship. These are relationships that have gone cold through neglect, not because the account is dead. I want to know who they are and have a re-engagement email ready for each one.
My accounts:
- Account list with contacts: [PASTE COMPANY, CONTACT NAME, TITLE — one per line]
- Account type: [CUSTOMER / PROSPECT / BOTH]
- What I sell: [PRODUCT / SOLUTION]
- What counts as active: [CUSTOMER WITH OPEN CONTRACT / PROSPECT IN PIPELINE / BOTH]
</context>
<task>
1. For each contact, search Gmail to find the last outbound email sent to that person:
- Date of last outbound email
- Subject and topic of that email
- Did the contact reply? What did the contact say?
- How many days since the last outbound touch?
2. Use Lusha to validate each contact:
- Still at the company in the same role?
- Title changed since the last email?
- Any account signal in the last 60 days: exec hire, funding, headcount shift, M&A
3. Flag each contact:
- COLD (90+ days, no recent touch): contact is still there — relationship at risk from neglect
- WARM (30–89 days): not urgent but worth noting
- ACTIVE (under 30 days): no action needed
- DEPARTED: contact has left — find replacement via Lusha
4. For every COLD contact, draft a re-engagement email:
- Subject: references the last topic discussed — not "Checking in"
- Opening: acknowledges the gap without over-explaining — one sentence maximum
- Body: one specific reason this outreach is relevant now — account signal, product update, or genuine question about the account
- Closing: one low-friction ask
- Under 80 words
5. Return:
- Full contact status list sorted by days since last touch (longest first)
- DEPARTED contacts with Lusha replacement details
- Draft re-engagement email for every COLD contact
- Summary: X COLD, X WARM, X ACTIVE, X DEPARTED
</task>
<constraints>
- Only flag contacts where the last outbound was genuinely more than 90 days ago — don't include contacts where a reply was received recently even if the original outbound was older.
- The re-engagement email must reference something specific — the last topic discussed, an account signal, or a concrete question. "Just wanted to check in" is not acceptable output.
- DEPARTED contacts get a replacement search, not a re-engagement draft.
- Under 80 words per draft. Count them.
</constraints>What you'll get back
The situation: A CS manager runs this monthly scan across 7 active customer and prospect contacts. Mix of customers on open contracts and prospects in late-stage pipeline.
Contact status list — sorted by days since last touch
| Contact | Company | Title | Status | Last touch | Signal |
|---|---|---|---|---|---|
| D.R. | Notion | Head of Sales Strategy & Ops | COLD | 112 days ago | Headcount +22% |
| M.T. | Clari | VP of RevOps | COLD | 97 days ago | None |
| A.L. | Zendesk | SVP of Global Sales | COLD | 94 days ago | None — ⚠ title changed (was VP) |
| M.C. | Seismic | VP of RevOps | WARM | 61 days ago | None |
| J.S. | Highspot | VP of RevOps | WARM | 44 days ago | None |
| A.O. | Gong | AVP Commercial Sales | ACTIVE | 12 days ago | None |
| B.N. | Highspot | Sr Director RevOps | DEPARTED | — | Lusha confirms no longer at Highspot |
Summary: 3 COLD · 2 WARM · 1 ACTIVE · 1 DEPARTED
DEPARTED — replacement found
B.N. at Highspot confirmed departed via Lusha. Replacement: J.S., VP of Revenue Operations — j.s@[highspot].com ✓ · direct mobile available
Re-engagement drafts — COLD contacts
D.R., Notion — 112 days
Last topic: data quality for the SDR ramp. Last outbound sent April 18 — no reply. Account signal: Notion sales headcount up 22% in the last 60 days.
To: d.r@[notion].com Subject: SDR ramp data — worth revisiting
Hi David,
It’s been a few months since we last connected on the data quality piece for your SDR ramp. Your team has grown significantly since then — 22% headcount increase in sales. That scale is exactly when the gaps in your data layer start to show.
Still worth 20 minutes?
[Name]
M.T., Clari — 97 days
Last topic: RevOps tooling evaluation, Q2 budget discussion. Last outbound sent March 3 — contact replied once asking about pricing, no follow-up sent. Account signal: None.
To: m.t@[clari].com Subject: Q2 pricing question — I dropped the ball
Hi Marcus,
You asked about pricing back in March and I never sent the detail. That’s on me. Attaching the current pricing breakdown — happy to walk through it if the Q3 budget conversation is still live.
Worth a quick call?
[Name]
A.L., Zendesk — 94 days · ⚠ title changed
Last topic: contract renewal discussion, February. Last outbound sent February 28. Contact status: A.L. confirmed at Zendesk — promoted from VP to SVP of Global Sales since last email. Account signal: None.
⚠ Update CRM title before sending. The re-engagement email should acknowledge the promotion.
To: a.l@[zendesk].com Subject: Renewal — and congratulations
Hi Andrew,
Saw you stepped up to SVP — congratulations. It’s been a few months since we talked through the renewal terms. Wanted to reconnect before the contract window closes and make sure the conversation is still with the right person on your side.
15 minutes this week?
[Name]
Thread data based on live Gmail connector field format. Contacts verified against live Lusha data, May 26, 2026. Names masked to initials.
Why use Lusha in Claude
The M.T. re-engagement works because it leads with accountability — “you asked about pricing in March and I never sent it, that’s on me.” That’s not a check-in, it’s closing an open loop that’s been sitting for 97 days. The A.L. draft works because it acknowledges the promotion before referencing the renewal — a SVP who gets emailed as a VP without acknowledgment knows immediately the sender hasn’t been paying attention. The 90-day threshold is the right one: under 90 days most reps are actively managing the relationship. Over 90 days the relationship is cooling and the rep may not have noticed. Gmail + Lusha surfaces that gap before the account does.
Data drawn from 300M+ verified contacts under GDPR, CCPA, SOC 2, ISO 27701, ISO 31700, and TRUSTe.
FAQ
Why 90 days specifically?
90 days is the threshold where a relationship shifts from “active but quiet” to “at risk from neglect.” Under 90 days a rep is usually aware of the gap. Over 90 days the account often doesn’t know if the relationship is still active. Adjust the threshold in the context field if your sales cycle or customer relationship cadence runs on a different clock — 60 days for fast-moving pipeline, 120 days for long-cycle enterprise accounts.
What if a contact went cold because the deal was lost or deprioritized?
The prompt flags the last email topic and date. If the context makes clear the relationship ended intentionally — “we decided to go with another vendor” — don’t send the re-engagement draft. The constraint is that the account must still be active. A lost deal is not an active account. Remove it from the input list before running.
What if Gmail shows no outbound emails to a contact at all?
The prompt flags it as “no prior outbound found” — the contact is new or was never emailed directly. The re-engagement draft becomes a first-touch email using Lusha context. Worth running the find the decision-maker prompt first in that case to make sure the contact is the right person to reach.
How is this different from the dark accounts scan?
The dark accounts scan checks both contact status and inbound engagement — it flags accounts where the prospect has gone quiet, not just where the rep has. This prompt is one-directional: it measures the rep’s outbound cadence and flags where the rep has gone quiet. Different accountability, different use case. Run the dark accounts scan for inbound silence, run this prompt for outbound neglect.
Ready to build this?
Get started with Lusha and set up this play in minutes.