Written by: Matt Beucler, CEO, Plura AI
Updated September 2026
Key Takeaways for Contact and Marketing Leaders
- TCPA caller ID rules under 47 C.F.R. § 64.1601 require accurate caller ID with a reachable callback number on every telemarketing call and text, with violations carrying $500–$1,500 statutory damages per contact.2
- Both voice calls and SMS marketing messages must transmit either the telemarketer’s CPN/ANI and name or the seller’s name and customer service number, and blocking or spoofing caller ID is prohibited.
- The FTC’s amended TSR and recent court rulings (Zelma v. Ram, Novia v. Mobiz) reinforce that accurate, reachable caller ID is independently enforceable and that AI-generated voices fall under the same restrictions.
- Exemptions are narrow, and commercial telemarketing calls remain fully covered while nonprofit, emergency, and purely informational calls have limited carve-outs that still require cell-phone consent compliance.
- Plura AI’s FCC-licensed carrier infrastructure embeds branded caller ID, STIR/SHAKEN authentication, and real-time TCPA/TSR enforcement at the network level.
Core TCPA Caller ID Rules You Need to Meet
The core caller ID transmission rule sits at 47 C.F.R. § 64.1601(e)(1).2 Under that provision, a telemarketing call must include either the CPN (calling party number) or ANI (automatic numbering information) and the name of the telemarketer, or the name and customer service number of the seller on whose behalf the call is made.
Several additional requirements follow from the rule and related law:
- The displayed callback number must permit any individual to make a do-not-call request during regular business hours, as specified in § 64.1601(e)(1).
- Blocking caller ID transmission on a covered telemarketing call is prohibited under § 64.1601(e)(2).
- Spoofing caller ID with intent to defraud or cause harm is prohibited under the Truth in Caller ID Act, codified at 47 U.S.C. § 227(e).
- The rule applies to both voice calls and SMS text messages. The FCC’s February 2024 Declaratory Ruling confirms that TCPA restrictions on artificial or prerecorded voice apply to AI-generated voices in voice calls. Because the FCC has previously confirmed that “calls” under the TCPA include text messages, these rules also apply to AI-generated voice content in SMS text messages. Novia v. Mobiz, Inc. (D. Mass. Mar. 2026) reinforces this interpretation.
In Zelma v. Ram, 2026 WL 1398784 (D.N.J. May 19, 2026), the court clarified what satisfies the rule. Displaying a company name alongside a reachable phone number is sufficient when the number connects to someone who can confirm the caller’s affiliation and accept do-not-call requests.4 The court dismissed the caller ID claim in that case because the displayed number was reachable and the agent confirmed his RE/MAX affiliation when called.
Most courts now recognize a private right of action to enforce § 64.1601(e) after the Sherriff line of cases. Caller ID display has become an enforceable obligation on every telemarketing call.
How Caller ID Rules Apply to Voice Calls and SMS
The caller ID rule operates across both channels, and leaders need a clear view of how it plays out in day-to-day operations.
Voice calls require accurate caller ID with CPN or ANI, the telemarketer’s or seller’s name, and a reachable callback number during business hours. Blocking is prohibited under § 64.1601(e)(2). STIR/SHAKEN (Secure Telephone Identity Revisited / Signature-based Handling of Asserted information using toKENs) authentication, mandated by the TRACED Act, adds a digital certificate layer that terminating carriers use to verify legitimate origination.
SMS text messages are subject to the same caller ID rule. The FCC has previously confirmed that autodialed texts count as “calls” under the TCPA. Its 2024 Declaratory Ruling extends the artificial-voice restrictions to AI-generated voices in voice calls, and the same rules apply to AI-generated voice content in texts. In Novia v. Mobiz, Inc. (D. Mass. Mar. 2026), the court held that § 64.1601(e) was promulgated pursuant to 47 U.S.C. § 227(c), which contains a private right of action, and that the rule applies to SMS marketing messages. The plaintiff established standing by showing concrete injury, including undermined trust in the source of the texts, difficulty identifying the sender, and wasted time checking the messages.
A circuit split exists on a related question. In Steidinger v. Blackstone Medical Services, No. 25-2398 (7th Cir. July 14, 2026), the Seventh Circuit held that a text message is not a “telephone call” within the meaning of § 227(c)(5), which affects do-not-call claims in Illinois, Indiana, and Wisconsin. That ruling does not affect § 227(b) claims or the caller ID rule under § 64.1601(e), and it is binding only in the Seventh Circuit. Operators outside that circuit, and operators with any Seventh Circuit exposure, should consult counsel before adjusting SMS compliance programs based on Steidinger.
For SMS, practical compliance means including accurate sender information and a functional opt-out path in every marketing text. 10DLC (10-digit long code) registration under A2P (application-to-person) messaging standards is the carrier-level mechanism for establishing sender identity on SMS campaigns.
When TCPA Caller ID Rules Do Not Fully Apply
Exemptions under the TCPA are narrow, and leaders should treat them as exceptions, not strategy. The following categories receive some form of relief from specific TCPA provisions, and the scope of each exemption is limited. Consult qualified counsel before relying on any exemption.
| Call Type | Exemption Status | Conditions |
|---|---|---|
| Tax-exempt nonprofit calls | Exempt from telephone solicitation rules under 47 CFR 64.1200(f) | Must be by or on behalf of a 501(c)(3); no commercial arrangement; cell-phone robocall consent rules still apply |
| Emergency purpose calls | Exempt from consent requirements under 47 CFR 64.1200(f)(4) | Health and safety situations only; narrow definition |
| Informational or transactional calls | Exempt from telemarketing-specific rules | Must not induce a purchase; purely informational or transactional in nature |
| Commercial telemarketing | Fully covered | Full caller ID, consent, and DNC (Do Not Call) requirements apply |
The nonprofit exemption excludes calls made by or on behalf of a tax-exempt nonprofit from the definition of “telephone solicitation” under 47 CFR 64.1200(f). The national DNC registry rules and certain telemarketing-specific requirements do not apply to qualifying nonprofit calls. The exemption does not extend to autodialed or prerecorded calls to cell phones, which still require prior express written consent regardless of the caller’s tax status. When a for-profit organization delivers its own commercial message alongside a charitable reference, the FCC has stated that the call is treated as commercial rather than nonprofit.
Emergency purpose calls are excluded from TCPA consent requirements by statute under 47 U.S.C. § 227(b)(1)(A), with emergency purposes defined as situations affecting the health and safety of consumers under 47 CFR 64.1200(f)(4).
Informational and transactional calls that do not induce a purchase fall outside the definition of telemarketing and are not subject to telemarketing-specific rules. The line between informational and telemarketing is fact-specific, and the FTC has found violations where calls framed as surveys were actually sales pitches.
Recent TCPA and TSR Changes Affecting 2026 Programs
As of September 2026, the core caller ID requirements under § 64.1601 remain in place, but several developments from 2024 and 2025 shape how leaders design outreach programs.
- The FCC’s one-to-one consent rule, adopted in December 2023 and scheduled to take effect January 27, 2025, was vacated by the Eleventh Circuit in Insurance Marketing Coalition Ltd. v. FCC, 127 F.4th 303 (11th Cir. 2025). The prior express written consent standard under 47 C.F.R. § 64.1200(f)(9) applies as of September 2026.
- The FTC’s amended TSR (Telemarketing Sales Rule), published as 89 FR 99069 and effective January 27, 2025, tightened caller ID accuracy requirements, extended consent rules to AI-generated voices, and made inaccurate caller ID a standalone TSR violation.
- The FCC’s August 2024 NPRM (Notice of Proposed Rulemaking) under CG Docket 23-362 proposed requiring explicit disclosure of AI use in consent forms and mandatory real-time disclosure during AI-generated calls. As of September 2026, those proposals remain under review and are not yet in effect.5
- Zelma v. Ram (D.N.J. May 2026) clarified what satisfies the caller ID display requirement for voice calls.
- Novia v. Mobiz, Inc. (D. Mass. Mar. 2026) confirmed a private right of action for SMS caller ID violations under § 64.1601(e).
- McComb v. Lackey (S.D. Ohio June 2026) and Trupia v. Bob Moore Enterprises, LLC (10th Cir. May 2026) held that no private right of action exists under § 227(e)(1), the Truth in Caller ID Act’s spoofing provision. Courts remain split on this question.
Operators should monitor FCC announcements and consult counsel before making compliance program changes based on pending rulemaking.
Financial Exposure for Caller ID Violations
The damage framework for TCPA caller ID violations is significant, and each call or text counts as a separate violation with no statutory cap on total exposure.
- Statutory damages under 47 U.S.C. § 227(b)(3): $500 per violation, trebled to $1,500 for willful or knowing violations.
- FCC administrative forfeitures: up to $23,727 per violation (inflation-adjusted), enforced separately from private lawsuits.
- Class-action settlements averaged $6.6M in 2023 (FCC, 2025; WebRecon LLC, 2024), with individual cases reaching $28M (Campbell v. Sirius XM Radio Inc.) and $20M (Bumpus v. Realogy Holdings Corp.).3
- Truth in Caller ID Act penalties under § 227(e): up to $10,000 per violation, or up to $30,000 per day for continuing violations. Courts are split on whether a private right of action exists under this provision, with the Tenth Circuit in Trupia v. Bob Moore and the Southern District of Ohio in McComb v. Lackey both finding no private right of action.
As noted earlier, statutory damages range from $500 to $1,500 per violation. A campaign sending 10,000 texts without proper caller ID creates a floor exposure of $5,000,000 at the base rate. Plura AI automatically enforces TCPA rules, DNC list checks, calling window restrictions, and consent requirements on every interaction, supporting operators in addressing these requirements before each contact attempt.
How the FTC Telemarketing Sales Rule Interacts with TCPA Caller ID
The TCPA is not the only rule governing caller ID. The FTC’s TSR, codified at 16 CFR Part 310, runs in parallel and addresses caller ID accuracy independently. The two frameworks are enforced by different agencies and do not replace each other.
Key TSR caller ID provisions include:
- Telemarketers must transmit a real, working callback number that remains valid for at least 15 minutes after the call.
- The December 2024 TSR amendments (89 FR 99069) made inaccurate caller ID a standalone TSR violation, separate from the prior practice of treating it as a deceptive practice.
- TSR penalties reach up to $51,744 per violation (2024 inflation adjustment), enforced by the FTC and state attorneys general. There is no private right of action under the TSR.
- The December 2024 amendments extended the consent framework to AI-generated voice calls, treating them the same as traditional prerecorded messages.
A single telemarketing call can violate both the TCPA and the TSR simultaneously. The TCPA creates private lawsuit risk at $500 to $1,500 per call. The TSR creates government-fine risk at up to $51,744 per call. Compliance programs must address both frameworks independently. Consult qualified counsel for guidance on satisfying both rule sets for your specific operations.
Operational TCPA Checklist for Dialers and SMS Platforms
The following checklist reflects the operational steps that compliance officers, contact center managers, and engineering teams typically address when configuring outbound voice and SMS programs. This is not legal advice; consult qualified counsel for guidance specific to your operations.
- Confirm your dialer transmits accurate caller ID with a reachable callback number on every outbound telemarketing call, including CPN or ANI and the telemarketer’s or seller’s name, per 47 C.F.R. § 64.1601(e)(1).
- Avoid blocking or spoofing caller ID on any covered telemarketing call or text.
- For SMS campaigns, include accurate sender information and a functional opt-out path in every marketing message. Register sending numbers through 10DLC A2P messaging standards.
- Scrub contact lists against federal and state DNC registries in real time before each dial attempt. The TSR requires scrubbing at least every 31 days, and real-time scrubbing addresses both TSR and TCPA exposure.
- Obtain prior express written consent for telemarketing calls and texts to cell phones. Document consent with timestamped, immutable records that capture the consent artifact, not just a database flag.
- Honor opt-out requests promptly. The FCC’s rules require processing revocations within ten business days, and the TSR requires honoring direct do-not-call requests indefinitely.
- Maintain audit-ready records of consent, call logs, and DNC scrub dates. The TSR requires records for five years under the December 2024 amendments, and the TCPA statute of limitations is generally four years.
- Work with a carrier that supports STIR/SHAKEN authentication and branded caller ID issuance at the carrier level instead of through a third-party reseller.
How Plura AI Supports TCPA Caller ID Compliance
Plura AI is an FCC-licensed carrier. Voice originates on Plura’s own domestic infrastructure, so caller ID is issued at the carrier level instead of through a third-party CPaaS (Communications Platform as a Service).
Plura’s compliance infrastructure includes:
- Branded caller ID issued directly through Plura’s FCC-licensed carrier identity, so calls present with the company’s name rather than an unfamiliar number or “Spam Likely” label.
- STIR/SHAKEN authentication on every outbound call, providing the digital certificate that terminating carriers use to verify legitimate origination.
- Real-time DNC scrubbing and TCPA-litigator screening enforced before each dial attempt, instead of a post-hoc batch process.
- Immutable consent logging with timestamped, audit-ready records, exportable in one click for legal review or regulatory inquiry.
- Automated quiet-hours enforcement through time-zone detection, applying federal and state calling-window restrictions to every campaign.
- 100% U.S. infrastructure for voice origination, model hosting, data storage, and call recording, with no offshore exposure under the FCC NPRM (CG Docket No. 26-52) or state onshoring laws.
Plura’s AI Predictive Dialer runs on this same carrier foundation. Branded caller ID and compliance enforcement are built into every outbound dial. The compliance engine operates as a first-class layer of the platform. Operators using Plura’s platform remain responsible for their own compliance obligations, and Plura provides the infrastructure that supports addressing those requirements at the network level.
Compare plans and rates side by side.
Frequently Asked Questions
What are the new TCPA rules for 2026?
As of September 2026, the core caller ID requirements under 47 C.F.R. § 64.1601 are unchanged. The FCC’s one-to-one consent rule was vacated by the Eleventh Circuit in early 2025, and the prior express written consent standard under 47 C.F.R. § 64.1200(f)(9) applies. The FTC’s amended Telemarketing Sales Rule, effective January 27, 2025, tightened caller ID accuracy requirements, extended consent rules to AI-generated voices, and made inaccurate caller ID a standalone TSR violation. The FCC’s proposed rules on AI-generated calls under CG Docket 23-362 remain under review and are not yet in effect. Operators should monitor FCC and FTC announcements and consult counsel before adjusting compliance programs.
Which calls are exempt from the TCPA?
The TCPA provides narrow exemptions for calls made by or on behalf of tax-exempt nonprofit organizations (exempt from telephone solicitation rules, but not from cell-phone robocall consent requirements), calls made for emergency purposes as defined by 47 CFR 64.1200(f)(4), and purely informational or transactional calls that do not induce a purchase. Commercial telemarketing calls remain fully covered and are subject to caller ID, consent, and DNC requirements. The nonprofit exemption does not extend to commercial vendors delivering their own message alongside a charitable reference, and it does not cover autodialed or prerecorded calls to cell phones without prior express written consent.
Does the TCPA apply to manually dialed calls?
The TCPA’s autodialer provisions under 47 U.S.C. § 227(b) apply to calls made using an ATDS (automatic telephone dialing system), which the Supreme Court defined in Facebook, Inc. v. Duguid (2021) as a system that uses a random or sequential number generator to store or produce numbers. Manually dialed calls generally fall outside the ATDS definition post-Duguid. The FTC’s Telemarketing Sales Rule applies to all telemarketing calls regardless of dialing method, and the caller ID rule under 47 C.F.R. § 64.1601(e) applies to telemarketing calls generally, not only to autodialed calls. Prerecorded voice calls to cell phones require prior express written consent regardless of how the number was selected. Consult qualified counsel for guidance on your specific dialing technology and call types.
What does the TCPA require for caller ID?
Under 47 C.F.R. § 64.1601(e)(1), a telemarketing call must transmit either the CPN or ANI and the name of the telemarketer, or the name and customer service number of the seller on whose behalf the call is made. The displayed callback number must permit any individual to make a do-not-call request during regular business hours. Blocking caller ID transmission is prohibited under § 64.1601(e)(2). Spoofing caller ID with intent to defraud or cause harm is prohibited under the Truth in Caller ID Act at 47 U.S.C. § 227(e). The Zelma v. Ram decision (D.N.J. May 2026) clarified that displaying a company name alongside a reachable phone number satisfies the rule when the number connects to someone who can confirm the caller’s affiliation.
What are the TCPA caller ID requirements for SMS?
The same caller ID rule that applies to voice calls applies to SMS text messages. The FCC has previously confirmed that text messages sent using an autodialer are “calls” under the TCPA, and its 2024 Declaratory Ruling, discussed earlier, extends the artificial-voice restrictions to AI-generated voices in texts. Novia v. Mobiz, Inc. (D. Mass. Mar. 2026) held that 47 C.F.R. § 64.1601(e) is privately enforceable and applies to SMS marketing messages, with the court finding that a plaintiff alleging a lack of caller ID on texts established standing through concrete injury. Practical compliance for SMS means including accurate sender information and a functional opt-out path in every marketing text, and registering sending numbers through 10DLC A2P messaging standards. The Seventh Circuit’s Steidinger decision created a circuit split on a related question, but that ruling does not affect the caller ID rule under § 64.1601(e). Consult qualified counsel for guidance on your SMS program.
1 Plura AI maintains SOC 2, HIPAA, ISO, and GDPR posture as part of its platform infrastructure. References to compliance frameworks in this article describe Plura’s platform capabilities and do not constitute a guarantee that any customer using Plura will themselves be compliant with applicable laws or standards. Customers remain solely responsible for their own regulatory obligations, certifications, consent management, recordkeeping, and the claims they make to their own end users. Consult qualified legal counsel for guidance specific to your use case.
2 This article describes regulatory frameworks at a general level and does not constitute legal advice. Laws and regulations vary by jurisdiction, change over time, and apply differently depending on facts and circumstances. Readers should consult qualified legal counsel before making compliance decisions.
3 Performance figures, customer outcomes, and industry statistics referenced in this article are drawn from cited third-party sources or Plura customer case studies. Individual results vary based on implementation, use case, industry, audience, and execution. Past or aggregate performance is not a guarantee of future results.
4 References to third-party products, services, companies, or research are made for informational and comparative purposes only. Plura AI is not affiliated with, endorsed by, or sponsored by any third party named in this article unless explicitly stated. Trademarks and product names referenced remain the property of their respective owners.
5 This article contains forward-looking statements regarding industry trends, technology adoption, and future capabilities. These statements reflect current expectations and are subject to change. Plura AI undertakes no obligation to update forward-looking statements except as required.
This article is provided for informational purposes only and reflects Plura AI’s understanding at the time of publication. Product capabilities, integrations, and specifications are subject to change. For the most current information, visit plura.ai.
This article was produced with the assistance of AI tools and reviewed by Plura AI prior to publication.