Find the right email address after a bounce
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 finds the verified current email address when an outreach email bounces. Lusha searches by name and company, confirms the contact is still there, and returns the verified work email. If they’ve left, it finds the replacement. Takes under 60 seconds.
The prompt
This prompt may contain placeholders — look for [BRACKETS] and fill them in.
<context>
An email I sent just bounced. I need to find the correct current email address for this contact and confirm they're still at the company before resending.
My bounced email:
- Contact name: [NAME]
- Company: [COMPANY NAME OR DOMAIN]
- Title I have on file: [TITLE — may be outdated]
- Last time I successfully reached them: [DATE OR "NEVER — first touch"]
</context>
<task>
1. Use Lusha to search for this contact by name and company:
- Confirm they're still at the company
- Return their current verified title — flag if it changed from what I have on file
- Return their verified work email
- Return their direct phone as a fallback if email isn't available
2. If the contact is no longer at the company:
- Flag the departure
- Find the most likely replacement in the same function via Lusha
- Return the replacement's verified email and title
3. Return:
- FOUND: verified email, current title, and whether title changed
- DEPARTED: confirmation they've left, replacement contact details if found
- NOT FOUND: Lusha can't confirm — flag for manual check
</task>
<constraints>
- Only return what Lusha verifies. Don't guess email formats.
- If the title changed significantly, flag it — it changes how the re-send should be framed.
- DEPARTED and NOT FOUND are valid outputs. Don't return an unverified address.
</constraints>What you'll get back
The situation: An SDR emailed M.C. at Salesforce. Bounce. CRM has him as “VP of Revenue Operations” — last updated 14 months ago. Running the prompt.
FOUND — title changed
- M.C. confirmed at Salesforce ✓
- CRM title: VP of Revenue Operations
- Current verified title: Senior Vice President of Accounts Receivable and Revenue Operations
- Change: promoted and scope expanded — not just a title bump
- Verified work email: [email protected] ✓
- Direct mobile: available (masked for privacy)
Title change note: He’s now SVP with a broader remit covering both AR and RevOps. The re-send should acknowledge the expanded scope — “Saw you’ve taken on the AR side as well” — rather than referencing the old conversation as if nothing changed.
Contact confirmed live via Lusha connector, May 24, 2026. Name masked to initials. Full email and phone available on live run.
Why use Lusha in Claude
A bounced email usually means one of three things: the contact left, the email format changed when their company rebranded, or the address was wrong from the start. Guessing a new format — trying firstname.lastname@ instead of f.lastname@ — is unreliable and risks sending to the wrong person or hitting a spam trap. Lusha in Claude skips the guesswork entirely. One call returns the verified current address, confirms the contact is still at the company, and flags any title change that should change how the re-send is written. The whole check takes under a minute and the result is either a confirmed address or a clear reason why it can’t be confirmed.
Data drawn from 300M+ verified contacts under GDPR, CCPA, SOC 2, ISO 27701, ISO 31700, and TRUSTe.
FAQ
Why did the email bounce if the contact is still at the company?
Two common reasons. The contact was promoted and their email format changed — some companies switch from
f.lastname@tofirstname.lastname@when people reach SVP level. Or the address in the CRM was entered incorrectly in the first place. Lusha returns the verified current format, not the one you had on file.What if the contact has left?
The prompt flags the departure and runs a second search to find the most likely replacement in the same function. You get the new contact’s verified title and email in the same output — no second prompt needed.
What if Lusha returns NOT FOUND?
It means Lusha doesn’t have a verified record for this person at this company. That’s a clean output — it tells you the contact needs manual research rather than a second attempt at guessing the email format. Check LinkedIn to see if they’ve left or changed roles, then re-run with updated information.
Should I update the CRM before resending?
Yes — especially if the title changed. A re-send that references the old title signals you’re working from stale data. Update the CRM first, then write the re-send with the current context.
How is this different from just searching Lusha directly?
Running it through Claude means the title change is flagged, the re-send framing note is included, and the fallback phone is returned in the same output. A direct Lusha search returns the contact record — this prompt returns the contact record plus what to do with it.
Ready to build this?
Get started with Lusha and set up this play in minutes.
