Prior Express Written Consent for SMS

Who This Is For / Who It Is Not For

Who this is for: US businesses, compliance owners, marketing ops, and product teams that send or enable A2P SMS and need practical registration, consent, or troubleshooting guidance tied to 10DLC/TCR and TCPA concepts.

Who this is not for: Readers seeking invented fine amounts, guaranteed approval rates, or universal throughput figures; purely P2P consumer texting with no application layer; teams outside US A2P rules who need only foreign-regulator advice.

Short answer: Prior express written consent (PEWC) is the TCPA consent standard that generally applies when you send marketing / telemarketing texts using covered autodialing or artificial/prerecorded technologies. Under 47 CFR § 64.1200, PEWC is a written agreement with a valid signature that clearly authorizes ads/telemarketing texts to a specified number. It is not the same thing as A2P 10DLC / TCR registration.

Definitions

PEWC in the Regulation (Plain English)

Section 64.1200 restricts certain calls and texts. For telemarketing/advertising using an automatic telephone dialing system or artificial/prerecorded voice, the rule generally requires the called party’s prior express written consent (with limited exceptions—for example, certain nonprofit or health-care message contexts described in the rule).

The regulation’s definition of prior express written consent centers on:

• An agreement in writing
• Bearing the signature of the person to be called/texted (electronic signatures may qualify when recognized under applicable federal or state law—see the rule’s signature language)
• Clearly authorizing the seller to deliver advertisements or telemarketing messages using ATDS or artificial/prerecorded voice
• Identifying the telephone number authorized to receive those messages

The written agreement must include clear and conspicuous disclosures, including that:

• Signing authorizes telemarketing calls/texts using ATDS or artificial/prerecorded voice; and
• The person is not required to sign (directly or indirectly) as a condition of purchasing property, goods, or services.

Always read the current eCFR text—definitions have been amended over time.

One-Seller and Topical Association Updates

FCC amendments to § 64.1200(f)(9) tightened PEWC so consent clearly and conspicuously authorizes no more than one identified seller, and so calls/texts are logically and topically associated with the interaction that prompted consent. The FCC announced OMB approval and compliance timing in a November 6, 2024 Federal Register document. Use that primary source (and counsel) for compliance-date analysis—do not rely on undated blog summaries.

Practical implication for lead-gen and comparison sites: shared “consent for our partners” designs that name many sellers in one click face heightened scrutiny under the one-identified-seller framework.

What PEWC Is Not

See single vs double opt-in for SMS.

Drafting Consent Language (Illustrative Patterns)

These are illustrative patterns, not a counsel-approved form:

“By checking this box, I agree to receive recurring automated marketing text messages from Acme Inc. 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 Terms.”

Checklist against the rule’s themes:

• Identify one seller clearly (Acme Inc.)
• State automated marketing texts authorization
• Capture the phone number
• Include not a condition of purchase disclosure
• Keep disclosure clear and conspicuous (not buried in a 40-page terms dump alone)
• Retain signature evidence (checkbox + ESIGN process, wet ink, etc.)

For Campaign registration, your CSP also wants a message_flow that a reviewer can verify—Twilio’s collect-business-info and approval best practices describe packaging expectations separately from TCPA litigation standards.

Evidence You Should Keep

Build a consent audit trail:

• Timestamp (with time zone)
• Phone number
• Exact disclosure text / version ID
• Signature or checkbox state
• IP address / user agent for web forms
• Landing page URL
• Campaign/program ID
• Opt-out history

More on trails: consent evidence video. MyTCRPlus tools can help review disclosure wording consistency before you submit Campaigns—without replacing legal review.

Revocation

§ 64.1200 addresses revocation of prior express consent, including PEWC, by reasonable methods. Reply keywords such as STOP (and related words listed in the rule) are treated as reasonable means per se in the current regulatory text. Honor opt-outs promptly; do not treat “STOP” as optional after registration.

Marketing vs Customer-Care Copy Tests

Ask of every template:

