agentos.guide › blog
Grok Bot For Sales: Five Copy-Paste Prompts For Outbound, Follow-Ups, Renewals And A Pipeline Page In Your Agent OS
Grok Bot for sales slots neatly into an Agent OS: your agent writes the briefs, rules and prompts, and Grok Bot does the research and drafting on its cloud computer, then waits for you.
Below are five copy-paste prompts and a weekly rhythm built around the two sales roles xAI documents.
Everything maps to the official Grok Bot use cases page, the skills and routines docs and the Grok Bot changelog.
Fancy a hand mapping it to your own pipeline? Book a free SEO strategy session with my team.
Quick start: five checks before the first prospect list
- Confirm access: Premium, Super and Ultra include Grok Bot under The X Subscription, and Plus does not, per the plan page.
- Connect your CRM app from Connect apps, or note that it has no app and the Bot will use its browser.
- Connect Gmail and Google Calendar for drafts and free-slot checks.
- Ask the Bot to claim its own mail.grokbot.com address, and choose the name with care: it is permanent.
- Add an Ask first rule before any external email.
Who plans, who works: your Agent OS and Grok Bot
Think of it as two jobs that should never blur.
Your Agent OS is the planner: it knows your offer, your ideal customer and your tone, so it writes the instructions.
Grok Bot is the worker: all your Bots share one cloud computer, each with its own screen, and they carry on with your laptop shut.
Grok Bot is also where approval cards appear, so nothing your Agent OS drafts reaches a prospect without your click.
On the CRM side, Zoho CRM sits in the connector list on the security page and a Salesforce plugin appears in the changelog; the docs do not mention HubSpot.
Prompt 1: write the outbound Bot's brief
The docs say a durable Bot starts with a description holding the job, the sources, the output format and the standing limits.
Give your Agent OS this:
Write a Grok Bot description for a "Sales outbound" role for my business.
Include: the job (research and score accounts from one CRM view, find up to three contacts each, draft first-touch email and a LinkedIn note), the source systems, the output (one review list, one row per account with score, reason, contacts and drafts), and the boundaries: never send, never enrol anyone, skip active sequences, ask before any external email.
Use my ideal customer notes below. Keep it under 200 words.Paste the result into the Bot's description, then move on.
Read it once before you save it: if a boundary is vague, the Bot will treat it as vague too.
Prompt 2: the first scored review list
xAI's sample task scores 25 accounts against the ideal customer profile and recent intent; start with ten so you can check every row.
Paste this straight into Grok Bot:
Research the 10 accounts in the CRM view "New this week". Score each one against the ideal customer profile in your description and any recent intent you can find on their site or in public X posts. Find up to three contacts per account. Draft one email and one LinkedIn note per contact in the style of the attached examples. Skip anyone already in an active sequence. Return a review list and stop; do not send or enrol anyone.Correct the scores in plain words, then ask the Bot to save the process as a skill and test it on a second view.
🔥 Want these prompts tuned to your offer on a live call?
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 building agent workflows.
Prompt 3: the Account health watch list
The second documented role ranks the customers you already have, using usage, support escalations, renewal timing and stakeholder activity.
It may not contact customers or edit the CRM.
The docs advise putting risk thresholds in the description so each week is judged the same way, so get your Agent OS to write them:
Write risk thresholds for an Account health Grok Bot. Define "at risk", "watch" and "expansion" using: renewal within 60 days, open support escalations, falling usage, and no stakeholder contact in 30 days. Output a short block I can paste into the Bot description, ending with: "Do not contact customers or edit the CRM."Prompt 4: a follow-up routine that leaves drafts
Routines run on a schedule or on an event, such as an email to the Bot's address or a webhook call, as the routines page explains.
Email a routine writes waits as a draft until you press Send, and the docs say there is no unattended option.
First-contact emails also carry a one-click unsubscribe link, and the Bot stops emailing addresses that bounced or unsubscribed.
Every weekday at 8:00 AM, run the proposal follow-up skill against the "Open proposals" sheet. For each proposal with no reply in 5 working days, read the Gmail thread and draft a short follow-up with two free slots from my calendar. Leave every email as a draft. If the sheet is unavailable, report the failure instead of using old data. Post a summary in this chat.Press Test once to see a run now, because a new routine otherwise waits for its first scheduled slot.
Prompt 5: the weekly pipeline page
In the files and results docs, a Page is a readable report or dashboard holding tables, charts and controls, and routines can refresh it.
The feature is reaching accounts gradually, Enterprise teams do not have it yet, and you need desktop 0.60.0 or phone 1.14.0 or later to see it.
Every Monday at 7:30 AM, build or update a page called "Pipeline this week": one table of open deals by stage, owner, last contact and next step, a chart of deals per stage, and a filter by owner. Pull from the CRM view "Open deals". Do not edit the CRM.Bonus: wire inbound leads in with a webhook
Inbound enquiries can start work too.
Ask the Bot to add a webhook trigger to a routine, then open it on desktop to copy the POST URL and the key.
Your form tool sends each submission with the header Authorization: Bearer and the key, plus the form fields as JSON.
A 200 reply only means a run has started; the result lands in the Bot's chat.
Any other reply means nothing ran, so check the routine is not paused and the key is current.
Add a webhook trigger to a new routine called "Inbound lead". When it fires, read the JSON body, look the company up on the web, score it against the ideal customer profile in your description, add a row to the "Leads" sheet, and draft a reply from the enquiries alias. Leave the reply as a draft and post a one-line summary here.Before you trust it, ask your Agent OS to list the failure cases: an empty body, a duplicate lead, a company it cannot find.
The docs say to define retries and failures before a routine goes live, and this is where that pays off.
A recruitment agency, start to finish
- The agency's Agent OS writes the outbound brief (Prompt 1) around firms that hire often.
- The owner connects the CRM and Gmail, and claims the Bot's address with an outbound alias.
- Grok Bot researches each firm, scores it and drafts outreach to hiring managers, skipping anyone already in a sequence.
- The owner reviews the list in the morning and sends the approved drafts.
- The skill becomes a nightly routine that still stops at the list.
A B2B sales trainer and a pest control firm
The sales trainer runs Prompt 3 on past clients to spot who is due a refresher course, then picks who to call.
The pest control firm wires its booking form to a webhook routine; each enquiry gets logged and a reply drafted from the Bot's enquiries alias, ready for the office to send.
In both, the review point is where a person decides.
If either business wants a second view of its sales funnel and search presence, a free strategy call with my team is the quickest route.
Team Bots in Slack: who answers the cards
Share the Bot with your Cursor team and bring it into Slack from its details page, as the shared Bots docs describe.
Every teammate's chat stays private, even from the owner, and each reply uses that teammate's own usage.
In a thread, only the person who asked can answer a Review an action card.
The changelog adds that Team Bots reply in threads and that routines can be set up from Slack.
📞 Want your sales prompts reviewed by my team?
Book a free SEO strategy session and we will go through your pipeline, your prompts and how prospects find you in search.
The weekly workflow
Run this rhythm for a month before adding anything new.
Monday: open the pipeline page and the Account health list.
Each morning: approve or bin the outbound review list and press Send on the follow-up drafts you like.
Friday: ask your Agent OS to tighten the brief and the thresholds from what you corrected that week.
Once a month: review installed apps and active routines, and pause any routine whose source sheet or CRM view has changed, as the approvals docs advise.
For the wider guardrails, see our Grok Bot for business guide, and for the coaching, the AI Profit Boardroom has the walkthroughs.
Also On Our Network
- 🌐 The eight-step build for an outbound Bot that stops at a review list
- 🌐 Whether an owner should use it, with three small-business sales use cases
- 🌐 The eight-criterion sales scorecard and a 7.5/10 verdict
- 🌐 Which AI models to pair with a sales Bot, with live Pages scores
- 🌐 The complete Grok Bot for sales guide on the AI Profit Boardroom blog
FAQ
Which prompt should I run first?
Prompt 1, so the Bot has a description with the job, sources, output and boundaries. Then run Prompt 2 on ten accounts and correct it.
Can my Agent OS send the outreach itself?
Keep sending in Grok Bot behind approval. Routine email from the Bot waits as a draft until you press Send, which keeps one place for every decision.
Does the pipeline page need a special version?
Yes. Pages needs Grok Bot 0.60.0 or later on desktop and 1.14.0 or later on the phone, and it is not on Enterprise teams yet.
Can teammates use the same sales Bot?
On a Cursor team, share it and add it to Slack. Each teammate's chat is private and only the person who asked can answer an approval card.
Final word on Grok Bot For Sales
Paste the five prompts, keep every send on review, and join the AI Profit Boardroom to run Grok Bot for sales in your Agent OS.
About Julian
I'm Julian Goldie, an AI entrepreneur, SEO expert and the founder of the AI Profit Boardroom, which has 3,400+ members.
I help business owners scale with AI agents, automation and SEO.
My YouTube channel has 400,000+ subscribers, and I run Goldie Agency, a seven-figure SEO agency.
Related guides on agentos.guide
→ Grok Bot For Marketing: Run A Campaign Desk In Your Agent OS
→ Grok Bot Ideas: Five Copy-Paste Builds Your Agent OS Can Brief, From Role Finder To Webhook
Get the whole Agent OS
The installable system behind every guide on this site — dashboard, agents, memory and pipelines — updated as new tools land, with 3,400+ members and four coaching calls a week.
Join the AI Profit Boardroom →📺 Video notes + links to the tools 👉
🎥 Learn how I make these videos 👉