Text to Call Compliance: TCPA Rules for SMS and Voice

Written by: Matt Beucler, CEO, Plura AI

Key takeaways for text-to-call leaders

• Text-to-call workflows require separate prior express written consent for SMS and voice. Consent for one channel does not extend to the other.
• TCPA litigation is rising sharply, with 292 cases filed in February 2026 alone and statutory damages of $500–$1,500 per violation, so compliance has direct financial impact.²
• Key 2025–2026 FCC rules include a 10-business-day revocation window, delayed cross-channel opt-out enforcement until April 2026, and one-to-one consent standards that prevent sharing consent across brands.²
• High-volume operators must scrub against federal and state DNC registries, enforce quiet hours by time zone, and maintain audit-ready consent records for at least five years.
• Plura AI’s FCC-licensed carrier stack automates DNC scrubbing, consent enforcement, and cross-channel suppression in real time, and you can see this protection in action in a live demo.

Text-to-call compliance in practice

Text to call compliance covers the federal and state rules that apply when an SMS message initiates or precedes a voice call to a consumer. These workflows are common in lead generation, appointment scheduling, and outbound sales, and they sit at the intersection of two separately regulated channels.

Courts have reached differing conclusions on whether the TCPA treats text messages as “calls” under the statute. The FCC’s February 2024 declaratory ruling confirms that AI-generated voice calls fall under TCPA restrictions unless the consumer has provided prior express consent or a statutory exemption applies.

Consent obtained for SMS does not automatically extend to a subsequent voice call. Each channel requires its own prior express written consent naming the specific seller, and the consent must be topically related to the page where it was collected. High-volume operators running text-to-call sequences need to treat each channel as a distinct consent obligation.

Litigation risk from SMS and text-to-call campaigns

TCPA litigation involving SMS has increased sharply. WebRecon data reported in February 2026 showed 292 TCPA cases filed in that month, and 72.3% of those filings were structured as class actions.^3,4 Year-to-date through February 2026, TCPA filings were up 26.8% compared with the same period in 2025.

The financial exposure is significant. TCPA statutory damages under 47 U.S.C. § 227(b)(3) are $500 per call or text for non-willful violations and treble to $1,500 per violation when a court finds the conduct knowing or willful, with no statutory cap on aggregate exposure. TCPA class action settlements have averaged over $6.6 million according to 2018 data,³ and individual settlements often range from $5,000 to $12,000 per claimant according to TCPASettlements.com 2025 data.

State-level exposure stacks on top of federal liability. Florida’s FTSA creates statutory damages of $500 to $1,500 per text with no harm requirement. Texas Senate Bill 140, effective September 1, 2025, expanded the definition of telephone solicitation to explicitly include text messages. Operators running nationwide text-to-call campaigns face layered exposure across multiple jurisdictions simultaneously.

See how Plura’s compliance engine protects against this multi-jurisdictional exposure with real-time DNC scrubbing and consent enforcement across both channels.

Federal and state SMS rules that shape text-to-call

The primary federal framework is the TCPA, administered by the FCC. The FCC’s implementing regulations at 47 C.F.R. § 64.1200(f)(9) define prior express written consent (PEWC) for marketing messages. The FTC administers the National DNC Registry under the Telemarketing Sales Rule.

Several 2025 and 2026 regulatory developments directly affect text-to-call workflows:

• Consent revocation rule (effective April 11, 2025): Businesses must honor reasonable revocation requests within 10 business days, and full cross-channel application begins April 11, 2026. A consumer who texts STOP must be suppressed from voice outreach as well once the cross-channel rule is fully in effect.
• Revoke-all rule (delayed to April 11, 2026): The FCC waived the broader “stop-one-stop-all” requirement until April 11, 2026, and operators should consult qualified counsel on current obligations.
• AI voice classification (FCC 24-17, February 2024): The FCC confirmed that AI-generated voices are “artificial” under the TCPA, which means informational calls require prior express consent and telemarketing calls require PEWC.
• One-to-one consent standard: On August 29, 2025, the FCC reinstated its prior standard after the Eleventh Circuit vacated the 2023 revision. Consent cannot be shared across brands or sold to third parties.
• FCC regulatory developments: The FCC has addressed additional restrictions on offshore handling of consumer data and call-center operations, and companion legislation including the Keep Call Centers in America Act (S.2495) and the Foreign Robocall Elimination Act (S.2666) extends the federal regulatory perimeter.

State mini-TCPA laws add further complexity. At least four states (Florida, Oklahoma, Maryland, and Washington) grant private rights of action under their mini-TCPA laws, which enables plaintiffs to sue for both state and federal violations in the same complaint. Several states maintain their own DNC registries that must be scrubbed separately from the national list. Operators should consult qualified counsel on the specific requirements applicable to their campaigns.

Operational checklist for text-to-call compliance

The following checklist reflects operational steps that high-volume operators commonly address in text-to-call compliance programs. This content is descriptive, not legal advice, and operators should consult qualified counsel to assess their specific obligations.

