SMS consent and opt-out
SAGE sends text messages only after a customer gives express permission. Consent is separate from account signup, email consent, checkout, and terms acceptance.
Customer opt-in language
SMS checkboxes are unchecked by default and appear next to the phone field or notification settings. The consumer-facing checkbox says:
I agree to receive recurring text messages from this shop through SAGE for order, reservation, saved-item, customer-care, and shop update messages. Message frequency varies. Message and data rates may apply. Reply STOP to opt out, HELP for help. Consent is not required to buy anything.
Where opt-in happens
- Customer pull-list signup pages, when a shopper chooses text reminders.
- Customer account notification settings, where shoppers choose SMS topics and cadence.
- Shop dashboard customer import or manual customer add, only when the shop has collected equivalent express permission from the customer.
Consent proof stored
When SMS consent is enabled, SAGE stores the consent state, timestamp, method, disclosure text, and opt-in source with the customer record. Live sending is blocked for customers without saved SMS consent.
Message types and frequency
Texts can include order updates, reservation confirmations, pull-list arrival notices, customer-care replies, saved-item or back-in-stock alerts, and shop updates. Frequency varies by shop and customer choices.
Opt-out and help
- Reply STOP to opt out.
- Reply HELP for help.
- Every SAGE SMS also includes a signed opt-out link when available.
- Message and data rates may apply.
Sample messages
Riverbend Comics: Your pull list is ready for pickup. Reply STOP to opt out.
SAGE SMS test for Riverbend Comics: replies, delivery status, quota, and opt-out handling are wired. Reply HELP to verify replies; STOP opts out.
Indie Bookshop: The title you saved is back in stock. Reserve it here: https://indieco.shop/... Reply STOP to opt out.
Compliance boundary: SAGE does not sell SMS opt-in data. Shops and customers can revoke SMS consent at any time. Public sending remains behind sender verification, consent proof, STOP/HELP callbacks, quotas, and explicit owner approval.