Audit a CRM export for stale, duplicate, and missing records

<context>
I have a CRM contact export that needs auditing before we use it for a campaign, forecast, or quarterly push. I want to know what's stale, what's missing, what's duplicated, and what needs to be fixed before anyone works this list.

My export:
- CRM: [SALESFORCE / HUBSPOT / OTHER]
- Export type: [CONTACTS / LEADS / ACCOUNTS]
- Paste your export here: [PASTE CSV DATA OR KEY FIELDS — Name, Title, Company, Email, Phone, Last Modified]
- What this list is being used for: [CAMPAIGN / FORECAST / TERRITORY REVIEW / QBR PREP]
- Our data quality standard: [e.g. "Every contact verified and reachable" OR "leave blank for default"]
</context>

<task>
1. For each record in the export, use Lusha to validate:
   - Is the contact still at the company in the same role?
   - Is the title current or has it changed?
   - Is the email verified and deliverable?
   - Is a direct phone available?

2. Flag each record with a status:
   - VERIFIED: confirmed at company, email valid, title current — no action needed
   - UPDATE NEEDED: still at company but title changed or email differs — update before use
   - DEPARTED: contact no longer at the company — find replacement if account is active
   - DUPLICATE: same contact appears more than once — flag the master record to keep
   - UNVERIFIED: Lusha cannot confirm — manual check required

3. For DEPARTED contacts on active accounts: use Lusha to find the current replacement in the same function.

4. Return a data quality report:
   - Overall score: % VERIFIED vs total records
   - Full flagged list with status per record and recommended action
   - DEPARTED records with replacement contacts found via Lusha
   - DUPLICATE pairs with master record recommendation
   - Records missing mandatory fields for the stated use case

5. Export-ready summary:
   - Records ready to use as-is
   - Records needing update before use
   - Records to remove or replace
   - Estimated time to bring the full list to VERIFIED status
</task>

<constraints>
- Only return what Lusha verifies. Don't infer or guess missing fields.
- DUPLICATE detection is by name + company — flag even if email differs slightly.
- The export-ready summary must be specific enough to paste into a Slack message or CRM task.
- If the list has more than 50 records, process in batches and return a running total.
</constraints>

The situation: A RevOps manager at a SaaS company exports 12 Meridian CRM contacts from the Sales and RevOps function before a Q3 campaign. Last CRM update: unknown. Running the audit before the campaign is scheduled.

Output from live Lusha run, May 26, 2026:

Overall data quality score: 50% VERIFIED — 6 of 12 records clean

Export-ready summary:

• 6 records ready to use as-is
• 3 records need title update before campaign personalization
• 1 duplicate pair — merge before import (keep record with most recent activity)
• 1 departed — remove, account covered by existing contact
• 1 unverified — manual check required

Data quality score: 50%. To reach 100%: 3 title updates (est. 10 min), 1 deduplication, 1 manual check. Departed record does not need replacement — account already covered.

Contacts verified live via Lusha connector, May 26, 2026. Names masked to initials.