TCPA Compliance for Text-to-Call Programs in 2026

Written by: Matt Beucler, CEO, Plura AI

Key Takeaways for Text-to-Call in 2026

These five pillars shape how high-volume teams run compliant text-to-call programs in 2026.

• Text-to-call campaigns require prior express written consent for marketing SMS. Programs must honor opt-outs immediately and respect 8 AM to 9 PM quiet hours in the recipient’s local time zone.
• Every message must clearly identify your business. Teams need detailed, auditable records of consent and opt-out events, retained for at least four years.
• 2026 changes include expanded DNC coverage for texts, a delayed “revoke-all” consent rule, vacated one-to-one consent, and stricter state mini-TCPA laws in Texas, Oregon, and Florida.
• AI-powered text-to-call adds complexity. AI voices are treated as artificial or prerecorded, A2P 10DLC registration is mandatory, and opt-outs must update in real time across every channel.
• Plura AI is an FCC-licensed carrier that embeds TCPA compliance at the infrastructure layer. Real-time DNC scrubbing, quiet-hours enforcement, and immutable consent logs are built into the platform. Book a live demo to see how this carrier-level approach works.

The Speed-to-Lead Race Under Compliance Pressure

SMS volume keeps rising, and speed-to-lead now decides who wins the deal. Contacting a lead within 5 minutes makes them up to 100x more likely to connect, and a 60-second response lifts conversions by 391% (industry research published on the Plura AI ROI calculator)³. Text-to-call delivers the strongest conversion pattern in lead response. Teams text first to qualify, then call to close. This model also doubles your compliance surface. Two touchpoints create two consent checks and two opt-out channels.

WebRecon data shows TCPA filings rose 26.8% year-to-date through February 2026, with class actions comprising 72.3% of all TCPA filings that month⁴. A midyear litigation report found TCPA class action filings surged by approximately 95% in 2025 compared to 2024, while overall TCPA volume stayed roughly flat. The 2026 environment adds new FCC rulemaking under CG Docket No. 26-52, a delayed consent revocation rule, and expanding state mini-TCPA laws. This guide walks through the full compliance lifecycle for text-to-call campaigns, with specific focus on AI-powered execution.

See how Plura AI handles compliance at the carrier layer in a live demo.

TCPA Coverage for Text Messages

The FCC interprets text messages, including SMS and MMS, as “calls” under the TCPA, so they follow the same framework as outbound voice calls.² Marketing texts to wireless numbers require prior express written consent (PEWC).² This means a written agreement, including an E-SIGN-compliant electronic signature, that clearly authorizes the sender to deliver advertising or telemarketing messages, identifies the phone number, and discloses that consent is not a condition of purchase (47 CFR § 64.1200(f)(9)). Informational texts, such as appointment reminders, follow the lower standard of prior express consent. Teams should review the regulation or consult qualified counsel for their specific program.

Five Core TCPA Rules for Text-to-Call Programs

1. Obtain prior express written consent. Marketing texts require PEWC. The agreement must be signed or E-SIGN-compliant, name your business, describe message types, and state that consent is not a purchase condition. Sample language: “By checking this box, you agree to receive recurring automated promotional text messages from [Company] at the number provided. Consent is not a condition of purchase. Msg & data rates may apply. Reply STOP to cancel.” FCC guidance treats pre-checked boxes as insufficient for prior express written consent, although some federal courts have found pre-checked boxes can constitute express consent in specific cases.
2. Honor opt-outs immediately. The FCC has identified seven per se revocation words: stop, quit, end, revoke, opt out, cancel, and unsubscribe. Under 47 CFR § 64.1200(a)(10), businesses must honor revocations within a maximum of 10 business days. High-volume teams treat real-time suppression as the standard. Consumers can revoke by any reasonable means, including reply text, verbal request, or email.
3. Respect calling and texting hours. Telemarketing calls and texts are restricted to 8 AM to 9 PM in the recipient’s local time zone (47 CFR § 64.1200(c)(1)). For text-to-call, both the SMS and the follow-up call must fall within that local window. State mini-TCPAs may tighten hours, such as Florida’s 8 AM to 8 PM window.
4. Identify your business. Every message must clearly identify the sender, and caller ID for the follow-up call must be real, accurate, and associated with your organization. Spoofing is prohibited. In SMS, your business name should appear alongside STOP instructions.
5. Keep detailed records. Teams should document when and how consent was obtained, including timestamp, method, exact disclosure language, and IP address. Under 28 U.S.C. § 1658(a), the federal catch-all statute of limitations for TCPA claims is four years, subject to state-specific variations when a state law sets a different period. The FTC’s Telemarketing Sales Rule (16 CFR 310.5(a)) calls for five years of record retention.

