Churn Early Warning

You have access to the SnitchFeed MCP. This has a one-time setup and then a daily run.

=== SETUP, RUN ONCE ===

1. Call snitchfeed_get_org_context.

2. I will paste our customer list: company names, domains, and the handles of their key people. Ask me for it if I have not already given it to you.

3. Call snitchfeed_get_query_grammar so you use valid syntax, then build one query per customer covering the company name, the domain, and their team's handles. Keep each query tight. A customer's name that is also a common word needs extra qualification or it will flood the listener.

4. Test every query before saving it, using snitchfeed_test_reddit_query, snitchfeed_test_twitter_query, snitchfeed_test_linkedin_query or snitchfeed_test_hackernews_query as appropriate. Show me two or three sample matches per query. Do not save anything that returns obvious noise.

5. Once I approve, call snitchfeed_create_listener to create the listener. Name it "Customers", write a 200 to 500 character intent describing what a relevant hit looks like (a tracked customer's own team talking about switching, frustration, or a support question), pick any color, and pass all the tested queries in the queries array so the listener and its queries are created together. Keep the returned listener_id for the daily run below, and use snitchfeed_create_listener_query with that id if I add more customers later.

=== DAILY RUN ===

6. Call snitchfeed_list_mentions scoped to the Customers listener with date_from set to yesterday.

7. Separately call snitchfeed_list_mentions with include_intents ["seeking_alternative", "comparison", "pain_point", "competitor_mention"] and sentiment "negative" for the same period, in case someone slipped through under a different listener.

8. Classify every hit into exactly one of:
   - AT RISK: evaluating alternatives, publicly frustrated, comparing us to a competitor, or threatening to leave
   - NEEDS A REPLY: a genuine support or how-to question asked in public
   - EXPANSION: hiring, funding, a new team, a new use case, or praise worth amplifying
   - NOISE: everything else

9. For every AT RISK item give me: which customer, who the person is, what they said verbatim, the link, and how urgent it looks on a scale of 1 to 3 with your reasoning.

10. For each of those, draft a reply the account owner could send, and a two-line internal note explaining the situation. Keep the reply human. Acknowledge the problem before offering anything.

11. Summarise EXPANSION separately at the bottom, since those are opportunities rather than fires.

Never reply, post or message anyone yourself. Everything waits for the account owner.