How to Use Grok Bot as a Business Owner

What is Grok Bot, in plain words?

Grok Bot (people also write Grokbot) is xAI’s always-on AI teammate, and it works on its own cloud computer. That computer has a browser, files and a terminal. A Bot signs in to your tools and does the work there. It keeps going when you close your laptop.

Each Bot has a name, a job and a memory. You message it in the desktop or phone app, in X Chat or in Slack. xAI launched it on August 11, 2026. We use it in client builds, so the rules below come from real work.

What does Grok Bot cost, and how do you get it?

Grok Bot comes with the top three plans of The X Subscription, and its usage draws from a weekly pool shared with Grok and Cursor.

Plan	Price	Grok Bot	As of
Free	$0	Not included	November 6, 2026
Plus	$8 a month	Not included	November 6, 2026
Premium	$30 a month or $300 a year	Included	November 6, 2026
Super	$100 a month or $1,000 a year	Included, larger pool	November 6, 2026
Ultra	$200 a month or $2,000 a year	Included, larger pool	November 6, 2026
Team seats	$30, $100 or $200 a seat	Included, and you can mix tiers	November 6, 2026
Older Cursor, SuperGrok and X Premium+ plans	Not listed on the pricing page	Included on most paid plans. See the Cursor matrix in sources	November 6, 2026
Enterprise	Not published	An admin turns it on	November 6, 2026

Press and older xAI posts name other plans. The current docs above replace them. xAI publishes no country list for Grok Bot as of November 6, 2026.

What are the five best jobs to give Grok Bot first?

Start with aging receivables and work down to vendor bills, ranked by money first and hours second. Every prompt stops at a review list.

1. Aging receivables. This is cash you already earned.

Read my open invoices from the accounting data I connected. Group them by customer into 1-30, 31-60, 61-90 and 90+ days past due. Show which accounts moved into an older bucket this week. For the ten largest balances, show the amount, oldest invoice, last payment and my last email to them. Draft one follow-up for each. Do not send anything or change any record. Give a source for every number.

2. Quiet customers. A customer who stops ordering does not call to tell you.

Compare each customer's orders in the last 90 days with their prior 90 days. List the customers who slowed down or stopped. Rank them by dollars lost. For each one, show the last order date, usual order size and my last contact. Suggest one next step. Do not contact anyone or edit any record.

3. Quote follow-up. An open quote goes cold while everyone is busy.

Find every quote we sent in the last 30 days with no order and no reply in the last 7 days. Rank them by dollar value. Show the customer, amount, date sent and last message for each. Draft a short follow-up in my voice. Do not send anything.

4. The morning brief. This is the job that gets you off the five-person chase. Run it by hand first, then ask for it as a routine.

Every weekday at 7:00 AM, review what changed since 6:00 PM yesterday in my connected email, calendar and sales data. Return only what needs me today: late orders, large payments, big quotes and complaints. Give a source link and the decision I owe for each item. If a source is down, say so and do not use old data. Do not send messages or change anything.

5. Vendor bill checks. A Bot can use a browser, so it can work in a vendor portal with no connector.

Read this week's vendor bills from my bills inbox. Match each one to its purchase order and the last price we paid. Flag any new fee, price increase, duplicate or bill with no purchase order. Show the dollar difference and the source for each flag. Do not pay, approve or change anything.

An agent sees only what it can reach. Point Grok Bot at 40 scattered tabs and it gives the wrong answer faster. Data first, then AI. That is why the Business Brain comes before the Bot, and this guide shows how the wrong answers happen.

How do you set up Grok Bot in 20 minutes?

You set it up in seven steps, and the only hard one is choosing what it connects to.

1. Check your plan. You need Premium or higher, or an older plan from the Cursor matrix.
2. Download the desktop app from x.ai/bot and sign in. Add the phone app so you can answer approvals.
3. Give your first Bot one job in its first message: “You own receivables.”
4. Connect one source. Use a read-only layer you control, never your production database. Your business rules live in your own system, and a raw database login goes around them.
5. Run prompt one by hand. Correct the result until you can review it without redoing it.
6. Ask the Bot to save the process as a skill. Test the skill on a second input.
7. Ask for a routine. Confirm the schedule and the source. Confirm the approval point and what happens when a source is missing.

For your own data, the Bot adds a custom connector by URL. We run ours on a public HTTPS address. xAI’s docs also allow a server on a private network, and that asks for your approval first.

What rules do you set before Grok Bot touches the business?

The order that works is Read, then Propose, then Act. Stay on Read until the numbers hold up. xAI’s docs show no read-only switch, so read-only means read-only access plus clear limits in every request. Add narrow Ask first rules on top.

• It may do alone: read and compare, then flag and draft.
• It must ask first: post to a shared channel, save a file others use or update a note.
• It may never do: move money or email a customer. It also may never change a price or delete records.

Paste this into your first chat:

Standing rules. Remember these. You may read, compare and draft. Ask me before you post, save or update anything. Never move money, email a customer, change a price or delete a record. If a number has no source, say so and stop.

Three more rules from our client builds:

1. Keep real write approvals in your own system. Approval cards from routines or other Bots expire in about 30 minutes, and the action then does not run. So the Bot writes a proposal to a table. A person approves it there. Your system makes the change and logs who said yes.
2. Never type a secret into chat. Use Vault, the masked secret card or a connector’s own sign-in.
3. Put standing rules in a skill and a file. A Team Bot description held 140 characters in our builds. xAI publishes no limit, so check yours. Personal Bots no longer have a description. Tell them in chat and ask them to remember.

Where does Grok Bot break?

Grok Bot breaks at shared logins, expired approvals and sites that block cloud computers.

1. All your Bots share one computer, its files and its logins. Separate Bots do not protect you from each other.
2. A routine belongs to the person who sets it up. A morning brief runs on one person’s own Bot, so each person who wants one sets up their own.
3. Some sites block cloud computers. Single sign-on, passkeys and CAPTCHAs hand the step back to you.
4. You cannot pick the model. It may be a third-party model from the sub-processor list.
5. A stop ends the work and leaves finished actions in place.
6. Some routine runs fail on a shared limit and do not retry. Check the run history for the first two weeks.

Should you use Grok Bot?

Use it if you have one person who will own the setup and a data layer it can read. Skip it for now if your numbers live in tabs nobody trusts, and compare it with ChatGPT dots and the others in our side-by-side.