agentos.guide › blog

Grok Bot For Lead Generation: Run A Prospect Engine In Your Agent OS With 5 Copy-Paste Prompts

By Julian Goldie · 9 November 2026 · agentos.guide

Grok Bot for lead generation slots into your Agent OS as the researcher on the outside: your Agent OS keeps the plan and the offer, and a Grok Bot finds prospects, fills the sheet and leaves drafts.

This guide gives you a quick start, five copy-paste prompts and a weekly rhythm, all built on what xAI documents.

Want my team to sanity-check your lead sources first? Book a free SEO strategy session.

Quick start: five checks before the first prospect sheet

• You are on Premium, Super or Ultra; Plus does not include Grok Bot (plan page).
• Google Sheets and Google Drive are connected under Connect apps.
• Zoho CRM is connected only if you already use it; it is the single CRM the docs name.
• You have an empty lead sheet you own, not one shared to you as Viewer.
• You have written an Ask first rule: "Ask first before sending any external email."

How the work splits between your Agent OS and Grok Bot

Your Agent OS holds the things that change slowly: the offer, the ideal customer profile and the tone of voice.

Grok Bot does the work that needs a browser and a schedule.

Its Bots run on one persistent cloud computer, each Bot with its own screen, and the private networks page notes those computers run in Cursor's cloud.

So you draft the brief in your Agent OS, paste it into a Grok Bot, and bring the finished sheet back for review.

Because the computer is shared, every Bot on your account sees the same browser sessions and files, so keep logins your lead work does not need off it.

Give the lead work a Bot of its own, as xAI suggests for any task you repeat, so its context stays about prospects and nothing else.

Grok Bot chooses its model for each task and has no picker, so model choice lives in your Agent OS, not here.

Prompt 1: write the lead-finder Bot's brief

Run this in your Agent OS first, then paste the output into a new Grok Bot called "Lead Finder".

Write a one-page brief for a lead-finding assistant.
Offer: [what we sell, in one line]
Ideal customer: [industry], [area], [size signal]
Buying triggers worth acting on: [e.g. new premises, hiring, public complaint about X]
Never contact: [current clients, competitors, personal accounts]
Output: a checklist the assistant scores each business against,
plus the rule that no one is contacted without my approval.

Prompt 2: the first X and website prospect sheet

Paste this into the Lead Finder Bot.

Built-in X search is read-only and needs no X login, and the cloud browser covers sites without an app.

Using the checklist above, search public X posts and local news from the last 7 days
for businesses showing one of the buying triggers.
Open each business's own website to confirm it.
Only use contact routes the business publishes itself, and skip any site whose terms
block automated visits. If a site asks for verification, stop and tell me.
Add rows to the "Leads" Google Sheet with columns:
business | website | trigger | source link | fit score | reason | contact route | status

🔥 Build the lead finder with other operators

The AI Profit Boardroom gives you step-by-step video trainings, the installable Agent OS, four coaching calls a week and 3,400+ members swapping prospecting prompts.

→ Join the AI Profit Boardroom

Prompt 3: score the rows and draft first emails

For every row scored 7 or above, draft a first email of no more than 80 words
that names the trigger and offers one specific thing. Use my tone from the brief.
Save each as a draft. Do not send anything.
For rows below 7, write the reason in the sheet and leave them alone.

If the Bot sends from its mail.grokbot.com address, first emails go to one person each with a one-click unsubscribe link, and it stops writing to anyone who bounces or reports spam.

Those limits are on the computer and apps page.

Read the drafts before you add any rule.

If the tone is off, fix it in your Agent OS brief, not in the Bot, so the next brief carries the change.

Prompt 4: the weekday 7 am routine

When three manual runs look right, save the skill and schedule it.

Save the process we used as a skill called "Lead Finder", including the checklist,
the sheet columns and the rule that nobody is contacted without my approval.
Then set up a routine: every weekday at 7:00 AM, run Lead Finder for triggers
since the last run, add new rows only, and post a short summary here.
If the sheet or a source is unavailable, report it instead of guessing.

Check When to run and press Test, as the skills and routines page advises.

Any email this routine prepares waits as a draft until you press Send.

Prompt 5: the inbound form webhook

Add a webhook trigger to a new routine called "Form leads".
When a call arrives, read the JSON body, score the enquiry against the Lead Finder
checklist, add it to the Leads sheet, and draft a reply offering two free times
from my Google Calendar. Do not send the reply.

Open the routine on desktop and copy the POST to URL and the header into your form tool.

A 200 response means the run started, not that it finished.