1. Does it advertise property, goods, or services or encourage a commercial transaction?
2. Is it only fulfilling an existing transaction or appointment the user already scheduled?
3. Would a reasonable recipient call it a “promo”?

If (1) or (3) is yes, design for PEWC. If you only send (2), document prior express consent appropriate to informational traffic—and still register the 10DLC Campaign accurately so samples do not look like marketing while labeled Customer Care.

Mixed inboxes (care + promo) need either separate Campaigns/lists or Mixed use-case packaging and consent that covers the promotional portion.

State Law Overlay

Some states impose additional telemarketing or texting requirements (registration, quieter hours, or consent nuances). PEWC under federal TCPA is a floor for covered traffic, not always a ceiling. Coordinate federal consent design with state counsel where you text residents heavily.

Operating Model and RACI

Treat compliance as an operating system. Assign owners who remain accountable after launch:

When ownership is ambiguous, shadow IT sending tools appear and registered Campaigns drift from production copy. Reconfirm the RACI every quarter and after any CSP migration. Document escalation contacts for rejection codes and who may edit live templates during incidents.

Evidence Binder and Audit Readiness

Maintain a living binder with Brand submission payloads or console screenshots (secrets redacted); formation and EIN documents used during verification; dated archives of website, privacy policy, and SMS terms URLs; opt-in journey screenshots or recordings; Campaign description, message_flow, and versioned samples; CSP approval or rejection emails and reason codes; STOP and HELP response templates; and monthly exports of opt-out volume and complaint tags. These artifacts accelerate CSP remediations and support legal holds. Align retention with counsel because message logs are frequently discoverable. Index the binder by Campaign ID so on-call staff can find evidence in minutes.

Technical Controls Matrix

Engineering should treat Campaign-not-active as a hard failure, not a warning. Pair controls with runbooks that name the first three debugging steps for the most common CSP error codes.

Governance Cadence

Weekly: deliverability and error-code review; spot-check Brand identification and STOP language on random outbound messages. Monthly: consent QA for every new lead source; confirm privacy and SMS URLs still load without login. Quarterly: full Campaign-to-production alignment; refresh training; read the CSP 10DLC changelog end to end. Annually: reconfirm legal name, tax ID, and authorized representatives; renew vendor diligence. Publish a one-page leadership scorecard covering share of traffic on registered Campaigns, opt-out rate, open remediations, and time-to-suppress after STOP.

Vendor and ISV Diligence

If an agency, ATS, EHR, CRM, or ISV sends on your behalf, contract for your organization as Brand of record unless a deliberate reseller model applies; notice within an agreed window of Campaign rejection or suspension; shared dashboards or weekly status exports; STOP propagation into your system of record within minutes; prohibition on mixing unrelated customers onto your Campaign; and an annual security and compliance questionnaire. Many filtering events originate in reseller infrastructure. Diligence is cheaper than silent non-delivery during peak season. Keep a vendor inventory that lists every system capable of emitting SMS.

Legal Overlay (Not Legal Advice)

Registration and consent are related but distinct. An approved Campaign does not prove TCPA consent for a particular send; perfect consent records do not move unregistered traffic through carrier blocks. Coordinate with counsel on when prior express written consent is required, how revocation must be honored under 47 CFR section 64.1200 and related FCC guidance, which state mini-TCPA rules apply to your footprint, retention periods for consent artifacts, and vendor liability terms. Do not invent statutory penalty figures in training decks—cite primary sources and counsel memos instead. Revisit the overlay whenever marketing launches a new list source or message purpose.

Soft CTA

Prepare Brand packets, public SMS disclosures, and pre-submission diagnostics with MyTCRPlus tools at https://mytcrplus.com/tools/ and related microsite options. They help you organize evidence for your CSP—they do not guarantee approval, throughput, or legal compliance. Pair preparation with the step-by-step TCR registration guide at https://mytcrplus.com/how-to-register-with-tcr-the-complete-step-by-step-process-for-10dlc/ and troubleshooting pages for unregistered traffic blocks when deliverability collapses.

