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.
plug your Grok Bot in
closeinstall this
A dispatch desk texting 100+ drivers in a few hours
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.Copy the prompt and paste it into Grok.
How it’s set up
- In Grok Bot, create a bot named Dispatch and connect Google Drive.
- Paste the reconstructed prompt below in as its standing instructions, then tell it the one job: freight operator.
- Give 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.
- Run it on demand; it acts once you approve each step.
- Watch the first few runs, correct anything off, then let it hold the job. Adapt the connected tools to match your own stack.
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.Why it’s cool
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 reconstructed by the Curator from @John__Ferguson's published setup — not their verbatim text
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.Copy the prompt and paste it into Grok.
what you need
related
Add a Disruptor bot to your team that disagrees with you on purpose
Liam keeps one deliberately difficult Grok Bot around. Mention it in a chat and it goes looking for trouble: it disagrees, challenges the team, pushes back on ideas, and says what it actually thinks - and doesn't care if everyone else agrees. A built-in devil's advocate that kills groupthink and sycophancy.
Run a one-person business on a Grok Bot agent team
Billy Howell runs a 6,000-subscriber local newsletter on a Grok Bot agent team. His method: one project per account, a Chief of Staff that audits the business and proposes the first three revenue agents, perfect each task by hand before spinning off a dedicated bot, then automate the routine work.
Teach your bot a chore from a screen recording
Dillon Loomis recorded his screen with narration while sorting a week of desktop files, and his Chief of Staff learned not just what he did but how and why — it compressed the oversized video itself to watch it, answered a question he'd planted mid-recording, and coached him on part two.
the week's best, in one email
new plugins, use cases and collections. one email a week. that's it.
▪ you're on the list