Flags requests that need ownership before the customer waits.
Clickable synthetic example. Nothing on this page is saved, sent, diagnosed, estimated, scheduled, or authorized.
Pre-Arrival example
Walk in better prepared—not carrying the whole conversation in your head.
Start a couple of days before service, or while you are still trying to establish a request. Project Lazon guides the customer through the details a service advisor would normally have to gather at arrival.
Customer request→Guided intake→Customer review→Advisor-ready handoff
The easy starting handoff
“Can I text or email you a link to help us better prepare for your visit?”
The link guides the customer through the vehicle, request, timing, transportation, relevant history, and anything they want the shop to know. It should reduce arrival questions—not create another job for the shop.
Choose an example path. Nothing will be sent.
Step 1 of 5
Example onlyPrepare for your scheduled visit
Which ride?
2018 Honda CR-VCustomer-selected vehicle
What should the shop know?
Routine service is due. No warning lights or new symptoms.In the real intake, the customer can use their own words.
Timing and transportation
Appointment Tuesday at 8:00 AM · customer plans to waitAsk the shop for an expected wait time and what happens if the scope changes.
The customer stays in control. Project Lazon organizes the request; the shop still confirms availability, scope, timing, price, and authorization.
Advisor-ready handoff
Customer-reviewedOne screen of useful arrival context
Shop-originated path
The advisor can start the relationship with one private link.
Choose the exact location, advisor, and request context. The customer confirms who they are, adds their ride and details, reviews what will be shared, and returns the intake to that exact service relationship.
Example Service CenterExact physical location
Jordan · Service AdvisorAssigned advisor
Pre-Arrival requestNo work authorized
- Expires and can be revoked
- No private details readable in the URL
- Customer consent before sharing
- No internal shop notes exposed
Location-owned records
Synthetic workspaceShared location queue, clear advisor responsibility
Customer requestAssigned advisorStatusLast activity
Oil change · Honda CR-VCustomer intake returnedJordanReady for review9:14 AM
Brake-noise concern · Ford F-150Waiting for customer detailsCaseyLink opened8:51 AM
Recent activity · simple audit trail
- 9:14 AM · Record openedJordan · shop workspace · Honda CR-V request
- 9:08 AM · Customer intake returnedSystem · customer-reviewed version 1
- 8:43 AM · Assignment changedService manager · Casey → Jordan · workload coverage
The timeline records who acted, when, at which location, and on which version. It does not duplicate private message content or appear in the customer view.
Service manager view · automatically available KPIs
Starts when intake returns and stops when an advisor meaningfully reviews it.
Shows repeated questions that better intake or wording may prevent.
Separates completed preparation from partial or abandoned intake.
Segments routine and complicated cases before comparing advisor load.
Measures whether the customer confirms they understand what happens next.
No event history means no score. These become real only from attributable workflow events. They support coaching and workload decisions; they do not invent performance or expose customer-private content.
Routine oil change and tire rotation
No warning lights or new symptoms reported. Customer is preparing ahead of a Tuesday visit.
Tuesday · 8:00 AM
Customer asks for an expected wait time and the process if additional concerns are found.
No new condition reported
This is a routine-service request. No diagnosis is claimed.
No documents needed
The customer has not attached records or photos for this routine visit.
Availability, timing, scope and price
Project Lazon does not pretend these are known before the shop responds.
No repair authorization created
The customer is establishing or preparing a request. The shop's normal authorization process still applies.
Five-minute shop value test
Can the shop reach one useful result without duplicate work?
Pass: useful context is understood and acted on within five minutes, with no required second inbox or discovery worksheet.
Pass Use againConditional Fix one obstacleFail Abandon without penalty
What this example is designed to prove
Less arrival burden
The customer supplies useful context before standing at the counter, while the details are still easy to recall.
Better advisor time
The advisor starts with a structured request, visible unknowns, and customer preferences—not a long discovery interview.
No extra shop homework
The shop sends one link by its normal text or email path, then judges the result during a normal interaction: use, edit, reject, or stop.