2026 TCPA and Mini-TCPA Changes That Affect Text-to-Call

2026 brings active rulemaking that directly affects outbound teams running text-to-call programs.⁵

• CG Docket No. 26-52. The FCC’s Notice of Proposed Rulemaking proposes a 30% cap on offshore customer-service calls and restricts offshore handling of sensitive consumer data, including passwords, MFA codes, SSNs, banking details, and card data. Per the Federal Register, any text-to-call operation with offshore components sits inside this discussion.
• Consent revocation rule delayed. The FCC extended the effective date of the “revoke-all” consent rule to January 31, 2027 (Order DA 26-12, adopted January 6, 2026). The rule would treat a single STOP as canceling consent for all unrelated messages from a caller.
• One-to-one consent vacated. On January 24, 2025, the Eleventh Circuit vacated the FCC’s one-to-one consent rule in Insurance Marketing Coalition Ltd. v. FCC, No. 24-10277, and the FCC formally eliminated it in September 2025. Multi-seller consent remains available at the federal level. Many operators still treat named-company consent as the safer standard.
• DNC registry coverage for texts. SMS campaigns now require scrubbing against the National Do Not Call Registry, similar to outbound voice calls.
• State mini-TCPA expansion. Texas SB 140, effective September 1, 2025, broadened telephone solicitation to include text messages, with private statutory damages of $500 to $1,500 per violation, subject to trebling for willful violations. The Texas Attorney General can seek civil penalties up to $5,000 per violation. Oregon HB 3865, effective January 1, 2026, restricts contact hours to 8 AM to 8 PM and limits daily calls to three per consumer.
• Related federal legislation. The Keep Call Centers in America Act (S.2495) and the Foreign Robocall Elimination Act (S.2666) expand the regulatory focus on offshore call-center operations.

Step-by-Step TCPA Checklist for Text-to-Call Teams

1. Audit your current consent records. Pull every opt-in and verify timestamp, method, exact disclosure language, named seller, and phone number. If you cannot produce the record, treat that contact as non-consented.
2. Implement double opt-in. Require a confirmation step such as “Reply YES to confirm” to create a cleaner record and catch bad or mistyped numbers early.
3. Add clear opt-out instructions to every message. Include “Reply STOP to opt out” in the first message and periodically thereafter, following CTIA best practices.
4. Set up automated STOP handling. Route STOP, CANCEL, UNSUBSCRIBE, and freeform revocations to a centralized suppression list in real time. Avoid nightly batch jobs for revocations.
5. Configure quiet-hours enforcement. Use recipient-local time zones instead of your office time zone. Account for state mini-TCPA variations in your routing and scheduling logic.
6. Maintain an immutable consent log. Store consent records with timestamps, IP addresses, and disclosure versions in a tamper-evident system. Retain records for at least four years, and align with any stricter internal or state requirements.
7. Scrub against DNC and RND. Check the National DNC Registry and Reassigned Numbers Database (RND) before every campaign. Numbers enter the DNC Registry daily, so a job run the night before will miss same-day registrations.

AI-Powered Text-to-Call: Additional TCPA Considerations

AI-driven text-to-call workflows introduce new compliance checkpoints across consent, routing, and carrier infrastructure. Many standard TCPA checklists do not cover these details.

