Loading
How it works
Estimates built from DVI results, sent for digital approval, declined lines deferred automatically.
Inspection results arrive with photos and notes. Advisor reviews and converts checked items into estimate lines — no retyping.
Customer receives an SMS/email link to the portal. They see the itemised estimate, photos, and recommended priority.
Approved lines proceed. Declined lines move to the deferred-work queue automatically — recoverable later with one SMS.
One click converts the estimate to a GST-compliant tax invoice. Parts are reserved; job moves to In Progress on the board.
Authorisation
Phone tag kills labour hours. Advisors send a portal link — via SMS or email — customers approve line by line, and the job starts. No chasing, no surprises on pickup. The board moves to In Progress when approval lands, parts reserve automatically, and declined work stays in the deferred pipeline so the next service conversation starts with "we flagged your rear brakes last time."
Why this category matters
Category pages should not be synonym stuffing. Here is the operating rationale every serious shop platform must address.
Car count dies on missed calls, weak booking, and messy intake — the OS must own first contact through check-in.
ARO dies when findings never become priced, decided lines — DVI and portal approvals are margin features.
Throughput dies when AWAITING_AUTH and AWAITING_PARTS are invisible — board stages must mean something.
Cash dies when invoices are re-keyed and AR is a Friday spreadsheet — money path starts on the repair order.
Vehicle lifecycle
The Automotive Workshop Operating System (AWOS) maps every customer moment from first contact to retention — so software follows how workshops actually earn margin.
Capabilities
Live means in the multi-tenant product/demo. Integrations use Live / Stub / Dry-run / Planned — never Connected for stubs. Roadmap means not production-complete.
Labour and parts as separate priced lines — so customers can approve the urgent service and defer the rest, rather than rejecting a $2,000 job outright because one line was $200 too much. Line approval is why ARO climbs.
SMS or email carries a deep link into the portal — one tap and each line can be decided on their phone, no shop login, no PDF to interpret. Decisions write back to the RO instantly so the board and parts reservation react without manual steps.
Learn more →Tech captures a finding during inspection; it becomes a priced estimate line the advisor sends — no re-keying, no description lost in translation, and the customer sees the same finding the tech documented.
Learn more →Declined lines do not disappear. They sit in a recoverable pipeline so the next booking conversation starts with "we flagged your rear brakes last time" — turning a past no into a future booked job.
FAQ
Structured for humans and search (FAQ schema). We update when ship status changes.
Line-level. Customers approve the major service but defer the wiper blades — that is normal behaviour. All-or-nothing approval forces bad compromises, unnecessary callbacks, and jobs that sit AWAITING_AUTH longer than they should.
The advisor can resend it. SMS carries the portal deep link when a provider is configured; email works out of the box via SMTP. The portal itself works independently of SMS once the customer has the URL.