Three unknowns before you can dispatch
Most service businesses take a call, get an address, and book a slot. Mobile tire service has to resolve three unknowns before it can dispatch at all, and a caller standing on a highway shoulder is the worst-placed person to resolve any of them.
Where they are. Not an address — a position. People on roads do not know addresses, and the ones they guess are frequently wrong by miles.
What size they need. A number moulded into a sidewall the caller may not be able to reach, in a format they have never looked at before.
Whether you have it. Because your inventory is in a van, and the answer determines whether this job takes forty minutes or two trips across a metro.
As of September 2026, the mobile tire companies that run profitably are the ones that resolve all three at intake rather than at the roadside. The ones that do not make a lot of drives that end in "we will have to come back tomorrow", which is a job done twice and paid once.
This guide is about that intake, plus the routing, inventory, pricing and fleet-versus-consumer split that follow from it. The operational system behind it is Run with Jarvis, whose natural-language control layer is described in the Jarvis AI Brain overview.
Finding a caller who does not know where they are
The instinct is to ask for an address, and on roadside work that instinct wastes minutes. A driver on a shoulder cannot see a street number, is often unfamiliar with the area, and under stress will confidently name the wrong road.
What works is a different question sequence. Which road are you on, and which direction were you heading? Then: what was the last exit or cross street you passed? Then anything visible — a mile marker, a business sign, a bridge, an overpass number. Then read it back and get confirmation, because the read-back catches the error that would otherwise cost a twenty-minute drive.
Better still, skip the description entirely. A customer's own phone knows exactly where it is, and a location shared from it is accurate to the shoulder rather than to the neighbourhood. A link the customer taps, which returns their position, removes the most error-prone step in the whole call — and it works even when the caller has no idea what road they are on, which is frequently the actual situation.
Two operational notes make this stick. First, the location has to land on the job record, not just in the dispatcher's head, or the technician ends up phoning the customer again for directions. Second, safety sits underneath all of it: a customer on a live traffic shoulder should be told to stay in the vehicle with hazards on if it is unsafe to stand outside, and the precision of the location is part of how quickly that situation ends. The broader roadside dispatch pattern — including handling callers who are somewhere genuinely difficult to reach — overlaps with the towing dispatch guide.
Getting the tire size right on the phone
The size is stamped on the sidewall in a pattern like 225/65R17: section width in millimetres, aspect ratio, radial construction, wheel diameter in inches. Most drivers have never read it and will not find it if you say "what size are your tires?".
What works is telling them the shape of the answer. "There is a line of raised numbers on the side of the tire — look for three numbers with a slash and the letter R, something like two-twenty-five slash sixty-five R seventeen." Callers find it quickly once they know what they are hunting for.
Then the read-back, because there are two reliable failure modes. The first is reading the DOT code or the load and speed index instead of the size — a string of characters in roughly the same neighbourhood that means something else entirely. The second, and the expensive one, is reading the spare rather than the flat, which on many vehicles is a different size altogether.
Two more fields matter and are almost never asked. Wheel position, because a staggered setup can carry different sizes front and rear, and a customer reading the front tire on a rear-wheel failure sends you with the wrong size. And TPMS, because a sensor that needs transferring or replacing is a part and a procedure, not an afterthought — arriving without one turns a completed job into an illuminated dash light and a callback.
Note also what the caller is actually asking for, which is not always a tire. A plug or patch on a repairable puncture, a spare fitted so they can drive to a shop, or a full replacement are three different jobs at three different prices, and the choice belongs to the customer once they know the options. A bot or a dispatcher that sells a replacement to someone who needed a ten-minute repair produces a refund conversation later. Getting that verification consistently on every call — including the 11 PM one — is exactly what the platform's AI receptionist is for, and it captures the same fields every time rather than the ones a tired dispatcher remembers.
Inventory on wheels is the whole business
In a tire shop, inventory is a stockroom question. In mobile tire service, inventory is the service. The van is the warehouse, the warehouse drives at fifty miles an hour, and its contents determine whether a call can be served at all.
That has three operational consequences most software gets wrong.
"Do we have it" is a dispatch question, not a stock question. The dispatcher needs to know what is in that van, right now before committing an ETA. A stock level that reflects a central warehouse is worse than useless here, because it says yes when the answer is no.
Consumption has to be recorded at the roadside. A tire fitted on a shoulder that does not leave the van's count until somebody does paperwork that evening means the next three dispatch decisions were made against fiction. This is the same discipline as the truck stock and parts inventory guide, just with a much shorter feedback loop and a much higher cost of error.
The load-out is a forecast. What you stock is a bet on the size mix of tomorrow's calls, which is why the data from past calls matters commercially: the sizes you get asked for most often, including the ones you had to decline, are the load plan. A company that tracks declined sizes learns what to carry; one that only tracks completed jobs learns nothing from its failures.
There is a related decision to make honestly: what to do with the call you cannot serve from the van. The three options are a same-day trip to a supplier, a next-day booking, or a straight referral. All three are acceptable; what is not acceptable is a vague "we can probably do it" that becomes a wasted drive.
| Intake field | Why it decides the job | Common failure |
|---|---|---|
| Position, not address | You cannot dispatch to a guess | Caller names the wrong road confidently |
| Tire size from the sidewall | Determines whether the van can serve it | Reading the DOT code or the spare |
| Wheel position | Staggered setups differ front to rear | Assuming all four match |
| TPMS sensor needed | It is a part and a procedure | Discovered after the wheel is off |
| Repair, spare or replace | Three prices, customer's choice | Selling a replacement for a puncture |
| Distance from current crew | Dominant cost in mobile work | Fee revealed on arrival |
| Consumer or fleet account | Different script, different payment | One interrogation for both |
Distance is the cost, so it has to be in the price
Drive time is the largest uncontrolled cost in mobile tire service. A forty-minute job forty-five minutes away is a two-hour-plus commitment for a single tire's margin, and a company that prices every job the same is quietly using its near work to fund its far work.
There are three honest structures, and any of them beats pretending distance is free. A hard service-area boundary — simple, easy to communicate, and it forces you to decline work, which is uncomfortable but correct. A distance-banded call-out fee quoted at intake, so the customer chooses with full information. Or a minimum job value that scales with distance, which is how most companies end up handling the far single-tire call: it is fine if they also need the other three, and not fine otherwise.
The non-negotiable is that the fee is stated on the call. A roadside customer who agreed to a price and then hears a different total when the wheel is already off has a legitimate grievance, and roadside disputes are unusually damaging because the customer is already stressed. The pricing logic and how to draw the boundary are worked through in the service radius and drive-time pricing guide.
ETA honesty is the other half of the same problem. Mobile tire customers are stationary and anxious, and the difference between "about forty minutes" that becomes ninety and "about ninety minutes" that is ninety is enormous in perceived service. GPS tracking with automatic en-route and arrival texts removes most of the follow-up calls, and it is part of the Core feature set rather than an upgrade. The general mobile-operations version of this problem — where a single van covers a wide area with expensive equipment on board — is also covered in the mobile welding operations guide.
Fleet accounts and stranded consumers are different products
The same van serves both, and almost nothing else about them matches.
A fleet caller is a dispatcher or a shop manager. They know the vehicle, usually know the size, know exactly where the unit is, are not emotionally urgent, and expect to be invoiced against an account with a reference number. They also bring volume and predictability, often with several units at one yard — which is the most profitable work in the trade because the drive is amortised across multiple tires.
A stranded consumer knows almost nothing, is stressed, needs reassurance as much as service, pays by card on completion, and is a one-off unless something goes memorably right.
Running both through one script hurts both. The fleet dispatcher gets asked to describe landmarks they already gave you as a yard address. The frightened consumer gets asked for a purchase order number.
The operational fix is a branch at the front of the call — account customer or not — and two intake paths behind it. For fleets, the customer record has to carry the account terms, the vehicle list where known, the authorised contacts and the reference-number requirement, because invoicing to an account with a missing PO is an unpaid invoice. For consumers, payment happens at the roadside, which means a payment link or on-site card capture rather than an invoice mailed later; the mechanics are in the get-paid-faster guide.
Nights, weekends, and where the calls come from
Mobile tire demand is not distributed like a business. It peaks in commute windows, on weekends, in bad weather, and at night — which is precisely when a company with staffed phones has no staffed phones.
The economics of after-hours work need deciding rather than drifting. Either you serve nights at a premium that makes them worth waking up for, or you do not serve them and say so clearly at intake with a morning booking offered instead. What loses money is the middle: taking the call, sounding available, and then not going.
Where the calls originate matters just as much. A stranded driver searches on a phone and taps the first plausible result with a phone number, which means local search visibility is the top of this funnel almost exclusively. Hours, service area, reviews and a working phone number on the profile are the difference between being found at 9 PM and not — the Google Business Profile guide covers what actually moves that.
And because a meaningful share of those searches convert on the first call answered, the response mechanics matter more here than in almost any other trade. The customer is not comparing three companies at leisure; they are calling until somebody picks up.
After the job
The tire is on, the customer is moving again, and two things are still unclaimed.
The review. A roadside rescue produces the highest-sentiment moment in service work — you turned a ruined evening back into a normal one. That sentiment decays within hours. An automated review request on completion, while the relief is fresh, captures it; one sent three days later does not.
The next job. Consumers who needed one tire frequently need the matching pair within months, and fleet accounts need a scheduled relationship rather than an emergency one. The platform's AI outbound follow-up calls are built for that kind of contact — reaching your own past customers and accounts about a known need, not cold prospecting. Whether that sits on your tier is detailed on the pricing page.
What to automate, what to keep human
Automate the intake script, the location capture, the size read-back prompts, the distance check against the service area, the ETA notifications, the roadside payment link, the review request, and the van inventory count. All of that is procedural, and all of it degrades in exactly the conditions where it matters most — late, busy, noisy.
Keep human the judgement calls: whether a puncture is safely repairable, whether a sidewall is compromised, whether a location is too dangerous to work, whether a vehicle can be safely jacked where it sits, and whether a far single-tire call is worth taking tonight. Those need a technician's eyes or a dispatcher's experience, and a system that automated them would eventually put someone on a shoulder they should not be on.
Where to start
Start with location capture, because it is the first thing that goes wrong and it wastes drive time, which is the resource you have least of. Get a shared-location step into every roadside call and confirm it onto the job record.
Then size verification with a read-back, then the van inventory answer available at dispatch, then distance stated in the price at intake, then ETA notifications so nobody has to call and ask.
Then split fleet from consumer at the front of the call, because those two customers are worth serving differently and cost you money when they are not.
Plans and minutes are on the pricing page — three flat monthly tiers, no setup fee, month-to-month. To size it against your own call volume, service radius and van count, get in touch.
