Topics ▾
Workflows ·

Have Bots email you numbered approvals you can answer from your phone

Intermediate, 15 minutes

Design what Bots send back as much as what you send them: a few email types, clear subject lines, and numbered items you reply to in one line each.

How this helps you

Approvals take seconds from your phone, so you stop being the bottleneck.

✦ Try it
When you need my approval, email me from your own address. Subject: [product] | [type] | [N] need you. Number each item, one line each, with a link to the work. End with how to reply, like "1 approve, 2 change: ...". Accept my short numbered replies and carry on.

Fill in: [product] and [type] are your labels (for example KPI pulse, Experiment, Tasks). [N] is how many items need you.

What they did

Brian Casel says your Bots can only be as productive as you are at managing them, so he designed what comes back to him, not just the instructions going out. Each Bot has its own email address (he set them up with AgentMail on his domain before Bots could claim their own). Bots send four kinds of email: a KPI pulse for the whole portfolio, a monthly experiment email with bets A, B and C, task emails that say how many items need him, and a quarterly strategy review. Each has a set subject line convention. In a task email the items are numbered, so he replies "1 approve, 2 approve, 3 I have a question" from his iPhone, and the Bot carries on. He iterated on the format when emails got too long to process.

Who it's for: People who manage several Bots and live in their inbox more than in chats.

Before you start

How to try it

  1. List the kinds of update you want, and cap it at a few types.
  2. Agree a subject line pattern for each, with the product and type in it.
  3. Ask for numbered items and a line on how to reply.
  4. Ask the Bot to accept short numbered replies.
  5. After a week, cut anything you skimmed past.

What to expect

An email with a clear subject and three numbered items; you reply in one line and get a short confirmation back.

Common mistakes

Related tips

Worth knowingCarved from a segment of this video starting at 11:31. Paraphrased by us; watch the original for the full walkthrough.
Next in Workflows →Get links to every comment you haven't answered

Learn more: Grok Bot Use Cases: Real Workflows From Real Users · All Grok Bot workflows tips

Related Grok Bot tips

More Workflows →
Workflows

Two habits that make usage last: batch requests, send words not screenshots

Every message makes a Bot reread the chat, so send related requests together, skip 'thanks' replies, and paste text or cropped images instead of full screenshots and PDFs.

How this helps you The same work uses fewer messages and less image reading, so your weekly usage goes further without dropping any jobs.
Spotted by Sharbel A. (YouTube) · 3 Nov 2026
Workflows

Let your Bot cancel free trials and unused subscriptions

Three built-in templates from 0.78: start a trial and cancel it before it bills, cancel plans you don't use, and watch renewal prices.

How this helps you You stop paying for trials and plans you forgot about, and nothing is cancelled without your OK.
Spotted by @spectnfa · 31 Oct 2026
Workflows

From support form to fix: a webhook, a Bot and a Cursor cloud agent

A support form posts to a webhook, a Bot picks up the ticket, and for bugs it starts a Cursor cloud agent that reproduces the issue, adds a failing test and opens a pull request for an engineer to review.

How this helps you By the time an engineer looks at a bug, it has repro steps, a test and a proposed fix waiting.
Spotted by Grok, Santi Garza (YouTube) · 29 Oct 2026