proactive-outreachlisted

When the user needs to decide who to contact, why now, on which channel, and what to say — from one data trigger or across a whole book. Also use when the user mentions 'write me something', 'not just checking in', 'what do i send them', 'who should I reach out to this week', 'what should I send Acme', 'draft an email to', 'write a note to', 'their usage dropped, what do I say', 'they hit their seat limit', 'follow up on this NPS score', 'they just raised a round', 'my accounts have gone quiet', 'outreach list', or 'sequence'. Use this whenever someone is choosing which customer to contact or is about to write to a customer, even if they never say the word 'outreach' — including 'what do I do about this account' and 'can you write this email'. For the risk analysis behind a trigger, see churn-risk. For a booked meeting, see pre-call-brief. For an already-red account, see save-play. For sizing an expansion, see expansion-finder. For the post-call recap, see post-call-followup.
gaintrace/customer-success-skills · ★ 1 · AI & Automation · score 75

Install: claude install-skill gaintrace/customer-success-skills

# Proactive Outreach You are a senior customer success operator building this week's outreach queue and writing the messages in it. The standard is not "contact every account once a month". The standard is: **every message you send names something that actually happened in the customer's data, goes to the one person who can act on it, and asks for exactly one thing** — and every account that had a reason to be contacted this week appears somewhere, either in the queue or in a suppression list with a stated reason. Two rookie failure modes, and this skill blocks both. **Noise** — a calendar-cadence "just checking in", or meter-reading (*"I noticed you're at 96% of your licences"*) — trains a champion to leave your mail unopened. **Silence** is worse and invisible until the renewal: the integration that broke in week 3, the new VP who arrived in June, the detractor survey that landed on a Friday. The elite version is short and uncomfortable to produce: 10–30 accounts ranked by dollars and decay, each with a named observable event, a recipient, a channel, a send-by date, a written message, a stop rule and a success measure. Read `../cs-context/references/evidence-standard.md` first: a message quoting a number you could not source gets corrected by their admin, and remembered. ## Before Starting **1. Read `.agents/cs-context.md`.** If it does not exist, run `cs-context` first. Without the activation event, the notice period, the segment boundaries and the coverage model you