Portal deep links
LiveApproval and pay paths open token URLs on mobile without a shop login.
Learn more →Loading
Loading
How it works
Booking, estimate, approval, payment, review request. All triggered from RO events, all replies in the Comms Centre.
Booking confirmation, estimate ready, approval approved, job complete — each event can trigger an automated SMS. No advisor action required.
Customer name, vehicle rego, and a short-link to the portal or payment page inserted automatically. Delivered via Twilio.
Replies land in the Comms Centre thread view. Advisor can respond inline — full conversation history, no switching apps.
Estimate approved via SMS link → RO moves to In Progress. Invoice paid via link → RO closes. No manual status update needed.
Comms · Partial ship
Category leaders sell unlimited two-way SMS as packaging. Workshop Wrench treats SMS/email as the notify channel and the customer portal as the decision surface: line-level approve / decline / defer with audit. Adapters ship with mock SMS by default; Twilio when keys are configured.
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.
Approval and pay paths open token URLs on mobile without a shop login.
Learn more →CX-35: inbound YES confirms booking; RESCHEDULE parks waitlist. Keyword path in demo — not AI voice or unlimited two-way chat.
Learn more →CX-23 safe keywords on public inbound + mock. Structured replies only.
SMTP path (Mailhog in dev) for booking, approval, and invoice events.
Provider port with mock default; Twilio-class config for real send. Never Connected without keys.
Learn more →Message history and dispatch surfaces on the repair order.
Learn more →Instant, 48-hour, and morning-of touches. Mock SMS until Twilio is keyed — never a live carrier claim.
Learn more →Template overrides API path; persistence across restarts expands.
Transactional vs commercial classes — marketing campaigns stay gated.
FORM_REQUEST and TABLET_READY dispatch the same packs as the counter iPad. Email on Starter; SMS on Growth.
Learn more →FAQ
Structured for humans and search (FAQ schema). We update when ship status changes.
No. Growth includes an SMS pack entitlement. Real send requires a provider. We do not claim Connected unlimited SMS packaging.
Yes in the demo keyword path (CX-35): YES confirms the booking; RESCHEDULE parks waitlist. Transport is mock SMS by default or Twilio when keyed — not a live carrier Connected badge.
Share the portal token link via any channel. SMS is optional transport; structured line state lives in the portal.