Dispatching is deciding who goes where, and when, then telling them. That’s the whole idea. In field service it means taking the day’s booked work, matching each job to a tech, putting those stops in an order that doesn’t waste the day, and getting it out to the crew so everybody knows where they’re headed next. At a small shop that might be the owner doing it from the truck at six in the morning. At a bigger one it’s a person at a desk watching a screen full of trucks. Same job, different chair.
What a dispatcher actually does
Picture the morning. You pull up the day and see what’s booked, who’s on the clock, and roughly where everyone is. Then you match the work to the people. Jim does boilers, so the boiler call is Jim’s. The job across town goes to whoever’s already on that side of the map. You send each tech their next stop with the address and whatever the customer told you on the phone. A job runs two hours long, an emergency drops in, somebody calls in sick, and you move the pieces around to cover it. That’s dispatching. The same handful of decisions, made over and over, all day.
Dispatching and scheduling aren't the same thing
These two get mixed up constantly. Scheduling is the plan you made ahead of time: Tuesday at ten, we’re at the Henderson place. Dispatching is the day of. Who’s actually rolling to the Hendersons, are they running behind, does the two o’clock need to slide because the morning blew up. Scheduling fills the calendar. Dispatching runs the day that calendar turns into. One looks a week ahead. The other is happening right now, in your hand.
Why it matters more than it sounds
Bad dispatching bleeds money, and it does it quietly. A tech drives clear across town for one job, then doubles back an hour later for the next, because nobody grouped the stops. That’s windshield time: gas and an hourly wage spent going nowhere. A customer waits past their window because no one thought to text that the tech got held up, and now you’ve got a one-star review brewing. An emergency call sits for forty minutes because nobody saw it land. None of this shows up as a line on your P&L. It’s just the difference between a day that pays and a day that leaks.
“Windshield time never shows up on an invoice. It still costs you a tech's whole afternoon.
How small shops actually handle it
Almost everyone starts with a whiteboard and a group text, and honestly, that holds up fine at three trucks. Push past that and it starts dropping things. A job falls off the board. Two guys get sent to the same address. The new tech never got the note about the gate code. You don’t need a dispatcher at a desk yet, that’s a later problem. What you need first is one shared place the whole crew can see: a calendar that lives on everyone’s phone, jobs with the address and the history attached, and a way to move a stop so that everybody sees it move the second you do.
Where ToolbagCRM fits
This is the thing a field service CRM is for. ToolbagCRM keeps your jobs, your customers, and the schedule in one place the whole crew pulls up on their phones, so the day isn’t living in your head and a text thread. Scheduling the calendar is part of the core, no card needed. Dispatch runs as a plug-in on top of it when you’re ready for it. If you’ve outgrown the whiteboard, you can get started on founders pricing and see whether it fits how you already run the day. See plan terms, plug-in slots, and payment fees.