1. Obtain channel-specific prior express written consent. Collect separate PEWC for SMS and for voice calls, each naming the specific business entity. This consent must include the business name, communication types, automated technology disclosure, opt-out mechanism, and a statement that consent is not a condition of purchase. These requirements can be satisfied through electronic signatures under the E-SIGN Act.
2. Build an audit-ready consent record at the point of capture. Each consent record should include the exact date and time, method of collection, precise disclosure language, source URL, IP address, and the recipient’s phone number. Records should be retained for at least five years under the FTC’s Telemarketing Sales Rule.
3. Scrub against federal and state DNC registries before every dial. Calling lists must be scrubbed against the National DNC Registry no more than 31 days before placing any call. Several states maintain separate registries that require independent scrubbing. Also check the Reassigned Numbers Database (RND) for numbers where consent was obtained more than 30 days prior.
4. Enforce quiet hours automatically by time zone. Federal TCPA rules restrict calls and texts to 8 a.m. to 9 p.m. local time of the called party. Oregon HB 3865 (effective January 1, 2026) limits contact to 8 a.m. to 8 p.m. Alabama restricts solicitation calls to 8 a.m. to 8 p.m. and prohibits them on Sundays or holidays. Campaigns spanning multiple states require per-state time-zone enforcement.
5. Honor opt-out requests across both channels within 10 business days. Honor opt-out requests across SMS and voice within the 10-business-day window established by the FCC’s April 2025 revocation rule, with full cross-channel enforcement beginning April 11, 2026. A STOP reply to a text should suppress voice outreach on the same campaign.
6. Identify the calling entity and disclose AI voice use at the start of every call. Artificial-voice calls must identify the calling entity by name and provide a contact number at the start of the call. Texas requires AI disclosure within the first 30 seconds. California, Florida, Colorado, Illinois, and Utah impose additional disclosure obligations. A practical default is a one-line statement within the first ten seconds identifying the business and noting that the call may be recorded.
7. Maintain centralized, cross-channel audit records. Compliance programs must retain opt-out logs, suppression lists with timestamps, and DNC screening records in a format that can be produced during audits without manual reconstruction. Records should tie each message and call to its associated consent record.

TCPA text-back scenarios and follow-up calls

TCPA text back compliance focuses on situations where a consumer replies to an outbound SMS and the operator then initiates a voice call. An inbound reply does not retroactively cure inadequate original consent for a follow-up voice call. FCC guidance states that a number captured through caller ID or ANI (Automatic Number Identification) does not, by itself, create consent for future autodialed or prerecorded solicitation.

The entity on whose behalf AI calls are made remains liable for TCPA violations even when a third-party vendor placed the call. This principle appeared in the proposed class definition in Lamb v. Mortgage One Funding, filed February 24, 2026. Operators cannot transfer compliance responsibility to a vendor through contract alone.

Plura AI supports this workflow by maintaining a stateful consent record across channels. AI SMS and AI voice agent share a stateful conversation database, so suppression, consent status, and conversation history stay consistent across channels. SOC 2, HIPAA, ISO certification, and DNC compliance are built into the infrastructure.¹ These features support operators in building audit-ready posture, and they do not substitute for the operator’s own legal obligations.

Walk through a live SMS-to-voice sequence to see how Plura’s stateful consent database maintains audit-ready records across both channels.

Sample TCPA-aligned calling script for AI voice

A TCPA-aligned calling script for an AI voice agent following an SMS outreach should address four elements. These elements are entity identification, AI disclosure, call purpose, and opt-out mechanism. The following sample reflects disclosure elements described in FCC guidance and state-level requirements, and operators should review it with qualified counsel before deployment.

Sample TCPA Compliance Calling Script (AI Voice, Post-SMS Outreach)

“Hi, this is an automated assistant calling from [Business Name]. This call may be recorded. You recently requested information about [product or service], and we are following up on that request. If you would like to be removed from our call list, please say ‘stop’ or press 9 at any time. Otherwise, I would be happy to help you with [specific purpose]. How can I assist you today?”

Key elements this script addresses:

• Entity identification by name at the start of the call, as described in longstanding TCPA rules
• AI and recording disclosure within the first ten seconds, aligning with FCC guidance and state laws including California, Florida, and Illinois
• Reference to the prior SMS or inquiry, which connects the call to the consent context
• An opt-out mechanism offered at the start of the message, as described in FCC consumer guidance
• A specific call purpose, which avoids the promotional-content classification that triggers PEWC requirements for informational calls

Plura’s AI voice agent runs this type of script through a no-code workflow builder with hard guardrails at each conversation node. When a caller says “stop” or any reasonable revocation phrase, the workflow flags the contact for suppression across both SMS and voice channels within the 10-business-day window described in the FCC’s April 2025 revocation rule, with the cross-channel requirement beginning April 11, 2026. The AI SMS sequence and the voice follow-up share the same stateful conversation database, so suppression applied in one channel propagates to the other.

Given the statutory damages described earlier and the prevalence of seven-figure class action settlements, the operational case for carrier-grade enforcement is clear. Manual compliance processes create gaps that bolt-on tools cannot close after the fact.