Senders put the key in an Authorization: Bearer header, so keep it out of public page code and rotate the form tool's copy if a contractor leaves.

Test it with one fake enquiry and read the row before you point real traffic at it.

Bonus prompt: give the Bot its own inbox for replies

Replies to your outreach need somewhere to land.

A Bot can claim one address at mail.grokbot.com, and nothing is claimed until you approve the card.

You only ever get one address and it cannot be renamed, so choose the name with care.

Get yourself an email address. Suggest three names based on our business name.
Then set up a routine on the alias +leads: when a reply arrives from a business
in the Leads sheet, update its status to "replied", summarise the reply in one
line, and draft my answer. Do not send it.

A routine on a plus alias runs only for mail sent to that alias, and anyone can write to an alias, so keep a sender filter on it.

xAI also says the Bot treats email from other people as information, never as instructions.

A worked example: a mobile coffee van booking office events

A coffee van business wants offices that host staff events.

Step one, Prompt 1 in the Agent OS sets the rules: offices within the delivery area, an upcoming event or open day, and no current bookings.

Step two, the Lead Finder Bot searches public X and local news for open days and launches, and checks each company's site.

Step three, it adds the company, event date and link to the sheet with a score.

Step four, it drafts a short note offering coffee for that event, and the owner sends the ones she likes.

Step five, enquiries from the van's website go through the Form leads webhook and arrive as scored rows with draft replies.

A second example: a bookkeeping practice qualifying enquiries

A two-person bookkeeping practice gets enquiries from businesses of every size and wants only small limited companies.

Step one, the Agent OS writes the checklist: company type, rough turnover band the client states, and the software they use.

Step two, the contact form posts to the Form leads webhook from Prompt 5.

Step three, the Bot scores each enquiry, writes the reason in the sheet, and drafts either a booking reply with two free slots or a polite referral.

Step four, the partner reads the drafts at lunch and sends the ones she agrees with.

Nothing leaves the practice without her pressing Send.

The weekly workflow

1. Monday: read the week's rows in the sheet and delete anything off-brief.
2. Daily: send the drafts you agree with, edit the rest.
3. Wednesday: copy any wrong scores back into your Agent OS and refine the checklist.
4. Friday: ask the Bot for a Page summarising the week's triggers and replies.
5. Once a month: update the skill with what you learned, and bring questions to the AI Profit Boardroom coaching calls.

Pages is rolling out gradually and is not on Enterprise teams yet, per the files and results page.

For follow-ups after a reply, our grok bot for sales guide picks up where this one stops.

🔥 Want a second view on your lead plan?

Book a free strategy session and my team will look at which lead sources deserve a Bot first.

→ Book a free strategy session

Stay on the right side of site terms and spam law

Put the rules in the skill so every run carries them.

Only read sites whose terms allow automated visits, and respect their robots rules.

Collect only the business contact routes companies publish.

Spam and privacy rules bind you as the sender, in your own country and in the recipient's, so check them before the first send.

Keep the list short and researched; this is not a tool for mailing thousands of people.

If a site expires your session or asks for verification again, the docs say to have the Bot pause and notify you rather than work around the check.

Want to see this set-up running? The AI Profit Boardroom covers skills, routines and webhooks in its trainings.

FAQ

Why write the brief in my Agent OS instead of Grok Bot?

Your Agent OS already holds your offer and voice, so it writes a sharper checklist. Grok Bot then runs it with a browser, X search and a schedule.

Do all my Bots see the lead sheet login?

Yes. Every Bot on your account shares one cloud computer, so sessions and files are shared, although each Bot works on its own screen.

Can the 7 am routine send the emails it drafts?

No. Routine email waits as a draft until you press Send, and the docs say there is no unattended sending option.

What if my CRM is not Zoho?

Keep the Google Sheet as the lead list and import it into your CRM yourself. Zoho CRM is the only CRM the docs name.

Final word on Grok Bot For Lead Generation

Paste the five prompts, read every row, book a free strategy session if you want a second view, and keep yourself as the sender when you run Grok Bot for lead generation.

Related guides on agentos.guide

→ Hermes Agent For Lead Generation: 5 Prompts In Your Agent OS

→ Hermes Agent For Content Creation In Your Agent OS

→ Grok Bot For Content Creation: A Weekly Engine In Your Agent OS

→ Hermes vs Genspark: Run Both Side By Side In Your Agent OS

📺 Video notes + links to the tools 👉

🎥 Learn how I make these videos 👉

🆓 Get a FREE AI Course + Community + 1,000 AI Agents 👉

← all guides on agentos.guide