RO In.
Session Ready.
Lane Pilot listens to your DMS so the tech never types vehicle info again. When the RO closes, the fix teaches the engine. Zero keystrokes. Closed-loop learning.
Shop, Multi-Bay & Fleet tiers · Shopmonkey write-back ready for pilot · Tekmetric intake pending API access
Where a job actually goes
Five stages, each labelled with what is running in production today.
Select a stage to see what moves through it.
Status is measured, not aspirational: Live means the table behind that stage has rows in production today. Built means the code is merged and the stage has not run yet.
The Closed-Loop
Data Flywheel
Most diagnostic tools are one-way: you feed data in, get a result out. Lane Pilot is a loop. Every repair order that enters and exits your DMS makes the next diagnosis more accurate.
Five Stages.
Zero Touch.
Click each stage to see exactly what happens under the hood.
When a service advisor writes up a repair order in Tekmetric, a webhook fires to Lane Pilot's ingress endpoint. We extract the vehicle (VIN, make, model, year, engine, mileage) and customer complaint — then run it through a Regex Gate that scans for 30+ diagnostic trigger words.
"Check engine," "misfire," "no start," "grinding," "transmission slip" — if the complaint contains any diagnostic keyword, the RO is flagged as requiring diagnosis and staged in the ingress queue.
When the vehicle status changes to "in bay" or "dropped off" AND the RO was flagged for diagnostics, Lane Pilot automatically promotes the queue entry into a live diagnostic session — pre-loaded with VIN, vehicle info, mileage, and the customer complaint.
The tech walks up to the car and opens Lane Pilot. The session is already there. Vehicle info pre-filled. Customer complaint loaded. They can scan the vehicle and start diagnosing without typing a single character.
The technician scans the vehicle, adds their own observations, and the Diagnostic Engine runs its agent pipeline: knowledge lookup, NHTSA recall check, complaint cross-reference, historical fix matching, and root-cause synthesis.
The diagnosis is queued back to the work order note from the diagnosis toolbar (Beta). The Shopmonkey write path is built and is switched on per shop after a verified first push; Tekmetric follows once production API credentials are issued. Once live, the service advisor sees the repair plan without leaving their DMS.
When the tech closes the RO in Tekmetric, the webhook fires again. This time, Lane Pilot captures the technician's cause and correction narrative — the diagnosis AND the fix — and links them back to the original diagnostic session.
The tech writes "CAUSE: faulty downstream O2 sensor / FIX: replaced O2 sensor bank 1, sensor 2 — cleared P0420." Lane Pilot captures that narrative, extracts the DTC codes, and upserts it into the repair_outcomes table with full provenance.
The captured repair outcome is now part of Lane Pilot's Historical Fix Database. The next time any tech — at your shop or across the platform — encounters the same DTC on the same vehicle, the Brain already knows what actually fixed it.
"P0420 on 2018 F-150: replaced downstream O2 sensor — confirmed fix 3x." That's not a forum post. That's a verified repair outcome from real technicians closing real work orders. The more cars that flow through your shop, the smarter every future diagnosis becomes.
What This Means for Your Shop
Sessions build themselves from DMS data. The tech never types vehicle info again.
The Regex Gate catches diagnostic intent from customer complaints automatically.
Name, phone, email, address, payment and ID fields are stripped by key before data touches the queue. Free-text complaint notes are forwarded as written — keep customer details out of them.
Every closed RO feeds the Historical Fix Database. More cars = smarter diagnosis.
Under the Hood
What Lane Pilot sees when your DMS sends a repair order.
[INGRESS] Webhook received → event: repair_order.created · shop: 7a3f…
[HMAC] Verified → SHA-256 signature valid · constant-time compare
[PII] Scrubbed → 36 field patterns checked · customer data [REDACTED]
[GATE] Match → "check engine light on, rough idle" → requires_diag: true
[VIN] Decoded → 2019 Ford F-150 · 5.0L Coyote V8 · 87,422 mi
[QUEUE] Staged → RO #14872 upserted to sms_ingress_queue
[PROMO] ✅ Promoted → RO #14872 → diagnostic session e8a2…
// — — — 4 hours later — — —
[INGRESS] Closing event → event: repair_order.posted · RO #14872
[EGRESS] Extracting → CAUSE: faulty downstream O2 sensor
[EGRESS] Extracting → FIX: replaced O2 sensor bank 1, sensor 2
[EGRESS] ✅ Outcome → DTCs: [P0420] · linked to session e8a2… · source: webhook
[RAG] Indexed → P0420 + 2019 F-150 5.0L → "downstream O2 sensor" (confirmed fix)
Enterprise-Grade Security
Customer data never touches the diagnostic engine.
HMAC-SHA256 Signature Verification
Every inbound webhook is cryptographically verified against your shop's unique webhook secret. Constant-time comparison prevents timing attacks. Invalid signatures are rejected with a 401 before any data is processed.
PII Sanitization Layer
Customer names, phone numbers, emails, addresses, payment methods, SSNs, and 20+ PII field patterns are scrubbed from the payload before data touches the staging queue. The Diagnostic Engine only ever sees: Shop ID, Vehicle Context, and Mechanical Complaint.
Append-Only Audit Trail
Every webhook event is logged with timestamp, event type, shop ID, and processing status. The staging queue tracks promotion status and links to the downstream diagnostic session for full traceability.
Integrations
Tekmetric
API Approved, Not LiveInbound RO intake is built for Tekmetric, with HMAC-SHA256-verified webhooks, and is awaiting its first live shop connection. Outbound write-back is built and runs simulated until Tekmetric issues production API credentials.
Shopmonkey
Built, Off By DefaultOutbound write-back is implemented against Shopmonkey's public v3 API and ships disabled — it is enabled per-shop once credentials are configured and the first live push is verified. Inbound RO ingestion from Shopmonkey is not built yet.
Webhook Ingress
Tekmetric OnlyThe ingress endpoint verifies HMAC-SHA256 signatures and resolves shops by Tekmetric shop ID, so it accepts Tekmetric today. Generic provider mapping is not built — tell us which DMS you run and we will scope it.
Stop Double-Entering Data.
Connect your DMS and let the diagnostic sessions build themselves. Every repair order in, every fix learned. The flywheel starts spinning from day one.