Mobile Detailing Dispatch: Route Your Crew

For a mobile crew, the enemy isn't the work — it's the driving between jobs. Book four stops across the city in the wrong order and you've quietly handed a whole billable hour to traffic. Nobody paid you for that hour. You just spent it behind the wheel, watching a fuel gauge drop and a detailer sit in the passenger seat on the clock. The car in the driveway you're driving away from and the one you're driving toward are both worth money. The forty minutes of asphalt in between are worth nothing.

That's the thing a fixed shop never has to think about and a mobile operation lives and dies on. When the cars come to you, your capacity is bays and hours. When you go to the cars, your capacity is bays, hours, andthe map. A day that looks full on paper — five stops, everybody booked — can still lose you a job's worth of time if those five stops zig-zag across town in the order the phone happened to ring. Same crew, same trucks, same hours. Different route, different number of cars done by six o'clock.

I say this as someone who runs a fixed studio, so let me be straight: I'm not going to pretend I've spent ten years chasing driveways. But I built the scheduling in Service VIN for both kinds of shop, and the mobile operators who use it kept telling me the same thing — the software that plans when a job happens is useless to them if it ignores where. So mobile detailing dispatch here is really about where: the calendar sequences the day for them. The route is the lever, and it's the one lever most mobile shops leave lying on the ground because their booking tool treats a day as a list instead of a path.

Here's where it starts. When you mark a booking as mobile and give it a service address, it doesn't just sit as another row on a list — it becomes a stop on the day's map. Flip the calendar map view and your schedule stops being a timeline and becomes a route: numbered pins, the drive distance between them, and a suggested running order. You're not squinting at five addresses trying to hold the geography of the city in your head at 7 a.m. with a coffee in one hand. The day is drawn for you.

The suggestion isn't decoration. The map view runs a nearest-neighbor pass over the stops — plainly, it looks at where you are and picks the closest sensible next stop, then the closest one after that — and proposes an order that stops you backtracking across town. You still see the drive distances, so you can sanity-check it against what you know that the software doesn't: that the client on 17th only opens their gate after nine, that the fleet job needs to be first because the lot fills by lunch. It suggests; you decide. When the order's right, every stop has one-tap navigation, so the crew isn't retyping addresses into a maps app between jobs.

The reason I like seeing the day as a route before anyone turns a key is that it makes the bad days obvious in advance. A list of five bookings all looks fine. The routefor those same five bookings sometimes looks like a plate of spaghetti, and that's your cue to move one stop to tomorrow or call the client on the far edge of the city and offer them a slot that doesn't drag your whole crew out there for one car. You can't fix a route you can't see. Drawing it is half the win.

The map view is the office's picture of the day. But the day happens in a driveway, not at a desk, so the routing has to live where the crew lives — on the phone. That's the route optimizer in the installer app: it takes the day's stops and hands the crew a distance-optimized run of them, with a one-tap maps link at each stop. The person actually driving doesn't need to understand routing theory or open the office view. They open the app, and the next stop is the right next stop.

One word in there matters more than it looks: deterministic. The optimizer isn't a black box that quietly reshuffles your day for reasons you can't see and can't reproduce. Same stops in, same route out — every time. That predictability is the whole point for a working crew. If your dispatcher reorders the day and the app spits out something different every time they refresh, nobody trusts it, and a routing tool nobody trusts is a routing tool nobody uses. Give a crew a sequence that's stable and makes obvious sense on the ground, and they'll follow it. Give them a mystery, and they'll drive it the way they always did.

Bounding all of this are your service areas. You draw the areas you actually cover, and bookings stay inside them, so you're not optimizing a route that includes a stop two hours out of town that you never should have taken. Routing tightens the drive between the jobs you want; service areas keep the jobs you don't want off the map in the first place. Both are in the same app the crew already uses to clock in and shoot before-and-after photos — they aren't a separate login or a bolt-on you go buy from someone else.

Routing answers "what order?" Dispatch answers a question that comes first: "who?" If you run more than one van, or a couple of detailers with different skill sets, a tight route means nothing if the job lands on the crew that can't run it. So dispatch works off a bay board with eligibility built in. The manager sees the unassigned jobs, sees the crews, and assigns work to the people actually cleared for it — the board only offers a job to workers eligible for its services. Set the skills matrix once, and you stop relying on your own memory of who does ceramic and who's still learning.

