sms_mock default · Twilio when env keys · not unlimited Connected SMS
Comms
SMS for workshops — mock default, Twilio when keyed
US cloud packages unlimited two-way texting as table stakes; AU peers vary between outbound-only and paid two-way add-ons. Workshop Wrench ships an adapter path: sms_mock in demo/CI, Twilio when credentials exist, with portal deep links as the decision surface. Pack entitlements are not the same as “Connected unlimited SMS.”
Problem shops feel
Customers ignore email; phone tag burns advisor time; estimate approval stalls when the link is hard to open on mobile.
How peers package it
Shopmonkey markets every-plan two-way SMS; Workshop Software sells two-way as an add-on; MechanicDesk historically leaned outbound. Transactional approval SMS sits under AU Spam Act expectations — consent and transactional purpose matter.
What works in Workshop Wrench today
- →Comms dispatch + RO timeline path Live+ for operational events
- →SMS provider: mock without Twilio SID/token; twilio mode when keys are configured
- →Estimate approval and reminders can carry portal deep links (decision on mobile without a desktop login)
- →Not marketed as unlimited two-way inbox on every plan
- →Email SMTP path works in dev via Mailhog; production SES is planned ops work
- →Marketing automation / review campaigns are separate Partial/Roadmap surfaces
Is SMS unlimited on Starter?
No such claim. Provider cost and plan packaging are honest when live; demo uses mock. Check Pricing for published entitlements — never invent “unlimited Connected.”
Do customers need an app to approve?
No. Token portal links open in a mobile browser for line approve/decline/defer when that flow is issued.
Spam Act / consent?
Transactional job messaging (booking, approval, invoice) is the primary design. Marketing blasts are not the day-one path and need separate consent handling when shipped.
Related: SMS feature hub · SMS estimate approval SEO · Comms feature · Portal process · All integrations