Grok Bot as a personal assistant for a small-business owner: what it does and how to start

Grok Bot isn’t a chat where you ask and wait for an answer. It gets a task, works in a browser and in your tools, and brings the result back for review. Below we summarise what the official documentation says and how to use it in a small business. Our own trial on a Google business profile is described in a separate article.

What it is

According to the documentation, Bot works from a persistent cloud computer with a browser, command line and filesystem, and keeps going with your laptop closed. Several bots on one account share one computer, each with its own screen. The FAQ describes it as a tool that uses a computer, tools, websites and files to finish work. You can also claim an email address at mail.grokbot.com, which Bot can read and send from, with limits.

How you talk to it

• Apps. A desktop app for macOS, Windows and Linux, and a companion app for iOS 18 or later and Android 9 or later (Get started).
• X Chat. You can chat with Bot there too, if you have a plan that includes Grok Bot.
• Voice. Voice chat and dictation are in the apps (chat and collaboration).
• Telegram and WhatsApp aren’t listed as channels for talking to Bot in the documentation we read.

What would help a small-business owner

The documentation lists example roles, such as expense manager, account health or “chief of staff” (use cases). The list of small-business tasks below is our own selection, not a list from the documentation:

• A morning summary: email, calendar and what is waiting for a reply.
• Draft replies to enquiries and reviews, based on your price list and style.
• Reminders: unanswered messages, overdue invoices, deadlines.
• Content preparation: draft posts and translation between Czech, Ukrainian, Russian and English.
• Collecting data from websites: suppliers’ and competitors’ prices, checking your own details on Firmy.cz and the maps.

This is work that repeats, has a clear output and can be checked. For anything that goes out to customers, expect a person to review it: Grok Bot’s terms require that for outward communication.

How to start: one role

1. One primary job. Give it in the first message and ask Bot to remember how it should work. The documentation recommends a focused Bot over a catch-all helper.
2. Reading and preparing first. The use cases advise starting with read-and-prepare work, reviewing the result, and only then adding approved actions or a routine.
3. Save the process as a skill once it works.
4. Only then a regular run, as a routine.

Skills and routines

A skill is a reusable set of instructions: you ask Bot to save the process you just used under a name. A routine tells one Bot when to run a process: on a schedule, or when something happens, such as an incoming email.

• One Bot can own up to 50 routines, and schedules must be at least five minutes apart.
• Times follow the time zone in the Bot’s settings, so check that it is set to Prague time.
• A new routine doesn’t run at once; it waits for its next scheduled time. The Test button does real work and uses up your limit.
• In our trial, a task scheduled for 18:10 started at 18:19, so we don’t promise exact times.

Access and passwords

• Apps connect through “Connect apps” by signing in at the provider. OAuth tokens are held on the connector backend and Bot doesn’t receive them (documentation).
• Passwords, cards and keys belong in Vault or a secure form; Bot doesn’t see the values. Vault isn’t supported on shared Bots.
• Single sign-on, passkeys and CAPTCHA: at such a step Bot hands control to you.
• A ready-made connection may not exist. In our trial Bot found none in its catalogue for a Google profile or Firmy.cz.

Approvals and their limits

According to the documentation, Auto Review is on by default. Most actions run on their own; for others a card appears with the options Allow once, Always allow and Deny. You can set up to 20 “allow automatically” rules and up to 20 “ask first” rules (Ask first), and Ask first wins when they conflict.

But the documentation clarifies that the review is model-based, doesn’t check every side effect, and should complement, not replace, limits on access. A background approval expires after 30 minutes. So don’t give Bot access it doesn’t need. In our trial Bot stopped before the Publish button only because of our instruction, not because of a confirmation card.

Data and privacy

• Location. The computers run in the United States. Regional data residency is, per the documentation, an optional Enterprise programme.
• Retention. Hibernation is not deletion. When an account is deleted, data is removed within 30 days.
• Training. It follows your account and privacy settings. With Privacy Mode on, customer data isn’t used for training.
• A shared computer. All bots on an account share the computer, files and sign-ins. A separate Bot is not a security boundary.

It follows that we wouldn’t put customers’ personal data into Bot at first, and using it needs a separate assessment, preferably with a lawyer.

Limits and what we don’t know

• Websites. Some websites block cloud computers or require a CAPTCHA. Bot is supposed to hand such a step to you.
• Model. You can’t choose it.
• Limit. The documentation doesn’t give the size of the weekly limit. With on-demand usage off, Bot stops when the limit runs out and resumes when it resets.
• Plans. Grok Bot is included in the X Premium, Super and Ultra plans; Plus and Free don’t include it. Current prices are on the pricing page.
• Countries. The documentation we read doesn’t mention availability in the EU or age limits. Check them when you create the account.

Who it suits and who it doesn’t

• It suits you if you have repeating work with a clear output and you actually read the drafts.
• It doesn’t suit as a chat for customers: the terms permit use for a business’s internal purposes.
• It doesn’t suit sensitive data, such as health data or data about children.
• It doesn’t suit automatic publishing without review.

What we don’t promise: time or money saved in advance. The product changes quickly, which is why claims here link to the documentation, and we advise rereading it before you start. As of 6 Nov 2026.