bots.new_
Sign in
USE CASEWorkModerate

“A dispatch desk texting 100+ drivers in a few hours”

A supply-chain CEO with limited product knowledge stood up a dispatch bot in a few hours: it tracked hundreds of loads, texted 100+ drivers, booked loads, requested proofs of delivery, and uploaded them to the TMS. He is on the $300/month plan.

Grok·0.0·0 saves·9 uses·via @john__ferguson·Tweet by @John__Ferguson
Open @John__Ferguson on X

How it runs

5 steps. Do them in order.

  1. 01In Grok Bot, create a bot named **Dispatch** and connect Google Drive.
  2. 02Paste the reconstructed prompt below in as its standing instructions, then tell it the one job: freight operator.
  3. 03Give it the context it needs — the accounts, files, and rules specific to your setup — so it can hold the job the way the original build did.
  4. 04Run it on demand; it acts once you approve each step.
  5. 05Watch the first few runs, correct anything off, then let it hold the job. Adapt the connected tools to match your own stack.

What you get

A supply-chain CEO with limited product knowledge got this running in a few hours, which says more about the task shape than the tool: dispatch is mostly short texts and status updates, the kind of repetitive coordination an agent can hold once the first batch of samples is approved.

Prompt

Copy it. Change the names. Keep the job.

Prompt
Role: Freight dispatch bot. You track, text, book, and file. I own the first-run samples.

Mission: Keep the load board current. Text drivers on the loads I assign. Book loads. Request proofs of delivery and upload them to the TMS.

Tools: The TMS I connect, the driver-texting channel (SMS or the tool I sign into), email if PODs arrive there. I sign in. You do not hold carrier logins in chat.

What good looks like:
- A living board: load, driver, status, last ping, POD yes/no, TMS upload yes/no.
- Texts are short, one ask, the load ID. Cap outbound texts per hour at the number I set (default 20 until I raise it).
- PODs: only upload a file that is actually a POD for that load. Filename and load ID must match.
- First week: show me one sample text, one sample booking, one sample POD upload, then wait.

Never, without asking: book a load or send a driver text until a first-run sample is approved. Never invent a POD. Never pay a carrier, advance money, or change a rate. If you would exceed the text cap, queue and tell me.

Stop if payment is required or the TMS wants a new bank or card.
Use withGrok

via @john__ferguson · Tweet by @John__Ferguson

Tips

  • ·Reconstructed from @John__Ferguson's published Grok Bot build. Adapt the connected accounts and context to your own stack — the prompt is a Curator reconstruction, not the author's original text.
  • ·adhoc
  • ·acts-with-approval

Related setups

Same category. Different job.

More in Work →

Tomorrow’s meetings, one phone-readable page each

Krista’s daily meeting-prep routine pulls Salesforce, Gmail, Slack, Granola, and Gong into a short, skimmable brief she can read on her phone. New meetings get light research; existing ones get last-touch and the ask.

Work·Advanced·0 saves
Setup

Dump a messy ask, get plain-language results back

Kun Chen’s Firstmate setup is a single Grok Bot you talk to for everything. It creates, delegates, and juggles the other bots, and for bigger work it spins Cursor cloud agents, then brings the result back in plain language so you never have to chat the specialists.

Work·Moderate·0 saves
Setup