Conclusion: Running compliant text-to-call at scale

Text to call compliance in 2026 requires real-time enforcement across both channels, not sequential review. The consent record needs to exist before the first SMS. The DNC scrub needs to run before the voice call. The opt-out needs to suppress both channels. State mini-TCPA laws layer additional obligations on top of federal TCPA rules depending on where the consumer resides. Various FCC proceedings address infrastructure-level requirements that affect any operator with offshore dependencies.

Plura’s FCC-licensed carrier stack enforces DNC scrubbing, SHAKEN/STIR caller ID verification, quiet-hours rules, and consent management as core layers of the platform, not bolt-on additions.¹ The AI SMS and AI voice agent share a stateful conversation database, so suppression, consent status, and conversation history remain consistent across channels. Plura’s carrier-grade infrastructure maintains the cross-channel compliance posture described throughout this article, with certifications and DNC scrubbing enforced at the platform level rather than added after the fact. Operators remain responsible for their own legal obligations and should consult qualified counsel on their specific compliance posture.

Run your numbers through Plura’s ROI calculator to see projected cost savings in real time.

Review Plura pricing to compare plans and rates side by side.

---

Frequently asked questions

Does consent for an SMS message automatically cover a follow-up voice call?

Consent for an SMS message does not automatically cover a follow-up voice call under the TCPA framework. Each channel requires its own prior express written consent that names the specific business entity, describes the communication types, identifies any automated technology used, and includes an opt-out mechanism. An inbound text reply or a web form submission provides consent only for communications related to the context in which the number was provided. Operators running text-to-call sequences often obtain dual consent at the point of capture that covers both channels explicitly, and they should consult qualified counsel to assess their specific obligations.

What happens when a consumer opts out of texts, and does that also stop voice calls?

Under the FCC’s consent revocation rule effective April 11, 2025, businesses must honor revocation requests made through any reasonable means, including a STOP reply to a text, within 10 business days. The requirement that revocation of consent in one channel applies across unrelated message types begins April 11, 2026. Integrated text-to-call campaigns need synchronized suppression lists across both channels once all rules are in effect. A consumer who opts out of SMS outreach and is then called by the same business on the same campaign may face a compliance gap that creates TCPA exposure depending on the specific rules in effect. Plura’s stateful conversation database propagates suppression across SMS and voice channels, which supports operators in maintaining synchronized opt-out records. Operators should consult qualified counsel on the specific revocation obligations applicable to their campaigns.

How do state mini-TCPA laws affect a nationwide text-to-call campaign?

State mini-TCPA laws operate independently of federal TCPA rules and frequently impose stricter requirements. Florida’s FTSA applies a broader automated dialing system definition and allows $500 to $1,500 per-violation damages that stack on top of federal TCPA exposure. Texas Senate Bill 140, effective September 1, 2025, expanded the definition of telephone solicitation to include text messages. Oregon HB 3865, effective January 1, 2026, limits contact to 8 a.m. to 8 p.m. and caps outreach at three contacts per consumer per day. Several states maintain their own DNC registries that must be scrubbed separately from the national list. A nationwide campaign that applies only federal TCPA standards faces state-level liability in every jurisdiction where stricter rules apply. Operators should consult qualified counsel to map state-specific obligations before launching multi-state text-to-call campaigns.

What records does a high-volume operator need to defend a TCPA claim involving a text-to-call workflow?

Audit-ready compliance records for a text-to-call workflow typically include the exact consent disclosure language shown to the consumer, the timestamp and source URL of consent capture, the IP address and phone number at the point of opt-in, and the opt-in action taken such as checkbox, keyword, or signature. They also include DNC scrub logs showing the date and registry checked before each contact, opt-out logs with timestamps and resulting suppression actions, and the ability to tie each SMS and voice call to its associated consent record. Records should be retained for at least five years under the FTC’s Telemarketing Sales Rule. Plura’s compliance engine generates audit-ready exports from the dashboard, which supports operators in producing these records on demand for legal review or regulatory inquiries.

How does Plura AI’s carrier stack differ from bolt-on compliance tools for text-to-call programs?

Most AI voice and SMS platforms are API resellers built on top of third-party CPaaS providers. They do not own the carrier, so branded caller ID, real-time DNC scrubbing, and SHAKEN/STIR caller ID verification are added after the fact rather than enforced at origination. Plura is its own FCC-licensed audio bridging carrier. Voice originates on Plura’s domestic infrastructure, branded caller ID is issued at the carrier level, and DNC scrubbing runs in real time before every dial through integration with Blacklist Alliance’s TCPA Litigation Firewall.⁴ The AI SMS and AI voice agent share a stateful conversation database, so consent status, suppression records, and conversation history stay consistent across both channels by default. Plura runs on 100% U.S. infrastructure, which also addresses offshore data-handling restrictions proposed in FCC rules and already enacted in states including New York, New Jersey, Connecticut, Missouri, and Florida. These features support operators in building audit-ready posture, and they do not substitute for the operator’s own compliance obligations or legal counsel.

---