Portal decide
LiveLine-level mobile approval without shop login.
Learn more →Comms · authorisation
SMS estimate approval that lands as structured line state
The winning pattern is not “reply YES to approve $2,400.” It is an SMS (or email) with a deep link into a portal where each line can be decided — so the shop floor and invoice stay honest.
Primary search intent: SMS estimate approval auto repair
AU shops should separate transactional service messages from marketing campaigns for Spam Act compliance. We treat that as a design requirement, not a footnote.
Buyer problem
What shops feel without a real OS
Free-text SMS approvals do not map to lines, tax, or audit — and fail Spam Act / consent scrutiny when mixed with marketing.
Why Workshop Wrench
Reasoning behind this category page
- 01
Portal is the decision surface; SMS/email is the notify channel.
- 02
Event catalog for approval-required style comms with adapters.
- 03
Transactional vs marketing consent treated as a product concern (AU Spam Act awareness).
- 04
Board and reserves react to structured outcomes, not inbox archaeology.
Capabilities
What ships — with honest status
Live means in the multi-tenant product/demo. Integrations: Live / Stub / Dry-run / Planned — never Connected for stubs.
Email path
LiveSMTP to Mailhog in dev; production SMTP configurable.
Learn more →SMS adapter
PartialProvider port with mock for local; Twilio-class config for real send.
Learn more →Reserve on approve
LiveApproved part lines can reserve stock so production is real.
Learn more →Also ranks for adjacent intent
- text estimate approval workshop
- auto repair approval SMS
- mobile estimate authorisation
FAQ
Questions buyers actually ask
FAQ schema included for search. Updated when ship status changes.
Do you send SMS out of the box?+
Local/dev uses mock SMS. Configure a provider for production send. Portal approval works independently of SMS once the customer has the link.