Loading
Loading
Customer experience
LiveCustomers will not create another password to approve brakes. Token links deliver line decisions, audit trails, and faster bay release.
Primary persona: Customer (external)
The problem
PDF estimates via text with “looks fine” replies do not create structured line state or audit.
Why it matters
Mobile-first decide path matches how customers actually respond.
No password reduces drop-off and support load.
Decisions write back to the RO for board and invoice integrity.
Foundation for pay links and service history expansion.
Proof from the live demo
Captured from the seeded multi-tenant demo. Open the same surface with demo credentials.


Stage sequence
Each stage lists the action, the business why, and the intended outcome. This is how we implement and test the product — not marketing fiction.
Action
Create secure link bound to the repair order / estimate context.
Why this stage
Scoped tokens limit exposure vs permanent customer passwords.
Action
View lines (and DVI summary as media expands); no shop login.
Why this stage
Friction kills approval speed and ARO.
Action
Approve, decline, or defer each recommendation.
Why this stage
Partial approval is normal; all-or-nothing UX forces bad compromises.
Action
Board leaves AWAITING_AUTH; reserves parts; production continues.
Why this stage
CX systems must change operational state or they are vanity portals.
Related search intent