Every text checked for SMS compliance

A cart reminder fires at 2am in California. A customer who replied STOP last week gets the restock text anyway. Each one can turn into a carrier complaint or a demand letter.

The enemy is a text that leaves without anyone checking who it goes to and when.

Every text your brand sends now takes one path: the Send SMS step in automations, the replies to STOP, HELP and START, and test sends. The compliance checks run first, then the text goes out from your own Twilio number. Some checks always apply: STOP suppresses the number and sends one confirmation, START lifts it, the suppression list blocks even transactional texts, a Twilio opt-out error adds the number to the list, and invalid numbers and states you excluded are skipped. Quiet hours are on by default for marketing texts: 8am to 8pm in the recipient's local time from the area code, 9am to 7pm in Pennsylvania with no Sundays or federal holidays, 9am to 8pm in Connecticut. A held text goes out at the next open time.

Consent, state rules (Florida needs written consent, for example), the cap of 3 marketing texts per 24 hours, content such as bit.ly links, and sender registration are checked too. In Warn mode, the default, they are logged as warnings and the text still sends. Strict mode skips the text instead. Marketing texts wait until someone on the brand accepts the consent statement in Settings, SMS. When a shopper ticks the SMS box on a checkout, the wording of the box and the page URL are stored with the consent, and Consent lookup shows the whole history of a number with a JSON export. Settings, Logs, SMS lists every attempt with its status and the reason it was skipped. Twilio only for now, US numbers only. Compliance with texting laws stays your responsibility.

Try it: open Settings, then SMS. On Senders, click Add sender and pick a Twilio number, accept the statement on Compliance, then text your own phone from Test send.