Grok Bot routines are worth switching on for a small business when you have a job that repeats every day or every week and only needs a person at the final yes.
A routine is a standing order for one Bot: run this workflow at this time, or run it when this thing happens.
It keeps running in the cloud after you close the laptop and lock the shop.
The catch is simple: every run spends usage from your plan, so a careless routine eats your weekly allowance.
If you want a second pair of eyes on which jobs to hand over, book a free strategy call with my team and we'll go through your week with you.
The owner's answer: worth it for prep work, not for hands-off sending
Routines shine at gathering, sorting, checking and drafting.
They are built to stop before anything risky goes out.
The Grok Bot apps docs say email written by a routine waits as a draft until you press Send, and there's no option for unattended sending.
So the time you get back comes from the hour of collecting and writing, not the ten seconds of clicking Send.
That's the right trade for most owners, because the risky step stays with you.
Which plans include Grok Bot routines
xAI's subscription page says Grok Bot is included on the Premium, Super and Ultra plans.
The Plus plan doesn't include Grok Bot at all.
Super and Ultra come with bigger shared weekly allowances, and Grok Bot usage draws from one weekly pool shared with Grok and Cursor.
If you pick a plan that can't run routines, the Bot tells you which plan can; that landed in v0.77.0 on 26 October 2026.
What changes when the shop is closed
The Grok Bot FAQ confirms that closing the app, laptop or phone doesn't stop a routine.
The Bot works on its own cloud computer.
A routine can start on a schedule, or when a Slack message, an email, a webhook call, or a GitHub, Linear, Sentry or PagerDuty event arrives.
For a small firm, the four that matter most are the schedule, email, the webhook and Slack.
The developer triggers suit agencies and software teams.
Use case: a local shop answering order questions
Picture a gift shop that gets the same order-status emails all week.
Give the Bot its own email address, then create an alias such as yourname+shop for customers.
Since v0.71.2, a routine that watches a tagged address runs only for mail sent to that tag.
The routine reads each question, checks the order and writes a reply draft for you.
You open the drafts at lunch and press Send on the ones that look right.
Keep a sender filter on it too, because the docs say an alias is a label, not a lock.
Use case: a service firm catching every web lead
A plumbing or cleaning firm lives on fast replies to its contact form.
Point the form at the routine's webhook so every new enquiry starts a run carrying the form fields as its JSON payload.
The Bot looks up the job area, drafts a reply with your standard availability text, and leaves it waiting for you.
A second routine on a weekday schedule can post a short morning list of yesterday's leads that still have no reply.
Neither routine contacts the customer on its own.
🔥 Want this set up for your own business, step by step? Inside the AI Profit Boardroom you get video trainings on scheduled and event-driven AI jobs, plus the Agent OS you install yourself, live coaching four times every week, and over 3,400 members comparing what works for real shops and service firms. → Join the AI Profit Boardroom
Use case: a salon checking tomorrow's bookings
A salon or clinic loses money quietly on no-shows and double bookings.
Set a schedule routine for 5:00 PM every weekday that reads tomorrow's appointments from your booking tool.
Ask it to flag gaps, clashes and clients with no confirmation, then post the list in your chat.
Reminder texts or emails stay as drafts for you to approve.
Before you rely on it, open the routine and check that When to run says 5:00 PM in your own time zone.
Schedules follow the Timezone setting in Settings, and Auto-detect follows the device you're using.
A routine built at 5:10 PM waits until the next day, so press Test if you want to see the list tonight.
Use case: an agency watching client channels
A small marketing agency often runs client work through shared Slack channels.
Set a Slack routine on one client channel that fires only when someone writes "needs review".
The Bot pulls the brief and the latest file, then posts a short summary in this conversation for the account lead.
Since v0.75.8 on 24 October 2026, the Bot's Slack posts from a routine don't notify your phone, so the team isn't pinged all evening.
On a shared Bot, a routine that replies in a Slack thread follows that thread and answers later replies without an @mention.
Where the hours actually come back
The time saved isn't a number anyone can promise you, so measure your own.
Time one manual run of the task this week, then multiply by how often it repeats.
That's the ceiling of what a routine can hand back.
Take off the minutes you'll still spend reviewing drafts and answering approval cards.
If the gap is small, leave the job manual and pick a heavier one.
Look at the run history after the first fortnight.
The phone app marks each recent run as Running, Succeeded or Failed, with the reason for a failure.
Count the failed runs, because every one of them is a job someone on your team still had to do by hand.
If the failure rate is high, fix the skill before you add another routine.
Brief the Bot like you'd brief a new hire
You create a routine by asking the Bot in plain words, so the quality of the brief decides the quality of the work.
The docs list six points to confirm: which Bot owns the job, the schedule and time zone, where the inputs come from, what a good result looks like, where approval is needed, and what to do if a source is missing.
Leave one out and the Bot has to guess.
Since v0.70.2, the Bot reads back a summary of what the routine does and who gets the result after you save it.
Read that summary as carefully as you'd read a new hire's notes from their first day.
On the phone you can also open the Bot's profile, tap Add routine under Routines, and finish the sentence it starts for you.
The usage bill nobody mentions
The official routines docs are blunt about this.
Each run spends usage, and an hourly schedule, a short interval or a Slack trigger on a busy channel can use a week of usage in a day.
A routine that never runs spends nothing, but Test does spend, because it does the real work.
If your weekly usage limit drains early, pause the routines you don't need first.
Then ask the Bot to widen schedules and tighten Slack triggers before you move to a bigger plan.
| Routine design | Runs it creates | Usage risk |
|---|---|---|
| Once every weekday morning | About 5 a week | Low |
| Email routine on one alias | One per matching email | Depends on volume |
| Every 2 hours, all day | 12 a day | Medium |
| Any message in a busy Slack channel | One per message | High |
Risks to settle before you switch one on
Write the approval line into the request: nothing sent, bought, deleted or published without you.
The approvals docs give background approval cards a 30-minute window before they lapse, so keep your phone close during the hours a routine runs.
Decide what the Bot does when a source is missing, so it reports the gap instead of using stale data.
Remember the caps: up to 50 routines per Bot, scheduled runs at least five minutes apart, and the 20 most recent run records kept per routine.
All your routines together can run 300 times an hour, and one routine up to 200, since v0.75.5 on 23 October 2026.
A run past those caps fails and isn't retried for you.
📞 Want a plan for which jobs to automate first? Book a free SEO strategy session and my team will look at your leads, your inbox and your busiest repeat tasks with you. → Book the free call
Rules for staff sharing one Bot
On a team, you decide who can create routines.
Since v0.75.2, the changelog says shared Bot owners and managers can let collaborators create routines from Configure.
From v0.61.0, staff can also manage their own routines by messaging the shared Bot in Slack.
Agree three house rules: one owner per routine, a clear name, and an approval step on anything customer-facing.
Review active routines on a fixed day each week, as the approvals docs recommend.
When a routine is the wrong tool
Skip routines for one-off jobs, because a normal chat does it faster.
Skip them for jobs where the inputs change shape every time.
Skip them for anything that needs a decision call from you halfway through.
The docs also say to re-test after a website, app or source format changes, so a job built on a messy, shifting source costs more upkeep than it saves.
And skip routines for anything you couldn't explain to a temp in two minutes.
If you can't write the rule down, the Bot can't follow it at 6:00 AM while you're asleep.
Deleting a routine can't be undone, so pause a doubtful one first and delete it only once you're sure.
A one-week rollout for a small business
- Monday: list five repeat tasks and time one run of each.
- Tuesday: run the heaviest one by hand in a Grok Bot chat until the output is right.
- Wednesday: save it as a skill with an approval rule written in.
- Thursday: create the routine, check When to run and press Test with safe inputs.
- Friday: switch it on and check the first real run in the Bot's chat.
If you want the trainings and the Agent OS behind a rollout like this, the AI Profit Boardroom has both.
Also On Our Network
- 🌐 The six-step setup order from first manual run to tested routine
- 🌐 An eight-criterion scorecard that rates routines 8 out of 10
- 🌐 Five Agent OS prompts that plan, count and review every routine
- 🌐 Which benchmarked models to pair with routines, scores quoted from the bench
- 🌐 The complete Grok Bot Routines guide on the AI Profit Boardroom blog
FAQ: Are Grok Bot Routines Worth It For A Small Business? Use Cases, Plans And Risks
Which plan do I need for Grok Bot routines?
Grok Bot is included on the Premium, Super and Ultra plans under The X Subscription. The Plus plan does not include Grok Bot.
Can a routine email my customers without me?
No. Email written by a routine waits as a draft until you press Send, and the docs say there is no option for unattended sending.
Will routines keep working when my computer is off?
Yes. Routines run on the Bot's cloud computer, so closing the app, laptop or phone does not stop them.
Why did my weekly usage run out early?
Every routine run spends usage, and busy triggers or short intervals add up fast. Pause routines you don't need, then widen schedules and narrow Slack triggers.
Can my staff create routines on a shared Bot?
Yes, if you allow it. Owners and managers can let collaborators create routines from Configure, a change that arrived in v0.75.2.
📺 Video notes + links to the tools 👉
🎥 Learn how I make these videos 👉
🆓 Get a FREE AI Course + Community + 1,000 AI Agents 👉
About Julian
I'm Julian Goldie, an SEO entrepreneur, author and founder of the AI Profit Boardroom, which has 3,400+ members.
I help business owners scale with AI agents, automation and SEO.
- I've built a 7-figure SEO and link building agency, Goldie Agency, with a team of 70+ SEO experts.
- I've grown a YouTube channel to 400,000+ subscribers.
- I wrote "Link Building Mastery".
- My Udemy courses have taught over 29,000 students.
→ Get my best AI training inside the AI Profit Boardroom
Start with one prep job, keep every send behind your yes, and watch the usage, and Grok Bot routines will earn their place in your business; if you want help choosing that first job, book a free SEO strategy session with my team.
