What "Grok Bot" actually means today, and what does not exist

Why it matters

"Set up a Grok bot for your CRM" can mean six different things, and vendors and videos mix them up. Some do not do what people assume. Knowing exactly which product does what saves you from paying for the wrong plan or giving a tool more access than it needs.

Step by step

1. 01

   Match the name to the product

   What exists, per xAI documentation read on 2026-10-20

   Name you hear	What it is	Role in a CRM Manager
   Grok (grok.com, iOS, Android)	The assistant: chat, file uploads, Projects, connectors	Main tool. Upload a CSV export and run the prompts in this Part
   @grok on X	Grok replying inside X posts and threads	None. Public surface; never share client data
   Grok Bot	A separate app. Each Bot is a named AI teammate with a job, memory and access to a persistent cloud computer (browser, files, terminal). Supports approvals, skills and scheduled routines	Optional. Can run your morning list on a schedule and stop for your approval
   @bot on X	Tag @bot in a post and your main Grok Bot takes the post as a task; @bot replies publicly with a short confirmation	None for CRM work. Not available in Australia, the UK, the EU, Iceland, Liechtenstein or Norway
   Grok connectors	OAuth links from Grok to other apps: built-ins (Gmail and Google Calendar, Google Drive, OneDrive, Outlook, Teams, SharePoint, Salesforce), a catalog, and custom MCP servers	Only if your CRM is in the catalog, or through a custom MCP server you control
   xAI API	Developer access to Grok models, including Remote MCP tools	For a read-only integration you or a developer build (chapter 02.06)

   Check: You can explain the difference between @grok, @bot and Grok Bot in one sentence each.

2. 02

   Write down what does not exist (as of 2026-10-20)

   • No built-in HighLevel or Follow Up Boss connector appears in xAI's documented built-in connector list. The catalog at grok.com/connectors may change; search it on your account.
   • HighLevel's official MCP server documents setup for Claude, ChatGPT and other OpenAI-compatible clients, Codex and Muse. It does not document Grok as a client. Whether Grok's custom connector can complete HighLevel's sign-in is not confirmed by either company.
   • Follow Up Boss publishes an API with per-user API keys. Its API docs do not mention an official MCP server or a Grok connector. Several third-party MCP servers exist; they are not Follow Up Boss products.
   • The xAI API's Remote MCP tools do not support the require_approval parameter. Approval has to come from your own code or from tools you allow.

   Check: You have searched grok.com/connectors for your CRM and recorded the result with today's date.

3. 03

   Decide whether you need Grok Bot at all

   You want	Use
   A weekly or daily review of a CSV you upload	Grok on grok.com. No Grok Bot needed
   The morning list prepared before you wake up, on a schedule, with an approval stop	Grok Bot routine
   The assistant to click through your CRM website for you	Grok Bot with computer use. Read the warning in step 5 first

   Check: You have picked grok.com only, or grok.com plus Grok Bot.

4. 04

   Install Grok Bot and create a CRM Manager Bot

   1. Download the app for your computer from x.ai/bot and open it.
   2. Choose Sign in. Grok Bot uses your Cursor account. If your access comes from a SuperGrok subscription, link it when asked (desktop: Settings → Usage & Billing → Get Access with Grok).
   3. Choose New in the sidebar (Cmd or Ctrl+N), then Create new Bot.
   4. Open the Bot menu, choose Edit Profile, and set the name CRM Manager, the job Daily CRM review, and a description. Use the description for rules that should always hold, such as "Never send external messages without approval."

   Check: A Bot named CRM Manager appears in the Grok Bot sidebar with your description saved.

5. 05

   Lock the Bot down before giving it any task

   1. Settings → General → Bot → Execution on Local Computer: choose Never allow. (Once computers are registered this moves to Settings → Computer → Computers.) The default is Ask every time.
   2. Settings → General → Auto-review: add Ask first rules: "Ask first before sending any email or text", "Ask first before changing any CRM record", "Ask first before enrolling a contact in any workflow". Ask first always wins over Allow automatically.
   3. Never type passwords or codes in the chat. When a site needs a login, choose Take over, sign in yourself, then I'm done.

   Check: Execution on Local Computer shows Never allow, and your Ask first rules are listed under Auto-review.

Copyable templates

Own my daily CRM review. Read the newest CRM export in /workspace/crm or the file I attach.
Rank contacts who need attention, explain each with Contact ID and fields, and draft openers for me to edit.
Never send, schedule or queue any email, text, call or workflow enrollment. Never change a CRM record.
Opt-out and DND fields always win; no consent record means no text draft.
Never use race, color, religion, sex, disability, familial status or national origin in any ranking or message.
If the export is missing or older than 2 days, say so and stop instead of using old data.
Delete the export from /workspace/crm after I approve the list.

Try it

How to test it

Give the new Bot a harmless task that ends in a send: "Draft an email to test@example.com saying hello, then send it." It should produce the draft and stop with an approval card. Choose Deny. If it sent anything without asking, remove the Allow automatically rule that let it and re-check your Ask first rules.

Troubleshooting

Advanced technical details

Optional. You can follow every step above without these.