ثلاث بوتات في Grok Bot يشتغلون مع بعضThree Grok Bots That Work Together

Key terms

Grok Bot

A product from x.ai. According to its official page, a team of always on agents. Each Bot has its own computer and signs into the tools you already use.

Bot

One AI teammate inside Grok Bot. You message it like a colleague and hand it work. It finishes the job and comes back when it needs your approval.

Group chat

A chat where you put more than one Bot. Per the official page, the Bots in it coordinate on their own: they pass work, assign ownership and only pull you in for judgment calls.

Routine

The steps of one job, saved by a Bot after it watches you do it once. Next time it runs the job itself and takes your corrections.

The steps

1. 1

   Step 1

   Understand what a Bot is

   According to the official page at x.ai, Grok Bot is a team of always on agents. Each Bot has its own computer in the cloud, so jobs do not stall when you step away. It signs into the tools you already use and works across apps, inboxes and websites, including ones with no clean API.

   It finishes the job end to end and only comes back when something needs your approval. You message it like a colleague from your phone or desktop and pick up the same thread on either.

   You can run several Bots at once. They message each other and work together in a group chat.

   This guide builds three: Zero, Mark and Sally. Those are names we pick, not names from the product.

   x.ai

   

   Tip: The announcement is dated 11 August 2026 and the product is in beta, so details can change.

2. 2

   Step 2

   Check your plan and download the app

   According to the official page, Grok Bot is in beta and available today with SuperGrok, SuperGrok Plus and SuperGrok Heavy, with Cursor Pro, Pro+ and Ultra, and with Cursor Teams Standard and Premium. It runs on desktop and iOS, and the download button on the page is for macOS.

   Bots come with their own usage, separate from your Grok and Cursor plans. Anything you hand to a Bot does not count against your existing usage.

   Enterprise users can join a waitlist for later access.

   Plans and availability change, so check the official page and your account when you read this. Then download the app and create your first Bot.

   Tip: If your plan is not on the list, confirm access before you follow the next steps.

3. 3

   Step 3

   Build Bot 1, Zero: sorts your email

   Create a new Bot, name it Zero, and ask it to sign into your Gmail. The official page shows an example of a Bot processing invoices that arrive in Gmail, so this is the kind of work it was made for.

   Zero has three jobs: draft replies, sort messages into folders, and clear spam. Make it save replies as drafts only, and you send, until you trust it.

   PromptSet up Zero

   Copy

   Your name is Zero. You manage my Gmail inbox.
   
   Sign into my account [your email]. Your jobs:
   1. Write a draft reply to every message that needs an answer, in my voice: [describe your voice in one line].
   2. Sort messages into folders (labels): [clients, invoices, new leads, other].
   3. Clear spam and promotions.
   
   Rules:
   - Never send a message yourself. Save every reply as a draft.
   - Delete nothing except obvious spam.
   - If you are not sure about a message, leave it in the inbox and flag it to me.
   
   When you finish a batch, send me a summary: how many drafts are ready and which messages need a decision from me.

   Tip: Start with the inbox only. Add new folders after you review the first batch.

4. 4

   Step 4

   Build Bot 2, Mark: researches a brand's campaigns

   Mark does research. You give him a brand name, he goes through the brand's site and pages and returns a one page summary of its latest campaigns and ads. The official page says Bots work across apps, tools and websites, even when there is no clean API.

   The key rule for Mark: every claim carries a source link. If he finds nothing, he says so and does not guess.

   PromptSet up Mark

   Copy

   Your name is Mark. You do brand research for me.
   
   When I give you a brand: [brand name], find its latest campaigns and ads on [its website, its social accounts and anywhere else I name]. Write me a one page summary with:
   1. The latest campaigns and their dates.
   2. The message and the offer in each one.
   3. The channels it ran on.
   4. What we can learn from it.
   
   Rules:
   - Put the source link next to every claim.
   - If you find nothing, tell me. Do not guess.
   - Do not contact anyone at the brand.

5. 5

   Step 5

   Build Bot 3, Sally: preps your sales calls

   Sally prepares notes before each sales call and gives you feedback after it. The official page shows a sales Bot updating the CRM with call transcript notes and drafting follow ups.

   Tell her where to find customer details and call notes. Keep her to follow up drafts only, and you send.

   PromptSet up Sally

   Copy

   Your name is Sally. You prepare my sales calls.
   
   Before each call with [customer or company name]: read what we have on them in [CRM, doc or folder] and prepare notes for me: who they are, what they asked for, the last contact, three questions to ask, and one likely objection with a reply.
   
   After the call: read [call notes or recording] and give me honest feedback: what worked, what I missed, and what to do in the follow up. Write the follow up message as a draft. Do not send it.

6. 6

   Step 6

   Put the three in one group chat with a hand off rule

   Create a group chat, name it [new leads room], and add Zero, Mark and Sally. Per the official page, Bots in a group chat pass work to each other, assign ownership and only pull you in for judgment calls.

   Write the hand off rule once: new lead, then Zero posts, then Mark researches, then he sends it to the sales team, then Sally preps.

   PromptHand off rule

   Copy

   This is the new leads room. Zero, Mark, Sally and I are in it.
   
   Hand off rule:
   1. When a new lead arrives by email, Zero posts here: the lead's name, company and what they asked for.
   2. Mark researches the lead's company and writes a one page summary.
   3. Mark sends the summary to the sales team: [names or emails of the sales team].
   4. Sally prepares the call notes from the summary.
   
   When you finish your step, write done and say who is next. If a step stalls, tell me why here. Pass nothing outside this chat before I approve.

   Tip: Test the rule on a fake lead before the first real one.

7. 7

   Step 7

   Set what needs your approval

   A Bot comes back to you when it needs approval, but you decide when that is. Write the list clearly for every Bot.

   The simple rule: anything that leaves the team, costs money or cannot be undone needs your approval. Reading, researching and writing drafts do not.

   PromptApproval rules

   Copy

   Approval rules for every Bot on this team:
   
   Ask me before any of these:
   1. Sending an email or message to anyone outside the team.
   2. Paying anything, buying anything or starting a subscription, however small.
   3. Deleting anything.
   4. Editing a customer record in the CRM.
   5. Sharing a file or customer detail with a third party.
   
   You do not need approval for: reading, researching, writing drafts and organizing files.
   
   When you ask me, tell me what you will do, why, and what happens if I say no.

   Tip: Start strict and loosen the rules as your trust grows. The official page says Bots take on more over time.

8. 8

   Step 8

   Teach a routine once and save it

   The best way to teach a Bot your workflow is to ask it to follow along the next time you do the job. Per the official page, it watches the steps, remembers how you like the work done, saves it as a routine, takes your corrections and runs it on its own next time.

   Pick a job you repeat every week, like the new lead report, and do it once while the Bot watches.

   PromptTeach a routine

   Copy

   The next time I do [the job], follow along step by step.
   
   Afterwards:
   1. Write down the steps you understood and I will correct them.
   2. Save it as a routine named [routine name].
   3. Next time, run it yourself and show me the result before anything is sent.
   
   Apply the approval rules I gave you.