Plumbing
Dispatch and scheduling for plumbing shops: fewer windshield hours
Updated · Alvin
A plumbing dispatcher's job is to put the right tech on the right job in the right order, so nobody drives across town twice. Smart dispatch groups jobs by area, matches each job to a tech with the right skills, and holds a slot or two open for emergencies. Alvin proposes the day's board each morning from your jobs and techs; the dispatcher reviews and approves it.
Where the whiteboard breaks
The classic dispatch setup is a whiteboard, a phone that never stops, and one person holding the whole day in their head. It works until it doesn't: the emergency call at 9am, the tech who calls in sick, the job that runs three hours long. Then the board gets re-drawn from memory, two customers get bumped, and a tech spends forty minutes crossing town because the new job landed on the wrong side of the map.
Windshield time is the quiet tax. Every hour a tech spends driving is an hour they aren't billing, and customers feel it too — the arrival window stretches, the "on my way" text comes late, and the shop looks disorganized. The fix isn't better techs. It's a board built around geography, skill, and buffers.
The three principles
Group by area. Each tech works one part of town per half-day. Jobs cluster; drive time collapses. A tech doing four jobs inside one zip code finishes more work than a tech doing four jobs across the metro, even at the same pace per job.
Match skill to job. Not every tech should do every job. Sewer and drain work goes to the tech with the camera and the experience. Water heaters go to whoever is fastest at them. Sending the wrong tech wastes the visit and usually means a second truck roll.
Hold emergency slots. Plumbing is an emergency business pretending to be a scheduled one. If the board is packed edge to edge, the first burst pipe of the day destroys the afternoon. Holding one or two slots open — or keeping one tech's afternoon flexible — turns emergencies from schedule-wreckers into just another booked job.
How Alvin builds the board
- Pull the day's jobs. Overnight, Alvin reads every scheduled job from your system: addresses, job types, promised windows, and any customer notes.
- Cluster by geography. Jobs get grouped so each tech's route stays tight — minimal backtracking, sensible order from first call to last.
- Assign by skill. Each job goes to a tech qualified for it, preferring the tech who does that work fastest. Certifications and specialties are part of the assignment, not an afterthought.
- Reserve emergency capacity. The board keeps its held slots visibly open, so when the emergency call comes in, dispatching it is one decision instead of a re-plan.
- The dispatcher approves. The proposed board arrives for review — usually a two-minute look. The dispatcher adjusts for the things only a human knows (the tech with the dentist appointment, the customer who needs the senior guy) and approves. Then it's locked and techs get their day.
Midday changes without the chaos
The board is a plan, not a prison. Jobs run long, emergencies land, techs call out. When something changes, Alvin re-balances: the affected jobs move to the next open window or to another tech in the same area, and the affected customers get a text with the new arrival time before they have to ask. The dispatcher approves the re-plan — nothing moves without a human okay — but the re-plan itself takes seconds instead of a phone-tag afternoon.
Customers notice the difference. "Running 45 minutes behind, new window 2:30–3:30" sent proactively reads as professionalism. Silence followed by a late tech reads as the shop not caring. Same delay, opposite review.
What Alvin handles vs. what stays with the dispatcher
| Alvin does | Dispatcher does |
|---|---|
| Assembles the morning board: jobs, routes, skill match, emergency slots | Reviews and approves the board — two minutes most mornings |
| Texts customers their arrival windows and "on my way" updates | Handles the 7am sick call and the judgment calls only a human makes |
| Re-balances the board when jobs run long or emergencies land | Approves every re-plan before it goes out |
| Tracks actual vs. planned times so tomorrow's board gets smarter | Coaches techs whose job times keep drifting |
| Logs every change on the job timeline | Talks to the angry customer — with the full thread in front of them |
Nobody hired a dispatcher to drag magnets across a whiteboard. Alvin does the assembly; the dispatcher does the decisions. The role gets more valuable, not less — it just stops being data entry.
The rules that keep the board honest
- The schedule is the source of truth. If a tech's day isn't in the system, Alvin can't route around it. Keep time-off, on-call, and shift changes current.
- Emergency slots are sacred. Don't fill the held slots with "quick" planned jobs. The moment you do, the emergency goes back to wrecking the afternoon.
- Promise windows you can keep. A two-hour window you hit beats a one-hour window you miss. Alvin plans from actual drive and job times, not optimistic ones.
- Customers hear about delays first. A proactive text about a late arrival protects the review. A customer who has to call you has already decided how the review reads.
A clean board also makes everything downstream easier — including answering every new lead in under a minute, because Alvin books from the real schedule instead of guessing.
What it costs to keep dispatching by memory
For example: a 12-tech shop where each tech loses an hour a day to avoidable drive time and re-routing is paying for a full extra truck that does no work. Add the bumped customers, the second truck rolls from wrong-tech assignments, and the dispatcher spending half the day on the phone re-explaining the plan, and the whiteboard is one of the most expensive tools in the shop. The board Alvin proposes each morning costs minutes. The chaos it replaces costs jobs.
Frequently asked questions
How should a plumbing shop organize its daily dispatch board?
Group jobs by area so each tech works one part of town, match each job to a tech with the right skills, and leave one or two slots open for emergencies. Alvin proposes the board each morning from your jobs, techs, and territories; the dispatcher reviews and approves it.
How do you handle emergency calls without wrecking the day's schedule?
Hold emergency slots on purpose instead of squeezing calls in. Keep one tech's afternoon flexible or leave buffer windows in each route. When an emergency lands, it fills a held slot instead of blowing up three other jobs — and customers with planned work stop getting bumped.
Should dispatch match tech skills to jobs, or just fill the board?
Match skills to jobs. Sending a junior tech to a repipe diagnosis wastes the visit and the customer's patience. Alvin knows each tech's skills and certifications, so sewer work goes to the sewer tech and water heaters go to whoever is fastest at them — which also shortens average job time.
What happens to the schedule when a job runs long?
The board re-balances. Alvin flags the overrun, moves the affected jobs to the next open window or another tech in the same area, and texts the affected customers with the new arrival time. The dispatcher approves the re-plan — nothing moves without a human okay.
Does the dispatcher still have a job if Alvin proposes the board?
Yes — a better one. Alvin does the tedious assembly: sorting jobs, checking drive times, matching skills. The dispatcher does the judgment: approving the board, handling the 7am sick call, and making the calls that need a human voice. Nobody hires a dispatcher to drag magnets across a whiteboard.
More jobs per tech, fewer miles between them.
Alvin is the personal assistant for plumbing companies — dispatch, lead response, invoicing, and reviews, all from one request. See what Alvin handles for your trade.
Alvin for Plumbing