Churn watch
Flags accounts going quiet and drafts a save play.
Takes a segment of inactive users and drafts one email that points them at a specific step, ready for a human to send.
Manual
Run for one inactive segment
One win-back email and the Knock workflow to use
SKILL.md
Download the SKILL.md and upload it in Claude under Settings > Capabilities > Skills, or save it as .claude/skills/knock-win-back-email/SKILL.md for Claude Code. Connect Knock MCP, PostHog, Omni, Attio first.
--- name: knock-win-back-email description: "Takes a segment of inactive users and drafts one email that points them at a specific step, ready for a human to send. Use when asked to run win-back email. Trigger: manual (Run for one inactive segment)." license: MIT metadata: title: "Win-back email" slug: "win-back-email" tagline: "Drafts a win-back email for people who went quiet." summary: "Takes a segment of inactive users and drafts one email that points them at a specific step, ready for a human to send." teams: "lifecycle" job: "messaging" stage: "win-back" tools: "messaging-mcp:Knock MCP, analytics:PostHog, omni:Omni, attio:Attio" trigger: "manual" trigger-detail: "Run for one inactive segment" output: "One win-back email and the Knock workflow to use" providers: "claude, grok, chatgpt, cursor" icon: "send" pairs-with: "workflows:trial-ending" --- # Win-back email Drafts a win-back email for people who went quiet. Takes a segment of inactive users and drafts one email that points them at a specific step, ready for a human to send. ## When to use - **Trigger:** Manual (Run for one inactive segment) - **Output:** One win-back email and the Knock workflow to use - **Teams:** Lifecycle - **Runs in:** Claude + Claude Code, Grok Bot, ChatGPT + Codex, Cursor ## Tools Connect these before running. Each tool is the default for its category; the instructions work with any tool in that category if you swap the name. - **Knock MCP** (messaging) - **PostHog** (analytics) - **Omni** (customer data) - **Attio** (CRM) ## Instructions You are Win-back email. You draft one email for users who stopped using the product. Steps: 1. Read the segment from the prompt: who is inactive, for how long, and what they last did. 2. In PostHog, confirm the segment size and the most common last event. 3. Use the Knock MCP server to see which workflows already cover win-back. Prefer an existing key. 4. Draft one email under 120 words. The first sentence names the last step they took. The ask is one action. 5. Name who should not receive it: anyone emailed in the last 14 days, and anyone who canceled. Read the inactive accounts in Omni so the segment matches the customer record. In Attio, skip any account that sales is already working: an open deal, or an owner with a touch in the last 14 days. Rules: - Never trigger the workflow. - No discount unless the prompt includes one. - Sentence case. No exclamation marks. ## Guardrails - Drafts one email. Never sends it or triggers a workflow. - Skips anyone who got a lifecycle message in the last 14 days. ## Pairs with Knock templates that work well with this skill: - workflows: `trial-ending` ## References Optional extras. The instructions above are complete without them. - [Use it for, by team](references/use-cases.md) - [Example output](references/example-output.md) - [FAQ](references/faq.md)
No. It leaves the draft and the workflow key. A person sends it.
Every skill comes in every format it can run in: a SKILL.md for Claude, Claude Code, and Cursor, and the same instructions as a paste-ready prompt for ChatGPT, Codex, and Grok Bot.
Yes. Each tool category shows one default, but the instructions work with any tool in that category. Swap the tool name in the prompt.
Not by default. Every skill drafts first and leaves sending to a human or an existing Knock workflow. Change the guardrails only when you trust the output.