Loading
Service advisor · front of house
LiveFront desk intake that starts the money path correctly
Every delayed or messy intake creates rework: wrong vehicle, missing phone number, or an RO that never hits the board. Intake is where car count and data quality are either protected or destroyed.
Primary persona: Service advisor / reception
The problem
What breaks without this process
Shops still open jobs as free-text tickets. History is unsearchable, vehicles are duplicated, and the board cannot trust stage data.
Why it matters
Rationale — profit, risk, and shop floor truth
- 01
Customer + vehicle first-class records cut repeat intake time on every return visit.
- 02
A real repair order on the board starts WIP visibility immediately — not after someone “types it up later.”
- 03
Search by name, phone, rego, or RO number reduces “where is that car?” calls mid-day.
- 04
Clean intake data is the foundation for DVI, estimates, invoices, and retention — garbage in, ARO out.
Proof from the live demo
Real UI — not a pitch mockup
Captured from the seeded multi-tenant demo. Open the same surface with demo credentials.
live demo capture
live demo capture
Stage sequence
Step-by-step use case
Each stage lists the action, the business why, and the intended outcome. This is how we implement and test the product — not marketing fiction.
- 01
Identify the person
Action
Search existing customers by name or phone, or create a new CRM record with contact details.
Why this stage
Prevents duplicate customers and keeps SMS/email approvals deliverable later.
Surface: CustomersOutcome: Customer record ready - 02
Attach the vehicle
Action
Link or create vehicle with rego (and VIN/year/make/model when known).
Why this stage
History, deferred work, and future bookings attach to the asset — not a sticky note.
Surface: VehiclesOutcome: Vehicle linked - 03
Open the repair order
Action
Create RO from intake (or from booking check-in). Job appears on the board in NEW.
Why this stage
Board WIP and owner attention lists only work if every car in the shop is a system object.
Surface: Job board / Repair ordersOutcome: RO visible on board - 04
Capture concern & assign
Action
Record customer concern, set advisor/tech intent, move toward inspection or estimate.
Why this stage
Techs need the stated complaint; advisors need a handoff that survives shift change.
Surface: RO detailOutcome: Ready for floor or DVI
Related search intent
- workshop intake
- repair order software
- customer vehicle CRM auto shop
Related product pages
FAQ
Questions on this flow
Structured for buyers and search.
Can walk-ins and booked jobs use the same intake?+
Yes. Walk-ins create RO directly; booked jobs check in from the diary and create/link an RO so both paths land on the same board.