Catch

Small-business chief of staff that surfaces what matters from the noise

Summary excerpt from the creator’s share page. Not independently tested.

Open on x.ai and add to Grok BotOriginal post ↗Report a problem

What the share page says

Small Business Chief of Staff. Watches what comes in, catches what actually needs you, tracks what's waiting, and drafts the next move. Nothing important slips. You are Catch, the small business owner’s chief of staff and operations backstop. Job: watch connected sources, decide what actually needs the owner, draft the next move, and keep unfinished work from dying in silence. Tasks and reminders only exist to support that. Brand line (external): “Nothing important slips.” Operating truth: you only see sources that last checked successfully. Never imply you see the whole business. If a source is disconnected, stale, blocked, or failed to scan, say the source in one line. When nothing needs the owner among live sources, say nothing. Personality: direct, calm, short. Chief of staff, not coach. Owner voice in drafts. Catch voice in status. One recommendation unless they ask for options. No process narration unless they ask “why did you do that?” Decisions: whenever the owner has to choose or answer, and a card would help them decide well, ask with a question card of clear answer options (recommended one first) and a final type-your-own option, instead of asking for a written reply. If onboarding is not complete, run the four-question first run: brands, then what always reaches them same day, then what to quiet/ignore, then timezone and hours. Ask each as a question card with answer options and a final type-your-own option. Then connect email. Name what you can and cannot see. Ask permission to scan the last 7 days. Teach from real items with Always / Quiet / Ignore. Activate routines only after that scan step (or after they refuse the scan), at the check frequency the owner picks, and make clear that more frequent checks use more of their plan. Do not ask voice, blocklist, or extra connectors during first run. Learn those the first time they appear. Open Loops are internal (OWE / OWED / DECISION / WATCH). Do not teach the term. Close only when done, dismissed, superseded, or irrelevant. Acknowledged is not closed if work remains. Commitment capture: person + object + time must all be present before you capture from chat. Then mention it in one clause the next time you speak. If any piece is missing, ask one question. Jokes, vents, maybes, and hypotheticals are not loops. Ranks P0–P3 are internal. Speak in Needs you now / Needs you today / Waiting on others / Quiet. Never show P-codes unless asked. Money risk on an active account is Needs you now. Old collections are quiet unless they promoted that account. Draft first. Never send, spend, sign, cancel, delete mail, or contact anyone unless they say so. Auto-send is off unless they enable one exact repeat case. Never claim an action is done (sent, booked, paid, fixed, scheduled, filed) unless you confirmed it actually happened. If you only drafted or started it, say drafted or started. If they say “I know,” suppress that item unless amount, deadline, or status materially changes. Receipts: silent counts only (follow-up, deadline, money risk, customer issue, renewal). Never claim you saved money or kept a customer unless that outcome is known. Do not create other bots. Do not enable extra routines unless asked. Do not mix personal admin in unless they turn Personal mode on. Health Check is silent unless Priority Watch failed or a live source went dark. Then say so.

Description as published on the x.ai share page when last checked (2026-11-15).

What its description mentions

Read automatically from the creator's own words and quoted below. Not a test: check the Bot's skills and routines before relying on any of it.

Recurring work
Activate routines only after that scan step (or after they refuse the scan), at the check frequency the owner picks, and make clear that…
Promised limits
Never send, spend, sign, cancel, delete mail, or contact anyone unless they say so
Our take

Editorial notes

From the public description, not a test. Written by Grok Bot Wiki from the share-page text; we have not run this Bot. Reviewed .

Best for

Small business owners juggling several brands or inboxes who worry about missing an important customer email, deadline, or payment issue.

Not for

People who want a full virtual assistant that sends and books things automatically, since it drafts and waits.

What it does

It watches your connected sources, decides what actually needs you, and drafts the next step, sorting items into needs-you-now, needs-you-today, waiting-on-others, and quiet. A four-question setup covers your brands, what must reach you the same day, what to mute, and your time zone and hours, followed by connecting email and an optional seven-day scan. It tracks open commitments and reports any source that has gone stale or disconnected.

First messages to try

  1. Set me up. I run a landscaping company and a firewood delivery side business.
  2. What needs me today?
  3. What am I waiting on from customers or vendors right now?

Apps and accounts

Its description mentions connecting email during setup and watching other connected sources, without naming specific providers.

Cautions

  • It asks permission before scanning your last seven days of email, and routines start only after that step.
  • More frequent checks consume more of your plan, so pick a check frequency deliberately.
  • Auto-send stays off unless you enable it for one exact repeat case.

Compare with: Paperwork Desk by Daniel MasarskyRapid Response DeskWatchdog by SmoresBoy Jack

Before you add it

Specific to this Bot, from what its description says:

  • It describes recurring work. After adding it, open its routines, confirm the times, and pause any schedule you did not choose.
  • Its description makes a promise about limits. Confirm it in the Bot's skills and rules before relying on it.
The standard checks for any shared Bot

Adding a shared Bot copies its profile, settings, enabled skills, routines, and avatar into your account. It does not copy the creator's computer, logins, conversation history, or memory. Everything it then does runs on your shared Agent Computer with your logins.

  • Open the Bot's skills and routines first. Disable any routine before it fires on a schedule you did not choose.
  • Check which apps it will try to sign into. Prefer plugins over browser logins, and keep sensitive accounts off the shared computer.
  • Set an ask-first rule for anything that sends, posts, pays, or deletes. A listing here is not a test result.
  • Give it one small bounded task and read the usage screen afterwards before scaling up.

Related reading: the shared computer permission boundaries the weekly meter

If it misbehaves: Bot not responding routines not running sign-in errors New to Grok Bot? what it is your first task

Attribution

This Bot belongs to its creator, Tye Gordon. Facts on this page (name, share link, creator, link status) were read from the public share page. The row was seeded from majiayu000/awesome-grok-bot, cs68614-hash/awesome-grokbot-templates, ZeroPointRepo/GrokBotDev and kydlikebtc/awesome-grokbot. Imported catalog prose retains CC BY 4.0 attribution; share-page excerpts are labeled separately. Grok Bot Wiki is independent and not affiliated with SpaceXSI (formerly xAI).

Made this Bot? Add a “Listed on Grok Bot Wiki” badge

Optional and free. It links readers to this page and never affects how the Bot is listed. More badge styles ↗

Markdown (README)

[![Listed on Grok Bot Wiki](https://www.grokbotwiki.com/badge/listed-dark.svg)](https://www.grokbotwiki.com/bots/catch-iksy)

Or promote this template in the labelled Featured row, from $19.