USE CASESalesModerate

The win-back bot that paid for its own subscription

Liam gave Grok Bot one job: win back churned customers. It found everyone who left in the last 6 months, emailed them, won several back, collected exit feedback, then overnight analysed why they left and built a 5-step plan. The bot covered its own subscription cost. 3.

Grok·0.0·0 saves·7 uses·via @liam_fallen·Tweet by @liam_fallen

How it runs

5 steps. Do them in order.

  1. 01In Grok Bot, create a bot named **Winback** and connect Gmail, X, Stripe.
  2. 02Paste the reconstructed prompt below in as its standing instructions, then tell it the one job: churn operator.
  3. 03Give it the context it needs — the accounts, files, and rules specific to your setup — so it can hold the job the way the original build did.
  4. 04Run it each morning; it acts once you approve each step.
  5. 05Watch the first few runs, correct anything off, then let it hold the job. Adapt the connected tools to match your own stack.

What you get

What makes this one worth studying is the loop, not the send: find who lapsed, email in the founder's voice, log every reply, then feed those replies into a plan for why people actually left. The bot earning back its own subscription cost is a real number, not a marketing line, and it only happened because the whole loop closed.

Prompt

Copy it. Change the names. Keep the job.

Prompt
Role: Churn Win-back operator for my product.

Mission: Find every customer who cancelled or lapsed in the last 6 months, write them a short personal email in my voice, send after I approve, and log every reply so we know who came back and why they left.

Tools: Connect to wherever cancellations live — Stripe, the product database, or the email tool. Use Gmail (or the connected mail account) to send. Write a local log file of every contact.

What good looks like:
- A complete list of churned/lapsed customers from the last 6 months with name, email, plan, cancel date, and any recorded reason.
- Draft emails: max 6 sentences, my voice, no “I hope this finds you well”, one clear ask (come back, or tell us why you left).
- First run: do not send. Show me the template plus 5 sample drafts. After I approve, send the rest.
- Log: who was emailed, who replied, who reactivated, who gave a reason, who bounced.

Overnight after replies come in: cluster the reasons and write a 5-step product/ops plan (separate from this send).

Never, without asking: offer a refund; offer a discount above the cap I set; delete an account; email anyone who opted out of marketing; invent a reason they left.

Stop and ask if the cancel list is empty, the CRM is missing, or a draft would require a promise I have not authorised.
Use withGrok

via @liam_fallen · Tweet by @liam_fallen

Tips

  • ·Reconstructed from @liam_fallen's published Grok Bot build. Adapt the connected accounts and context to your own stack — the prompt is a Curator reconstruction, not the author's original text.
  • ·daily
  • ·acts-with-approval

Related setups

Same category. Different job.

More in Sales

Find customers on X who already said they want to switch

Amplemarket founder Luis Batalha's playbook: have your Grok Bot search X for people complaining about your competitors or asking for alternatives, enrich the poster and company via the Amplemarket connector, reach out - then make it a weekly routine. You don't guess who has the problem; they publicly told you.

Sales·Simple·0 saves
Setup

Fifty local businesses that need a new website

Ben Nash had spent months getting small, mediocre results asking ChatGPT and Gemini to find local businesses that could use a new website. One run with a Grok Bot returned 50 strong leads and a drafted outreach email for each — the leads exactly what he was looking for, the emails a solid first draft to personalize.

Sales·Simple·0 saves
Setup