Dispatching 5+ vans without a dispatcher

You can run five or more vans without a full-time dispatcher if three things are true: every job arrives with the information needed to assign it, assignment follows written rules instead of gut feel, and you can see where every van is without calling anyone. Get those right and the owner’s job shifts from moving jobs around all day to handling the few exceptions. This article covers how to set that up, and the point where a human dispatcher is still worth hiring.

Key takeaways

• Zone your service area and give each van a home zone. It cuts drive time before any software is involved.
• Book time windows, not exact times, and cap jobs per window per van.
• Score techs on distance, skills, workload and job value. The nearest tech is often the wrong one.
• Keep a standard parts load on every van so most jobs are one-visit jobs.
• Use GPS arrival detection and idle alerts so you manage by exception, not by phone call.

Why dispatch breaks at five vans

With one or two vans, the owner is the dispatcher and it works. Somewhere between three and five vans it stops working, for predictable reasons:

• The phone never stops. Customers call to book, techs call to ask where next, customers call to ask where the tech is.
• The day gets rearranged by hand. One job runs long, one customer isn’t home, and the whole afternoon has to be redone.
• The best tech gets overloaded. Owners send hard jobs to the tech they trust, who ends up two hours behind while others sit idle.
• Drive time creeps up. Jobs get assigned in the order they come in, so vans crisscross the metro.

The fix is not a person sitting at a desk all day. It’s a set of rules that a system can apply every time.

Step 1: zone the service area

Split your metro into zones that a van can cross in 20 to 30 minutes at normal traffic. Use highways, rivers and bridges as boundaries, because they’re where drive times jump.

• Give each van a home zone where it starts and ends most days.
• Allow one neighboring zone per van for overflow.
• Keep one floater van (or tech) once you pass six or seven vans, for emergencies and fleet calls.

Every metro is different. Our city guides cover how the geography shapes routing in 30 US metros, for example Austin, where I-35 and the river split the area in ways that matter for scheduling.

Step 2: book windows, not times

Promise a two-hour arrival window and cap each window per van. A simple template for a five-van operation:

Caps are an example. The point is that the booking system, whether a person, a web form or an AI receptionist, can see when a window is full and offer the next one instead of overbooking. Customers accept a window if it’s confirmed by text and they get a heads-up when the tech is on the way.

Step 3: score techs, don’t just pick the nearest

“Nearest available tech” is easy and usually wrong. A better rule scores every eligible tech for every job on four things:

1. Distance and ETA from where the tech will be, not where they are now.
2. Skills and certifications. Brake-certified, diesel, electrical, fleet-approved.
3. Workload. How many jobs they already have today and how far behind they are.
4. Job value. A high-value diagnosis goes to the tech most likely to finish it on the first visit.

Here’s what that looks like on the simulated Lone Star Mobile Auto day in our demo (sample data). A caller books a brake job for a 2019 Honda CR-V. The system scores three techs:

The reasons matter as much as the score. When the system writes “Marcus: 94. 1.8 mi, brake-certified, 2 jobs today.”, you can check its logic in one second and override it if you know something it doesn’t.

You can do this on paper with a points table for a while. At five or more vans and 20+ jobs a day, doing it by hand for every booking is where the owner’s day goes. Dispatch AI does it in under a second per job. In our own operation the result was +30% revenue per job from ML dispatch, in our backtest, largely by matching higher-value jobs to the techs who complete them.

Step 4: put the right parts on every van

Dispatch fails when the right tech arrives without the part. Keep a standard van load based on your top jobs:

• Brake pads and rotors for your most common vehicles
• Batteries in the three or four group sizes you install most
• Wipers, bulbs, fuses, filters, fluids
• Serpentine belts for your top models

Track what each van carries. When a job needs a part the assigned van doesn’t have, the scoring should either pick another tech or build a parts stop into the route. Scanning parts at install also gives you a clean record for warranty.

Step 5: see every van without calling anyone

Without a dispatcher, visibility has to come from the vans themselves:

• Arrival detection. The tech app marks a tech arrived when GPS shows the van at the job address. No “I’m here” call.
• On-the-way texts to the customer, triggered when the tech departs for the job.
• Stationary alerts. If a van sits somewhere that isn’t a job or a parts store for longer than a set time, you get an alert. On the simulated Lone Star day, Tyler’s van #6 triggers one after 22 minutes. Most of the time there’s a normal reason; the point is that you find out without having to ask.
• Proof of visit. Time-stamped arrival, photos and parts scans settle disputes about whether work was done.

This is management by exception: you look at the board when something turns amber or red, not every ten minutes.

Step 6: a daily rhythm

A dispatcher-free operation still needs a routine. One that works:

Taking payment on site, by card or pay link, closes the loop. A tech who collects cash should see it on a ledger the same day; Payments & Payouts keeps that ledger and handles payouts.

When to hire a dispatcher anyway

Software handles the routine. Some situations still need a person:

• Many fleet accounts with custom rules (approved techs only, PO numbers, specific windows).
• Heavy same-day emergency volume, such as roadside work, where customers need reassurance on the phone.
• Roughly 15 to 20 vans across several zones, where exceptions alone fill a day.
• Complex customer service: complaints, comebacks, warranty disputes.

Even then, the dispatcher’s job changes. Instead of assigning every job, they handle exceptions and customers while the system does the scoring. One person can then cover far more vans.

Getting started

If you’re at three to five vans and the owner is the dispatcher, start this week:

1. Draw your zones and assign home zones.
2. Switch to two-hour windows with caps.
3. Write a simple scoring table: distance, skills, workload, value.
4. Standardize the van parts load.
5. Put GPS arrival and on-the-way texts in place.

Then make sure the calls that fill the board get answered; see how mobile mechanics lose 30% of their calls. And price the drive time you’re now saving correctly with the mobile mechanic pricing guide.

To see scoring, live van positions and stationary alerts on a full simulated day, watch the demo, read about software for mobile mechanics with multiple vans, or see pricing.

Written by the Ride N Repair OS Operations Team. Built by the team running 160,000+ repair jobs.