We are here for you
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
.webp)
A tire failure on I-70 in Kansas at 3 PM has an obvious answer: send a mobile technician. An aftertreatment derate with a fault stack on a late-model Kenworth in the same location at the same time has a less obvious one: dispatching a mobile tech who cannot access the PACCAR diagnostic software means the code gets cleared, the truck moves, and the derate returns within 200 miles. That is not a mobile repair. That is a delay with an invoice attached.
The decision between mobile and shop is not a preference. It is a routing problem with specific variables, and fleets that do not govern it with a defined framework absorb the cost of misrouted repairs in two forms: mobile events that should have been shop visits producing repeat breakdowns, and shop visits that should have been mobile events generating towing costs and unnecessary downtime. For a fleet without an in-house shop, the framework has to be built around external resources in both channels, which means the vendor relationships and routing criteria need to exist before any specific truck breaks down.
The capability threshold for mobile technicians has expanded significantly in recent years. Tom Sessoms, president of Ardamas Fleet Services, estimates that 80 to 85 percent of commercial repair work can be handled on-site, covering inspections, minor repairs, and diagnostics using portable scan tools that can interface with most major truck platforms. That figure is supported by Heavy Duty Journal's analysis of mobile service deployment data, which puts mobile resolution rates at 80 to 90 percent of common commercial vehicle problems when the technician is properly equipped.
The jobs that fall into that 80 to 85 percent tier cover most of what a fleet encounters on a daily basis: tire service and emergency replacements, brake adjustments and air brake service, electrical diagnostics including battery, alternator, and starter, fluid services with filter and belt replacements, air system inspections and minor repairs, DOT pre-trip reviews, and light to medium diagnostic work on engine systems that do not require lift access or controlled environment conditions.
The 15 to 20 percent that mobile cannot handle is where the channel decision matters most, because misrouting these jobs to a mobile technician is where fleets lose time and money on repeat events. Internal engine rebuilds require disassembly of components that cannot be managed safely in a parking lot or on a highway shoulder. Complete transmission overhauls require drivetrain lifts and precise torque calibration that mobile units do not carry. Differential and axle housing replacements need heavy lifting equipment and controlled alignment tools. DPF replacements on systems with cascading fault codes require platform-specific diagnostic software, lift access, and controlled conditions for aftertreatment work that affects engine performance.
The failure mode on that last category is the one most relevant to modern fleets. A late-model Class 8 truck with an active derate presents as a breakdown that could theoretically be cleared in the field. A mobile technician without the OEM-specific diagnostic software cannot distinguish between a code that is safe to clear and continue and a code that indicates an underlying failure that will produce a more serious event if the truck moves. Sessoms notes directly that some repairs require space, specialized tools, or deeper diagnostics that simply cannot be done in a parking lot. A coordination program that cannot make that distinction before dispatching a vendor is sending the wrong resource to the wrong job.
A decision framework that routes every breakdown to the right channel before the truck is already waiting needs four variables evaluated in sequence.
Failure type and diagnostic confidence. Does the failure description from the driver and the initial assessment suggest a mechanical event with a known resolution, or does it involve an active fault code, a derate condition, or a symptom without a confirmed cause? Confirmed mechanical failures with known solutions route to mobile. Fault codes, derates, and undiagnosed symptoms route to a shop with the platform-specific diagnostic capability for that OEM. Running a Freightliner with a Cummins fault stack to a mobile tech without Cummins diagnostic software produces the same result every time: a temporary fix and a return event.
Geographic proximity to a vetted shop. If the truck is within a reasonable towing or drive distance of a shop with confirmed capability for the failure type and the OEM platform, the tow plus shop route may be faster and cheaper than waiting for a mobile technician to attempt a field repair on a job that has a high probability of requiring a shop visit anyway. The ATRI research on breakdown event costs shows that mobile repair eliminates towing expenses of $500 to $3,000 per incident and reduces daily downtime costs of $448 to $760 per vehicle, but those savings only materialize when the mobile technician actually resolves the issue. A mobile dispatch that does not resolve the issue adds the mobile call cost to the eventual towing and shop cost.
Time sensitivity of the load. A truck carrying a time-sensitive load on a short remaining distance may justify a mobile dispatch even for a repair type that would normally route to a shop, because the alternative is a tow and a multi-hour shop queue. A truck with a non-urgent return haul on a flexible timeline may be better served by towing to a shop immediately rather than waiting for a mobile technician to work on a problem that the shop will need to revisit. The load's commercial consequence should be a variable in the routing decision, not an afterthought.
After-hours availability of each channel. Mobile technician availability after midnight on secondary corridors is not the same as mobile availability during business hours on major interstates. The nationwide coverage problem covered in the nationwide semi truck roadside assistance coverage article applies specifically to mobile technician availability: a program whose mobile coverage thins out at night or in rural markets needs a shop channel with confirmed after-hours capability as the fallback, or the routing framework breaks down at exactly the moments when it matters most.
Under 49 CFR Part 396, the documentation standard for a repair event is the same regardless of where it occurs. A mobile repair produces the same required record as a shop repair: vehicle identification, date and nature of the work, parts replaced with specifics, and for brake and inspection work, technician qualification documentation. The practical difference is that a shop with an established record system produces compliant documentation as a matter of routine. A mobile technician dispatched as an emergency vendor may produce a handwritten invoice that does not contain the information the FMCSA audit chain requires.
The defect-to-repair chain that FMCSA auditors trace, covered in detail in the FMCSA fleet maintenance records article, applies equally to mobile repair events. A DVIR defect that was addressed by a mobile technician on the side of the road needs the same linked repair record as a defect addressed at a vetted shop. The mobile event creates a documentation obligation that is easy to miss when the priority in the moment is getting the truck moving.
This is the practical argument for routing mobile repair through a coordination program with documentation standards rather than dispatching an available technician from a directory: the coordination layer captures the repair record and links it to the vehicle file regardless of which vendor performed the work. A fleet handling mobile dispatch ad hoc collects whatever documentation the technician provides, which is inconsistent at best and audit-exposing at worst.
For fleets already using a coordinated truck repairs and diagnostics program, the documentation standard should apply to mobile events in the same way it applies to shop visits. If it does not, the mobile channel is a compliance gap regardless of how well the shop channel is documented.
A fleet without an in-house shop that has not structured its mobile and shop channels in advance makes routing decisions reactively under pressure. That produces the two failure modes described at the start: mobile dispatches to jobs that need a shop, and shop visits for jobs that could have been resolved faster and cheaper in the field.
Building the framework before a breakdown means three things are in place. A list of vetted mobile technician resources exists for each of the corridors where trucks run most frequently, with confirmed Class 8 heavy-duty capability and confirmed platform coverage for the makes in the fleet. A list of vetted shops exists for the same corridors, with confirmed OEM diagnostic software access and confirmed after-hours capability. And a routing criteria document exists that tells dispatch which failure descriptions go to mobile and which go to shop, so the decision is not being made fresh during a live event by whoever picks up the phone.
The fleet maintenance program evaluation article on this site includes questions about after-hours coverage and vendor capability confirmation that apply directly to structuring both channels: the question of whether a program can confirm Class 8 capable coverage at specific coordinates at 2 AM matters as much for mobile channel coverage as it does for shop channel coverage.
If your fleet runs across multiple states and the mobile and shop channels are currently structured as whoever is available when a driver calls, the routing framework does not exist in a form that controls cost or compliance outcomes. A coordinated preventive maintenance program through a vetted nationwide truck repair network with confirmed mobile and shop resources by corridor handles both channels to a consistent standard with documentation produced on every event. If you want to understand what that looks like for your specific fleet profile, operating footprint, and OEM mix, reach out through the contact page. That conversation is more productive with your breakdown history and corridor map in front of us than in the abstract.
This article draws on the following sources:
