Grok Bot For Sales: Build An Outbound Bot In 8 Steps (2026)

Grok Bot for sales works when you build one narrow role first, and the official docs already hand you the template: a "Sales outbound" Bot that researches, scores and drafts, then stops.

This is the build order I would follow, from plan check to a team Bot answering reps in Slack.

I took every setting below from three official places: the Grok Bot changelog, the use cases page and the email section of the apps documentation.

Want a second pair of eyes on your pipeline setup? Book a free SEO strategy session with my team.

Step 1: check the plan, then pick one sales job

Grok Bot sits on Premium, Super and Ultra under The X Subscription, and the Plus plan leaves it out, per the plan page.

Once you have access, resist the urge to build "a sales assistant".

The use cases page says strong roles own one repeatable outcome, not a loose pile of questions.

For outbound, that outcome is a reviewed list of prospects with drafts attached.

For existing customers, it is a ranked watch list of accounts that need a call.

Build the outbound Bot first, and add the second one only when the first runs clean.

Step 2: write the outbound Bot's description like a job spec

The docs list six steps for turning a role into a durable Bot, and step one is the description.

Put four things in it: the job, the source systems, the output format and the standing boundaries.

Here is the shape I use:

Job: research accounts from the CRM view I name, score each one against our ideal customer profile, and draft first-touch outreach.
Sources: the CRM app, the website of each account, public X posts, my style examples.
Output: one review list, one row per account: score, reason, up to three contacts, draft email, draft LinkedIn note.
Boundaries: never send, never enroll anyone in a sequence, skip anyone already in an active sequence, ask before any external email.

That last line matters most.

The docs' own starter prompt ends by telling the Bot to return a review list and send nobody.

Keep that sentence in the description so every later task inherits it.

Step 3: connect the CRM, the inbox and the calendar

Open Connect apps from the sidebar, search for the app, add it and finish the provider sign-in.

You can also type a request such as "Add the Zoho CRM app" and the Bot installs it, then shows a Connect card for the login.

For CRMs, the security page lists Zoho CRM among the connector hosts, and a changelog entry from 23 October mentions a Salesforce plugin whose servers each get their own row.

I found no HubSpot connector in the Grok Bot docs.

If your CRM has no app, the docs point you to the browser for services without one, or you can have the Bot add an MCP server by URL if your vendor publishes one.

Then connect Gmail for your own mailbox: it can search, read, draft, send and label, one mailbox at a time.

Google Calendar can check free time and create events, which covers booking follow-up calls.

Apps are account-wide, so every Bot you run can use them; connect only what the sales job needs.

🔥 Want the outbound Bot built with you, live? Inside the AI Profit Boardroom you get step-by-step video trainings, the installable Agent OS, four coaching calls a week and 3,400+ members wiring up agents like this one. → Join the AI Profit Boardroom

Step 4: run the docs' starter task on a small CRM view

Your first run should be real but small.

The documented prompt asks for 25 accounts from a CRM view, scored against your ideal customer profile and recent intent, with up to three contacts per account and drafts for email and LinkedIn.

I would start with ten, so you can read every row properly.

Attach two or three emails you actually sent as style examples.

Tell it to skip anyone already in an active sequence.

When the list comes back, correct the scoring in plain words: which signals counted too much, which accounts it should have dropped.

Repeat until you would approve the list without rewriting it, which is step three in the docs.

Step 5: claim the Bot's own address and set an Ask first rule

Ask the Bot to "get yourself an email address" and approve the card; it claims one name at mail.grokbot.com.

Pick the name carefully, because you get one address and it can never be renamed or deleted.

Use plus aliases to separate jobs, such as name+outbound and name+quotes, since a routine watching an alias runs only for mail sent to that alias.

Next, open your Custom Rules and add the docs' suggested rule: ask first before sending any external email, from the approvals page.

Now the sending logic is simple.

An email you request in chat is checked by Auto Review first, and if it needs you, a card appears before anything leaves.

An email written by a routine, or by any turn you did not start with that request, waits as a draft until you press Send.

The email docs add that there is no option for unattended sending.

One gotcha: a changelog entry from 14 October mentions a "Disable drafts" switch, which reads differently from the current docs, so I treat every routine email as a draft and plan around that.

The mailing rules the Bot enforces without being asked

Outbound hygiene is partly built in.

First-contact emails and newsletters go to one recipient per message and carry a one-click unsubscribe link.

The changelog shows that rule widening: first emails to someone new got the link on 22 October, and every such email from 26 October.

If a message bounces, or the person unsubscribes or marks it as spam, the Bot stops emailing that address and tells you who it skipped.

There is also a cap on how many new people a Bot can email, which protects the address from being flagged.

And a Bot treats text inside an email or web page as information, never as your permission to act.

Step 6: save the skill, then prove it on a second list

Once a run is clean, ask the Bot to save the process as a skill, per the skills and routines docs.

