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 checks whether a contact’s title in your CRM matches what Lusha has on record right now — before you reference the wrong role in an email or walk into a call with outdated context. Returns the verified current title, classifies what changed, and tells you whether it affects how to open the conversation.
<context>
I have a contact in my CRM and I'm not sure their title is current. I want to verify what Lusha has before I reach out — so I don't reference the wrong role or miss that they've been promoted.
My contact:
- Name: [NAME]
- Company: [COMPANY NAME OR DOMAIN]
- Title I have on file: [TITLE FROM CRM]
- Last updated in CRM: [DATE OR "UNKNOWN"]
</context>
<task>
1. Use Lusha to look up this contact:
- What is their current verified title?
- Are they still at the company?
- Has their title changed from what I have on file?
- How long have they been in the current role?
2. Classify the change (if any):
- SAME: title matches what I have on file
- PROMOTED: same company, higher seniority
- ROLE CHANGED: same company, different function or scope
- DEPARTED: no longer at the company — flag and find replacement if possible
- UNVERIFIED: Lusha can't confirm — needs manual check
3. If PROMOTED or ROLE CHANGED:
- Return the new title and note what changed
- Flag whether the change affects how I should open the conversation
4. Return the verification result with the current verified title, tenure, and one note on what (if anything) changes about the outreach.
</task>
<constraints>
- Only return what Lusha verifies.
- SAME is a useful output — it confirms the CRM is current.
- A promotion is not a reason to delay outreach — it's a reason to acknowledge it in the first line.
</constraints>The situation: An SDR has E.L. at a customer support SaaS in a cold sequence. CRM shows ‘VP of Sales’ — entered 11 months ago. Running the check before Touch 1 goes out.
PROMOTED
Outreach note: The CRM title is wrong. Emailing a SVP and addressing them as VP signals stale data immediately. Open the first touch with “Saw you stepped up to SVP” — one line that shows you checked. That’s the difference between a cold email that gets deleted and one that gets a reply.
Contact confirmed live via Lusha connector, May 24, 2026. Name masked to initials. Full details available on live run.
CRM titles decay at roughly 30% per year. A contact entered 12 months ago has a one-in-three chance of being wrong. The problem isn’t just that the email looks sloppy — it’s that a promotion changes the conversation. A VP of Sales and a SVP of Sales have different budgets, different pressures, and different ways of evaluating a new tool. Reaching out with the wrong title and the wrong framing for the wrong seniority level is three strikes in the first line. Lusha in Claude catches it in 60 seconds before anything goes out.
Data drawn from 300M+ verified contacts under GDPR, CCPA, SOC 2, ISO 27701, ISO 31700, and TRUSTe.
Not always — but it changes the seniority read. A VP becoming SVP still owns the same function, so the problem you’re solving is the same. What changes is the framing: acknowledge the promotion in the first line, then connect it to why the conversation is more relevant now. “More people reporting to you means more of the problem I’m calling about” is a different opener than ignoring it entirely.
SAME is a useful output — it confirms the CRM record is current. You can reach out with confidence that the title you’re referencing is accurate. Takes 60 seconds and removes the doubt.
That’s ROLE CHANGED. The prompt flags it and notes whether it affects the outreach. If a VP of Sales became a VP of Customer Success, the problem you were selling to has changed — the prompt surfaces that so you can decide whether to continue the sequence or re-qualify.
Run it for any contact where the CRM record is more than 6 months old, or where the deal is high-stakes enough that a stale title would be embarrassing. For high-volume sequences, the campaign list cleaning prompt validates the whole list in one pass.
The bounced email fix prompt fires after a bounce — it finds the correct address. This prompt fires before outreach — it checks the title is current before anything goes out. Run this one first. If the email still bounces, run the other one.
One data connection. Works in Claude, ChatGPT, your CRM, or any agent you build.
