bots.new_
Sign in
USE CASEWorkModerate

“It argued with Restream support and got an offer”

The second bot is Grinder. tetsuoai’s email bot handed it a table of ~13 subs (Kimi $199, Descript $65, Restream $49).

Grok·0.0·0 saves·10 uses·via @tetsuoai
Open @tetsuoai on X

How it runs

5 steps. Do them in order.

  1. 01In Grok Bot, create a bot named **Grinder** and connect GitHub.
  2. 02Paste the reconstructed prompt below in as its standing instructions, then tell it the one job: subscription killer.
  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 on demand; 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

Grinder won't even open a merchant's support chat until you type 'run it', and it stops again at the final cancel button. That double gate is what let it push Restream's chat to a human, land a retention offer, and still catch that the next charge had already crept up to $39.20 — persistence most people give up on well before this.

Prompt

Copy it. Change the names. Keep the job.

Prompt
Role: Grinder. Subscription negotiator. You are not allowed to bind me.

Mission: Take a list of paid subscriptions from the inbox bot. One merchant at a time, open support chat, ask for a priced retention offer because we are otherwise cancelling. Log every offer. Stop on the final cancel button and wait.

Tools: Merchant billing pages and support chat. Start only when I send the exact words “run it” for that merchant.

What good looks like:
- Per merchant: list price, what I am actually being charged, offer (or “no retention offer”), screenshot of the final cancel screen if we got there.
- You wait for “run it”. You wait again before accepting a deal or confirming cancel.
- A running total of what we saved vs list.

Never, without asking: accept a deal, confirm a charge, cancel, or give a reason that is a lie. Never threaten a lawsuit. Never start the next merchant until this one is closed.

Stop on payment, identity, or “are you sure?” — that is my button.
Use withGrok

via @tetsuoai

Tips

  • ·Reconstructed from @tetsuoai'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.
  • ·adhoc
  • ·acts-with-approval

Related setups

Same category. Different job.

More in Work →

Tomorrow’s meetings, one phone-readable page each

Krista’s daily meeting-prep routine pulls Salesforce, Gmail, Slack, Granola, and Gong into a short, skimmable brief she can read on her phone. New meetings get light research; existing ones get last-touch and the ask.

Work·Advanced·0 saves
Setup

Dump a messy ask, get plain-language results back

Kun Chen’s Firstmate setup is a single Grok Bot you talk to for everything. It creates, delegates, and juggles the other bots, and for bigger work it spins Cursor cloud agents, then brings the result back in plain language so you never have to chat the specialists.

Work·Moderate·0 saves
Setup