MowProHQ Blog/Dispatch
Dispatching Snow From a Group Text vs a Real Board
A group chat is not dispatch. Publish the list, move crews when the band shifts, and stop asking who has which driveway.
A group chat is not dispatch. It is a pile of unread messages, a photo of a clipboard, and three people asking who has the corner lot while the band is already on the next neighborhood. Publish the list, move crews when the forecast shifts, and stop using the owner’s thumbs as the routing engine.
This is the storm-night board. The list you publish was built in October. The money follows invoices before the thaw. Software shape lives in the small plow crew buying guide. Here is why the thread fails and what replaces it.
What the thread actually does at 4 a.m.
It makes noise. It does not assign.
Typical failure, first heavy squall:
- Owner drops a list in the chat at 3:42
- Helper is still asleep, then scrolls past the list looking for a meme
- Second truck takes the same street because the list was a screenshot
- Customer texts the helper’s personal phone: cars in the drive
- Helper never pastes that into the crew chat
- Owner asks “where are you” four times
- Two drives sit until 8:15
- Completions are “I think we got them” at breakfast
None of that is a people problem. It is a system that cannot answer four questions without a meeting: who has the stop, what is next, what is open, what did the customer just say.
A board answers those without a roll call. The chat can still exist for “ice on the bridge” and “I’m out of diesel.” That is not dispatch. That is radio.
What a real snow board holds
Not a prettier map. A published sequence.
- Named crew on each stop
- Order that matches the commute plan from October
- Property notes: stack, trigger, ice, access
- Complete / open / abort
- Room to move a pocket when the band shifts south
If the helper has to call you for the third stop, the board failed or the notes failed. Fix the written standard. Do not add another chat.
Solo operators still need this. You are dispatcher and driver. The list on a phone you can mark complete is still a board. The list in your head is a single point of failure the first time you take a second person.
Two trucks without a named dispatcher (often still the owner) is two group chats. Someone owns the move. Crew leads can abort a single stop for cars or a closed road. Nobody invents a new city-wide order because they “felt” the other neighborhood was worse.
Publish, then move — do not rebuild
Snow dispatch is not lawn-care rain with colder hands, but the bulk-move habit is the same idea: you already had a list. The weather changed. You move open work. You do not hold a referendum.
Night before: Forecast is real enough to staff. List published. Trucks staged. People know if they are on the 4 a.m. call.
During: Completions tick off. Open stops stay visible. If the band dies, cancel the rest as a block and tell customers once. If it shifts, reassign open pins to the truck that is actually in that pocket.
Do not: Start “new list 2” in the thread. Do not alphabetize live. Do not send the helper a voice memo of twelve addresses.
Customer messages go out from Conversations: we are on your street; we aborted because of cars; second pass is extra. The crew does not need those threads in the same soup as “who has Elm.”
In MowProHQ
Worked example: band shifts south at 5:05 a.m.
Two trucks. North pocket almost done. South pocket still has eleven open drives. Radar shows the heavy band sliding south. School run is 7:10.
Thread dispatch: Owner types a new order. Truck A is in a dead zone. Truck B already turned north to “help finish.” Three south drives sit. Two customers text different personal phones. Nobody owns the leftover eleven. Commute window missed. Reviews write themselves.
Board dispatch:
- Owner sees eleven open in the south pocket.
- Truck B is closest and still has capacity — those opens move to B.
- Truck A finishes the last two north and deadheads south only if time remains.
- One customer message to the south list: we are in your neighborhood now, window is before 7.
- Completions keep ticking. Nothing depends on who read the chat.
Same snow. Same iron. The difference is a list that can move.
Who owns 4 a.m., and who is on which iron
If everyone can “just jump in,” nobody owns the leftover eleven. Name the dispatcher even when it is the owner in a cab. Crew leads abort a single stop. They do not redesign the city.
Match equipment on purpose:
- Plow truck on drives and lots you sold as blade work
- Helper with a shovel on walks and stairs, not wandering the same street twice
- The mechanic is not automatically on the call list
- The person who will not pick up is not “maybe” — they are off the roster
Commercial vs residential is a brand decision you wrote in October. If the lot window is first, the drives know they wait. If the mow book is the company, the lot waits or you refused it. Flipping that in the dark to chase whoever sounded louder in the thread is how you miss both commute and dock.
Night-before checklist (ten minutes, not a meeting):
- List published, assignees on every open stop
- Trigger still matches the forecast (two inches is not a debate at 3:40)
- Who is on shovel vs blade
- One person who will move opens if the band slides
- Customer message drafted for “we’re running” vs “band died, standing down”
If step 1 is still a screenshot, GPS will only document the chaos. Put the schedule on a phone the helper can open with gloves. Then the board can do its job.
GPS is a timeline, not a personality test
When two trucks are out, “where are you” is expensive. Event-based GPS on Growth tells you who started and who finished without turning the phone into a babysitter. Use it to fill a gap. Do not use it to narrate a route that was never published.
GPS does not invent density. If Tuesday’s snow book is a hero drive across the county, a pin just documents the waste. Fix the property list first.
Introduce it like dispatch, not like distrust: we need ETAs, we need to move opens, we need to stop calling every cab. You will not screenshot a ping in the crew debrief. If you cannot say that sentence, you are not ready for GPS. You are still angry at the thread.
Timeclock lives next to this on Growth. Overtime on a stacked storm week is real. A clock you can defend is calmer than a fight in March about who was “basically out since 3.”
Crew chat vs customer inbox
Keep them apart on purpose.
| Channel | For | Not for |
|---|---|---|
| Dispatch board | Assignment, order, complete/open | Jokes, diesel, customer feelings |
| Crew radio/chat | Hazards, breakdowns, ice on the overpass | Who has which driveway |
| Conversations | Customer: ETA, abort, extras, pay | Crew roll call |
When a homeowner says the drive is full of cars, that abort has to hit the job. If it dies in a helper’s iMessage, you will either skip them forever or invoice a push you did not do. Both are brand damage. The mow customer you still want in May reads winter like a test. More on not wrecking that in the first-season playbook.
Failure modes you can review after one storm
| Failure | What it looks like | Fix |
|---|---|---|
| Screenshot list | Two trucks, same street | Publish on a board with named assignees |
| Text-first order | Who yelled last goes next | Hold the October sequence |
| Personal phones | Customer abort never hits the job | Conversations + abort on the stop |
| Owner bottleneck | Nobody moves a pin without a call | Named dispatcher, even if it is you |
| Invisible completes | Breakfast debate about who is done | Mark complete in the cab |
| GPS on a scramble | Tracking chaos | Publish first, then ping |
Run that table after storm one. Pick one failure. Fix it before storm two. Dispatch improves by repetition, not by buying a prettier map in January when you are already behind.
How MowProHQ replaces the thread
MowProHQ puts properties, the schedule, and dispatch on one desk so the night is not a separate spreadsheet. Free holds the list, quotes, invoices, dual pricing, portal, and Conversations. Growth at $39 adds the board, GPS, unlimited seats, live site, and timeclock — the layer where two trucks stop needing your narration. Pro is $89. Phone $19. AI $29.
Start free, publish one list in daylight, then trial Growth before the first real 4 a.m. call. The goal is not a quiet phone because nobody is working. The goal is a quiet phone because the board already said who has the corner lot.
A group text will always feel faster the first minute of a squall. It is slower by 5 a.m. Publish the list. Move the opens. Keep customers in one inbox. Mark complete so the invoice is not a Sunday reconstruction. That is dispatch. Everything else is a thread you will mute when you should have been plowing.
Frequently asked questions
- Why isn’t a group text enough to dispatch snow?
- A group chat cannot publish a sequence, show who still has open drives, or reassign when the band shifts. It is unread messages and three people asking who has the corner lot. Dispatch is a board with a named list, not a thread.
- What should a snow dispatch board show?
- Who is on which stop, in what order, what is complete, what is still open, and the notes that travel with the property. If the owner is still the only person who knows the next driveway, you do not have dispatch. You have a radio show.
- How do I move a snow crew when the forecast changes?
- Move the open stops on the board as a block. Do not start a new chat titled ‘new list.’ Tell affected customers once from the company inbox. The October sequence stays unless a road is closed.
- Should customer texts and crew texts live in the same thread?
- No. Crew noise buries the homeowner who says the drive is full of cars. Customer messages belong in Conversations. Crew assignment belongs on the board. Mixing them is how you miss an abort and still invoice a full push.
- When does a small plow crew need GPS?
- When two trucks are out and ‘where are you’ is a 4 a.m. phone tree. GPS on Growth answers who is actually free. It does not replace a published list. Track a plan, not a scramble.
- Who owns the 4 a.m. call?
- One named person. If dispatch is ‘whoever wakes up first,’ you will miss the customers who needed you before their commute. Write the owner in October. Snow dispatch is not a group decision at 3:50 a.m.
- Which MowProHQ plan includes snow dispatch?
- Dispatch, GPS, unlimited seats, a live site, and timeclock sit on Growth at $39 a month. The property list, schedule, quotes, invoices, dual pricing, portal, and Conversations inbox stay free. Pro is $89. Phone is $19. AI is $29.
