How to Use GrokBot for Cold Email without doing a single thing (yes really)
文章目录
Most cold email dies after the reply.
Someone says interested. You answer four hours later. They're gone. Someone books three weeks out and never shows. Someone's OOO names the real buyer and nobody follows it.
Copy gets the attention. The money is in speed and follow through.
So I stopped rewriting the same emails by hand and stood up GrokBots for the work around the send.
The one rule
11 bots. I still approve every send. Nothing goes out without my yes.
Reading a good draft takes seconds. Writing it from scratch is where deals die.
Three of them (market, list, campaign) are next to build. The other eight already run. Below is the full stack, in the order a lead hits it, with prompts you can copy.
First: drop your operating brief
GrokBot is useless on vibes. Feed it the offer, the markets, the booking rules, and what you're allowed to claim.
Copy this:
Working context for my cold email. Save it where I can reuse it. Offer: [what we sell, who for, deal size, first-call name]. Markets under test: [verticals]. ICP: [roles, company size, industry, geo]. Pain: [problems]. Objections: [list]. Triggers: [events that make them buy]. Disqualifiers: [who we skip]. Booking: we book from our side and send the invite; never a self-book link; weekdays only; 8:30am to 5pm ET; never more than 7 business days out; one specific time in their timezone; log offers so bots don't collide. Proof I approve: [case studies / numbers]. Voice samples: [emails]. Sign with the name on the last email in the thread. Every URL must be a real hyperlink. Draft only. Silence means hold. Use jev wherever this stack calls for fit scoring. Ask for an export if a source is blocked. Flag guesses.
Update it when the offer or rules change.
Bad brief in. Bad drafts out.
Now walk one lead through the stack
Each bot shows up at the moment you need it. Short setup. Prompt. What comes back. Rules. One take.
Bookmark this if you want the prompts handy. Skip the fluff.
1. Strategist Bot
You have an offer and a pile of markets. This picks where ROI actually lives. GrokBot runs jev on offer-market fit and finds the roles that feel the pain.
Prompt:
-
Score these markets against my offer with jev: [list]
-
Rank markets and roles by fit
-
For each: pain, buy triggers, disqualifiers
-
One line on why it is high or low ROI
-
Prefer a short sharp list over a long weak one
It returns:
-
Ranked markets + roles
-
Pain and triggers per segment
-
Disqualifiers
-
Fit notes from jev
Rules:
-
No invented pain or proof
-
Draft only. Do not launch.
Take: wrong market burns domains. Rank fit before you spend a send.
2. Lead List Builder Bot
Strategist locked the segments. This builds the list and runs jev on B2B fit before anyone gets added.
Prompt:
-
Build a list from these approved markets and roles: [from Strategist]
-
Run jev B2B fit before adding anyone
-
Show company, role, fit score
-
Show who got cut and why
-
Flag gaps where we need more sources
It returns:
-
Fit-cleared contacts
-
Rejects + reasons
-
Source gaps
Rules:
-
No invented names, emails, or titles
-
No uploads. No campaign starts. Draft only.
Take: send volume on people who can buy. Everyone else is noise.
jev is the gate. Not a vibe check.
3. Campaign Creator Bot
Turns the approved segment into angles, sequence, and copy. Drafts only.
Prompt:
-
Build campaign drafts for [segment] from the approved brief
-
Give the angle
-
Outline the sequence
-
Write each step in my voice
-
CTA that leads to a call we book from our side
It returns:
-
Angle
-
Sequence map
-
Copy per step
-
Claims that need my proof flagged
Rules:
-
No self-book links
-
Real hyperlinks only
-
Nothing sends without my yes
Take: strategy without campaigns is a slide. This makes something you can approve.
Heads up: Strategist, Lead List Builder, and Campaign Creator are the next three we're building. Everything after this already runs.
Same rule for the new ones when they land: drafts only.
4. Reply Bot
Positive reply lands. This drafts the next email fast, in your voice, and pushes toward a booked call.
Prompt:
-
Draft a reply from my outbound brief
-
Classify: interested / question / named a time / referral / wrong person / not now / objection
-
Answer what they asked
-
Offer one specific day and time in their timezone
-
Show the calendar check
It returns:
-
Classification
-
Draft reply
-
Slot + why it's free
-
One-line reason
Rules:
-
We book. We send the invite. Never a self-book link.
-
Weekdays, 8:30am to 5pm ET, max 7 business days out
-
Vary times across leads. Log them. Draft only.
Take: outbound is a speed and follow through game dressed up as a copywriting game. Ten-second draft beats a blank screen.
5. Booking Rules Bot
Shared calendar brain so two bots never offer the same hour to two leads.
Prompt:
-
Check my calendar + the offered-slots log
-
Only weekday slots, 8:30am to 5pm ET, inside 7 business days
-
Skip anything already held
-
Pick one best slot in their timezone
-
After I approve, log it and release other holds when booked
It returns:
-
Valid slots
-
The one to offer
-
Log update ready
Rules:
-
No weekends. No far-out bookings.
-
Confirm once in-thread after booking. Draft only.
Take: far-out calls no-show. Intent decays. Logging stops collisions. We book from our side. Prospects don't do homework.
6. Show-Up Bot
A booked call that doesn't happen is worth zero. This confirms before and tracks held, not booked.
Prompt:
-
For calls in the next [N] business days, draft a short confirmation
-
Include day, time in their timezone, what the call is for
-
List meetings booked vs held
-
For no-shows, draft a one-line rebook
It returns:
-
Confirmation drafts
-
Booked vs held
-
Rebook drafts
Rules:
-
Short. No guilt. No self-book links.
-
Draft only. Nothing goes out without my yes.
Take: track meetings held. That's the number that pays.
7. Out-of-Office Bot
OOO and "talk to my colleague" used to be dead ends. They're warm data: who to email, and when they're back.
Prompt:
-
Handle this OOO or referral auto-reply
-
Pull return date if present
-
Pull named colleague or role + verified email
-
Draft a forward of our original with a short note, or a follow-up after they return
-
Offer one specific time to the new contact and log it
It returns:
-
Return date
-
Next contact
-
Forward or timed follow-up draft
Rules:
-
Same inbox as the original thread for forwards
-
No invented names or emails. Draft only.
Take: ignoring OOO leaves free pipeline on the table.
Warmest data in the inbox if you treat it like a lead.
8. Call Prep Bot
Brief before you join. Who they are, what they said, what to push.
Prompt:
-
Build a call prep for this booked meeting
-
Company context from connected sources only
-
Quote what they said in the thread
-
Likely objections + the ask
-
Three pushes tied to their words
It returns:
-
Who + company
-
Quoted thread points
-
Objections / ask
-
Three pushes
Rules:
-
No invented facts. Mark inferences.
-
Ask for an export if a source is blocked.
Take: cheapest close-rate lift there is. Thirty seconds to read, not thirty to write.
9. Angle Hunter Bot
Finds something real in their world so the opener is about them.
Prompt:
-
Find a timely angle for [lead or list]
-
One concrete trigger: regulation, hire, funding, launch, deadline, public change
-
One sentence on why it matters to our offer
-
Two-line opener, not over-researched
-
List sources and what you could not verify
It returns:
-
Trigger
-
Why it matters
-
Opener
-
Source gaps
Rules:
-
No fake personalization
-
If nothing is real, say so. Don't invent a hook.
Take: relevance beats personalization. Why them, why now.
10. Revival Bot
Quiet calls are cheaper than new leads. These people already took a meeting.
Prompt:
-
Pull past sales calls from [Fathom or your recorder]
-
Score fit against my ICP
-
Draft a follow-up from what was actually said
-
Include fit score, what was discussed, reactivation draft, timing
It returns:
-
Fit score + reason
-
Call notes in their words where possible
-
Reactivation draft
-
Suggested next step
Rules:
-
Real call content only. No invented quotes.
-
Draft only. Nothing goes out without my yes.
Take: I pulled 574 Fathom calls, scored fit, drafted from the tape. Graveyard pipeline beats bought lists.
11. Cost Bot
Watches spend so the stack stays cheap.
Prompt:
-
Report tokens, requests, and spend per outbound bot for [period]
-
Flag waste: retries, fat context, polling, duplicates
-
One cut that keeps reply quality
It returns:
-
Per-bot usage + cost
-
Waste flags
-
One cost cut
Rules:
-
Real meters only. No estimates.
-
Say when a meter is missing.
Take: one fit-scoring run hit 25.4M tokens across 6,377 requests. Bill was $0.96. Cost is not the excuse.
Order I'd stand them up
If you're already sending: Reply Bot first. Then Booking Rules + Show-Up. Then Out-of-Office. Then Call Prep + Angle Hunter. Revival and Cost monthly.
If you're still picking markets: wait for Strategist, Lead List Builder, and Campaign Creator. Don't burn a domain guessing.
Don't stand up eleven on day one. Stand up the bottleneck you can judge in seconds.
For teams already live on send, that bottleneck is the reply.
What this is not
This is not autopilot. GrokBot drafts. I approve. Judgment stays with me.
Polished garbage still gets killed in review.
If a draft says something I wouldn't defend on a call, it dies in review.
Want the stack for your outbound? Say so.
Or drop your operating brief and start with Reply Bot.
Simple sequence.
Execute.
沿着这个主题继续读
从一篇文章,找到相关的教程、经验和阅读路径。



