How to Have Grok Bot Chase Your Storm Leads for You (Step-by-Step)

This is part of How to Have Grok Bot ______ for You. Second niche spin. Roofing only. Real shop workflows, not a find-replace of HVAC or the generic follow-up post.

You are the estimator and the office. Active leak texts while you are still on a ladder. Post-storm inspections that never got a confirm. Estimates left on the kitchen table. Adjuster meetings that slid. Storm leads do not die because you do not care. They die because chase never happened.

Done tonight is not “AI files the claim.” Done is one named Storm Lead Chase Clerk, one inbox where storm work dies, and one dry-run stack of drafts sorted by real roofing urgency. Drafts only. You send from the truck.

Hire a Storm Lead Chase Clerk

Name the bot Storm Lead Chase Clerk. Or Roof Claim Follow-Up Drafter. Pin a three-line charter on it.

• Owns: unanswered storm leads and roof messages in the one inbox where work dies. Classifies each thread by roofing urgency. Leaves a send-ready draft (or a [NEED] line).
• Good: a morning stack on your phone: active leaks first, then inspection confirms, estimate bumps, adjuster dates, supplements, install windows, then quiet “just checking” threads. Different copy per class. No one template.
• Never: send. Never invent claim approval, coverage %, dollar amounts, square footage, material ETA, or install day. Never say “your roof is totaled.” Never give legal, medical, or financial advice. Never talk to a live customer unattended.

That is the job. Sort the pile. Draft what you would actually say. Leave the send to you.

This is not the generic follow-up with leads post (any local shop). Not HVAC call triage (no-cool, filters, parts). Not email to-do list (ranked actions across life). Not the daily business briefing (van, three decisions). This is Small Business / roofing. Storm lead. Inspection. Estimate. Adjuster. Install.

What the stack has to hold

One screen. If every draft sounds the same, it failed.

1. Active leak / emergency tarp. Same-day priority. Short. Empathy. Ask where water is entering, whether they can catch it, and whether anyone is home for a tarp. Do not invent a scope. Do not invent “crew at 2.”
2. Post-storm inspection booked. Waiting on homeowner confirm. Remind the window you already set. Ask for gate codes, dogs, or attic access only if you need it. Do not invent a new day.
3. Estimate left after inspection. 24–48 hour bump if quiet. Name the elevation or damage you walked. Hold the number only if you typed it. Offer a clear next step: approve, ask a question, or set the adjuster meet.
4. Insurance adjuster meeting. Confirm or reschedule only. Never invent claim status, coverage, or ACV vs RCV. If the carrier note is missing, [NEED] and stop.
5. Supplement / additional damage found. Status only. What you documented. No invented dollars. No “they’ll pay for the whole roof.”
6. Material lead time / install window. Only dates you typed. If the supplier note is missing, [NEED]. Never invent shingle ETA or crew day.
7. Quiet “just checking” / competitor compare. Short status. No guilt trip. No second pitch. One clear next step you can keep.

What you connect (and what you don’t)

Grok Bot is early beta. SpaceXAI and Cursor are building it. Connectors live under Settings → Plugins. One shared computer for all your bots. Start thin.

Night one, connect only what the clerk needs:

• The one inbox where storm leads die. Gmail, texts, Facebook Marketplace, or the messenger your shop actually uses. One. Not all four.
• Optional: a notes doc where you keep crew days you can keep, storm counties you work, and the estimate wording you actually use.
• Optional: paste three cold threads in chat if a plugin is not there yet. Paste works.

Do not connect banking, email send, or social write access. Do not paste a JobNimbus or AccuLynx password in chat. Authorize in the browser. Open Settings → Plugins from the sidebar, or press Cmd+,.

Tonight, in seven steps

