bots.new_
Sign in
USE CASEWorkSimple

“Have your Grok Bot cancel subscriptions for you - workarounds and all”

Morgan Linton asked his Grok Bot to cancel a service - and it just figured it out. When it couldn't log in, instead of getting stuck it clicked a 'manage plan' link in an email, triggered a one-time sign-in email, and used that to finish the cancellation. He had to ask the bot how it pulled it off.

Grok·0.0·0 saves·5 uses·via @morganlinton·Tweet by @morganlinton
Open @morganlinton on X

How it runs

2 steps. Do them in order.

  1. 01Cancelling a subscription is one of those small, annoying jobs that companies deliberately make hard. Morgan Linton just handed it to his Grok Bot - and the interesting part isn't that it worked, it's *how* it worked. The bot couldn't log in to the account, but rather than getting stuck and pinging him, it went looking for another way in: it found a "manage plan" link in one of the service's emails, had a one-time sign-in link sent to the inbox, used that to get in, and cancelled. He literally had to ask the bot afterward how it had done it.
  2. 02To set this up you don't need much: a Grok Bot with access to your email and a browser. You name the service you want gone, and it works the account the way a determined human would - trying the normal path first, then finding a legitimate workaround when the front door is locked. The prompt below adds one guardrail Morgan's story didn't need but you'll want: confirm the exact thing being cancelled before the final, irreversible click.

What you get

This is the moment a lot of people realize their bot isn't just following steps - it's problem-solving. A locked login is exactly where a script (or a less capable assistant) stops and asks for help. Morgan's bot treated the wall as a puzzle instead of a dead end: it reasoned that a "manage plan" email link and a magic sign-in code were another legitimate route to the same account, and took it. That's the difference between automation and an agent - and it's why "cancel this for me" is such a satisfying first real task to hand off. The one thing worth adding for everyday use is the confirm-before-cancel step, so the same resourcefulness never ends the wrong subscription.

Prompt

Copy it. Change the names. Keep the job.

Prompt
I want you to cancel a subscription / service for me: [SERVICE NAME, and the email or account it's under].

You have access to my email and a browser. Handle it like this:
1. Find the account and the cancellation path - check the service's site and my inbox for anything relevant (billing receipts, "manage plan" or account emails).
2. Try to cancel through the normal account settings first.
3. If a normal login does not work, do not get stuck and do not give up - look for a legitimate workaround: a "manage subscription/plan" link in one of their emails, or request a one-time sign-in / magic link to my inbox and use that to get in.
4. Before you click the final, irreversible "cancel" button, show me exactly what you are about to cancel (the service, the plan, any end date or refund note) and get my OK.
5. After it is done, confirm the cancellation (grab the confirmation email or number) and tell me the effective date.

Rules: only touch the ONE service I named - never cancel or change anything else. If you genuinely cannot complete it, tell me exactly where you got stuck and what you need from me.
Use withGrok

via @morganlinton · Tweet by @morganlinton

Tips

  • ·Morgan describes the outcome, not a prompt; the setup below is a curator reconstruction. Give your bot access to your email and a browser, name the exact service to cancel, and let it work - the resourcefulness (using a magic sign-in link when a normal login fails) is emergent, not scripted.
  • ·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