Get the full data quality report on a rep’s territory before the quarter starts

<context>
Before the quarter starts, I want a full data quality report on the contacts across a rep's territory — not just who's stale, but what the staleness is costing: which accounts are at risk, what the pipeline exposure is, and where to focus the clean-up effort first.

My territory:
- Rep name: [REP NAME]
- Contact list: [PASTE NAME, TITLE, COMPANY, LAST TOUCH DATE — one per line]
- Active deals in territory: [PASTE DEAL NAME, COMPANY, STAGE, ACV — one per line, OR "none"]
- Quarter starting: [Q1 / Q2 / Q3 / Q4 YEAR]
</context>

<task>
1. For each contact, use Lusha to check current status:
   - Still at the company?
   - Title current or changed?
   - How long in the current role?

2. Categorize each contact:
   - CURRENT: confirmed, verified — no action needed
   - UPDATE NEEDED: still there, title changed — CRM update required
   - DEPARTED: no longer at the company — find replacement if possible
   - UNVERIFIED: Lusha can't confirm — flag for manual check

3. Cross-reference stale contacts against active deals:
   - For any DEPARTED or UNVERIFIED contact tied to an active deal, flag as DEAL AT RISK
   - Return the deal name, stage, ACV, and what specifically is stale

4. Return a territory data quality report:
   - Overall data quality score: % of contacts CURRENT vs stale
   - Contacts by category with counts
   - DEAL AT RISK list: sorted by ACV descending
   - Total ACV at risk from stale or unverified deal contacts
   - Clean-up priority list: the 5 contacts to fix first, ranked by deal ACV impact

5. One-paragraph summary the manager can use in a 1:1 with the rep — what's the state of the territory data, what's at risk, and what needs to happen before Q[X] starts.
</task>

<constraints>
- Total ACV at risk is the number that matters most — lead with it.
- The 1:1 summary must be direct. Not "some contacts may need updating" but "3 of your active deals have stale or unverified contacts, totalling $X in ACV."
- If all contacts are CURRENT, say so — that's a good result worth noting.
</constraints>

The situation: A sales manager runs this before Q3 kicks off for rep J.R. Territory: 8 accounts, 4 active deals totalling $397K ACV. Contact list last refreshed 7 months ago.

Output from live Lusha run, May 25, 2026:

Territory data quality score: 50% current — 4 of 8 primary contacts need updating.

DEAL AT RISK Zendesk renewal — $180K — Proposal stage 3 of 3 contacts at Zendesk have stale titles. All three have been promoted since the deal was created. The approval path and seniority context in the CRM no longer reflects reality.

Total ACV at risk: $180K (45% of territory pipeline)

Clean-up priority (fix before Q3 starts):

1. A.L. at Zendesk — SVP, verified email/phone available — update CRM, brief J.R. on promotion before renewal call
2. E.L. at Zendesk — SVP, verified — same
3. J.P. at Zendesk — VP Worldwide Sales Ops — update scope in CRM

1:1 talking point: “45% of your pipeline — $180K — sits in a Zendesk renewal where all three contacts have been promoted since the deal started. The CRM still shows VP titles for people who are now SVPs. Before the Q3 renewal call, update all three records and brief yourself on the expanded scope. This isn’t a data hygiene task — it’s deal prep.”

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