On this page
Dispatching is deciding which technician or crew goes to which job, in what order, and keeping everyone updated as the day changes. Good dispatch matches skills to the job, groups work by area, leaves room for urgent calls, and tells customers when the crew is on the way. Run it on a daily rhythm: plan the night before, confirm in the morning, adjust at midday and close out before the trucks park for the night.
Key takeaways
- Scheduling books the appointment. Dispatching decides who goes, in what order, and handles the changes.
- Assign by skill first, then location, then capacity and customer history.
- Hold a little open capacity each day for emergencies and same-day work.
- On-the-way texts cut missed appointments and calls to the office asking where the tech is.
- Watch on-time arrival, jobs per tech per day, drive time and callbacks.
In a one-truck company, dispatching is the owner looking at tomorrow's jobs over dinner. Add a second truck and it becomes a real job: who gets the water heater install, who takes the emergency leak at 10 a.m., which crew is closest to the customer who just called back. Done badly, dispatch shows up as late arrivals, crisscrossing routes, overtime, angry customers and techs sitting idle while work waits across town.
This guide covers the basics of running dispatch in a small service business: what the job is, how to assign work, a daily rhythm, handling emergencies, and the numbers that tell you whether it is working. No software sells this for you; the habits matter more than the tool.
What is the difference between scheduling and dispatching?
The two get blurred, but they are different jobs:
- Scheduling is booking the appointment: the customer, the service, the day and the arrival window. It happens when the customer calls, books online or approves a quote.
- Dispatching is turning those appointments into a workable day for each tech or crew: who goes where, in what order, with what parts and information, and what changes when the day does not go to plan.
In small companies the same person often does both, which is fine. What matters is that someone owns dispatch every day and that the field knows who that person is. A tech should never have to guess who to call when a job runs long.
How to decide who gets which job
Use a simple order of priorities when you assign work:
- Skills and qualifications. Can this person do this job, safely and to your standard? Some work requires specific training, certifications or licenses under your state's rules. Never send someone who is not qualified because they are closest.
- Location. Group jobs by area so trucks are not crossing town. For grouping stops into tight loops, read route optimization for service businesses.
- Capacity. Realistic job durations plus drive time. If a tech's day only works when every job goes perfectly, it will not work.
- Equipment and parts. The right truck, the right trailer, the parts on board. A tech who has to stop at the supply house mid-route loses an hour.
- Customer history. Repeat customers often prefer the same tech. Customers with a past complaint deserve your most reliable person.
Track how long each job type actually takes, by tech. After a few months you will know that a standard install takes your senior tech three hours and your newer tech four, and you can schedule each day accordingly instead of by hope.
A daily dispatch rhythm
| When | What dispatch does |
|---|---|
| Afternoon before | Build tomorrow's routes; check parts, equipment and access notes; send appointment reminders |
| Start of day | Short check-in with each crew; confirm the first job; flag anything unusual |
| Through the morning | Track progress; send on-the-way texts; slot in urgent calls |
| Midday | Re-plan the afternoon: who is ahead, who is behind, what can move |
| End of day | Confirm every job is closed out; reschedule anything unfinished; update tomorrow |
The midday check is the one most companies skip and the one that saves the most afternoons. A job that ran two hours long at 11 a.m. is a problem you can solve by moving one appointment and calling one customer. At 4 p.m. it is three angry customers.
Put the rhythm in writing so it runs the same when the regular dispatcher is out. Our guide to writing standard operating procedures covers how.
Handling emergencies and same-day work
For trades with urgent calls (plumbing, HVAC, garage doors, locksmiths, storm work), the emergency is often the most profitable job of the day and the one most likely to wreck the schedule. Plan for it:
- Hold some capacity open. Leave a gap in one tech's afternoon, or designate an on-call tech who takes short jobs that can be bumped.
- Define what counts as urgent. Active water leak, no heat in freezing weather, a door that will not close: yes. "I'd like it done today": maybe, at a same-day price if you charge one.
- Decide who gets bumped and how. Flexible customers (maintenance visits, quotes) move first. Call them before the original window, offer the next opening, and note it in their record.
- Capture urgent calls immediately. An emergency caller who reaches voicemail simply dials someone else. An AI receptionist can answer, ask the triage questions you set, and alert dispatch while the customer is still on the line.
Keeping customers informed
Most "where is my tech?" calls happen because the customer has heard nothing since they booked. Three messages remove most of them:
- A reminder the day before with the arrival window plus any prep the customer should handle (open the gate, move the car, secure pets).
- A heads-up text as the tech pulls away from the previous stop, ideally with the tech's name and an estimated arrival.
- A completion message with the invoice or summary and how to reach the office.
When a tech is running late, tell the customer before the window closes, not after. Customers forgive late; they do not forgive silence. Text messages need the right consent and rules, which our guide on two-way texting explains. Reminders also cut no-shows; see our list of ways to reduce no-shows.
Keeping crews informed
The tech should arrive knowing everything the office knows: what was quoted, what the customer said on the phone, the gate code, the dog, the photos from last time, and whether the customer has an open balance or a past complaint. If that information lives in someone's email or memory, the tech walks in blind.
Put it on the job. Every job should carry the scope, notes, photos and access details where the tech can see them on a phone. Changes made during the day (a new job added, a cancellation, a moved appointment) should reach the tech in one place, not as five separate texts from three people.
A worked example: one long job, three fixes
Two techs, eight jobs. At 10:40 a.m. Tech A calls in: the morning repair needs a part and will run until 1 p.m. instead of 11. Tech A still has three afternoon jobs, and one is a first-time customer with a narrow window.
- Move the most flexible job. Tech A's last stop is a maintenance visit for a long-time customer. Dispatch calls, offers tomorrow morning, and the customer agrees.
- Shift the first-time customer. Tech B's afternoon has a gap near the new customer's street. The job moves to Tech B, who gets the notes and photos on the phone.
- Tell everyone. The remaining customer gets a text with the new arrival estimate before the original window starts.
Ten minutes of dispatch work at 10:45, and nobody waits at home for a truck that is not coming.
The numbers that tell you dispatch is working
- On-time arrival: the share of jobs where the tech arrived within the promised window.
- Jobs per tech per day and revenue per tech per day: rising numbers usually mean tighter routes and better job matching.
- Drive time as a share of the day: high drive time means routes need regrouping or your service area is too spread out.
- Callbacks and second trips: often a sign of wrong tech, wrong parts or missing information.
- Same-day calls captured: how many urgent calls you could fit in versus turned away.
Review them weekly. Our guide to owner dashboard metrics shows how dispatch numbers fit with the rest of the business.
Tools: whiteboard, software or both
A whiteboard works for one or two trucks. Past that, you need a dispatch board everyone can see: a calendar view by tech, jobs that can be dragged between people, and updates that reach the tech's phone instantly. Off-the-shelf field service software does this well for many companies. Where it falls short is usually the details of your trade: your job types, your triage questions, your service area rules. A custom CRM can be built around how your company actually dispatches, with the same customer and job record shared by the phone, the office and the field.
Frequently asked questions
Do I need a full-time dispatcher?
Not at first. In small companies the owner or office manager usually dispatches. Once you run several trucks with frequent same-day changes, a dedicated dispatcher often pays for itself in fewer late arrivals and less drive time.
How much open time should I leave for emergency calls?
It depends on your trade and season. Track how many urgent calls you get per day and how long they take, then hold roughly that much capacity, or designate one tech whose short jobs can be moved.
What should an on-the-way text say?
The tech's name, the estimated arrival time, and how to reach the office. Keep it short and send it when the tech actually leaves the previous job.
What is the most common dispatching mistake?
Building days that only work if every job finishes on time. Use real job durations, include drive time, and re-plan at midday.
General information for service-business owners, not legal, tax or financial advice. Rules vary by state; check with a qualified professional for your situation.