The short answer: Samsara, Geotab, and Motive all detect fault codes and can create alerts or work orders. What they do not do is book the repair, find a time the vehicle is free, tell the driver, and follow up with the shop. To automate that, set severity rules for which codes need action now versus at the next service, then connect your telematics to a coordination layer that books the work with your shops. HoneyRuns' AI agent, Riggs, does that last part over Slack, Teams, and text.
Why fault codes pile up
A telematics dashboard can show dozens of active codes across a fleet on any given day. Many are minor. A few are urgent. The problem is that someone has to read each one, decide which is which, and then do the scheduling work for the ones that matter.
When nobody owns that job, two things happen. Urgent codes sit next to trivial ones and get missed. And codes that should have been fixed at the next oil change turn into roadside breakdowns because nobody bundled them into a visit.
Step 1: Sort codes by what they mean for the vehicle
A simple three-level rule set covers most service fleets:
- Stop and fix now. Codes tied to safety or engine damage: overheating, low oil pressure, brake system faults, a flashing check engine light (usually an active misfire). The vehicle should come off the route and get looked at the same day.
- Fix this week. Codes that will get worse but are not immediately dangerous: emissions system faults, sensor failures that affect fuel economy, charging system warnings, a steady check engine light.
- Bundle with the next service. Minor or intermittent codes that can wait for the next scheduled visit, as long as they do not escalate.
Your telematics platform can tag severity for many codes. Your mechanic's input is what makes the rules fit your vehicles.
Step 2: Connect codes to the vehicle's schedule
A van that is booked solid tomorrow should not be sent to the shop tomorrow if the repair can wait two days. Good scheduling looks at the vehicle's jobs or routes, the shop's availability, and the code's severity together. This is the step most fleets do by phone and text, and the step that eats a coordinator's day.
Step 3: Send the repair to the right shop with context
The shop or mobile mechanic needs the code, the vehicle's history, its location, and when it is available. Sending all of that up front saves a diagnostic call and often a second visit.
Step 4: Follow up and close the loop
The job is not done when the appointment is booked. Someone has to confirm the vehicle showed up, get the estimate approved, find out when it is ready, and log the work in your maintenance records.
What each platform does on its own
- Samsara surfaces fault codes with severity and suggested actions, and can group open faults, inspection defects, and scheduled maintenance into work orders.
- Geotab reports active fault codes and engine data and supports maintenance reminders, with more workflow available through Geotab Marketplace partners.
- Motive reports fault codes and vehicle health and supports maintenance tracking and work orders.
All three handle detection well. The booking, driver coordination, follow-up, and record keeping still need a person or an agent.
Automating the whole path with Riggs
HoneyRuns reads fault codes from Samsara, Geotab, and Verizon Connect, and mileage from Motive, Azuga, and Ford Pro for interval-based service. When a code fires, Riggs applies your severity rules, finds a time that fits the vehicle's schedule, books the work with your preferred shop or mobile mechanic, tells the driver, follows up until the vehicle is back, and logs the completed service in a system like Fleetio once you approve. Repair estimates come to you before work goes ahead.
Frequently Asked Questions
Q: Can Samsara automatically schedule a repair when a fault code appears? A: Samsara can turn fault codes into alerts and work orders, but it does not book the appointment with an outside shop or coordinate the driver. A coordination tool like HoneyRuns connects to Samsara and does the booking and follow-up.
Q: How do I handle diagnostic trouble codes across a whole fleet? A: Set three severity levels (fix now, fix this week, bundle with next service), route every code through those rules, and make one person or one system responsible for turning each actionable code into a booked repair.
Q: What should a fleet do when a vehicle's check engine light comes on? A: Pull the code from telematics first. A flashing light usually means an active misfire and the vehicle should come off the road. A steady light usually means service within a few days. Then book the repair around the vehicle's schedule.
Q: Does HoneyRuns work with Geotab and Motive as well as Samsara? A: Yes. HoneyRuns is listed on the Geotab Marketplace and reads Geotab fault codes. With Motive, it reads mileage and location for interval-based service. It also connects to Verizon Connect and Azuga.
Q: Do fault-code workflows need a maintenance manager to run? A: Not with an agent like Riggs. It applies the rules, does the booking and follow-up, and brings a person in to approve repair estimates.
Get Started with HoneyRuns
Connect your telematics and see which open codes need action today. See how Riggs would handle your fleet.
HoneyRuns gets fleet maintenance done. It watches mileage, intervals, and telematics, books the repair with the shops and vendors you already use, stays on the driver and the shop until the vehicle is back, and logs the completed service in the system you already run. Your team approves repair estimates before work goes ahead. Founded by fleet operators who manage 70 vehicles across three fleets today.