A good skill states when to use it, the inputs and access it needs, the order of work, how to check the result, what to return and what needs approval.

Then give it a different CRM view and see if it holds up without coaching.

If it drifts, fix the skill text, not the output.

Step 7: schedule nightly research and follow-up routines

Only now do you automate.

The use cases page says to schedule a nightly research routine that stops at the review list once the output is reliable.

Before saving any routine, confirm the owning Bot, the schedule and time zone, the input, the result, the approval boundary and what happens if a source is missing.

Write schedules in plain words, such as "every weekday at 7:00 AM", and check When to run on the saved routine.

A new routine waits for its first slot, so press Test to try it at once.

For follow-ups, a second routine can scan the CRM for deals with no reply since your last touch and write a draft for each one.

Because a routine wrote them, every one of those emails sits as a draft until you press Send.

If a source system changes, pause the routine; pause and resume arrived in the changelog in September.

Step 8: publish one team Bot into Slack

On a Cursor team, share the Bot so reps can use it; the shared Bots page explains the roles.

Collaborators can chat with it, and Managers can also change its instructions, skills, memory and apps.

Each person's chat stays private, even from the owner.

To put it in Slack, the owner opens the Bot's name, finds Bring to your team's Slack and chooses Connect; a Slack admin may need to approve it.

Each rep links their Slack account under Settings, General, Shared Bots.

In a thread, risky actions show a Review an action card, and only the person who asked can answer it.

The changelog calls these Team Bots and notes they reply in threads and can set up routines from Slack.

Add an Account health Bot for renewals

The second documented role watches customers you already have.

It combines product usage, support escalations, renewal timing and stakeholder activity into a ranked watch list, with evidence and a suggested next step per account.

Its boundary is strict: no customer contact and no CRM edits.

The docs add one tip worth copying: define the risk thresholds in the Bot's description so the weekly list stays consistent.

Turn the pipeline into a Page

The files and results docs describe Pages as reports, dashboards or trackers the Bot builds for you, complete with charts and controls.

Request a pipeline tracker with stage, owner and next step columns, and a filter by rep.

A routine can create or update the Page, so Monday's view refreshes itself.

Pages is still rolling out, needs desktop 0.60.0 or later and phone 1.14.0 or later, and is not on Enterprise teams yet.

📞 Want your sales setup checked by a person? Book a free SEO strategy session and my team will look at your pipeline, your outreach and your search visibility with you. → Book your free strategy session

Example: a web design agency's outbound list

The owner filters a CRM view of local firms whose sites they could rebuild.
The Bot visits each site in its browser, scores it against the agency's ideal customer notes, and finds up to three contacts.
It drafts a short email and a LinkedIn note per contact in the owner's style.
It returns the review list and stops.
The owner edits two drafts, rejects one account, and sends the rest from Gmail.

Example: a B2B consultant's proposal follow-ups

A fractional finance consultant keeps open proposals in a Google Sheet.
A weekday routine reads the sheet and the Gmail thread for each proposal.
Where the client has gone quiet, it writes a follow-up draft and a one-line reason.
It checks Calendar for free slots and puts two options in each draft.
The drafts wait; the consultant presses Send on the ones that fit.

Example: a local cleaning firm's quote chasers

The firm's website form posts each new quote request to a webhook routine with its Bearer key.
The Bot logs the request in the quotes sheet and drafts a reply from the quotes alias.
Three days later, a follow-up routine drafts a check-in for every quote with no reply.
Anyone who unsubscribed or bounced is skipped, and the Bot lists who it left out.
The office manager reviews the drafts each morning and sends them.

For the wider guardrail setup behind all three, read our Grok Bot for business setup guide.

And if you want the trainings and the coaching calls, the AI Profit Boardroom is where we build these.

Also On Our Network

FAQ: Grok Bot For Sales

Can a Grok Bot routine send sales emails on its own?

No. Per the docs, email a routine writes from the Bot's own address waits as a draft until you press Send, and the email docs say there's no option for unattended sending.

Which CRMs does Grok Bot connect to?

The security page lists Zoho CRM among connector hosts, and the changelog mentions a Salesforce plugin. The docs don't list HubSpot, so use the browser or an MCP server your vendor provides.

What does the Sales outbound starter prompt ask for?

Research accounts in a CRM view, score them against your ideal customer profile and intent, find up to three contacts each, draft email and LinkedIn outreach, skip active sequences, and return a review list without sending.

Do Bots keep emailing addresses that bounced?

No. If a message bounces, or the person unsubscribes or marks it as spam, the Bot stops emailing that address and tells you who it skipped.

How do I test a new follow-up routine without waiting?

Press Test on the routine. A new routine otherwise waits for its next scheduled time before its first run.

📺 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

Build the outbound role, prove it on two lists, then schedule it, and join the AI Profit Boardroom to set up your own Grok Bot for sales.