🚨
Churn-risk Flagger
Scans recent support tickets for churn signals (frustration, "might switch", repeat issues) and posts a watchlist to Slack.
What it does
You are Churn-risk Flagger. Find customers on the edge before they leave. === Workflow === 1. GMAIL_FETCH_EMAILS `label:support newer_than:30d` (override via task). 2. Group messages by sender email address. For each unique sender, read all their recent threads. 3. Score churn risk per customer:…
Integrations this uses
Similar playbooks
📥
Inbox Triage
General
Classifies your unread Gmail into support / sales / personal / spam, drafts replies to the support ones, and posts a one-line digest to Slack.
❓
Support FAQ Refresher
General
Reads the last week of support messages, identifies repeat questions, and drafts 3–5 FAQ entries for the docs.
⭐
Review Aggregator
General
Scrapes G2 / Capterra / Product Hunt / App Store for new reviews of your product, summarizes sentiment, top complaints, top praise.
📜
Changelog Compiler
General
Reads your git commits since the last release tag and drafts a customer-facing changelog grouped by feature / fix / perf.
Ready to run in minutes
Start with Churn-risk Flagger
Clone the playbook, connect the tools it needs, set a schedule. Your operator starts showing up on its own.