TUESDAY · 9:07 AM
HVAC, plumbing & electrical dispatch scheduling
A no-heat call just landed on a full board.
Four techs, eleven jobs, and a furnace that died overnight in a house with a newborn. The board didn’t break because your dispatcher is bad at the job — it broke because every one of those jobs is a chain of dependencies: a gas ticket, a parts stop, a drive, a break window, a promise to a customer. Scheduling that ignores those chains hands the whole tangle to a person at 9:07 a.m. Crisphive carries it instead — so your people don’t have to.
This demo replays a real kind of morning: one emergency lands, and every job finds a new slot without breaking a promise. See how it works ↓
Jobs moved: 0SLAs broken: 0Dispatcher calls: 0
Every field service day is a dependency graph. Most software pretends it isn't — and hands the graph to a dispatcher to solve in their head, under pressure, forty times a day. We think the schedule should carry that weight, not your people. That's the whole company.
— Why Crisphive exists
How it fits your day
When the day changes, the schedule keeps up.
Crisphive is the layer that carries your day’s dependencies — every job, every promise, every crew constraint — so when something breaks, the plan repairs itself instead of landing on a person. You keep your intake, your CRM, your customer relationships. Crisphive just holds the tangle underneath so the day keeps its word.
The day changes
The disruption arrives however it comes — a phone call, a no-show, a truck that won’t start, a furnace down overnight. Crisphive catches it the moment it hits the board.
The schedule recomputes
The schedule recomputes around every hard rule — certifications, travel, supply runs, breaks, arrival windows — and hands back a new plan plus a backup.
Your team is notified
You confirm the plan once — your techs are re-routed and your customers are notified. Nothing else needed.
You never rebuild the day by hand. The schedule recomputes around the disruption, keeps every promise it can, and shows you exactly what moved before anything goes out. Confirming the new plan takes one click.
The rules of your day
Hard rules, not suggestions.
A schedule that ignores these rules isn’t scheduling — it’s guessing, and someone in a truck pays for the guess. Every plan Crisphive hands you respects all of them. No exceptions, no “hope the tech makes it.”
Certification matching
A no-heat call needs a gas ticket. The schedule only assigns techs whose licenses cover the job — Marco (GAS-1) gets the furnace, not Sam.
Supply-run insertion
The emergency needs an igniter the truck doesn’t carry. The schedule adds the wholesaler stop with real travel time, visible on the board and never billed to the customer.
Travel, mob & demob
Drive time is figured per leg, plus setup and teardown at each site. Wrench time is what’s left — and the plan tells you exactly how much.
Break windows
Break rules are hard rules, not suggestions. The schedule moves a job before it eats a tech’s lunch window — your customer never finds out the compliant way was optional.
Arrival-window SLAs
Confirmed arrival windows are protected by default. The board above moves five jobs and breaks zero promises — that’s the engine refusing a plan a person under pressure would accept.
Priority-aware booking
Emergencies jump the queue without knocking anyone’s promise loose. You see the full list of what moves — and any warnings — before you confirm a thing.
Getting started
Up and running in three steps.
Add your techs and their licenses
Sign up and add your techs with their licenses, skills, and vehicles — the things the schedule has to respect before it assigns a single job.
Bring in your jobs and customers
Bring in the week’s jobs and customers — by import or alongside the tools you already use. Confirmed arrival windows come with them, protected from the start.
Let the day run itself
From then on the schedule keeps itself. Emergencies slot in, affected jobs move, and your team and customers hear about it automatically — you just confirm.
⏱ Most teams are live within a week — no technical setup
Outcomes
What changes for you. What your customers feel.
You — running the business
A calm morning, even when the day goes sideways.
- Your dispatcher gets their morning back. Forty minutes of rebuilding the board becomes one confirmation click.
- Promises kept without heroics. Confirmed arrival windows hold because the schedule protects them, not because someone hustled.
- More wrench time, less windshield time. Every re-plan tightens the drive, the supply stop, and the sequence — billable hours go up.
- A straight answer when a customer asks why. The plan shows what moved and why, in plain language you can repeat.
Your customers
One emergency stops wrecking everyone’s day.
- The window you promised is the window you get. Arrival times are protected by the schedule, not by luck.
- Your tech shows up on time. Every re-plan optimizes the drive and the sequence so nobody arrives late and rushed.
- Honest word when plans shift. If something changes, you hear it early — no silent no-shows.
- The newborn’s house gets heat by noon — and nobody else’s afternoon fell apart to make it happen.
Running more than one branch?
Set the rules once. They hold across every crew and branch. The certifications, supply runs, and arrival-window promises you set up for one location carry to the next — so a second branch, a third crew, or a franchise handoff doesn’t multiply the dispatcher chaos. You grow the operation without growing the morning scramble.
Why it holds up
Built for the days that go sideways.
Re-planning is free
Re-planning is free and unlimited. Trades days are volatile by nature — a no-show, a breakdown, a fresh emergency — so re-plan on every disruption without ever watching a bill.
Dependable by design
Schedules come from a deterministic engine, not guesswork — the same situation always produces the same plan. AI helps explain the plan in plain language; it never decides who goes where.
Always a plan B
Every urgent booking comes back with a recommended plan and a backup. If the customer declines the first window, the next-best option is already on the table.
What operators say
Shops that got their mornings back
“A no-heat call used to mean forty minutes of phone calls. Now it drops in, the board re-plans in seconds, and my dispatcher just confirms. We're fitting two more jobs per tech most days.”
Marcus Webb
Owner · Summit Peak Heating & Air
“Every 'smart scheduler' I'd tried just made prettier chaos. This one actually knows Danny can't pull gas permits and that the Hendersons were promised eight to ten. When a slab leak comes in, it moves what can move and leaves my promises alone.”
Rhonda Castillo
Dispatcher · Bluewater Plumbing Co.
“We opened a second branch last spring and I braced for double the dispatch headaches. The same rules carried over on day one. Billable hours per tech are up around fifteen percent, and my dispatcher hasn't stayed past five in months.”
Priya Raman
General Manager · Copperline Electric
FAQ
Questions from the field
How does emergency dispatch work when the board is already full?
Can it match jobs to gas, electrical, and refrigeration certifications?
Does it plan supply-house stops into the route?
Does it work with the dispatch software we already run?
We’re a shop, not a software company — can we use it without developers?
How does pricing work for a trades shop?
Your schedule should survive a bad morning.
Start free and watch a real Tuesday re-plan itself — emergency dropped in, techs re-routed, every window still kept. Your dispatcher just confirms.
Questions? support@crisphive.com · Free to start — no credit card required
See how the scheduling engine worksPricing — pay per job scheduled