NCLC Tells FCC “Callers can easily avoid making calls to telephone numbers that have been reassigned….” – But Is it That Simple?

The National Consumer Law Center is at it again.

In response to the Department of Health and Human Services’ recent letter to the FCC seeking clarity on whether the TCPA applies to texts it would like to make to alert Americans of certain medical benefits, the NCLC–an organization that nominally represents consumers, but really seems to represent the interests of the plaintiff’s bar–has filed a comment.

Unsurprisingly, the NCLC takes the position that HHS needs no relief. Government contractors are covered by the TCPA–it says–but the texts at issue in HHS’ letter are consented, so they’re fine. (Although it later clarifies that only “many” but not “all” of the enrollees whom HHS wishes to call have “probably” given their telephone numbers as part of written enrollment agreements–so perhaps not.)

Hmmmm. Feels like a trap. But we’ll ignore that for now.

The critical piece here though is what the NCLC–very powerful voice, for better or (often) worse–is telling the FCC about the effectiveness of the new Reassigned Number Database:

3. Callers can easily avoid making calls to telephone numbers that have been reassigned to someone other than the enrollee

A primary source of TCPA litigation risk has been calls inadvertently made to numbers that are no longer assigned to the person who provided consent. Courts have held the caller liable for making automated calls to a cell phone number that has been reassigned to someone other than the person who provided consent to be called.29

The Commission has implemented the Reassigned Number Database specifically to address that risk of liability, as well as to limit the number of unwanted robocalls:

The FCC’s Reassigned Numbers Database (RND) is designed to prevent a consumer from getting unwanted calls intended for someone who previously held their phone number. Callers can use the database to determine whether a telephone number may have been reassigned so they can avoid calling consumers who do not want to receive the calls. Callers that use the database can also reduce their potential Telephone Consumer Protection Act (TCPA) liability by avoiding inadvertent calls to consumers who have not given consent for the call.31

The database has been fully operational since November 1, 2021. It provides a means for callers to find out before making a call if the phone number has been reassigned. If the database wrongly indicates that the number has not been reassigned, so long as the caller has used the database correctly, no TCPA liability will apply for reaching the wrong party. 32 Thus, as long as HHS’s callers make use of this simple, readily available database, they can be confident that they will not be held liable for making calls to reassigned numbers.

While I steadfastly support both the creation and use of the RND, it also must be observed that there are myriad problems with the RND as it currently exists. Most importantly, the data sets in the RND are only comprehensive through October 1, 2021 and spotty back to February, 2021 (beyond which there are no records!)

So for folks like HHS–and servicers of mortgages, and retailers, and credit card companies–who want to reach customers who provided their contact information before 10/2021 or 2/2021 the RND is simply not helpful.

The NCLC’s over simplification of a critical issue is not surprising. They once told Congress that the TCPA is “Straightforward and Clear” after all.

Full comment here: NCLC Comments-c3

We’ll keep an eye on developments on HHS’ letter and all the FCC goings ons.

© 2022 Troutman Firm

Potato, Potahto… Email, Slack

First came email.  Then came Slack, WhatsApp, Zoom, Teams, texts, and a host of social media platforms where we can communicate…in writing…and those communications are saved as electronically stored information (ESI).  “Collaboration software,” like Slack, Zoom, and Teams, is the newest eDiscovery challenge.  But the challenge lies in the preservation, capture, and review, as well as the analysis of proportionality, and not in the question of whether it is discoverable.

The United States District Court for the Central District of California recently ruled that Plaintiff’s Slack messages were both relevant and proportional to the needs of the case and ordered their production.  Benebone LLC v. Pet Qwerks, Inc., 2021 WL 831025 (2/18/21).  The main points of contention between Plaintiff and Defendant focused on the cost to extract, process, and review 30,000 Slack messages.

Although the Court described Slack as a relatively new communication tool, it was part of Plaintiff’s internal business communications and there was no real dispute that Plaintiff’s Slack messages were likely to contain relevant information.

On the topic of burden and proportionality to the needs of the case, the court held a (Zoom) hearing and determined that “requiring review and production of Slack messages by Benebone is generally comparable to requiring search and production of emails and is not unduly burdensome or disproportionate to the needs of this case.” Id. at *3.

One of the key takeaways from this case is to get an eDiscovery expert. Defendant’s expert testified that there are readily available third-party tools for collection and review of Slack and that searches of the data could be limited to certain Slack channels, users, or custodians (similar to focusing an email search on custodians and time frames).  Defendant’s estimate of cost for the project was vastly different than Plaintiff’s unsupported estimates ($22,000 compared to $110,000-$255,000).  To that end, Defendant’s expert proposed that contract attorneys could do first-level review at a rate of $40 an hour as opposed to a $400 an hour attorney rate.  Plaintiff failed to provide a declaration or testimony from an eDiscovery expert.

When facing federal litigation, your case will involve electronically stored information. Slack is considered a more dynamic form of ESI, making search, collection, and processing more difficult.  Choosing the right application programming interface (API) is important as Slack data is exported in JSON format, which is difficult to decipher and requires the right processing to get to more user-friendly data for review purposes.  Additionally, the level of subscription used impacts what can be recovered.

©2021 Strassburger McKenna Gutnick & Gefsky


For more articles on Slack and WhatsApp, visit the NLR Corporate & Business Organizations section.