TCPA Compliance Masterclass: Understanding What Is Covered Under the TCPA Today

In a recent presentation by John Ryan of Hinshaw & Culbertson LLP, the industry was reminded that the TCPA is not a static statute—it is a living regulatory beast. This masterclass transforms that presentation into a comprehensive compliance guide, covering the latest FCC rulings, state mini-TCPA expansions, and the operational steps necessary to survive a plaintiff's attorney's scrutiny. Whether you are a call center operator, a debt collector, or a marketing agency, understanding what is covered under the TCPA today is not just a legal exercise—it is a business survival imperative.

1. Background & Legal Analysis

The TCPA, codified at 47 U.S.C. § 227, prohibits unsolicited calls and text messages using an automatic telephone dialing system (ATDS) or an artificial/prerecorded voice, without prior express consent. However, the statute's scope has been shaped by a series of FCC declaratory rulings and court decisions. The 2020 Supreme Court decision in Facebook v. Duguid narrowed the definition of ATDS, but the FCC has since expanded the interpretation of "called party" and consent revocation. Moreover, the rise of state mini-TCPA laws—such as the Florida Telephone Solicitation Act (FTSA), the Oklahoma Telemarketing Act, and the Texas Business & Commerce Code § 304—has created a patchwork of compliance requirements that often exceed federal standards. For instance, the FTSA imposes liability for calls to numbers on the Florida Do Not Call list, even if the caller did not have a business relationship, and it allows for statutory damages of $500 per violation, with treble damages for willful violations. These state laws are not preempted by the TCPA, so telemarketers must comply with both federal and state regimes.

2. Impact on Telemarketers & Call Centers

The current legal landscape creates a minefield for telemarketers. Under 47 U.S.C. § 227(b)(3), statutory damages are $500 per negligent violation, up to $1,500 per willful violation. With class action litigation, these damages can reach millions of dollars. Additionally, the FCC's recent declaratory ruling on the definition of ATDS (still in flux) means that even predictive dialers with a random or sequential number generator may be covered. The impact is multi-fold:

• Litigation Trap Detection: Plaintiff's attorneys are increasingly using "lead generator" websites to capture consent that is then transferred to multiple telemarketers. If the consent is not clear and conspicuous, or if the calls exceed the scope of consent, each call becomes a violation. You must audit every lead source for proper TCPA consent language.
• National DNC Registry Scrubbing: The Telephone Consumer Protection Act requires telemarketers to scrub their call lists against the National Do Not Call Registry at least every 31 days (47 C.F.R. § 64.1200(c)(2)). However, state mini-TCPA laws may require more frequent scrubbing. For example, Oklahoma requires scrubbing every 30 days, and Texas requires a 60-day internal do-not-call list. Failure to scrub can result in per-call penalties.
• Real-Time API List Cleaning: Static list scrubbing is no longer sufficient. To avoid calling consumers who have recently registered on the DNC list or who have revoked consent, you must implement real-time API integrations that check numbers against the DNC registry, the company's internal do-not-call list, and the consumer's revocation status. This is especially critical for high-volume calling campaigns.

3. Safe Harbor & Risk Mitigation Checklist

To establish a safe harbor under 47 C.F.R. § 64.1200(c)(2), you must demonstrate that you have maintained and honored a company-specific do-not-call list, and that you have scrubbed against the National DNC Registry within the last 31 days. However, the FCC has clarified that the safe harbor only applies to calls that are not made with a prerecorded voice or an ATDS. For calls that require consent, you must obtain prior express written consent, which includes a clear and conspicuous disclosure that the consumer will receive calls from a specific seller. Here is a step-by-step operational workflow:

1. Step 1: Implement a written policy that designates a compliance officer responsible for TCPA and state law compliance.
2. Step 2: Purchase or develop a reliable DNC scrub system that automatically checks numbers against the National DNC Registry, state-specific lists, and your internal do-not-call list. Schedule scrubbing at least every 30 days, but consider real-time scrubbing for high-volume campaigns.
3. Step 3: Develop a consent tracking system that records the date, time, and method of consent, and the exact script used to obtain consent. Ensure that consent is specific to the seller and the type of calls (e.g., telemarketing or informational).
4. Step 4: Implement a real-time API integration with your dialing platform to check each number against the DNC registry and internal lists before placing the call. If the number is on any list, the call must be suppressed.
5. Step 5: Train all agents and call center staff on TCPA compliance, including how to honor revocations immediately and how to document consent. Use call recordings to audit compliance.
6. Step 6: Conduct regular compliance audits, including random call monitoring and list reviews, to identify and correct potential violations before they become lawsuits.

In conclusion, the TCPA today is more complex than ever. John Ryan's presentation underscores that the statute's coverage extends to every call, text, and fax, and that state laws add another layer. By understanding the statutory framework, staying updated on FCC rulings, and implementing the operational workflows outlined above, you can navigate this treacherous regulatory environment with confidence.