Consent in automated flows. The FCC’s February 2024 Declaratory Ruling confirmed that AI-generated voices qualify as “artificial or prerecorded voices” under the TCPA, which brings marketing calls into the prior express written consent framework. Under the Fifth Circuit’s interpretation in Sovereign, verbal opt-in during an AI call may count as prior express consent if recorded, timestamped, and properly disclosed, while written consent remains the standard outside that circuit. For AI-initiated SMS, the opt-in URL must stay live and carrier-verifiable for A2P 10DLC registration.

Real-time opt-out handling. AI agents need to recognize opt-out expressions in real time during both text and voice conversations, then push that revocation immediately to all suppression lists and CRMs across the enterprise. Revocations should not queue for a nightly batch job. They must propagate before the next dial attempt.

A2P 10DLC registration. As of February 2025, U.S. carriers block unregistered A2P 10DLC traffic at the network level. Businesses register a Brand and at least one Campaign in The Campaign Registry (TCR) and link both to the phone numbers used to send. Sample messages submitted must match what the AI agent actually sends in production.

Carrier-level enforcement. The infrastructure layer determines whether compliance holds at scale. Plura AI is an FCC-licensed carrier that issues branded caller ID at the carrier level, enforces real-time DNC scrubbing before every outbound contact, and provides an immutable consent ledger with audit-ready exports. Plura’s AI SMS agents run text-to-call workflows by texting every lead in seconds, qualifying them, then calling and live-transferring a warm buyer to your rep, with TCPA controls wired into the carrier layer. Plura’s compliance engine includes real-time DNC scrubbing, automated quiet-hours enforcement, and timestamped, immutable consent records. Customers remain responsible for their own compliance obligations, and Plura supplies the underlying infrastructure.

¹

Watch a live demo of AI-powered text-to-call with carrier-level controls.

Common TCPA Violations and How to Avoid Them

The table below summarizes frequent violations, their risk levels, and practical steps to avoid them in day-to-day operations.

Violation	Risk Level	How to Avoid It
Texting without consent	Critical: $500 to $1,500 per message (47 U.S.C. § 227(b)(3))	Implement double opt-in and document every consent event with timestamp, IP, and disclosure version
Ignoring opt-outs	Critical: willful violation can trigger $1,500 per message	Automate STOP handling and propagate revocations in real time across all channels
Quiet-hours violations	High: increasingly popular basis for lawsuits	Enforce recipient-local time zones and account for state mini-TCPA variations
Failing to identify your business	High: FCC enforcement exposure	Include your business name in every message and use branded caller ID on follow-up calls
Poor record-keeping	High: inability to defend consent in litigation	Maintain immutable consent logs and retain at least four years per 28 U.S.C. § 1658

The table above highlights the most common violations. The financial stakes increase quickly at scale. A single non-compliant campaign to 50,000 contacts creates $25 million in theoretical exposure before trebling for willfulness. Year-to-date through March 2026, 798 TCPA lawsuits were filed, up 23.7% compared to the same period in 2025. TCPA class actions comprised 77.7% of all TCPA filings in March 2026. Each text or call counts as a separate potential violation under 47 U.S.C. § 227(b)(3).

Frequently Asked Questions

These answers recap the most common TCPA questions leaders raise about text-to-call programs.

Does the TCPA apply to text messages?

The FCC interprets text messages, including SMS and MMS, as “calls” under the TCPA. Marketing texts to wireless numbers require prior express written consent, the same standard that applies to outbound telemarketing voice calls. Informational texts, such as appointment reminders, follow the lower standard of prior express consent. Teams should consult qualified counsel to determine which standard applies to a specific program.

What are the new TCPA rules for 2026?

Several developments shape the 2026 compliance landscape. The FCC’s CG Docket No. 26-52 proposes a 30% cap on offshore customer-service calls and restrictions on offshore handling of sensitive consumer data. The consent revocation rule, which would treat a single STOP as canceling consent for all unrelated messages from a caller, has been delayed to January 31, 2027 per Order DA 26-12. The one-to-one consent rule was vacated by the Eleventh Circuit in January 2025 and formally eliminated by the FCC in September 2025, leaving multi-seller consent available at the federal level. The DNC registry now covers text messages. State mini-TCPA laws in Texas, Oregon, Florida, and other states impose stricter hours and higher per-violation damages than federal rules. Operators running text-to-call campaigns should review each development with qualified legal counsel.

