02Dispatchlead agent DaxL3
A dispatch rail on your own WhatsApp
A dispatch rail is the WhatsApp thread where job cards go out to your technicians. Each ticket becomes a card in the format <zip> <JOB> K?, the first tech to reply K takes it, and every stamp after that (on the way, on site, closed) lands on the timeline in your ledger. It replaces a dispatcher on the phone and the group-chat guesswork.
runs on your accountsyour keysno price list
Reply K to take it. First reply wins.
01 · What changes
What it replaces, what it automates, what it amplifies.
02 · How it runs
Scope, connect, run, hand over.
The same four moves as every build, in the order they happen for this one.
- 01
Scope from your last month of jobs
We read how jobs actually move today: how a tech hears about a job, how long a card waits, where it gets lost. The rail is shaped around that.
- 02
Set up the groups and the roster
Your techs, your areas, your job codes and price rules go on file. One WhatsApp group per rail, on your WhatsApp Business account.
- 03
Wire the ticket to the card
A ticket from the phones or a web form becomes a card automatically. The format is fixed: <zip> <JOB> K?. Techs learn it in a day.
- 04
Run it beside the old way
For the first week the rail runs next to your current dispatch. You watch the timeline. When it matches reality, the old way stops.
- 05
Hand over or manage
The groups, the roster and the timeline are yours. We hand over, or keep running the reminders and the nightly review for you.
03 · Compared, plainly
Who does what, and what breaks.
No dollar figures. Coverage, ownership and what happens at 2 AM. The last row is yours to fill in.
| What matters | Clever build | Dispatcher on the phone | Group chat | Field-service software |
|---|---|---|---|---|
| Job card in a fixed, readable format | Yes | Partly | No | Yes |
| First tech to claim gets it, visibly | Yes | Partly | No | Partly |
| Runs at 2 AM without a person awake | Yes | No | Partly | Partly |
| Timeline: claimed, on site, closed | Yes | Partly | No | Yes |
| Reminder when a card sits unclaimed | Yes | Partly | No | Partly |
| Techs use the app they already have | Yes | Yes | Yes | No |
| Feeds payout math on close | Yes | No | No | Partly |
| Built around your areas and job codes | Yes | Yes | Partly | Partly |
| No per-seat logins or app training | Yes | Yes | Yes | No |
| Nightly review of what went out and closed | Yes | No | No | Partly |
| Your current costper month · write it in, we never will | blank, for your own figure | blank, for your own figure | blank, for your own figure | blank, for your own figure |
04 · Proof · our own fleet
This build runs on our companies today.
Read from the ledger when this page loaded. A dash means the source was down. Not measured yet means the ledger has no source for it.
jobs on the rail · 7d
jobs · created · 7d
techs on the roster
dispatch_techs
Companies on the fleet
ledger · cc_companies
Connects to your accounts
Plugs into what you already pay for.
- WhatsApp Business (your groups, your number)
- Your ledger (Supabase) or your field-service tool
- Your phone line, via the ticket from the receptionist
- Your tech roster: names, areas, payout terms
- Google Business Profile, for the address and hours on the card
Access is granted per account with your own tokens and can be revoked in your own settings. Nothing is shared between clients.
Where we build
Our own companies in New York and South Florida. The same rail, remotely, anywhere in the US.
FAQ
Questions about the dispatch rail build
- What is a dispatch rail?
- A dispatch rail is a WhatsApp thread where job cards go out to technicians in a fixed format: zip, job code, and a K? asking who takes it. The first K claims the job. Everything after that is stamped on a timeline so the owner can see it without calling anyone.
- Do my techs need a new app?
- No. It runs on WhatsApp, which they already have. The only thing they learn is the format: reply K to take a job, then send the on-site and closed stamps. Most crews pick it up on day one.
- What if two techs claim the same job?
- The first K wins and the card shows who took it. A second K gets a reply that the job is taken. If the first tech drops it, the card reopens and goes back out.
- Does it work with the field-service software I already pay for?
- Usually. The rail reads tickets from your ledger or your existing tool and writes the stamps back. If your tool has no way in or out, we tell you that during scoping, before anything is built.
- Can it dispatch by area or skill?
- Yes. The roster holds each tech's areas and job types. A card only goes to the group where someone can actually do the job. You set those rules, and you can change them without a rebuild.
What ran this week · Sunday night
One email. What ran, what broke, what got fixed.
Written by Clever from the ledger, read by Ori before it goes out. No pitch, no course, no partner offer. Leave whenever you like.
Apply · DISPATCH-RAIL
Apply for this build.
Trade, name, phone. Clever reads it within a minute and a written plan for the dispatch rail build comes back before anything is built. No price list; the scope is written from your own data.
- · scoped from your own data
- · runs on your accounts
- · proven on our fleet first