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 monitors
key contacts at strategic accounts, detects when someone leaves or changes roles via Lusha, and posts a direct alert to Slack — the account owner tagged, the replacement already identified, one specific next action included. Same-day detection instead of a QBR surprise.
Tools: Claude, Lusha, Slack
<context>
I want to alert my team on Slack when a key contact changes roles or leaves a strategic account — so the right person finds out the same day instead of weeks later in a QBR.
My strategic accounts:
- Account list: [PASTE COMPANY NAMES — one per line]
- Key contacts to monitor: [PASTE NAME, TITLE, COMPANY — or "find the key contacts from Lusha"]
- Slack channel to post to: [CHANNEL NAME OR "DM the account owner"]
- Who owns each account: [REP NAME PER ACCOUNT — or "find from context"]
</context>
<task>
1. For each account, use Lusha to check the status of the key contacts:
- Is each contact still at the company in the same role?
- Has their title changed significantly — seniority shift or function change?
- Has anyone new joined the account in the last 30 days in a role relevant to the relationship?
2. For any contact that has left, changed roles significantly, or where a new relevant hire appeared:
- Flag the change with specifics: who, what changed, when (approximate)
- Find the replacement or new contact via Lusha: verified title, email, direct phone
- Assess the impact: does this change the deal or relationship dynamic?
3. Draft a Slack message for each flagged change:
- Direct, under 60 words
- Names the contact, the change, and the impact
- Tags the account owner
- Includes one recommended next action
- Format for Slack: uses *bold* for key fields, no markdown headers
4. Post the Slack message to the specified channel or DM.
5. If no changes detected: post a brief "all clear" summary to the channel.
</task>
<constraints>
- Only flag changes Lusha verifies.
- The Slack message must include a specific next action, not just the change.
- If the account owner can't be identified, tag the channel and note the gap.
- One Slack message per changed account.
</constraints>The situation: A CS manager runs this weekly on 8 strategic accounts. This week Lusha detects two changes: a VP of RevOps who left, and a new Head of IT who joined.
Output: Two Slack messages posted to #account-alerts. Account owners tagged. Replacements found. Next actions specific.
⚠ Contact change at Meridian Logistics — @sarah.k
M.T. (VP RevOps) has left the company. Lusha no longer shows them at Meridian. Replacement found: J.P., Head of Revenue Operations — j.p@[meridian].com, joined 8 months ago.
Next action: Reach out to J.P. before the September renewal — they likely don’t know the contract is up for renewal and may not know us at all.
(48 words)
📌 New stakeholder at Cartway Technologies — @james.r
D.F., Head of IT joined 3 weeks ago. Not a departure — but IT now has a named head for the first time. They’ll likely be involved in vendor approvals going forward.
Next action: Ask your main contact whether D.F. needs to be looped in before the contract renewal in Q3.
(54 words)
Waverly Digital · Finova Group · Dune Analytics · Bright Arc Systems · Kestrel Labs · Novela Group — no contact changes detected this week.
Contact status checked via Lusha connector, May 19. Slack messages posted to #account-alerts. Details masked for privacy.
A champion leaving a strategic account is one of the most common causes of unexpected churn — and it’s usually discovered too late, on a QBR call or when an email bounces. Lusha in Claude checks contact status across multiple accounts in one pass and posts the alert directly to Slack where the account owner is already working. The replacement is found in the same pass so the next action is specific: “reach out to J.P. before the September renewal” rather than “someone left, figure it out.” Two minutes of running the prompt is worth significantly more than discovering either change three weeks later.
Data drawn from 300M+ verified contacts under GDPR, CCPA, SOC 2, ISO 27701, ISO 31700, and TRUSTe.
Weekly is the right cadence for strategic accounts. Daily is overkill — contact changes don’t happen that fast. Monthly misses the window to act. Weekly gives you same-week detection with enough time to respond before the change compounds.
Put “find from context” in the account owners field. Claude will attempt to identify the owner from the account name and any context available. If it can’t confirm, the message goes to the channel without a tag and flags the gap.
Not natively in Claude — but the prompt is designed to be run manually in under 2 minutes. For automated monitoring, Lusha’s API and webhook capabilities are the right tool. This play is for the team that wants to run it manually on a cadence without building infrastructure.
The quarterly contact change log is a structured audit for RevOps — runs once a quarter, covers the whole account base, produces a formal report. This play is a weekly operational alert for CS and AE teams — covers strategic accounts only, posts directly to Slack, optimized for speed of response over completeness.
One data connection. Works in Claude, ChatGPT, your CRM, or any agent you build.
