Compliance
Tools to support your consent and messaging responsibilities
SMS is a regulated channel. Application guardrails do not replace legal advice, documented consent, carrier registration, or your own compliance review.
Consent comes first
US carriers require documented opt-in before you text anyone. MassText records a consent attestation — who confirmed it and when — on every contact list you import, and blocks imports without one.
Opt-outs before dispatch
Validated STOP-family replies add the recipient to the workspace suppression list. START can update consent when a newer verified event permits it; HELP receives an informational response. Suppression is checked before dispatch, but a message already submitted to a provider cannot be recalled. Webhook or provider delays can affect when an opt-out is known.
A2P 10DLC registration
US long-code traffic may require A2P 10DLC registration through Twilio. Because you use your own account, you are responsible for registration and applicable provider policies. Reported carrier errors can help investigate, but are not a guarantee of the cause or remedy.
Delivery you can audit
Provider acceptance and available carrier callbacks are recorded separately and can be exported. Missing callbacks remain unknown rather than being treated as delivered. Logs can assist your own records but do not prove consent or compliance.
What we expect from you
Only message recipients with valid consent. Identify your business, honor applicable quiet hours and opt-outs, and follow the laws and carrier policies that apply to your content and audience. The application does not automatically determine recipient-local quiet hours or the legality of your campaign.