1. Name what a missed storm lead costs you. A leak that hired the door-knocker. An estimate that sat four days after hail. An adjuster meet the homeowner forgot.
2. Pick the one inbox. Texts. Voicemail forward. Marketplace. Email. Where storm work dies. Write it down.
3. Hire Storm Lead Chase Clerk. Paste the charter below. Say drafts only. Say never send. Say this is roofing storm chase, not HVAC triage, not a generic lead SDR, not a van dispatch brief.
4. Connect that one inbox (or paste). Settings → Plugins. Or paste three cold threads. Do not connect the whole stack.
5. Run one manual stack. Ask it to classify each thread and draft. Kill any invented claim approval. Kill any invented dollars or square footage. Kill any “your roof is totaled.” Kill leftover HVAC or generic sections.
6. Pick a trigger. Weekday mornings before you roll, and tighter the week after a named storm. Click the bot name in the chat header to open the info pane, or press Cmd+Shift+I. Save a routine: every weekday morning, scan that inbox, leave the chase stack in this chat, do not send. Confirm the time zone. Active-leak rule stays same-day.
7. Five-minute truck check. Skim class, draft, [NEED] lines. You edit. You send. You drive.

That is tonight. A clerk that sorts storm urgency the way your roofing shop already thinks. You still own the send, the numbers, and the crew day.

Copy-paste charter

You are Storm Lead Chase Clerk (Roof Claim Follow-Up Drafter) for my one-person / small roofing shop.

Owns: unanswered storm leads and roof messages in the one inbox I connect. Classify each thread. Leave a send-ready draft or a [NEED] line.
Good: a morning stack I can skim in five minutes on my phone, sorted by real roofing urgency. Different copy per class. No one template.
Never: send, post, or spend. Never invent claim approval, coverage %, dollar amounts, square footage, material ETA, install day, or “your roof is totaled.” Never give legal, medical, or financial advice. Never talk to a live customer unattended. Never promise a crew day I did not type.

Every weekday morning (and tighter after a named storm), 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:

1) active leak / emergency tarp (same-day priority)
2) post-storm inspection booked, waiting on homeowner confirm
3) estimate left after inspection (24–48h bump if quiet)
4) insurance adjuster meeting (confirm/reschedule only; never invent claim status)
5) supplement / additional damage found (status only; no invented dollars)
6) material lead time / install window (only dates I typed)
7) quiet “just checking” / competitor compare (short, no guilt trip)

Write 4 to 8 sentences in my shop voice. Short. Plain. Use their name if we have it. Mention the actual storm, elevation, or job they asked about. End with one clear next step I can keep.

If a name, address, price, date, crew day, claim status, coverage, square footage, or material ETA is missing, do not invent it. Put a [NEED] line under the draft that names the missing fact. Then stop on that thread.

After a hail or wind event: put every active leak / emergency tarp at the top. Do not bury them under estimate bumps.

Leave the drafts in this chat. I send them.
If you cannot see the inbox, write [NEED] and stop. This is roofing storm chase, not HVAC triage, not a generic lead SDR, and not a van dispatch brief. Drafts only.

What done means

You open the stack, spend five minutes in the driveway, and send the ones that are clean. That is it.

If every draft sounds like “just circling back,” tighten the charter. If it invented claim approval or a dollar amount, kill the line. If it promised Thursday install and you did not type Thursday, kill the line. Generic lead timing belongs in follow-up. HVAC urgency stays with HVAC call triage. Shop van decisions stay with the daily business briefing. Storm Lead Chase Clerk stops when the pile is sorted and the drafts are yours to send.

Limits worth saying out loud

It is beta. Expect rough edges. One shared computer means protect the logins. Do not connect every tool night one. Do not let it send. Do not let it spend. Do not let it talk to a live customer unattended. Do not ask it for legal, medical, or financial advice. Never invent claim approval, coverage, dollars, square footage, material ETA, or install day. Missing facts get [NEED]. Never paste passwords.

If you want the product itself, start at Grok Bot Explained. Any local shop follow-up: follow-up with leads. HVAC callbacks: HVAC call triage. Public facts before first contact: research leads. Shop calendar plus three decisions: daily business briefing. Inbox into ranked actions: email to-do list. Public rival changes: competitors. New prospect lists: find customers. One meeting, one brief: meeting prep. One idea into a dated week of drafts: content week. Your day across work and home: morning briefing. Topics and URLs you named: watchlist. A tiny team on top: Chief of Staff.

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