Change-Control Playbook

When templates, vendors, or CSP rules change: log the source URL and timestamp; classify impact across Brand, Campaign, consent UX, billing, and API; freeze related sends if resubmission is likely; assign one incident owner with a clear due date; notify support and marketing with non-speculative language; retest major US carriers after the fix; and write a short postmortem that updates the runbook. Controlled change beats reactive copy edits during an outage. Store playbook outcomes beside the evidence binder so audits show both prevention and response.

Launch and Scale Checklist

Do not skip the smoke test. A Campaign can show approved while a single MNO still has not provisioned the share, producing carrier-specific failures that look like random filtering to marketers.

Decision Framework Recap

1. Confirm you are sending US A2P over local 10DLC (vs toll-free or short code).
2. Map each template to marketing or operational purpose.
3. Assemble accurate Brand identity and public website evidence.
4. Write Campaign narratives and samples that match production truth.
5. Submit through your CSP and wait for Brand eligibility before Campaign create.
6. Attach numbers only after Campaign approval and provisioning.
7. Enforce STOP globally and monitor error codes.
8. Audit consent artifacts and sample drift on a fixed calendar.
9. Escalate CSP reason codes with evidence—not guesses.
10. Keep TCPA counsel in the loop for new message purposes.

This framework applies whether you run healthcare reminders, staffing shift fills, nonprofit fundraising, or retail promotions.

Operating Model and RACI (continued 10)

Treat compliance as an operating system. Assign owners who remain accountable after launch:

When ownership is ambiguous, shadow IT sending tools appear and registered Campaigns drift from production copy. Reconfirm the RACI every quarter and after any CSP migration. Document escalation contacts for rejection codes and who may edit live templates during incidents.

Evidence Binder and Audit Readiness (continued 11)

Maintain a living binder with Brand submission payloads or console screenshots (secrets redacted); formation and EIN documents used during verification; dated archives of website, privacy policy, and SMS terms URLs; opt-in journey screenshots or recordings; Campaign description, message_flow, and versioned samples; CSP approval or rejection emails and reason codes; STOP and HELP response templates; and monthly exports of opt-out volume and complaint tags. These artifacts accelerate CSP remediations and support legal holds. Align retention with counsel because message logs are frequently discoverable. Index the binder by Campaign ID so on-call staff can find evidence in minutes.

Technical Controls Matrix (continued 12)

Engineering should treat Campaign-not-active as a hard failure, not a warning. Pair controls with runbooks that name the first three debugging steps for the most common CSP error codes.

Risks and Failure Modes

FAQ

Do informational appointment texts need PEWC?

Not always—the telemarketing/advertising PEWC trigger depends on content and technology. Many informational programs rely on prior express consent standards that may differ. Have counsel classify your templates.

Is a checked box “written”?

Often yes when designed as an ESIGN-compliant electronic signature process—but implementation details matter. Courts and the FCC focus on clarity and process.

Does 10DLC registration equal PEWC?

No. Registration identifies the sender/use case for carriers; PEWC is a TCPA consent concept.

Can one consent cover email and SMS marketing?

Only if disclosures clearly authorize each channel and otherwise meet PEWC for texts. Do not bury SMS authorization in unrelated email fine print.

Key Takeaways

• Meet both carrier registration duties and consent/legal duties—neither replaces the other.
• Keep Brand identity, website evidence, Campaign samples, and production traffic aligned.
• Document who messages are for and how consumers opted in; honor STOP quickly.
• Use CSP reason codes and primary sources when remediating—not rumor threads.
• Avoid inventing fees, fines, or throughput guarantees in policies or marketing.
• Audit quarterly for consent drift, template drift, and vendor sprawl.
• Escalate legally sensitive launches to qualified counsel.
• MyTCRPlus tools can help organize evidence; they do not guarantee approval or delivery.

Disclaimer

This article is for informational purposes only and is not legal advice. TCPA/FCC rules and case law change. Confirm consent language and processes with qualified counsel before sending marketing SMS.