Keep CRM contact data accurate without a full-time admin
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 output, but were not pulled from a live session. Run the prompt with your own contact list and connectors to see live results. Personal details in any live examples are masked or abbreviated for privacy.
CRM data decays at roughly 30% per year. A full quarterly audit catches the problems — but by then, deals have already been affected. This Claude prompt runs a lightweight weekly check on CRM contacts via Lusha, surfaces only what changed since the last run, and posts the change summary to Slack. No admin needed. No full list re-report. Just the changes, sorted by urgency.
The prompt
This prompt may contain placeholders — look for [BRACKETS] and fill them in.
<context>
I want to keep my CRM contact data accurate on an ongoing basis — catching departures, promotions, and stale records before they affect outreach or forecasting. I don't want to run a full quarterly audit every time. I want a lightweight weekly check that surfaces only what needs attention.
My CRM contacts to monitor:
- Contact list: [PASTE NAME, TITLE, COMPANY, LAST VERIFIED DATE — one per line]
- CRM: [SALESFORCE / HUBSPOT / OTHER]
- Date of last check: [DATE OR "NEVER RUN THIS BEFORE"]
- Alert destination: [SLACK CHANNEL / EMAIL / "RETURN AS LIST ONLY"]
</context>
<task>
1. For each contact, use Lusha to check current status against what's on file:
- Still at the company?
- Title the same?
- Email and phone still valid?
2. Only flag contacts where something changed since the last check:
- DEPARTED: no longer at the company — find replacement via Lusha
- PROMOTED: title changed upward — update CRM
- ROLE CHANGED: same company, different function or scope
- NEW CONTACT: Lusha detects a new relevant hire at this account since last check
3. For DEPARTED contacts on active accounts: find the replacement in the same function.
4. Return only what changed — not the full list:
- Changes sorted by account priority (active deals first, then prospects, then others)
- For each change: what it was, what it is now, recommended CRM action
- For NEW CONTACTS: verified name, title, email, phone — add to CRM
5. If an alert destination is specified: post the change summary there.
Format: concise, one line per change, sorted by urgency.
If nothing changed: "No changes detected this week — CRM data current."
</task>
<constraints>
- Only surface changes. Unchanged contacts add noise, not value.
- PROMOTED is not urgent — flag for the next CRM update session.
- DEPARTED on an active deal account IS urgent — flag immediately regardless of alert destination.
- "No changes detected" is a valid and useful output.
</constraints>What you'll get back
The situation: A RevOps manager runs this every Monday for 12 contacts across active deals and key accounts. Last check was 7 days ago.
Weekly CRM change summary — week of May 26 Posted to #revops-alerts
🔴 DEPARTED — active deal — act today B.N., Sr Director RevOps, Vantage Enablement — no longer at company per Lusha Active deal: Negotiation stage, $58K ACV Replacement found: J.A., VP Revenue Operations, Vantage Enablement — j.a@[vantage].com ✓ → Update CRM, assign J.A. as primary contact, notify AE before next scheduled call
⚠ PROMOTED — update CRM P.M., Meridian Analytics — VP Sales → SVP of Sales → Update CRM title field. Not urgent but {{title}} token will break in next campaign send.
📌 NEW CONTACT — add to CRM K.R., CTO, Crestline Software — joined 8 days ago Relevant to active enterprise deal at technical evaluation stage Verified: k.r@[crestline].com ✓ · direct mobile available → Add to CRM, loop into deal communications before technical evaluation phase begins
9 remaining contacts — no changes detected. CRM data current.
Illustrative example. Run with your own contact list to see live results.
Why use Lusha in Claude
The DEPARTED flag on the Vantage Enablement deal is the only reason to run this every week rather than monthly. A departed contact at Negotiation stage is not a slow-burn data quality issue — it’s a deal problem that compounds every day the AE doesn’t know about it. The weekly cadence catches it in days. A monthly audit would have caught it after the next scheduled call went wrong. The NEW CONTACT flag — a CTO joining during an active technical evaluation — is equally valuable in the other direction: the rep gains a critical stakeholder before the evaluation phase rather than discovering the gap mid-process. Both findings are invisible without the check.
Data drawn from 300M+ verified contacts under GDPR, CCPA, SOC 2, ISO 27701, ISO 31700, and TRUSTe.
FAQ
How do I decide which contacts to monitor?
Start with the primary contacts on every active deal and the key contacts at the top 10 accounts by ACV. That’s typically 20–40 contacts — manageable in a weekly pass and covering the relationships where a change matters most. Expand the list as the territory grows.
What if the same contact is flagged as DEPARTED two weeks in a row?
Once DEPARTED is flagged and a replacement is assigned in the CRM, remove the departed contact from the monitoring list. Running a check on a known-departed contact adds noise to the weekly output and makes the relevant changes harder to spot.
How is this different from the quarterly CRM audit?
The quarterly CRM export audit is a deep clean across the full database — it catches duplicates, missing fields, and bulk stale records. This prompt is a lightweight weekly watch on a curated high-priority list — it only surfaces changes since the last run. Run both: the weekly check for real-time changes on active deals, the quarterly audit for the full org-wide database.
What if nothing ever changes week to week?
“No changes detected this week — CRM data current” is the correct and useful output. A clean result confirms the monitored contacts are accurate — which is confidence the team can act on. If weeks pass with no changes and then a DEPARTED flag appears, the contrast makes the urgency clearer.
Can I run this for a specific rep's accounts before a 1:1?
Yes — paste that rep’s key contacts and the output scopes to that rep’s accounts. Useful before a 1:1 or QBR when a manager wants to know whether any contact changes have happened that the rep hasn’t flagged. Pairs well with the rep account data quality scorecard.
Ready to build this?
Get started with Lusha and set up this play in minutes.
