Few legal phrases can make marketers, compliance teams, and class-action lawyers spill their coffee quite like “automatic telephone dialing system.” The phrase sounds harmless enough, almost like a dusty label on an office phone from 1997. But under the Telephone Consumer Protection Act, or TCPA, the meaning of an ATDS can decide whether a promotional text message is ordinary marketingor the opening scene of a very expensive lawsuit.
The headline “Second Circuit follows Marks ATDS includes texts sent from list” points to a major moment in TCPA litigation: the Second Circuit’s 2020 decision in Duran v. La Boom Disco, Inc. At the time, the court joined the Ninth Circuit’s broad reading from Marks v. Crunch San Diego, LLC, treating certain platforms that sent texts from stored lists as automatic telephone dialing systems. For businesses sending SMS campaigns, it was the legal equivalent of discovering the “send” button might be connected to a trapdoor.
But the story did not stop there. The Supreme Court later narrowed the ATDS definition in Facebook, Inc. v. Duguid, and the Second Circuit itself took a narrower approach in Soliman v. Subway Franchisee Advertising Fund Trust, Ltd. That means the old “follows Marks” headline is historically important, but today’s compliance analysis must account for newer authority. In other words, this topic is not just about what happenedit is about how fast TCPA law can change when courts, technology, and marketing collide.
What Is an ATDS Under the TCPA?
The TCPA was enacted in 1991 to curb intrusive telemarketing practices. Congress was worried about robocalls, fax spam, and automated systems that could bombard consumers without meaningful consent. The law restricts certain calls and messages made to cell phones using an automatic telephone dialing system, unless the caller has the recipient’s prior express consent or another exception applies.
The statutory definition of an ATDS is deceptively short. It refers to equipment with the capacity to store or produce telephone numbers to be called, using a random or sequential number generator, and to dial those numbers. That wording has caused years of courtroom grammar combat. Lawyers have argued over whether “using a random or sequential number generator” modifies both “store” and “produce,” or only “produce.” If that sounds like a fight over commas and modifiers, congratulationsyou have found the glamorous side of telecom law.
The practical question is simple: does a texting platform become an ATDS merely because it can automatically send messages to a stored customer list? Or must it randomly or sequentially generate the numbers it contacts? For businesses, the answer determines whether ordinary text-message marketing sits inside or outside the TCPA’s strict autodialer restriction.
The Marks Decision: A Broad View of Autodialers
In Marks v. Crunch San Diego, the Ninth Circuit took a broad approach. The plaintiff alleged that Crunch Fitness sent promotional text messages using a system that stored numbers and automatically sent messages. The court held that the ATDS definition included devices that store telephone numbers to be called and then dial them automatically, even if those numbers were not generated randomly or sequentially.
That interpretation mattered because modern marketing platforms usually do not call random phone numbers like chaotic robots with a caffeine problem. They usually send texts to lists: leads, customers, loyalty-program members, event attendees, app users, or people who signed up somewhere and may or may not remember doing so. Under the Marks approach, a system that automatically texts a stored list could fall within the ATDS definition.
The Ninth Circuit’s reasoning leaned heavily on the idea that the TCPA should cover the modern equivalent of automated mass dialing. If a system can blast messages to a stored list without individual manual dialing, the consumer experience may look the same: a phone lights up with an unwanted message. From a consumer-protection perspective, the source of the number may seem less important than the automated delivery of unwanted texts.
Duran v. La Boom Disco: The Second Circuit Follows Marks
The Second Circuit entered the debate in Duran v. La Boom Disco, Inc. The plaintiff, Radames Duran, alleged that he received hundreds of unsolicited text messages from La Boom Disco over roughly a year and a half. The messages were allegedly sent using platforms such as EZ Texting and ExpressText. La Boom argued that its systems were not ATDSs because they did not randomly or sequentially generate phone numbers and because some human action was involved in launching campaigns.
The district court sided with La Boom, concluding that the platforms did not qualify as ATDSs. The Second Circuit disagreed and vacated the summary judgment. In doing so, the court aligned itself with the Ninth Circuit’s broader Marks interpretation. It concluded that the systems could qualify as ATDSs because they stored lists of numbers and dialed or texted those stored numbers without the kind of human intervention that would remove them from the statute’s reach.
The key takeaway from Duran was direct and business-shaking: a platform did not necessarily escape ATDS treatment merely because it sent messages from a stored list rather than generating numbers randomly. A person clicking “send” did not automatically save the day. The court looked at whether the system itself performed the dialing or texting function automatically once the campaign was initiated.
Why the “Human Intervention” Argument Did Not Win
Many defendants in TCPA cases have argued that if a human being selects the list, writes the message, schedules the campaign, or clicks a button, the system should not be considered automatic. That argument has intuitive appeal. After all, if a person is involved, how automatic can it be?
The problem is that courts have often treated “human intervention” as a fact-specific issue, not a magic password. In Duran, the Second Circuit viewed the relevant question as whether the system dialed or texted the stored numbers automatically after being instructed to do so. If a marketing employee uploads contacts, selects a template, and presses a button, the platform may still perform the actual dialing function on its own.
This distinction made marketers nervous because most campaign tools are designed to reduce manual work. Nobody buys SMS software so an employee can lovingly type each phone number by hand like it is 1986. Automation is the point. Under the broad Marks and Duran view, that convenience could also create TCPA exposure.
The Circuit Split Before the Supreme Court Stepped In
Before the Supreme Court resolved the issue, federal appellate courts were divided. The Ninth Circuit and Second Circuit favored a broader interpretation that could include systems texting from stored lists. Other courts, including the Third, Seventh, and Eleventh Circuits, leaned narrower, requiring random or sequential number generation.
The Seventh Circuit’s decision in Gadelhak v. AT&T Services, Inc. famously described the statute’s wording as difficult, then held that a system must use a random or sequential number generator to qualify as an ATDS. The Eleventh Circuit took a similar path in Glasser v. Hilton Grand Vacations Co., rejecting the idea that dialing from a stored list alone was enough. The Third Circuit also resisted an overly broad definition in cases involving text-alert systems.
This split created a messy national compliance map. A company running the same SMS campaign could face different ATDS risk depending on where the lawsuit was filed. That is not exactly ideal for national brands, unless their compliance strategy involved a dartboard and a prayer.
Facebook v. Duguid Changed the ATDS Landscape
In 2021, the Supreme Court decided Facebook, Inc. v. Duguid, bringing much-needed clarity to the ATDS definition. The case involved automated security texts sent by Facebook to a person who claimed he never created the account associated with the alerts. The Supreme Court held that to qualify as an ATDS, equipment must have the capacity to use a random or sequential number generator to store or produce phone numbers to be called.
This was a major narrowing of the autodialer definition. The Court rejected the idea that any system capable of automatically dialing or texting from a stored list is automatically an ATDS. Instead, the equipment must use random or sequential number-generation technology in the relevant way.
For businesses, Facebook v. Duguid reduced some of the fear created by Marks and Duran. A standard SMS platform that sends messages to a curated customer list may not be an ATDS merely because it automates delivery. However, that does not mean businesses can text freely. Consent, opt-out handling, state mini-TCPA laws, carrier rules, platform policies, and other TCPA provisions still matter.
Soliman v. Subway: The Second Circuit’s Updated Position
The Second Circuit revisited the issue in Soliman v. Subway Franchisee Advertising Fund Trust, Ltd. The plaintiff alleged that Subway sent an automated marketing text using a pre-existing list of phone numbers. The Second Circuit affirmed dismissal, concluding that the TCPA’s ATDS restriction did not apply to a system that used a stored list without randomly or sequentially generating telephone numbers.
This decision is crucial because it shows that the Second Circuit’s earlier broad approach in Duran must now be read in light of Facebook v. Duguid. While Duran remains an important historical case, Soliman reflects the modern rule: a text sent from a stored list is not enough, by itself, to establish use of an ATDS under the federal TCPA autodialer provision.
Soliman also rejected the argument that a text message qualifies as an artificial or prerecorded voice. That part of the ruling matters because some plaintiffs have tried to plead around the narrowed ATDS definition by invoking other TCPA language. The court did not accept that theory for a standard text message.
What This Means for Text Message Marketing
The modern TCPA lesson is more nuanced than “texts from a list are safe” or “all automated texts are illegal.” Both statements are too simplistic. The better rule is this: after Facebook v. Duguid and Soliman, a system that merely sends texts to a pre-existing list is less likely to qualify as an ATDS under federal law, but marketers still need strong consent and opt-out practices.
Consent remains the foundation of compliant SMS marketing. Businesses should collect clear permission before sending promotional texts, document when and how consent was obtained, identify the sender, and honor revocation requests quickly. A consumer who replies “STOP” should not need to send a notarized scroll, a carrier pigeon, and three follow-up emails. The opt-out should work, and it should work promptly.
Companies should also avoid assuming that federal ATDS law is the only issue. Several states have enacted or expanded telemarketing laws that may reach conduct not covered by the federal ATDS definition. Florida, Oklahoma, Washington, and other jurisdictions have drawn attention for state-level telemarketing rules. A national SMS campaign must account for more than one layer of regulation.
Specific Examples of Risk After Duran, Facebook, and Soliman
Example 1: A Restaurant Texts Its Loyalty List
Suppose a restaurant sends a Friday promotion to customers who joined its loyalty program. The platform sends the message to a stored list. Under the old Marks and Duran logic, plaintiffs might argue the system is an ATDS because it automatically texts stored numbers. Under the current federal rule after Facebook and Soliman, the stronger defense is that the platform did not use a random or sequential number generator. Still, the restaurant needs valid consent and a working opt-out process.
Example 2: A Nightclub Uploads Purchased Leads
Now imagine a nightclub buys a list of phone numbers and blasts event promotions. Even if the platform is not an ATDS under the narrowed definition, the business may still face serious risk. Consent may be missing, the list source may be questionable, and state telemarketing rules may apply. Buying leads for text campaigns is often where compliance goes to take a long, dramatic sigh.
Example 3: A System Generates Numbers Sequentially
If a system actually generates phone numbers randomly or sequentially and sends messages to them, the ATDS risk is much higher. That is closer to the technology Congress targeted when it wrote the TCPA. In that situation, a company cannot rely on the “stored list” defense because the system’s number-generation function may bring it directly within the statute.
Compliance Lessons for Businesses
Businesses using SMS marketing should treat the ATDS debate as only one part of a broader compliance program. A careful company should know what its platform does technically, how numbers enter the system, whether any number generator is involved, and how consent records are stored. The legal team should not have to discover the platform’s features for the first time during a deposition. That is not discovery; that is archaeology with panic.
A strong SMS compliance program should include written consent language, clear disclosure of message frequency, a link or reference to terms, accurate sender identification, opt-out instructions, suppression-list management, and vendor oversight. If a third-party platform sends the texts, the brand should still understand the vendor’s technology and contractual promises.
Documentation is especially important. In litigation, the best compliance policy is the one a company can prove it followed. Consent screenshots, timestamped records, IP addresses, webform language, campaign logs, opt-out logs, and vendor certifications can make the difference between a quick defense and a long, expensive mess.
Consumer Protection Still Matters
Although the Supreme Court narrowed the ATDS definition, the consumer-protection purpose of the TCPA has not disappeared. People still dislike unwanted texts, especially when they arrive during dinner, work, sleep, or the sacred five minutes when they are trying to ignore everyone equally. Courts may be narrower on ATDS technology, but regulators and plaintiffs continue to scrutinize unwanted outreach.
The smartest businesses do not ask, “What can we technically get away with?” They ask, “Would a reasonable consumer understand and welcome this message?” That question is not only legally useful; it is good marketing. A clean list of people who actually want your texts will usually outperform a questionable list of annoyed strangers.
Why the Title Still Matters
The phrase “Second Circuit follows Marks ATDS includes texts sent from list” captures a real and important chapter in TCPA history. In 2020, Duran expanded risk for businesses in the Second Circuit by embracing the broader view that stored-list texting platforms could qualify as ATDSs. That decision intensified the circuit split and helped set the stage for Supreme Court review.
Today, however, the title must be read with an update sticker attached. After Facebook v. Duguid, and especially after the Second Circuit’s later decision in Soliman, the federal ATDS analysis is narrower. Texting from a stored list alone is generally not enough. The equipment must use random or sequential number generation to store or produce numbers.
That evolution is the real story. TCPA law is not frozen in 2020. It has moved from broad interpretations like Marks and Duran toward a more text-focused statutory reading under Facebook and Soliman. For lawyers, marketers, and compliance officers, the lesson is clear: old case headlines can be useful, but relying on them without checking later authority is like using a 2012 GPS and wondering why you are in a lake.
Experiences and Practical Takeaways Related to the Topic
In real-world marketing and compliance work, the ATDS debate often becomes most confusing when business teams treat text messaging as “just another channel.” Email, push notifications, social ads, and SMS may all sit together in a campaign dashboard, but legally they do not carry the same risk. SMS reaches a personal phone number, often produces an instant alert, and is governed by rules that can create statutory damages. That makes it different from sending a newsletter or posting a coupon on social media.
One common experience is that businesses focus heavily on the software platform but not enough on the list. After Facebook and Soliman, a company may feel relieved that its platform does not randomly or sequentially generate numbers. That is helpful, but it does not answer the consent question. If the list was scraped, purchased, inherited from an old vendor, collected through vague language, or mixed with users who opted out, the company may still be standing in legal quicksand while proudly announcing that its shoes are dry.
Another practical challenge is opt-out management. Many companies understand that “STOP” must be honored, but problems arise when data is spread across multiple systems. A customer opts out through one campaign, but another vendor or franchise location still has the number. A brand refreshes its CRM and accidentally reloads suppressed contacts. A local operator runs a separate promotion without checking the master opt-out list. These are not exotic failures. They are ordinary operational mistakes, and ordinary operational mistakes can become class-action allegations when repeated at scale.
Vendor contracts also deserve more attention than they usually receive. A business may rely on an SMS provider’s promise that the platform is compliant, but TCPA exposure often follows the sender whose brand appears in the message. Good vendor management should include technical descriptions of the platform, warranties about number-generation functionality, data-security promises, opt-out synchronization duties, audit rights, and indemnity provisions. The contract should not read like a cheerful handshake wrapped in legal confetti.
From a content perspective, compliant text marketing also requires restraint. Messages should be clear, brief, and expected. If a consumer signed up for shipping alerts, sending nightclub coupons is not a clever cross-sell; it is a consent problem wearing sunglasses. If a person opted into appointment reminders, that does not automatically mean they agreed to weekly promotional blasts. The scope of consent matters, and marketers should match message content to the permission actually obtained.
The biggest experience-based lesson is that compliance should be built before the campaign launches, not after complaints arrive. Legal review, consent capture, platform testing, opt-out workflows, and recordkeeping should be part of campaign design. When these steps happen early, SMS marketing can be effective, respectful, and defensible. When they happen after the first demand letter, everyone suddenly becomes very interested in screenshots they forgot to save.
For companies reading about Duran, Marks, Facebook, and Soliman, the practical message is balanced. The federal ATDS definition is narrower today than it appeared under the old Second Circuit “follows Marks” approach. But narrower does not mean risk-free. The safest SMS programs combine technical awareness with clean consent, fast opt-outs, careful vendor controls, and consumer-friendly messaging. That is not just legal hygiene. It is also how brands avoid becoming the text-message equivalent of the person who keeps ringing the doorbell after everyone inside turned off the lights.
Conclusion
The Second Circuit’s decision in Duran v. La Boom Disco once made the TCPA world buzz by following the Ninth Circuit’s Marks approach and treating certain stored-list texting platforms as ATDSs. That broad reading increased pressure on businesses using automated SMS tools and deepened a national circuit split. But the legal landscape changed after the Supreme Court’s Facebook v. Duguid decision, and the Second Circuit’s later Soliman ruling confirmed a narrower federal ATDS standard for texts sent from pre-existing lists.
The modern rule is not that SMS marketing is automatically dangerous, nor that it is automatically safe. The real answer is more practical: know your technology, prove your consent, honor opt-outs, monitor vendors, and keep up with changing federal and state law. In TCPA compliance, the “send” button should never be the first time someone asks whether the campaign is legal.
Note: This article is for general informational and SEO content purposes only. It is not legal advice. Businesses should consult qualified counsel before launching or defending SMS marketing campaigns.