TCPA text message rules for marketing teams

Treat text messages as calls under the TCPA

Text messages are treated as calls under the TCPA. A business cannot avoid the statute simply by using SMS instead of voice. The applicable restrictions depend on the message's purpose, the technology used, the number receiving it, and any relevant exemption. Other federal and state rules can apply even where a particular automated calling restriction does not.

Facebook v. Duguid narrowed the federal autodialer definition in 2021. That decision is relevant to systems sending texts, but it does not make every business messaging program exempt. Do-not-call obligations, state laws, and carrier consent requirements need separate review. Ask counsel to assess the actual sending system and campaign, rather than treating the word manual in a platform description as the complete legal analysis.

For a broader treatment of the federal framework and court decisions, read TCPA regulations for lead generators. This article provides general information, not legal advice. Laws, interpretations, and carrier requirements change, so confirm the standards relevant to your program.

Obtain written consent for covered marketing texts

Prior express written consent is required for marketing texts sent using an automatic telephone dialing system within the TCPA definition, absent an applicable exception. Operationally, obtain documented written opt-in before marketing enrollment rather than relying on a disputed technology classification. The agreement should clearly authorize the seller's covered messages to the specified number and include the required statement that consent is not a condition of purchase.

The signature process matters as much as the disclosure. An electronic action can qualify when it satisfies applicable signature requirements and expresses agreement to the terms presented. Entering a phone number to receive an order update does not by itself establish permission for unrelated promotions. Keep marketing enrollment clear when the same form also handles a quote, purchase, or service request.

Use SMS consent records to connect the disclosure and action to the subscriber. Retain the actual agreement, rather than only a field saying that the person is subscribed. A useful record lets a reviewer determine which seller, program, purpose, and channel the person authorized.

Separate service messages from promotions

Classify messages by their content and purpose. A delivery update and a promotional offer raise different consent questions. Adding a sales pitch to an otherwise operational message can change the analysis. Document which message categories belong in each program and have counsel review mixed content before it reaches the sending queue.

Giving a number during a transaction can support permission for communications within the context of that transaction, depending on the facts and applicable rules. It should not be treated as unrestricted permission for every later marketing use. If the business wants to add a promotional program, collect the appropriate agreement and preserve it separately from the original service interaction.

Make the opt-in understandable before submission

Present the brand or program identity, message purpose, and frequency clearly. Explain when frequency varies, if that accurately describes the program. Include message and data rates language, STOP instructions, a HELP route, and links to the applicable terms and privacy policy. These elements support industry expectations alongside the written consent requirements that apply to covered marketing texts.

• Identify the seller and explain what messages the consumer will receive.
• Keep the disclosure near the action that signifies agreement.
• Use an affirmative choice and avoid preselected marketing checkboxes.
• Explain how to stop messages and how to request assistance.
• Preserve the disclosure as it appeared when the person subscribed.

Check the flow on a phone, including text size, link access, and changes caused by error messages. The consent verification features include disclosure checks that help surface missing wording. Automated review supports your assessment of the flow, while the actual screen and consumer action remain essential evidence.

Keep the invitation with the opt-in event

Web and keyword enrollment need context. For a web form, preserve the page, wording, phone number, submission action, and timestamp. For a keyword invitation, retain the material explaining what sending the keyword means and the incoming response associated with that invitation. A keyword used to ask for support does not automatically enroll the sender in marketing.

If the program uses an additional confirmation step, keep that interaction with the original request. Confirmation can help resolve uncertainty, but it does not repair a misleading invitation. Review purchased or transferred numbers against the agreement that was actually collected. A list described as opted in does not establish that each recipient authorized your seller or your program.

Apply quiet hours at the recipient's location

Use the federal telemarketing window of 8 a.m. to 9 p.m. local time as a starting boundary when reviewing marketing texts. Applicable state laws and carrier policies can require a tighter sending window. A uniform national schedule can create problems when recipients live in different time zones or when a state imposes additional restrictions.

Determine the relevant local time using appropriate information, with a documented approach for uncertain locations. Area codes are imperfect because people move and keep their numbers. Apply the timing check when a message is released, including automated follow-ups and delayed retries. A campaign scheduled during an allowed period can still generate a later message outside that window.

Operational messages need their own classification and rules. Do not label promotional texts transactional to bypass a quiet-hours control. Keep the campaign purpose and applicable schedule associated with each message so support and compliance teams can explain why it was released.

