Every department starts the story again.
Customer and vehicle details are re-entered, paper moves between teams and approvals become difficult to trace.
Reception, workshop and cashier work from the same visit. Approved work and changes move forward while exceptions remain with the responsible person.
What changes
Customer and vehicle details are re-entered, paper moves between teams and approvals become difficult to trace.
One visit record carries approved work, responsible users and the cashier handoff without losing exceptions.
A simple guided tour
Reception
Clear operating boundary
Working example
Prototype interface is currently in English.
CONNECTED VISIT · FICTIONAL WORK ORDER
Fictional records and prices. No dealer systems, real invoice, payment or message. Department switching illustrates responsibilities, not access control. Changes reset on reload.
RECEPTION VIEW
OPTIONAL EXPANSION · NOT CONFIRMED DELIVERED SCOPE
A customer app and service reminders can extend the connected record. Dates, consent, channels and responsibility need their own agreed scope.
Sample follow-up date: 5 October 2026. Illustrative only — not a maintenance recommendation.
Finish the sample handoff and invoice draft first.
FABLELABS / Car Dealership 360