Loading
Loading
Authorisation · margin protection
LiveShops lose money two ways: unapproved work that becomes write-offs, and weak ARO because recommended work was never decided. Line state is the control plane.
Primary persona: Service advisor + customer
The problem
Whole-job “OK” signatures hide which lines were declined; variations expand silently; invoicing becomes negotiation.
Why it matters
PENDING → APPROVED | DECLINED | DEFERRED is explicit and auditable.
Only approved lines should become billable invoice content.
Deferred work is a first-class opportunity, not a lost sticky note.
Portal tokens remove desktop login friction for customers on-site or at work.
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
Add labour and parts lines from menus, DVI conversion, or advisor pricing.
Why this stage
Speed to estimate is speed to authorisation — bays wait on decisions.
Action
Generate portal link; dispatch via SMS/email adapters (deep link to token).
Why this stage
Customers decide on the phone they already hold — higher response rates.
Action
Customer sets approve/decline/defer; board reflects AWAITING_AUTH clearance.
Why this stage
Floor starts only what is paid for; advisor coaching targets declined lines.
Action
New discovery returns to estimate/auth rather than silent expansion.
Why this stage
Trust and legal posture require re-authorisation of material changes.
Related search intent