AI diagnostics

OwnerGeneral ManagerService ManagerService WriterTier 1 Technician

Updated September 23, 2026

What this does

Service Board → Diagnostics turns a complaint into a structured starting point. You give it the vehicle, the symptoms, any trouble codes, photos, and detail; it returns a report built from the vehicle's specs, decoded codes, this shop's history on the vehicle and model, and open recalls. Every run is saved as a session on the vehicle, so the next technician sees what was tried.

Before you start

diagnostics.create: Tier 1 Technicians, Service Managers, General Managers, Owner. Tier 2 Technicians and writers can view sessions. Pick the customer first; the vehicle list is per customer.

Steps

  1. Select the Customer, then the vehicle.
  2. Tap the symptom chips that apply: Check Engine Light, No Start, Noise, Overheating, Rough Idle, Vibration, Electrical.
  3. Enter trouble codes ("P0300, P0171, B1234…"). They're decoded from the app's code library.
  4. Additional Details — when it happens, patterns, what's already been checked. This is the field that most improves the result.
  5. Photos — dash warning lights, fluid, damage.
  6. Run it. The Report has a Summary, a Confidence level, DTC Analysis, Probable Causes in order, Recommended Next Steps (tests to confirm or rule out), Safety Concerns, and Shop History Insights drawn from past work orders on this vehicle and model.
  7. Sources below the report list what it drew on, including NHTSA recalls for the vehicle and related videos.
  8. Use Chat on the session to ask follow-ups against the same context.

Closing the session

When the fault is found, Resolve Session with Resolution Notes saying what it actually was. Resolved sessions are what make the shop-history insights useful next time. Archive a session that led nowhere. Past sessions are searchable and show on the vehicle.

Common problems

"Diagnosis failed." Usually a connectivity hiccup. Run it again; the inputs are kept.

The report is generic. Thin inputs. Add codes, the conditions under which it happens, and what's been ruled out.

It suggested a part we replaced last month. That's what the Shop History section is for; if the earlier session wasn't resolved with notes, the report can't know. Resolve sessions.