Split dispatch into three parts (booking, the morning check and handling exceptions), give each a fixed time block, and write down the rules so booking decisions don't need you. The goal is that most of the day runs on rules and only the real exceptions reach whoever is covering dispatch.
Whether you should hire a dispatcher at all is covered in dispatcher or software. This page assumes the answer is "not yet," and the job falls to the owner, an office manager or a lead tech.
Why part-time dispatch breaks
A full-time dispatcher handles three different kinds of work all day:
- Booking: fitting new jobs into the schedule.
- Running the day: making sure each tech's plan holds, and adjusting when it doesn't.
- Exceptions: sick calls, emergencies, jobs that run long, angry customers.
When someone does that part-time, all three arrive as interruptions, and every interruption costs focus. Worse, booking decisions made in a hurry (any open slot, any tech) create the exceptions later in the day. The fix is to separate the three and remove as much of the first one as possible.
Part 1: take booking off your plate
Booking is where most of the time goes, and it is the most rule-based. Write the rules down:
- Which techs can do which job types.
- How long each job type takes, from your actual on-site times, not a guess.
- Which areas each tech covers, or which days each area gets.
- Minimum notice before a booking, and how far ahead you book.
Once the rules exist, anyone in the office, or the customer, can book. Online booking does the most for a part-time dispatcher, as long as it only offers times a tech can actually make. If it offers any empty slot regardless of the drive, it just creates the morning's problems faster.
CrewLink's booking page offers only start times a qualified tech can actually make, counting their other jobs, their calendar, time off and the drive from the previous job. A picked time is held for 5 minutes and rechecked against the live schedule, so two people can't book the same tech for the same time.
Part 2: a 20-minute morning check
Block 20 minutes before the first truck leaves. Go through each tech's day:
- Is anything impossible: two jobs too far apart for the gap between them, or a job that needs parts the truck doesn't have?
- Are there gaps you can fill from the waitlist or from flexible work?
- Is anyone overloaded compared to the others?
Fix those now, while customers can still be told calmly. The dispatch day planning guide covers how to check a day against drive time.
Add a second, shorter check at midday: who is running late, and what has to move.
Part 3: exceptions, with a playbook
Exceptions are what you actually need a person for. Make them faster with written playbooks:
| Exception | First move |
|---|---|
| Tech calls in sick | Rank their jobs by cost of moving, place the top ones, call the rest early |
| Emergency call | Find the nearest qualified tech with a gap, or quote the first morning slot |
| Job running long | Decide early: extend and move later jobs, or come back another day |
| Customer not home | Call once, wait a set time, then move on and rebook |
Let techs handle the simple ones themselves. A tech who knows the "customer not home" rule doesn't need to call the office.
Let techs see the board
Much of a dispatcher's day is answering "where am I going next" and "what's the gate code." Put each tech's day, with addresses and notes, on their phone. Let them tap on my way, arrived and done so you can see where things stand without calling anyone.
A live view of every tech's status turns "call everyone at 11" into a 30-second look. CrewLink's live board shows a status dot for each tech (green if they will arrive at least 5 minutes early or are on site, yellow if between 5 minutes early and 10 minutes late, red if more than 10 minutes late, grey when done for the day), what they're doing and the ETA to their next job.
The arithmetic of part-time dispatch
Every number is invented for the example. The shape is what matters: booking and check-in calls are most of the time, and both shrink when the rules and the status updates exist.
When it's time to hire
If exceptions alone take more than a couple of hours a day, or you find yourself dispatching from the truck, the job is outgrowing part-time. The glossary entry on dispatching breaks down what the role covers, and dispatch software for small business covers what to look for in a tool.
What to take away
- Split dispatch into booking, running the day and exceptions.
- Write booking rules (skills, durations, areas, notice) so others, or customers, can book.
- Block a 20-minute morning check and a short midday check.
- Keep a one-line playbook for each common exception, and let techs handle the simple ones.
- Give techs their day on their phone and use their status taps instead of check-in calls.
Common questions
Can the owner be the dispatcher?
Yes, in many small companies the owner dispatches. It works when booking runs on written rules and the owner does two short daily checks rather than reacting to every call. It stops working when exceptions take most of the day.
How many trucks before you need a full-time dispatcher?
There is no fixed number. It depends on job length, how many jobs are booked same-day and how much of booking runs on rules. Watch the hours spent on exceptions; when they eat a large part of someone's day, it's time.
Can technicians dispatch themselves?
Partly. Techs can handle simple exceptions, like a customer not home, with a written rule. Letting techs pick their own jobs usually leads to uneven days and more drive, so keep booking decisions under one set of rules.
Does online booking work for small service companies?
It can, if it only offers times a qualified tech can reach, including the drive from the job before. Booking that offers any empty slot creates conflicts the person on dispatch has to fix later.