Features · Scheduling & dispatch
A schedule that holds when the day doesn't.
Cancellations, emergencies, techs stuck in traffic. The board absorbs all of it. Every schedule looks perfect at 7 a.m.; what matters is what happens to it by noon.
Scheduling & dispatch
- The boardevery job, truck, overlap
- Reassignmenta drag, not a phone tree
- Customer textsconfirm · delay · en route
- SinceJun 2025 · shipped
Why it matters
The argument, in three rows.
A truck that's driving isn't earning
Jobs sequence by geography so the day spends its hours on work, not windshield. The gap in the afternoon is visible at 6:40, not at 2 p.m.
The day goes sideways on schedule
A burst line jumps the queue; the board reshuffles; every affected phone updates itself. The emergency is an insertion, not a meltdown.
The customer hears it first
Confirmations, delay notices, and status texts go out from the board, before the customer wonders, not after they call.
Run the day
Built where the work happens.
Every operating feature answers to one test: does it hold up in a crawlspace, on a ladder, with one hand.
Up close
How it runs.
One Friday, start to finish
A cancellation at 9, an emergency at 11, a truck stuck at 2, and a board that ends the day full anyway, with every change logged and every customer told.
Capacity, planned ahead
Recurring visits place themselves, and the weeks ahead show how booked each day already is, so the quiet week gets a capacity push before it arrives.
The right tech, not just the next one
Skills and licenses match to the work, and multi-day installs hold their crew across the days.
On the roadmap
What is still being built. In its own words.
Drag-and-drop with double-book warnings
In development
Daily route optimization
Planned
Fleet connectivity: $20 / device, posted
Later
Start
One bill. Every module.
$99 / company. Unlimited people. Plus metered usage. $15 included each month. Nothing on this page is a tier.
Waitlist open. One email when your invite is ready, nothing else.
Coming from a suite? We’ll extract your records.
Rather talk first? Email the team.

