Executive Summary
TCPA texting compliance is the discipline of obtaining, documenting, and honoring consent before your business sends automated or autodialed SMS to US wireless consumers—and of treating opt-out as a hard stop, not a marketing preference. FCC rules in 47 CFR § 64.1200 distinguish prior express written consent (typically for marketing/telemarketing texts using covered technology) from prior express consent (often sufficient for many informational messages). Separately, US carriers require A2P 10DLC Brand and Campaign registration for local long-code traffic. Registration identifies the sender; it does not invent consent for any phone number on your list.
Short answer: For US business SMS, assume you need a documented consent strategy. Marketing texts generally require prior express written consent. Many informational texts still require prior express consent. Honor reasonable revocation requests—including STOP and listed synonyms—within a reasonable time not to exceed ten business days, and preferably immediately in your messaging stack. 10DLC / TCR registration is not TCPA compliance.
Who This Is For / Who It Is Not For
Who this is for
- Compliance, legal-ops, and marketing teams sending US A2P SMS
- Product and CRM owners who design opt-in forms, POS flows, and keyword programs
- Agencies and ISVs that text on behalf of brands
- Operators who already registered 10DLC and still need a consent evidence program
Who this is not for
- Pure person-to-person texting with no application or automated platform
- Non-US destination regimes (different statutes and sender-ID rules)
- Anyone seeking case-specific legal advice, guaranteed litigation outcomes, or invented statutory dollar claims beyond what counsel confirms from primary law
- Programs that only need carrier registration checklists without consent architecture (see TCR how-tos instead)
Definitions
| Term | Working definition for operators |
|---|---|
| TCPA | Telephone Consumer Protection Act and FCC implementing rules restricting certain calls/texts |
| 47 CFR § 64.1200 | Primary FCC delivery-restriction rule for telemarketing/autodialed communications |
| ATDS | Automatic telephone dialing system—statutory/regulatory concept that still drives many consent analyses |
| Prior express consent | Consent that is affirmative but not necessarily “written” in the PEWC sense—often discussed for informational texts |
| Prior express written consent (PEWC) | Signed written agreement authorizing seller marketing texts/calls with required disclosures (see § 64.1200(f)(9)) |
| Telemarketing / advertisement | Content promoting goods or services—triggers higher consent expectations when technology rules apply |
| Revocation | Consumer withdrawal of consent by any reasonable method |
| A2P 10DLC | Carrier registration path for application-to-person SMS on US local numbers |
| TCR | The Campaign Registry—Brand/Campaign hub used by CSPs |
| Consent evidence trail | Reconstructable record of what the consumer agreed to, when, where, and for which program |
What TCPA Texting Compliance Covers
The TCPA and FCC rules restrict certain calls and texts to wireless numbers, especially when an ATDS or artificial/prerecorded voice is involved. Courts and the FCC have treated many modern SMS platforms as within the statute’s reach for consent analysis. Operationally: assume your business A2P texts need a documented consent strategy, even when your vendor markets “compliance built-in.”
TCPA texting compliance is not the same as:
- Passing spam filters
- Completing TCR Brand/Campaign registration
- Publishing a privacy policy alone
- Buying a scrubbed list
Those may be necessary or helpful, but none substitutes for recipient-level authorization and revocation handling.
For carrier registration context, see Twilio’s A2P 10DLC overview and MyTCRPlus consent evidence trail.
Consent Tiers for SMS
| Message purpose | Typical consent bar (operator framing) | Practical implication |
|---|---|---|
| Marketing / telemarketing texts using covered autodialing or related technology | Prior express written consent | Signed agreement; clear disclosures; number identified; not a condition of purchase |
| Informational / transactional texts (appointment reminder, account alert, order status) using covered technology | Often prior express consent (not always PEWC) | Still need affirmative permission tied to the program; document it |
| Manual, one-to-one human texts without covered automated dialing | Fact-specific; DNC and state rules may still apply | Do not assume “manual” means unregulated |
Classify by content and context, not by which CRM button you pressed. A “shipping update” that ends with a promo code is often treated as marketing by plaintiffs and reviewers.
Prior express written consent elements
Under the reinstated formulation reflected in the August 2025 Federal Register revision of § 64.1200(f)(9), prior express written consent is an agreement in writing bearing the signature of the person called that clearly authorizes the seller to deliver advertisements or telemarketing messages using an ATDS or artificial/prerecorded voice, and that identifies the telephone number authorized. The written agreement must include clear and conspicuous disclosure that:
- By signing, the person authorizes such telemarketing calls/texts; and
- The person is not required to sign or agree as a condition of purchasing property, goods, or services.
“Signature” includes electronic or digital forms recognized under applicable federal or state contract law. Confirm current eCFR text and counsel guidance before locking templates—definitions have been litigated and revised.
One-to-one consent note (label uncertainty)
The FCC previously revised PEWC toward a stricter one-to-one seller model and topical association requirements. Court action vacated that revision as of a 2025 mandate, and the Commission reinstated the prior definition in the Federal Register materials cited above. Do not assume either the vacated one-to-one rule or a permanent return to older practice without checking current § 64.1200(f)(9) and counsel. State AG theories and platform policies may still push toward narrower consent scopes.
Opt-Out and Revocation for Texts
FCC rules address how consumers revoke consent for covered calls and texts. Per § 64.1200 materials reflected in the March 2024 Federal Register and Cornell LII text:
- Consumers may revoke by any reasonable method that clearly expresses a desire to stop.
- Certain methods are reasonable per se, including reply texts using words such as stop, quit, end, revoke, opt out, cancel, or unsubscribe.
- Other reply wording must be honored if a reasonable person would understand it as a revocation request.
- If your protocol cannot accept reply texts, each message must clearly disclose that limitation and provide reasonable alternative revocation methods.
- Honor requests within a reasonable time not to exceed ten business days.
- Senders may not designate an exclusive means of revocation.
Confirmation texts
FCC guidance has long recognized that a one-time, non-promotional confirmation of an opt-out generally does not restart consent. Keep confirmation texts free of offers, cross-sells, and “are you sure?” marketing. Prefer near-real-time suppression in your platform even though the outer regulatory window is ten business days.
Multi-program senders
If a consumer receives fraud alerts, payment reminders, and marketing from the same brand, a vague STOP can be ambiguous. Some FCC materials discuss clarification prompts and default treatment when the consumer does not clarify. Build product logic with counsel: default to broader suppression when intent is unclear, and never continue marketing after a clear stop.
TCPA vs 10DLC / TCR (Do Not Confuse Them)
| Dimension | TCPA / FCC consent | A2P 10DLC / TCR |
|---|---|---|
| Primary question | Did this recipient authorize this message type? | Is this Brand/Campaign registered for carrier routes? |
| Unit of compliance | Phone number + purpose + technology | Brand identity + Campaign use case |
| Typical artifact | Signed disclosure, form log, IVR recording, keyword log | Brand ID, Campaign ID, samples, message flow |
| Failure mode | Private actions, regulatory scrutiny, reputation harm | Filtering, blocking, registration rejection |
| Fix when broken | Stop sends; remediate consent; counsel review | Fix packaging; resubmit; remediate content |
You can be fully registered and still violate consent rules. You can have perfect consent files and still fail carrier registration. Mature programs run both tracks.
Building a Consent Evidence Trail
CTIA Messaging Principles recommend retaining records such as:
- Timestamp of consent
- Medium (web form, POS, keyword, paper, IVR)
- Capture of the language and action used
- Specific campaign for which opt-in was provided
- Identity of the individual (or session identifier)
- Phone number consented
Minimum viable evidence fields
| Field | Why it matters |
|---|---|
phone_e164 |
Exact destination authorized |
consent_type |
PEWC vs express vs transactional disclosure |
program_id |
Maps to Campaign / use case |
disclosure_version |
Reconstruct what the consumer saw |
captured_at |
Timing defenses and audits |
channel |
Web, POS, SMS keyword, voice |
ip_or_store_id |
Context for disputes |
revoked_at / revoke_method |
Prove honor timeline |
Store evidence outside ephemeral chat logs. If a vendor rotates out of your stack, export consent and suppression lists first.
Decision Framework: Message-by-Message Gate
Before any template goes to production, run this operating procedure:
- Purpose test: Is the content advertising/telemarketing or purely informational?
- Technology test: Is an automated platform selecting and sending to stored numbers?
- Consent tier: PEWC vs prior express consent vs “do not send”?
- Scope test: Does the stored consent cover this brand, this program, and this content type?
- Age / reassigned number test: Scrub or verify numbers; handle recycled wireless numbers with a documented process.
- Quiet hours / state overlays: Check state telemarketing and texting rules that may be stricter than federal baselines.
- Opt-out readiness: Can STOP land in a suppression service within minutes across all senders?
- Audit sample: Pull five random recipients monthly and reconstruct their consent story end-to-end.
If any gate fails, block the send. Do not “fix after launch.”
Risk and Failure Modes
| Failure mode | Why it hurts | Mitigation |
|---|---|---|
| Lead-gen / shared consent claims | Consumers did not clearly authorize your brand | First-party consent; review lead contracts with counsel |
| Pre-checked marketing boxes | Consent looks coerced or unclear | Unchecked boxes; affirmative click |
| Bundled “I agree to Terms + SMS marketing” | Hard to prove clear authorization | Separate SMS marketing action |
| Assuming 10DLC approval = consent | Registration does not authorize recipients | Dual program: TCR + consent CRM |
| Slow STOP propagation | Texts continue after revoke | Central suppression; vendor SLAs under 10 business days (prefer hours) |
| Marketing inside transactional templates | Reclassifies message as promo | Separate templates and audiences |
| Buying lists | No PEWC chain | Do not text purchased lists for marketing |
| Ignoring state law | Federal floor is not always enough | Maintain state matrix with counsel |
Private TCPA litigation often cites statutory damages frameworks under 47 U.S.C. § 227. Exact exposure is case-specific—do not treat blog “average settlement” figures as your risk model. Engage qualified counsel for quantified risk analysis.
Implementation Checklist
| Step | Owner | Artifact |
|---|---|---|
| Inventory all SMS templates by purpose | Marketing ops | Template register |
| Map each template to consent tier | Compliance | Consent matrix |
| Rewrite web/POS disclosures for PEWC where needed | Legal + UX | Approved copy deck |
| Instrument consent logging | Engineering | Schema + retention policy |
| Implement keyword + reasonable-method revocation | Messaging admin | STOP/HELP handlers + alternate channels |
| Centralize suppression across ESP/CPaaS/CRM | Engineering | Suppression service API |
| Align 10DLC Campaign samples with real consent flows | CSP admin | Campaign packet |
| Train staff (no verbal “you’re on the list” shortcuts) | Ops lead | Training attestation |
| Monthly evidence audit | Compliance | Audit worksheet |
| Incident playbook for complaint / demand letter | Legal | Response SOP |
Soft CTA
If you are packaging carrier registration alongside consent pages, use MyTCRPlus tools to preflight Brand/Campaign consistency and review compliance microsite options for public disclosures. Tools help packaging quality; they do not create legal consent or guarantee dispute outcomes.
Internal Linking Suggestions
/video-wall/the-consent-evidence-trail-tcpa-protection//single-vs-double-opt-in-for-sms//how-to-register-with-tcr-the-complete-step-by-step-process-for-10dlc//msg-and-data-rates-disclosure-required-wording-placement-and-when-it-applies/- Draft companions:
15-tcpa-text-message-rules.md,76-tcpa-exemptions.md,36-tcpa-compliance-certification.md,05-how-to-document-verbal-consent-for-sms.md
Practical Program Architecture for Marketing vs Informational SMS
Mature organizations separate lanes:
- Lane A — Service / account / transactional: order status, password resets, appointment reminders, fraud alerts. Capture purpose-limited consent at the moment of the relationship event (checkout, booking, account open). Keep templates free of offers.
- Lane B — Marketing / loyalty promos: recurring offers, win-backs, abandoned-cart promos. Capture PEWC with unchecked affirmative action, frequency and rate disclosures, and links to privacy/terms.
- Lane C — Care conversations: two-way support after the consumer texts in or opens a ticket. Document the conversational context; do not silently enroll the number into Lane B.
Each lane should map to different audiences in your ESP/CPaaS, different 10DLC Campaigns when carrier packaging requires it, and different suppression logic. A STOP on Lane B should never be ignored because Lane A still needs to deliver a fraud alert—design product exceptions with counsel, and prefer asking the consumer to clarify when multiple programs exist.
Illustrative disclosure patterns (educational only)
Marketing PEWC checkbox (unchecked): “I agree to receive recurring automated marketing text messages from [Brand] 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. See Privacy Policy and SMS Terms.”
Informational booking disclosure: “By providing your mobile number, you agree to receive text messages from [Brand] about this appointment (confirmations, reminders, and day-of updates). Msg & data rates may apply. Reply STOP to opt out of these texts, HELP for help.”
Have counsel localize these patterns. Do not treat them as guaranteed safe harbors.
Record Retention, Audits, and Vendor Offboarding
Consent evidence is only useful if you can produce it years later. Align retention with litigation hold practices and vendor contracts:
- Define a retention period with counsel (many teams keep consent and suppression logs for multiple years).
- Prohibit vendors from deleting consent metadata on contract termination without an export.
- Run quarterly audits: sample 25 random sends, reconstruct consent, confirm Campaign alignment, and confirm STOP latency.
- Document reassigned-number handling (wireless number recycling) so you do not keep texting a new subscriber who never opted in.
When offboarding a CPaaS or CRM, export: active consents, revocation list, disclosure versions, and Campaign IDs. Losing the evidence trail is a silent failure mode that surfaces only when a demand letter arrives.
Quiet Hours, DNC, and State Overlays
Federal TCPA rules interact with National Do Not Call concepts for certain telemarketing calls and with state mini-TCPA or consumer-protection statutes. Operational checklist:
- Maintain a state matrix for consent wording, time-of-day restrictions, and private rights of action.
- Do not assume wireless marketing texts are “safe” solely because a number is absent from the National DNC Registry—consent rules still apply.
- Coordinate email unsubscribe and SMS STOP where consumer expectations blur channels, even if legal standards differ.
Exact state requirements change; assign an owner to refresh the matrix at least annually with counsel.
FAQ
Does TCPA apply to SMS?
Yes—FCC rules and TCPA litigation routinely treat many business texts as covered communications when consent and technology triggers apply. Read § 64.1200 with counsel for your fact pattern.
Is 10DLC registration enough for TCPA texting compliance?
No. Registration satisfies carrier identity/use-case requirements for 10DLC routes. TCPA compliance is about recipient authorization and revocation.
What consent do I need for marketing texts?
Typically prior express written consent when marketing texts are sent with covered autodialing or related technology. Confirm definitions and disclosures against current § 64.1200(f)(9).
What about appointment reminders?
Often framed as informational with prior express consent—but adding offers can convert them into marketing. Keep templates clean and document the disclosure at booking.
How fast must I honor STOP?
Rules require a reasonable time not exceeding ten business days. Best practice is near-instant suppression across all systems, plus a single non-promotional confirmation.
Which STOP words count?
Enumerated examples in FCC materials include stop, quit, end, revoke, opt out, cancel, and unsubscribe. Other clear language can also count. Do not require magic spelling only.
Can I buy a list if the broker “guarantees consent”?
Treat purchased marketing SMS lists as high risk. You need a reconstructable consent chain to your brand and program—not a broker warranty alone.
Do state laws matter if I follow the TCPA?
Yes. States may impose additional consent, quiet-hours, or private-right theories. Maintain a state overlay with counsel.
What changed with one-to-one consent?
A stricter one-to-one PEWC revision was vacated by court mandate and the prior definition was reinstated in 2025 rulemaking materials. Verify the live eCFR text before redesigning forms.
Where should legal and marketing start this week?
Build the consent matrix, fix marketing disclosures, implement cross-system STOP, and align Campaign samples with real opt-in pages—then schedule counsel review.
Key Takeaways
- TCPA texting compliance centers on consent tiers, evidence, and revocation—not carrier logos on a registration portal.
- Marketing texts generally need prior express written consent with clear disclosures and a valid signature form.
- Informational texts still need documented prior express consent in most automated programs.
- Honor reasonable opt-outs within ten business days; design for minutes, not the outer deadline.
- 10DLC/TCR registration does not create consent for any recipient.
- Preserve a reconstructable evidence trail for every opt-in and opt-out.
- Watch definitional changes in § 64.1200 with counsel; do not rely on outdated one-to-one assumptions without verification.
- Pair legal process with carrier packaging so samples, message flows, and live forms tell the same story.
Disclaimer
This article is for informational and educational purposes only and is not legal advice. TCPA, FCC, state, and carrier requirements change and are fact-specific. Confirm consent language, technology coverage, revocation workflows, and litigation strategy with qualified counsel before sending.