The reason that matters on the road specifically: a mobile mis-assign is expensive in a way a shop mis-assign isn't. If you put a job on the wrong installer inside a fixed studio, you walk twenty feet and hand it to the right one. If you dispatch a coating job to a crew forty minutes across the city that isn't cleared to do coatings, you don't find out until they're standing in the driveway, and now the fix is another truck and another drive. Eligibility on the board is how you catch that at 7 a.m. on a screen instead of at 10 a.m. in someone's driveway.

And it's a live board, so the day isn't frozen the moment you plan it. A car runs long, a client cancels, a walk-in text turns into a real job — the dispatcher moves work between crews on the same board and everyone's view updates. Skills plus area plus a board you can actually push jobs around on. That's dispatch that reflects how your shop really runs, instead of a static list you printed at breakfast and stopped trusting by lunch.

Here's the part I most want mobile operators to hear, because it's the part that gets assumed away: going mobile does not mean giving up the scheduling safety a fixed shop takes for granted. This is the same calendar. Not a stripped-down mobile cousin of it — the same one. Which means the same database-level bay guard applies. A single-capacity resource can't hold two overlapping jobs, and that's enforced by the data layer, not by a warning popup you click past when the phone's ringing. Your real working hours apply too. The map and the routing are added on top of all that, not swapped in for it.

I labor this because a lot of mobile shops end up running two tools — some booking app for the calendar and a separate maps or routing thing bolted alongside — and the two never quite agree. A job moves in one and not the other. The route is built off yesterday's schedule. The crew's phone shows a stop the office already cancelled. Every seam between two tools is a place for the day to fall apart, and a mobile day has enough moving parts without inventing new seams. One board that's both the schedule and the route means the route is always built off the real, current schedule, because they're the same object.

So the trade you might be bracing for — lose scheduling discipline to gain routing — isn't a trade you have to make. You keep the guard that makes a double-book impossible, you keep working hours, you keep the single source of truth, and you gain the map. Mobile is a mode of the calendar here, not a different product with a different set of rules and a different set of failures.

Now the math, and I'm going to be careful here because this is exactly the place software companies lie. The chart above is illustrative — it shows the shapeof what happens as a route tightens, not a measured promise. A random stop order is your baseline. Grouping stops by area helps. A proper nearest-neighbor pass helps more. That directional shape is real and it's the whole reason routing exists. But the actual number — how much time yourshop saves — depends on your geography and how densely you book, and anyone who hands you a clean "save two hours a day" figure without knowing your city is guessing at your expense.

What I'll stand behind is the mechanism. Drive time is the one big cost in a mobile day that produces zero revenue, and route order is a lever you control that moves it. Every hour you claw back out of the windshield is an hour that can hold a billable job — or an hour your crew goes home instead of chasing a route that never made sense. That's more cars detailed with the same people and the same trucks, which is the only kind of growth that doesn't immediately cost you a hire. Tighter route, more capacity, no new payroll. You can see how the whole road stack fits together on the mobile detailing software page.

The honest catch: routing only pays off if the calendar has jobs to route. A perfectly sequenced day of two stops is still a slow day. The biggest lever isn't the optimizer — it's booking density, the number and closeness of jobs you've got to work with. Which is why the routing and the booking side of Service VIN are the same product: fill the day, then tighten it. One without the other is half a solution.

None of this is exotic, and that's the point. Draw your service areas so you're not saying yes to stops that eat a day. Set the eligibility matrix once so dispatch stops depending on your memory. Book in clusters so the route has something to tighten. Then let the map view sequence the day and the installer app carry that sequence out to the crew. It's the same discipline a good fixed shop runs on — a single trustworthy schedule — with the map added because a mobile day is a routing problem as much as a scheduling one.

On what it costs: the calendar and the map view are in the core product from the Essentials plan at $79/mo CAD, and every signup starts with a 14-day free trial that runs on the full product — so you can load a real week of stops, watch the map suggest an order, and see whether it holds up against your city before a card ever touches the account. You can compare the tiers on the pricing page. My honest suggestion is to test it on your worstgeography — the day with the client on the far edge of town — because that's the day routing either earns its keep or it doesn't, and thirty seconds watching the map redraw that day tells you more than any paragraph I can write.

I run a fixed studio and a roll of STEK, not a fleet of vans, so I'm not going to end this by pretending I've got your exact route memorized. What I know is that the shops doing this well stopped treating the drive as a fact of life and started treating it as a number they could shrink. Stop donating hours to traffic. Draw the day as a route, hand it to the crew, and go do more cars.