Check if a prospect changed jobs before outreach in ChatGPT

Built by: Lusha
Time to build: 1 min
Difficulty: Easy
Tools: ChatGPT ▪ Lusha
Type: Prompt

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 prospect list to see live results.

A stale contact can quietly break your outreach.

The person may have changed companies. They may have moved into a new role. They may no longer own the problem you wanted to discuss. Or they may still be the right contact, but the title in your CRM is out of date.

The problem is that most teams only discover this after a bounce, a bad call, or a reply that says “I’m no longer there.”

This prompt uses Lusha in ChatGPT to check whether prospects have changed jobs, verify their current title and company, and recommend what to do next. Instead of sending outreach to old records, you can contact the right person, update the CRM, or find a replacement before the sequence starts.

How to start

Open in Claude Open in ChatGPT
1

Open Lusha in ChatGPT

Go to Lusha in ChatGPT 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

Paste your prospect list and send

Copy the prompt below, paste the contacts you want to check, add your outreach context, and send. Lusha checks for job-change signals, verifies current roles, and recommends whether to contact, replace, or update the record.

The prompt

Start from Lusha in ChatGPT or type @Lusha before sending.

@Lusha Check whether these prospects changed jobs before
I send outreach.

PROSPECT LIST:
Paste contacts in this format:
1. [Name] | [Company] | [Title] | [Email or LinkedIn URL if available]
2. [Name] | [Company] | [Title] | [Email or LinkedIn URL if available]
3. [Name] | [Company] | [Title] | [Email or LinkedIn URL if available]

OUTREACH CONTEXT:
What I was planning to discuss: [one sentence]
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 EACH PROSPECT
   For each contact, confirm:
   - Current company
   - Current title
   - Department
   - Seniority
   - Location
   - LinkedIn profile if available
   - Whether the person appears to still be at the
     company I provided

2. CHECK CONTACT SIGNALS
   Check for recent person-level signals from the last
   6 months.

   Prioritize:
   - Company change
   - Promotion

   For each signal, return:
   - Signal type
   - Signal date
   - Current company
   - Current title
   - Whether this changes the outreach path

3. CLASSIFY EACH RECORD
   Assign one status:

   Contact now:
   Prospect is still in the right role and company.

   Update and contact:
   Prospect is still relevant, but the title, company,
   or contact data should be updated first.

   Find replacement:
   Prospect left the company or no longer owns the
   relevant problem.

   New opportunity:
   Prospect changed companies and may now be a good
   contact at the new account.

   Remove:
   Prospect cannot be verified or is not relevant.

4. ENRICH CONTACT DATA
   For contacts marked Contact now, Update and contact,
   or New opportunity, return:
   - Verified business email availability
   - Direct or mobile phone availability
   - DNC status if available
   - Last updated date if available

5. FIND REPLACEMENT CONTACTS
   For contacts marked Find replacement, find up to
   3 relevant contacts at the original company who match
   the target persona, department, seniority, or likely
   ownership of the problem.

   For each replacement 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

6. WRITE THE NEXT ACTION
   For each prospect, recommend one next action:
   - Send outreach
   - Update CRM and send outreach
   - Contact them at the new company
   - Replace with another contact
   - Remove from sequence

   Explain the reason in one sentence.

7. WRITE OUTREACH ONLY WHEN RELEVANT
   If the prospect is still relevant or now relevant at
   a new company, write one short first-touch message.

   Subject line:
   Under 7 words.

   Body:
   Under 100 words.
   Reference the current role or company context.
   Do not mention that you were checking their job history.
   Do not make the job change sound creepy or overly personal.
   End with one clear, low-friction ask.

8. OUTPUT FORMAT
   Return:
   - Prospect verification table
   - Job-change or promotion signals
   - Record status
   - Verified contact data availability
   - Replacement contacts, if needed
   - Recommended next action
   - Outreach message, if relevant

Do not invent contacts, companies, emails, phone numbers,
or signals. If Lusha cannot verify a prospect, mark it
clearly rather than guessing.

What you’ll get back

 

A cleaned prospect list that shows who is still in seat, who changed jobs, who should be replaced, and what to do next. Here’s what the output looks like:

Prospect job-change check — Lusha

FieldValue
Prospects checked10 contacts · 8 verified · 2 need review
Job-change signalCompany change detected · prospect now at [Company B]
Record statusNew opportunity · contact is relevant at new company
Replacement contactA.B. · Director of Sales Operations · original account
Verified dataBusiness email available · mobile available · DNC false
Next actionUpdate CRM, contact prospect at new company, and replace original account contact

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 prospect list to see live results.

 

Why use Lusha in ChatGPT to check job changes

 

Job changes create two problems and one opportunity. The problem is that your CRM or sequence may point to the wrong person at the wrong company. The opportunity is that the same person may now be relevant at a new account.

Lusha helps make that distinction before outreach goes out. The prompt verifies each prospect’s current role and company, checks for company-change or promotion signals, and recommends whether to contact, update, replace, or remove the record. That keeps reps from wasting touches on stale contacts.

The replacement step matters because a job change does not always mean the original account is dead. If the contact left, the account may still be worth working. Lusha helps find another relevant stakeholder at the same company so the rep can keep the account moving.

The result is cleaner outreach, fewer stale records, and a better chance of turning job movement into pipeline instead of confusion.

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

  • When should I use this prompt?

    Use it before launching a sequence, before calling an old prospect list, before reviving stale CRM records, or anytime you suspect contacts may have changed roles or companies.

  • What if a prospect changed companies?

    The prompt separates the old account from the new opportunity. It can recommend contacting the prospect at their new company while also finding a replacement contact at the original account.

  • What if a prospect was promoted?

    A promotion may make the contact more relevant, less relevant, or relevant in a different way. The prompt asks Lusha to verify the current role and then recommends whether to update the record and outreach angle.

  • Should I mention the job change in my message?

    Use it carefully. The prompt avoids awkward language and does not make the message sound like you were tracking the person. If the job change is relevant, it connects the new role to the business problem you solve.

  • Can this help clean CRM data?

    Yes. This prompt is useful for identifying stale contacts, title changes, company changes, and replacement contacts before records are added to a campaign or sequence.

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