Night Dispatch for Multi-Truck Shops

Saturday night, three trucks' worth of territory, and the after-hours line rings: no-heat call on the north side, water heater leaking on the south side, and a "funny smell from the panel" downtown. One on-call tech can't cover all three. Two techs get dispatched, one call waits till morning — and by Monday nobody can reconstruct who went where, what was promised, or which invoices are still open. The night made money; the morning lost track of it. Multi-truck night dispatch is the scale layer of the after-hours system pillar: the board, the queue, and the reconciliation that keep nights profitable and accounted for.

The on-call board (who's up, who's backup, who's dark)

At scale, "the on-call tech" becomes "the on-call rotation" — and it needs to be visible to everyone, not stored in the owner's head. The board has three tiers:

• Primary (1–2 techs): first dispatch for all after-hours calls. Two primaries for 4+ trucks — one can't cover a real Saturday night alone, and the second primary prevents the "sorry, he's already on a call" dead end.
• Backup (1 tech): dispatched when both primaries are committed or when a call needs a second skill set. Backup is paid standby, not free availability — the stipend is what makes the phone get answered.
• Dark (everyone else): explicitly off. Phones on do-not-disturb, no guilt, no "just this once" — the dark tier is what makes the rotation sustainable. A tech who's dark but still gets called isn't on a rotation; he's on call forever.

The board rotates weekly and publishes every Friday by noon — in the group text, on the shop whiteboard, wherever your techs actually look. Include the escalation path: primary → backup → owner (owner is the last resort, not the first call). And include the triage rules for the night crew (below) so the primaries aren't waking the owner to ask "should I roll on this?"

The triage queue (sorting the night's calls)

Multiple simultaneous calls need a queue with priority rules, not a free-for-all. The night dispatcher — which may be the primary tech, a dedicated dispatcher, or an answering service with your script — sorts every call into three lanes:

• Lane 1 — Roll now: safety issues and active damage. No heat in freezing weather, active water intrusion, electrical hazards, sewer backups. Dispatched immediately to the nearest primary.
• Lane 2 — Schedule tonight, serve in order: urgent but stable. No AC in 95-degree heat with elderly residents, water heater out (cold showers are miserable, not dangerous). Queued by call time; the dispatcher texts each customer their position: "You're second in the queue — expect [Tech Name] around [time]."
• Lane 3 — Morning queue: everything that can wait. The dispatcher books them into tomorrow's first slots and texts the confirmation. Lane 3 is where the morning-vs-night choice (from the emergency pricing system) does its filtering — many callers choose morning when offered it honestly.

The queue lives in one place — a shared note, a dispatch channel in your messaging app, or the dispatch board in your field-service software (field service management software). One queue, visible to primaries, backup, and the morning office. The failure mode at scale isn't bad triage — it's three people triaging separately with no shared picture.

The morning reconciliation (where the money gets found)

This is the piece multi-truck shops skip, and it's where revenue leaks. Every morning, the office runs a 15-minute reconciliation of the previous night before the day starts:

• Every night call gets a row: caller name, address, time of call, lane assigned, tech dispatched, arrival time, outcome (fixed / parts ordered / scheduled follow-up), invoice number, amount, paid or open.
• Open invoices get today's follow-up. Night work has the worst payment discipline — the tech was tired, the customer was stressed, nobody closed the loop. The reconciliation catches every open night invoice and fires the payment-request text that morning.
• Follow-ups get scheduled. "Parts ordered" from last night needs a parts-tracking entry and a customer update text. "Scheduled follow-up" needs a real appointment on today's or tomorrow's board. The night's loose ends become the morning's tasks — nothing evaporates.
• The board gets reviewed. Did the primaries get overwhelmed? Did Lane 2 waits stretch past 90 minutes? The reconciliation is also the feedback loop for staffing the rotation — add a second primary on Saturdays if the queue says you need one.

Example reconciliation sheet (one Saturday night, 5-truck HVAC shop):

Four calls, every outcome accounted for, the open invoice chased the next morning, the follow-up on the board. That's the reconciliation doing its job: the night's revenue captured, the night's promises kept.

The night-dispatch setup guide (one page for the crew)

Laminate the night protocol for every primary and backup: (1) check the shared queue before rolling anywhere; (2) update the queue when dispatched, arrived, and complete — three timestamps, no exceptions; (3) quote the after-hours rate before dispatch, every call; (4) text the customer at dispatch ("rolling now, ETA [time]") and at completion (the job summary); (5) log parts used and invoice numbers in the queue before going home. Five rules. The queue is the source of truth; the morning reconciliation reads the queue. If it wasn't logged, it didn't happen — and the invoice doesn't exist until it's logged.

When to add a dedicated night dispatcher

The primary-tech-as-dispatcher model works until the call volume breaks it — the sign is primaries missing triage texts because they're under a house. The threshold for most shops: when after-hours calls regularly exceed 4–5 per night, or when you've got 6+ trucks. Options in order of cost: a part-time dispatcher working from home (evenings only, paid per shift), an answering service running your triage script (cheaper, less flexible), or a full-time dispatcher with night coverage as part of the role. The math that justifies it: one lost Lane-1 call per week to a missed triage, at your average emergency ticket, versus the dispatcher's shift cost. At multi-truck scale, the dispatcher usually pays for themselves in captured calls alone — before counting the reconciliation discipline they bring.

Related guides in this series

Night dispatch is the scale layer of the after-hours lead capture pillar — the triage, text-back, and pricing systems that work for a single on-call tech, extended across a rotation with a shared queue and a morning reckoning. The reconciliation is the discipline that separates shops where nights are profitable from shops where nights are merely busy.

The done-for-you version

This post is System 6 from the Leveraged Owner Starter Pack — the done-for-you version with the full step-by-step setup guide, every script, the worksheets, and screen-by-screen setup instructions for all 8 systems. The on-call board template, the triage lane definitions, and the morning reconciliation sheet are pre-built and ready to use.

Stats sourced as labeled: no statistics used in this post.

Keep building your systems

Related guides from the Leveraged Owner blog: