Compliance
Consent, sender registration, message content, opt-outs, and quiet hours.
Business texting in the US is regulated by law (the TCPA), governed by carrier rules (the CTIA guidelines and 10DLC registration), and enforced in practice by carrier filters that silently drop traffic they don't like. Most of this is handled by your account setup and by the platform. The part that lands on the integration (what you send, to whom, and when) is small and concrete. This page covers that part.
It's an engineer's summary of the rules that affect what your code does. Your business is responsible for its own compliance; talk to counsel for anything specific.
Who handles what
| Concern | Handled by |
|---|---|
| Registering your brand and campaign with carriers (10DLC) or verifying a toll-free number | Your account setup, with EZ Texting's help. Done once, before you send at volume. |
| Honoring STOP, UNSUBSCRIBE, and the other opt-out keywords | The platform. The contact is marked optOut and future sends are blocked automatically. |
| Answering HELP | The platform. |
| Collecting consent before the first message | You. |
| Identifying your business in each message | You. Put the name in the message, or set companyName (the Subject in the web app). |
| Message content | You. |
| Sending at reasonable hours | You, with help: sendAt lets you schedule into the window. |
| Keeping consent records | You. |
Consent
The rule: get prior express written consent before you text someone. That means an affirmative, unambiguous action by the person, with a clear disclosure of what they're signing up for. A purchase, a booking, or a phone number on file isn't consent by itself.
Common ways to collect it: an unchecked checkbox next to clear consent language where you collect the number, a keyword texted to your number, or a double opt-in confirmation.
What makes consent language adequate, in practice: who's sending, what kind of messages, roughly how often, that message and data rates may apply, how to opt out, and that consent isn't a condition of purchase. A typical disclosure:
By checking this box you agree to receive recurring automated marketing texts from Acme at the number provided. Consent is not a condition of purchase. Msg frequency varies. Msg & data rates may apply. Reply STOP to opt out, HELP for help.
For API integrations specifically:
- Store the consent record: timestamp, source (form URL, keyword, or a recorded verbal opt-in), the exact disclosure shown, the number, and for web forms the IP address of the person signing up. If a complaint ever comes, this is what you produce.
- Don't infer consent. A number in your CRM, or a past purchase, is not consent. The use-case guides all use the same shape: a
smsConsentflag captured where the number is collected, with the record stored alongside it. - Keywords are consent. When someone texts
JOINto your number, the platform records the opt-in. If you subscribe to thekeyword.opt_inwebhook, you get a record for your own system too. - Consent is per brand. If you text on behalf of multiple businesses, each needs its own.
Sender registration: 10DLC and toll-free
Carriers require businesses to be registered before sending application-to-person (A2P) traffic. Unregistered traffic is heavily filtered or blocked outright.
| Number type | Registration | Good for |
|---|---|---|
| 10DLC (standard 10-digit local number) | Brand + campaign registration via The Campaign Registry (TCR). You declare who you are and what you'll send. | Most business use. Local presence. Throughput depends on your brand's trust score. |
| Toll-free (8XX) | Toll-free verification: a form describing your use case and sample messages. | Higher throughput, nationwide identity, strong for OTP and notifications. |
| Short code (5–6 digits) | Dedicated approval process; leased. | Very high volume. The preferred choice for OTP and large campaigns. |
Registration happens in your EZ Texting account, not through the API. What the API integration needs to know:
- Your registered use case constrains your content. If your campaign is registered for "account notifications" and you start sending promotions, expect filtering, and possibly a registration review.
- Sample messages matter. The samples submitted at registration should look like what your code actually sends. If you change your message templates significantly, tell whoever manages the registration.
- Throughput is a property of the number. If you need more, the answer is a different number type, not more API calls.
Message content
What every message should have:
- Your business name. Put it in the message, or set
companyName(the Subject in the web app) on the send or template, which adds it in parentheses before the text. A message that doesn't say who it's from reads as spam to both recipients and carrier filters. - Opt-out instructions (
Reply STOP to opt out) on the first message of any relationship and periodically on recurring marketing. How often is a compliance question (carrier and CTIA guidance differ by program type); confirm the cadence for your registered use case rather than assuming "first message only". - A reason to exist. Say the thing: the code, the time, the tracking link.
What gets messages filtered or accounts suspended:
| Avoid | Why |
|---|---|
| Public URL shorteners (bit.ly, tinyurl, etc.) | Carriers associate them with spam. Use a branded short domain or EZ Texting's own link shortener. |
| ALL CAPS, excessive punctuation, "FREE!!!" | Classic spam signals. |
| Content outside your registered use case | See Sender registration. |
| SHAFT content (sex, hate, alcohol, firearms, tobacco), plus cannabis/CBD, gambling, high-risk financial offers, debt collection without proper setup, third-party lead gen | Carrier-prohibited or restricted categories. Some are allowed with age-gating and specific registration; most aren't allowed at all on 10DLC. |
| Phishing-adjacent patterns: "your account is locked, click here" from an unregistered brand | Will be filtered and may get your number blocked. |
If a legitimate message is being filtered, the fix is to change the content or the registration, not to work around the filter. Troubleshooting has the diagnostic steps.
Opt-out
What EZ Texting does: when a contact replies STOP, UNSUBSCRIBE, QUIT, END, CANCEL, or REMOVE, the platform marks them optOut: true, sends a confirmation, and refuses to deliver further messages to that number from your account, including ones your code sends. You don't have to implement any of that, and you can't bypass it.
Your side:
- Read
optOuton contacts and reflect it in your own system. A "text this customer" button that leads to a silent not sent is a bad experience for your staff. - Honor opt-outs across channels. If someone unsubscribes on your website, opt them out with
POST /v1/blocks. Use it only for real opt-outs: it marks the numberoptOut: true, and the API can't undo it. - Don't re-add opted-out numbers by re-importing a list. Upserting a contact doesn't clear
optOut, but double-check after bulk imports withfilters[optOut][eq]=true. - Opt-out requests that aren't standard keywords ("please stop texting me") land in your inbox as normal inbound texts. If you run a two-way integration, handle them: block the number and reply once.
Quiet hours
Federal rules prohibit marketing texts before 8am or after 9pm in the recipient's local time. Several states are stricter (narrower windows, holiday restrictions, or a cap on messages per day). Check the rules for the states you send to.
For the integration:
- Store a time zone (or at least an area-code-derived guess) per contact.
- Schedule with
sendAtinto the window rather than sending immediately from a nightly job. - For campaigns, send mid-morning to early evening local. Don't blast a national list at 9am Eastern. That's 6am in California.
- Your EZ Texting account also has a quiet hours setting, but it may not apply to every send (one-to-one API sends, for example). Handle the window in your own code rather than relying on it.
Coverage
This page covers US rules. Messages to Canadian numbers are also subject to Canada's anti-spam law (CASL) and CRTC rules.
Keep records
Retention is cheap and discovery is expensive. Keep:
- Consent: when, how, and what was shown, per number.
- Sends: the message
id, recipient, text, and timestamp. - Opt-outs: the platform tracks them; export periodically (
GET /v1/contacts?filters[optOut][eq]=true). - Inbound messages: if you run two-way, keep the thread.
Checklist for a new integration
- Brand and campaign registered (10DLC) or toll-free number verified, for the use case you're actually building.
- Consent captured at the point the number is collected, with appropriate language, and stored.
- Every message identifies your business, in the text or with
companyName. - Opt-out language on first-contact and recurring marketing messages.
-
optOutrespected in your own UI; opt-outs from other channels sent viaPOST /v1/blocks. - Sends scheduled into 8am–9pm local (narrower where required).
- No public URL shorteners; content matches the registered use case.
- Consent and send records retained.
Related
- Core concepts — opt-in, opt-out, and keywords
- Webhooks — opt-in and opt-out events
- Campaigns to a group — marketing sends and consent
- Order & shipping notifications — consent at checkout
Further reading
- CTIA Messaging Principles and Best Practices, at ctia.org
- The Campaign Registry — 10DLC registration
- FCC TCPA rules, at fcc.gov
- EZ Texting support — for registration help and content questions
Try Troubleshooting, check status.eztexting.com, or contact support.
Updated 3 days ago