Lime speech bubbles and a stack of draft cards on black. Follow up. You send.

How to Have Grok Bot Follow Up With Leads for You (Step-by-Step)

This is part of How to Have Grok Bot ______ for You. Capability first. HVAC, roofer, and realtor spins come later.

You already get the inquiries. Then they go cold.

HVAC. Plumber. Roofer. Cleaner. Landscaper. Handyman. One person, a van, and a phone that lights up while you are on a roof. Texts. Facebook Marketplace. Email. The voicemail you meant to return Tuesday. You are not a Salesforce team. You are the whole shop.

Done tonight is not “follow-up automated.” Done is three real drafts sitting on your phone that you actually send today. Not fifty leads. Not auto-send.


Hire a Follow-Up Drafter

Name the bot Follow-Up Drafter. Pin a three-line charter on it.

  • Owns: unanswered leads in the one inbox where work dies.
  • Good: a morning stack of drafts on your phone, classified, ready to send.
  • Never: send. Never quote a price you are not sure of. Never promise a time slot you did not type.

That is the job. Not “handle my customers.” Not “be my SDR.”


What you connect (and what you don’t)

Grok Bot is early beta. SpaceXAI and Cursor announced it August 11, 2026. Access is SuperGrok Heavy, Cursor Ultra, or Cursor Teams Premium. There is a trial. Pro and Pro+ do not include it. Cursor Ultra is $200 a month. That is the only plan price we will name.

You get one cloud computer, shared by every bot you create. Sign-ins and files live on that machine, not on one bot. If you connect the whole stack day one, the blast radius is the whole stack. Don’t.

Connect only Gmail, or the inbox or messenger the shop actually uses. Open Settings → Plugins from the sidebar account button, or press Cmd+, . Hand the screen for the login. Never paste a password in chat.


Tonight, in seven steps

  1. Pick the inbox where leads die. One. If they die in texts, that is the inbox. If they die in Marketplace, that is the inbox. Not all four.
  2. Create the bot. Name it Follow-Up Drafter. Give it a title that matches the job.
  3. Paste the charter below. That is the first message.
  4. Connect that one tool. Settings → Plugins. Authorize in the browser. Confirm it shows as Installed. Stop.
  5. Do three real follow-ups together while it watches. Open three cold threads. Say out loud who they are, what they asked, and what you can actually offer this week. Let it draft. You edit. You send. It learns your voice from work, not from a vibe.
  6. Save a morning routine. Click the bot name in the chat header to open the info pane. Ask it to follow along and save a routine: every weekday morning, scan that one inbox, leave drafts in this chat, do not send. Confirm the schedule and the time zone.
  7. You send from your phone in the driveway. Three drafts. Check the names, the prices, the days. Send. Drive.

Copy-paste charter

Paste this as the first message. Change the trade and the inbox name. Keep the never lines.

You are Follow-Up Drafter for a one-person local shop. 
You own unanswered leads in the one inbox I connect. 
Good looks like a morning stack of drafts I can send from my phone. 
You never send. You never quote a price I am not sure of. 
You never promise a time slot I did not type.

Every morning, look at that inbox. 
Skip anything I already answered or that said never mind. 
For each remaining thread, 
classify it as one of these and write a different follow-up, n
ot one template:

- new lead
- estimate requested
- "just checking"
- no-show
- after the job

Write 4 to 8 sentences in my shop voice. Short. Plain. 
No "just circling back to touch base." Use their name if we have it. 
Mention the actual job they asked about. End with one clear next step I can keep.

If a name, address, price, date, or time slot is missing, do not invent it. 
Put a [NEED] line under the draft that names the missing fact. 
Then stop on that thread.

Timing:
- new HVAC or plumbing inquiry: same day
- estimate sent, no reply: 24 hours
- still quiet: 3-day bump
- still quiet: 2-week "still want this?"
- after that: leave it

Leave the drafts in this chat. I send them. 
If you cannot see the inbox, write [NEED] and stop. Do not start a second job.

Different follow-up, not one template

A new lead wants a same-day yes, we can look at that. An estimate that sat a day wants “still want me to hold that number, or did the job change?” “Just checking” wants a short status, not a second pitch. A no-show wants a clean reschedule window you actually have, not a guilt trip. After the job is a thank-you and “anything else before I close this out,” not another upsell.

Same-day on a new HVAC or plumbing ask. 24 hours on an estimate. A 3-day bump. Then a 2-week “still want this?” That is shop timing. Do not invent a pipeline tool. If you keep jobs in a notebook, say that in the charter. If you keep them in your head, say that too.


What done means

Three drafts you actually send today. That is the win.

If the bot wrote you a strategy memo, the charter was too polite. Tighten it. If it quoted a number on a job you have not seen, that is a [NEED], not a send. If it promised Thursday at 2 and you did not type Thursday at 2, kill the line.

You still own the send. You still own the price. You still own the calendar.


Limits worth saying out loud

It is beta. Expect rough edges. One shared computer means one leaked login is every bot’s login. Do not connect the whole stack day one. Do not let it send. Do not let it talk to a live customer unattended. Do not ask it for legal, medical, or financial advice. Do not paste passwords.

If you want the ten-minute paste-and-send loop without a standing bot, that is Answer every customer message in ten minutes. If you want one overnight chore with a no-send contract, that is Your first overnight agent. If you want the product itself, start at Grok Bot Explained.

If you want this built for your shop, that’s a different conversation.


Posted

in

, ,

by

Comments

0 responses to “How to Have Grok Bot Follow Up With Leads for You (Step-by-Step)”

Leave a Reply

Your email address will not be published. Required fields are marked *