Skip to content
Workshop Wrench

Retention · Roadmap

Review automation when it is real — not a Connected badge today

Leaders automate Google review requests after paid jobs. Workshop Wrench will not claim a live review suite. Foundations (comms events, consent classes, customer contact) ship first. This page exists so searchers get an honest status, not silence.

Request a demoSee pricingAll processesView pricing

Why this category matters

Profit levers behind the keyword

Category pages should not be synonym stuffing. Here is the operating rationale every serious shop platform must address.

  1. 01

    Car count dies on missed calls, weak booking, and messy intake — the OS must own first contact through check-in.

  2. 02

    ARO dies when findings never become priced, decided lines — DVI and portal approvals are margin features.

  3. 03

    Throughput dies when AWAITING_AUTH and AWAITING_PARTS are invisible — board stages must mean something.

  4. 04

    Cash dies when invoices are re-keyed and AR is a Friday spreadsheet — money path starts on the repair order.

Vehicle lifecycle

Complete vehicle service lifecycle

The Automotive Workshop Operating System (AWOS) maps every customer moment from first contact to retention — so software follows how workshops actually earn margin.

  1. 01Lead
  2. 02Customer
  3. 03Vehicle
  4. 04Booking
  5. 05Check-in
  6. 06Inspect
  7. 07Estimate
  8. 08Approve
  9. 09Parts
  10. 10Labour
  11. 11Produce
  12. 12Invoice
  13. 13Pay
  14. 14Release
  15. 15Retain
Explore every use case with stage sequences →

Shop day sequence

Six moments that protect cash

The same operational spine as the product board — detailed use cases live under Processes.

  1. 01

    Book or walk in

    Public booking or front desk intake with customer + vehicle first-class. Why: car count dies when first contact never becomes a system object.

  2. 02

    Check in & board

    Booking becomes a repair order; board shows stage, tech, and blockers. Why: WIP you cannot see is WIP you cannot manage.

  3. 03

    Inspect with evidence

    DVI findings with severity convert to estimate lines or deferred work. Why: verbal upsells without structure kill trust and ARO recovery.

  4. 04

    Authorise work

    Line-level approve / decline / defer via portal tokens. Why: silent scope expansion creates write-offs and disputes.

  5. 05

    Parts & labour

    Reserve stock, raise POs, clock labour on the RO. Why: authorised work without parts is fake progress; unbilled labour is pure waste.

  6. 06

    Invoice & collect

    GST invoice from approved lines, payments, AR visibility. Why: revenue is not cash until collected — money path stays on the RO.

Deep dive every use case with stage sequences →

Capabilities

What ships — with honest status

Live means in the multi-tenant product/demo. Integrations use Live / Stub / Dry-run / Planned — never Connected for stubs. Roadmap means not production-complete.

Post-job review campaign

Roadmap

Automated ask after paid RO — product surface roadmap (W5).

Consent / commercial message class

Live+

Commercial campaigns skip without consent — foundation live.

Learn more →

Service reminders

Partial

Retention reminders expand before full review product.

FAQ

Questions buyers actually ask

Structured for humans and search (FAQ schema). We update when ship status changes.

Why publish a roadmap page?+

Buyers search the term. We own the keyword with honest status rather than implying a live suite we do not ship.

Related

Prefer a live board to another Workshop Wrench slide?

Request a signed access desk and walk the seeded shop in under a minute.