How do I handle STOP replies in a text-to-call workflow?

STOP replies need to be honored immediately across all channels. The FCC has identified seven per se revocation words: stop, quit, end, revoke, opt out, cancel, and unsubscribe. Under 47 CFR § 64.1200(a)(10), the maximum window for honoring a revocation is 10 business days, but real-time suppression is the operational standard for text-to-call programs. A final confirmation message is permitted and must contain no promotional content. Under the FCC’s TCPA revocation rules effective April 11, 2025, an opt-out from SMS automatically cancels consent for voice calls, and the reverse, when the revocation is made by any reasonable means. Suppression therefore needs to propagate across every channel in your stack before the next dial attempt.

How does AI affect TCPA compliance for text-to-call?

AI affects compliance at every layer of the text-to-call workflow. The FCC’s February 2024 Declaratory Ruling confirmed that AI-generated voices qualify as “artificial or prerecorded voices” under the TCPA, which subjects outbound AI voice calls to the same prior express written consent requirements as traditional robocalls. AI SMS agents sending outbound messages must be registered through A2P 10DLC before the first message is sent. AI agents must recognize opt-out expressions in real time during both text and voice conversations and propagate revocations immediately to all suppression lists. Consent captured verbally during an AI call can be acceptable when recorded, timestamped, and paired with the same disclosures used on a web form, subject to jurisdictional differences. The infrastructure layer, including the carrier, the consent ledger, and the DNC scrubbing system, determines whether compliance holds at scale. As noted earlier, customers retain responsibility for their own compliance obligations regardless of the platform they use.

What are the quiet hours for text-to-call campaigns?

Federal rules under 47 CFR § 64.1200(c)(1) restrict telemarketing calls and texts to 8 AM to 9 PM in the recipient’s local time zone. For text-to-call campaigns, both the SMS and the follow-up call must fall within the recipient-local window, not the sender’s office time zone. State mini-TCPA laws may impose stricter windows. Florida restricts automated calls and texts to 8 AM to 8 PM. Oregon’s HB 3865, effective January 1, 2026, restricts contact hours to 8 AM to 8 PM and limits daily calls to three per consumer. Operators running nationwide campaigns often apply the strictest applicable rule for each recipient’s state after consulting qualified counsel.

Conclusion and Next Steps for Text-to-Call Leaders

Text-to-call delivers top-tier conversion in lead response and carries significant risk when the compliance lifecycle is not wired correctly. The 2026 rules, state mini-TCPA expansion, and the rise of AI agents in the text-to-call stack push teams toward a compliance-first operating model. Leaders should audit current text-to-call workflows, review consent records, and assess whether their platform enforces controls at the carrier layer or adds them later in the stack.

Plura AI is an FCC-licensed carrier that builds compliance into the infrastructure layer with real-time DNC scrubbing, automated quiet-hours enforcement, immutable consent records, and branded caller ID issued at the carrier level. Plura’s AI SMS and AI Predictive Dialer products run text-to-call workflows at scale with TCPA controls embedded in the platform. Customers remain responsible for their own compliance obligations, and Plura supports those efforts with carrier-grade tooling.

Explore a live demo of Plura’s text-to-call compliance infrastructure and see how carrier-level controls fit into your stack. To connect this to budget planning, run your numbers through Plura’s ROI calculator or compare plans and rates side by side.

---

Read Next

• Text to Call Compliance: TCPA Rules for SMS and Voice
• What Is TCPA Compliance? Key Rules for Calls and Texts
• TCPA Compliance for Automated Sales Campaigns in 2026
• TCPA Consent Requirements for AI Voice and SMS Campaigns
• TCPA Compliant AI SMS: Carrier-Layer Compliance at Scale