Recognize revocation by any reasonable means

The FCC revocation framework allows consumers to withdraw consent by any reasonable means. STOP is an important mechanism, but a reasonable request can use ordinary language or arrive through another appropriate channel. Train staff to recognize a request to stop even when it does not match the keyword your messaging system expects.

A recipient might ask an agent to stop texting or send a message saying they no longer want promotions. Preserve the wording, timestamp, program context, and response. Apply the relevant timing and scope requirements, and route ambiguous requests for prompt review. The workflow should prevent the affected outreach from continuing while staff determine how to handle the request.

Counsel should define how current rules apply across different programs and message categories. Systems should implement that scope consistently and avoid narrowing a clear request merely because subscriptions are stored separately. An opt-out received by support needs a reliable path to the sending systems and any vendor acting for the business.

Make STOP handling reach every relevant queue

Configure STOP processing before the program sends marketing messages. Preserve the incoming request and suppression event, then prevent further affected messages from being released. Review scheduled sends, automated journeys, retries, and vendor-managed queues. A suppression flag in the CRM is insufficient if another system continues sending from an earlier export.

• Recognize supported opt-out keywords and reasonable plain-language requests.
• Associate the request with the correct number and affected program scope.
• Remove or block affected queued outreach and retain handling evidence.
• Keep any permitted confirmation limited to its allowed purpose.
• Prevent imports from silently restoring a suppressed subscription.

If a person later asks to subscribe again, obtain and retain the appropriate new agreement. A fresh lead delivery is not automatically a fresh opt-in. Keep the original enrollment, withdrawal, and subsequent permission connected so the subscription history remains understandable.

Distinguish CTIA guidance from carrier requirements

CTIA messaging guidance addresses wanted messaging, transparent enrollment, and functional opt-out and help processes. Carrier and messaging provider policies can add requirements for program content, registration, disclosures, and acceptable use. These industry expectations are distinct from statutory TCPA duties, even when they address similar issues such as consent and suppression.

Review the rules for the channel and use case you operate. Maintain a working HELP response that identifies the program and provides a usable support route. If you state a frequency, make sure actual sending behavior matches it. Program materials, opt-in screens, and message content should describe the same service, rather than different versions of the campaign.

Carrier approval does not decide whether a particular recipient consented under applicable law. Likewise, a legal assessment of the sending technology does not ensure carrier acceptance. Track both reviews and keep the supporting materials available when a reviewer asks how subscribers enter and leave the program.

Keep 10DLC registration connected to consent evidence

Business messaging through applicable US long-code channels involves 10DLC brand and campaign registration requirements. Registration describes the sender, use case, and messaging program. It does not grant permission to contact every number in a database, guarantee message delivery, or resolve the legal status of a purchased list.

Prepare a consistent account of the enrollment flow, program purpose, opt-in wording, and STOP and HELP handling. Carrier reviewers may request additional material based on the use case. Use the 10DLC compliance workflow to organize evidence that matches the program you actually operate. Reassess that material when the acquisition flow or campaign purpose changes.

Review state mini-TCPA and do-not-call obligations

States including Florida and Oklahoma have telemarketing laws that can affect text campaigns. State requirements can differ from the federal framework in their technology definitions, consent standards, scheduling restrictions, contact limits, exemptions, and remedies. Do not assume a conclusion about federal autodialer coverage settles the state analysis. Review the law and current interpretations applicable to the consumer and campaign.

Federal and state do-not-call requirements may also apply to marketing texts. Review relevant registry screening, internal suppression, and any legally supported exception as separate controls. Use DNC list scrubbing alongside TCPA consent verification, with counsel defining how the results affect outreach. An opt-in certificate and a registry check answer different questions.

Preserve a subscription history your team can explain

Keep the initial disclosure, affirmative action, collection context, and later requests together. Retain message content and sending history where appropriate so a reviewer can compare actual outreach with the permission collected. Access controls and a retention policy should account for applicable legal requirements, disputes, and privacy obligations.

Periodically trace a subscriber through enrollment, campaign assignment, message release, and suppression. Confirm that the evidence remains retrievable and that each system applies the same current status. Record and correct discrepancies before repeating the affected workflow. Useful checks address what the consumer experiences, rather than only whether an integration reports success.