Find a replacement contact after a bounced email in ChatGPT

Example outputs in this play are illustrative — they reflect the structure, fields, and format of real Lusha connector output, but were not pulled from a live session. Run the prompt with your own contacts and bounced email details to see live results.

An email bounce doesn’t mean the account is dead. It usually means something changed — the contact left, the address is stale, the person moved teams, or the CRM record was never clean to begin with.

The worst move is to keep retrying the same bad email. The better move is to verify what happened, find the right replacement contact, and restart the conversation with someone who actually owns the problem.

This prompt uses Lusha in ChatGPT to check whether the original contact is still at the company, find verified replacement contacts in the same department or buying group, and write a short restart email that keeps the account moving instead of letting one bounce kill the opportunity.

Start from the ChatGPT Marketplace or type @Lusha before sending.

How to start

1

Open Lusha in ChatGPT

Go to the ChatGPT Marketplace, search for Lusha, and click “Start chat.” Every conversation started this way is automatically Lusha-enabled.

2

Or invoke Lusha in any existing conversation

Type @Lusha in the prompt bar and select Lusha from the dropdown. Unlike Claude, Lusha does not activate automatically in every ChatGPT conversation. You must invoke it every time.

3

Fill in the bounced contact details and send

Copy the prompt below, fill in the bounced contact, company, and outreach context, and send. Lusha verifies the original contact, finds replacement contacts, and helps you restart the conversation in one pass.

The prompt

Start from the ChatGPT Marketplace or type @Lusha before sending.

@Lusha An email bounced. Before I give up on the account,
verify what happened and help me find the right replacement
contact.

BOUNCED CONTACT:
Name: [full name]
Company: [company name or domain]
Title: [title, if known]
Email that bounced: [email address]

OUTREACH CONTEXT:
What I was trying to discuss: [one sentence describing
the reason for outreach]
Target persona or department: [persona or department]
My product: [one sentence describing what you sell and
the problem it solves]

Using Lusha, do the following:

1. VERIFY THE ORIGINAL CONTACT
   Check whether this person is still at the company.
   Return current title, company, department, seniority,
   location, LinkedIn profile if available, and any recent
   role-change or company-change signal.

   If the contact is no longer at the company, flag it
   immediately and do not recommend retrying the same email.

2. EXPLAIN THE BOUNCE RISK
   Choose the most likely reason:
   - Contact changed company
   - Contact changed role
   - Email is stale
   - Contact could not be verified
   - Contact appears valid, but the email should be reviewed

   Explain the reason in one sentence.

3. FIND REPLACEMENT CONTACTS
   Find up to 5 contacts at the same company who match
   the original persona, department, seniority, or likely
   ownership of the problem.

   For each contact, return:
   - Name
   - Current title
   - Department
   - Seniority
   - Location
   - LinkedIn profile if available
   - Verified business email availability
   - Direct or mobile phone availability
   - DNC status if available

4. RECOMMEND THE BEST NEXT CONTACT
   Pick the best person to contact next.
   Explain why based on title, department, seniority,
   and fit with the original outreach context.

5. WRITE THE RESTART EMAIL
   Write one email to the replacement contact.

   Subject line:
   Under 7 words. Specific to the account or problem.

   Body:
   Under 100 words.
   Do not mention the bounced email.
   Do not say "I was trying to reach your colleague"
   unless it is useful and non-awkward.
   Lead with the account context and the reason this
   person is likely relevant.
   End with one clear, low-friction ask.

   Do not:
   Use "just following up."
   Apologize for the bounce.
   Make the replacement contact feel like a backup option.
   Invent details that Lusha did not return.

6. OUTPUT FORMAT
   Return:
   - Original contact status
   - Bounce risk
   - Replacement contact table
   - Recommended next contact
   - Restart email
   - Why this contact is a better next step

If Lusha cannot verify the original contact or find a
replacement, say so clearly rather than guessing.
Built by: Lusha
Time to build: 1 min
Difficulty: Easy
Tools: ChatGPT, Lusha
Type: Template

What you’ll get back

 

A verified replacement contact and a restart email that keeps the account moving after a bounced email. Here’s what the output looks like:

Bounced email replacement — Lusha

FieldValue
Original contact statusCould not confirm current email · contact may have changed roles
Bounce riskEmail likely outdated
Best replacementA.B. · Director of Revenue Operations · same account
Verified dataBusiness email available · mobile available · DNC false
Recommended actionContact the replacement instead of retrying the bounced email
Draft includedYes · 94 words · no mention of the bounced email

Example outputs in this play are illustrative — they reflect the structure, fields, and format of real Lusha connector output, but were not pulled from a live session. Run the prompt with your own contacts and bounced email details to see live results.

 

Why use Lusha in ChatGPT after an email bounce

 

A bounced email is easy to treat like a technical problem. Try again. Check the spelling. Guess the format. Move on.

But in outbound sales, a bounce is often a data problem. The contact may have left the company, changed roles, moved departments, or never had a reliable email in the first place. If you keep retrying the same record, you are not following up. You are spending time on a contact path that may no longer exist.

Lusha gives reps a cleaner next step. Instead of guessing what happened, the prompt checks the original contact, verifies whether they are still connected to the company, and finds replacement contacts who match the same persona, department, or likely buying role. That means the account stays alive even when one email address fails.

The replacement step matters because timing can still be good. The original reason for outreach may still be relevant to the account, even if the first contact is not. Lusha helps turn a dead-end bounce into a verified path back into the company.

Lusha data is sourced and used in accordance with Lusha’s Privacy Policy and Terms of Use. Lusha is GDPR compliant and covers contacts across North America, EMEA, and APAC.

FAQ

  • Should I retry the bounced email before looking for a replacement?

    Usually no. If an email bounces, the first step should be verification, not another send. Use Lusha to check whether the contact is still at the company and whether there is a better verified contact to reach instead.

  • What if the original contact is still at the company?

    If Lusha confirms the person is still at the company, the prompt helps you decide whether to review the email, use another verified contact method, or continue with a different channel. If a direct or mobile phone is available and compliant to use, that may be a better next step than retrying the bounced email.

  • What if Lusha finds several possible replacement contacts?

    The prompt asks ChatGPT to rank replacement contacts by title, department, seniority, and relevance to your original outreach context. That way, you are not just getting more names. You are getting the best next person to contact.

  • Should I mention the bounced email to the replacement contact?

    In most cases, no. The replacement contact does not need to know that your first email bounced. Lead with the business reason for reaching out, not the data issue that led you to them.

  • Can I use this for stale CRM records?

    Yes. This prompt works well when a CRM record looks outdated, an email bounced, a title seems old, or a contact has not engaged in a long time. Use it to verify the person and find a cleaner path into the account.

Related Plays

Ready to run this?

Connect once, run anywhere. Works in Claude, ChatGPT, n8n, Clay, or any agent connected to Lusha.

Get free access Read the Docs