More Resources
Prompt

Prep a cold call using the last email thread

Time to build: 1 min
Difficulty: Easy
Tools: Claude ▪ Gmail ▪ Lusha

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.

Before dialing, this Claude prompt checks Gmail for any prior email history with the prospect or the prospect’s company. Lusha validates the current title, confirms the prospect is still at the company, and returns a verified direct mobile. The output is a one-screen brief — readable while the phone rings — with a specific opening line that references the email history or the account signal. Most calls that feel cold don’t have to be.

The prompt

Open in Claude Open in ChatGPT 
<context>
I'm about to make a cold call to a prospect. Before I dial, I want to check whether there's any prior email history with this person or the prospect's company, validate current contact details, and get a direct dial — so the call isn't truly cold and I know exactly how to open.

My prospect:
- Name: [NAME]
- Company: [COMPANY NAME OR DOMAIN]
- Title I have on file: [TITLE OR "UNKNOWN"]
- What I sell: [PRODUCT / SOLUTION]
- Why I'm calling: [SIGNAL / REASON / OR "FIND ONE"]
</context>

<task>
1. Search Gmail for any prior thread with this contact or the prospect's company domain:
   - Has anyone from my team emailed this prospect before?
   - Did the prospect reply? What did the prospect say?
   - What topic was discussed and how long ago?
   - Is there an open thread I should reference on the call?

2. Use Lusha to validate the prospect and pull call details:
   - Confirm current verified title — flag if different from what I have on file
   - Confirm the prospect is still at the company
   - Return direct mobile number (preferred over office line)
   - Pull any account signal from the last 30 days: funding, exec hire, headcount shift

3. Build a cold call brief — one screen, readable in 60 seconds:

   WHO I'M CALLING
   - Verified name, current title, tenure in role, seniority read

   PRIOR CONTACT
   - Any email history: topic, date, outcome, whether the prospect replied
   - If no history: "First contact — no prior thread"

   ACCOUNT SIGNAL
   - Live signal if detected, or "No signal — calling on ICP fit"

   OPENING LINE
   - One specific opener based on prior email history or account signal
   - If prior history exists: references the thread — "We emailed back in [month] about X"
   - If no history: references the signal or ICP fit

   DIRECT DIAL
   - Verified mobile number

4. Flag anything that should change the call approach:
   - Title mismatch — the prospect was promoted or changed roles since any prior outreach
   - Prior outreach went unanswered — note it so the opener doesn't pretend otherwise
   - Strong signal detected — lead with the signal, not the product
</task>

<constraints>
- One screen. The rep reads this while the phone is ringing.
- The opening line must be specific — not "I wanted to introduce myself."
- If prior email history exists, the call is not cold — frame the opener accordingly.
- Direct dial only. Flag if only a switchboard number is available.
</constraints>

What you'll get back

The situation: An SDR is about to call D.R. at [collaborative AI workspace] — Head of Sales Strategy and Operations. Has a number on file but isn’t sure it’s direct. Knows an AE emailed [collaborative AI workspace] a few months ago but doesn’t know what was said. Running the prompt while pulling up the phone.

WHO I’M CALLING

D.R., Head of Sales Strategy and Operations, [collaborative AI workspace] ✓ 18 months in role · Decision-maker / influencer level · Reports into VP Sales

PRIOR CONTACT

Email thread found — 38 days ago. Subject: “Data quality for the SDR ramp — [collaborative AI workspace]” An AE sent the original outreach. D.R. replied: “This looks interesting — we’re in the middle of an ops review and data quality is actually on the list. Can you send something over on how the enrichment works?” A case study was promised in reply but never sent. Thread went cold on the AE’s side.

⚠ Flag: Prior outreach went unanswered from our side — D.R. replied and was waiting on material that was never delivered. Don’t open as if this is a first touch. Reference the thread and acknowledge the gap.

ACCOUNT SIGNAL

[Collaborative AI workspace] sales team headcount up 22% in the last 60 days — 8 new AE and SDR roles currently open. Active hiring surge into the function the product serves directly.

OPENING LINE

“Hi David — it’s [name] from Lusha. My colleague emailed you back in April about data quality for the SDR ramp. You replied asking for detail on the enrichment and we dropped the ball — that’s actually why I’m calling. With your team growing the way it is, I wanted to connect directly rather than let another email sit unanswered.”

DIRECT DIAL

Verified mobile: available (masked — returned on live run)

Thread structure based on live Gmail connector field format. Contact details illustrative — run with your own data to see live results.

Why use Lusha in Claude

Most “cold” calls aren’t actually cold — a colleague emailed the same company three months ago, or the prospect is on a re-engagement list from a sequence that ran last quarter. Without checking Gmail first, the rep calls and says “I’m reaching out for the first time” to someone who already replied to a previous email and never heard back. That’s a worse opener than the truth. Gmail in Claude catches the prior thread in seconds. Lusha validates the direct dial and the account signal. The opener in the example — acknowledging that the team dropped the ball — works precisely because it’s honest. That’s what earns 30 seconds on a cold call.

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

FAQ

  • What if Gmail finds a thread but the prospect never replied?

    The prompt flags it — “prior outreach sent, no reply received.” The opener adjusts: instead of referencing a two-way conversation, the rep acknowledges the earlier email and gives the prospect a reason this call is worth 30 seconds now. The signal or the account context does that work.

  • What if there's no prior thread at all?

    The brief returns “First contact — no prior thread” and the opening line is built from the account signal or ICP fit instead. The call is genuinely cold in that case, but the opener is still specific — it leads with something happening at the account, not a product introduction.

  • What if the number Lusha returns isn't a mobile?

    The prompt flags it — “office line only, no direct mobile available.” The rep can still call but should be prepared for a gatekeeping scenario. A fallback email opener is worth having ready.

  • How is this different from the cold call prep play that already exists?

    The existing cold call prep play builds a brief from a LinkedIn profile and account signals. This play adds the Gmail layer — checking whether the prospect or the prospect’s company has been contacted before and using that history to change the opening. The two plays complement each other: use the existing one when you have no prior contact, use this one when there might be history worth surfacing.

  • Should I mention the prior email drop on every call where history exists?

    Only when the prior thread has a specific open item — a commitment that wasn’t followed through, a question that wasn’t answered. If the prior thread was just a cold email that went unanswered with no reply from the prospect, there’s no need to lead with it. The opener in that case focuses on the account signal instead.

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