Crew dispatch and scheduling built around how household movers actually operate. Capacity caps, COI gating, route optimization, and the end-of-day debrief — in one system the sales team and the dispatcher can both see.
You can have the fastest lead response in your market, the most polished estimate, the best Google reviews on the block — and if dispatch falls apart at 6:30 AM on a Saturday in June, you lose the day, lose the customer, and lose the crew.
The seven dispatch failures that quietly drain moving-company margin — overbooking, wrong crew composition, no-shows, COI mishaps, curbside paperwork, scope creep, skipped debriefs — are all structural problems with structural fixes. The companies that scale past five trucks are the ones that have engineered each failure mode out of the operation instead of relying on the dispatcher's brain.
The full playbook lives in our field note: Dispatch Without Drama: A Playbook for Scheduling Moving Crews That Don't Burn Out.
| Operation | Whiteboard / spreadsheet | ZapTheMove dispatch |
|---|---|---|
| Daily capacity | Implicit, depends on dispatcher's memory | Hard cap, surfaced to sales in real time |
| Move complexity | Guessed at intake, fixed at curb | Scored at intake, drives crew + truck sizing |
| COI workflow | Sales flags, dispatch may miss | Captured at intake, gated day-before |
| Crew assignment | Round-robin or "who's free" | Match crew strengths to move type |
| Paperwork | Signed at the curb on a clipboard | Sent and signed in advance, confirmed at start |
| Scope creep | Crew judgment call, often unbilled | Signed re-quote protocol before extra work begins |
| End-of-day debrief | Usually skipped, info lost | 5-min structured debrief in the same system |
| Source of truth | 3+ calendars, reconciled weekly | One record across sales, dispatch, ops |
Dispatch lives in one person's head and on a marker board. Works at five trucks. Starts breaking at ten. A dispatcher leaving takes the whole company's institutional memory with them.
Better than whiteboard. No integration with sales or intake. Reconciliation between three calendars is a weekly job. Sales books moves dispatch doesn't see until Monday.
Salesforce, HubSpot, or similar with custom fields. Better data hygiene, but the system wasn't built for movers. Half the fields don't fit. Customizations rot over time as plugin versions change.
Integrated intake, quoting, dispatch, and post-move workflow in one record. ZapTheMove is one option; there are others. The key feature is the same system that captured the lead is the one the dispatcher works in.
A hard daily capacity number is configured during onboarding — typically based on your last six months of actual move data, not theoretical truck count. Sales sees the cap in real time when booking; exceeding it requires an explicit dispatch approval, not a sticky note. Overbooking is the single most common dispatch failure and the easiest to engineer out.
Every move gets a score at intake based on room count, stairs, walk-up vs elevator, special items (pianos, gun safes), long carries, and COI requirements. The score drives recommended crew size, truck size, and time allocation. Crew composition becomes a calculation, not a guess — see our field note on the seven dispatch failures for the full breakdown.
COIs are captured at intake (the AI asks about destination building requirements), routed to your COI process, and surfaced to dispatch as a checklist gate the day before every move. No move starts without explicit COI verification — eliminating the "showed up at a building that won't let us in" failure mode.
You configure a backup pool per shift — typically 110% of slot count for peak Saturdays. When a driver flags unavailable (or no-shows in real time), the system pages the bench and re-routes assignments. The cost of carrying that bench is real; the cost of not having it is catastrophic.
Yes. The dispatch board reads from the same data as the sales calendar and the lead intake. We integrate with most common scheduling and CRM tools. The principle is one source of truth — sales, dispatch, and the lead-handoff workflow all reading from the same record so reconciliation is not a Monday-morning job.
Yes. Bill of lading, inventory, high-value declaration, and released-value coverage acknowledgment are sent to the customer in advance, signed in advance, confirmed at the start of the move. FMCSA bill-of-lading requirements for interstate moves are non-negotiable and digital execution makes compliance easier, not harder.
A sub-five-minute structured debrief in the same system that holds the lead and the move. What went well, what went wrong, customer feedback, any damage. The volume of operational learning lost to skipped debriefs is enormous; making it five minutes and same-system removes most of the friction.
Generic field-service tools expect you to design your own move-complexity scoring, COI workflow, FMCSA bill-of-lading logic, and crew-to-move matching. ZapTheMove ships with those already built for household movers. Setup is configuring your specific rules, not building the system from scratch.
The seven dispatch failures that quietly drain moving-company margin — and the structural fixes that make crew operations less chaotic and more profitable.
Read →COI handling is part of your trust stack — buildings know which movers can deliver them reliably. Includes a five-layer trust diagram.
Read →Capturing the after-hours lead is half the battle; dispatching it well the next morning is the other half.
Read →A 20-minute walkthrough using your actual booked moves, your real crews, and your last 30 days of dispatch decisions. We will pull the failure modes you are bleeding margin to and show you what changes.
Get started →No card. No commitment.