TCPA Phone Call Compliance: What Businesses Need to Know About Calls, Autodialers, and Ringless Voicemail
Most businesses that invest in TCPA compliance do so through the lens of SMS — and for good reason. Text message violations are visible, well-documented, and increasingly litigated. But the Telephone Consumer Protection Act was written to govern the full spectrum of phone-based business communications, and the rules applying to voice calls, automated outreach, and ringless voicemail drops are every bit as consequential as those covering your text messaging program. Ignoring call compliance while focusing only on SMS is a common and costly oversight.
If your business uses the phone to reach customers — whether through outbound sales calls, appointment reminders, debt collection outreach, political messaging, or any other automated or semi-automated communication — understanding the TCPA’s call-specific requirements isn’t optional. This guide breaks down what consent is required before you dial, how autodialers are defined and regulated, where ringless voicemail sits within the TCPA framework, and how your call compliance strategy should connect to your broader messaging compliance program.
The TCPA’s Scope: It’s Not Just About Texts
The Telephone Consumer Protection Act was enacted in 1991 — well before SMS marketing existed — and its original focus was on regulating unwanted telephone calls and fax transmissions. Over the decades, the FCC has expanded and updated the TCPA’s implementing regulations to address new technologies, including text messaging, predictive dialers, and most recently ringless voicemail. But voice calls have always been at the core of what TCPA governs.
Under the TCPA, businesses face restrictions on several categories of phone-based outreach: calls made using an automatic telephone dialing system (ATDS), calls that deliver a prerecorded or artificial voice message, and calls made to numbers on the National Do Not Call Registry. Each category carries its own consent requirements, exemptions, and enforcement exposure. Violations can result in statutory damages of $500 per violation for negligent violations and up to $1,500 per violation for willful or knowing violations — and because calls are often made in bulk, class-action exposure can be enormous.
Autodialers and the ATDS Definition
The definition of an automatic telephone dialing system — commonly referred to as an ATDS or autodialer — has been one of the most contested legal questions in TCPA litigation over the past decade. At its core, an ATDS is a system that has the capacity to store or produce telephone numbers using a random or sequential number generator and to dial those numbers automatically. But the practical boundaries of that definition have been litigated all the way to the Supreme Court.
In 2021, the Supreme Court issued its decision in Facebook, Inc. v. Duguid, narrowing the definition of an ATDS to systems that actually use a random or sequential number generator to store or dial numbers — as opposed to systems that simply dial from a stored list. This ruling provided some relief for businesses using predictive dialers and list-based calling systems, which many argued should not qualify as autodialers under the narrower definition.
However, the practical compliance picture remains complicated. State laws in several jurisdictions use broader definitions of automated dialing technology, and plaintiffs’ attorneys have continued to find creative theories of liability. More importantly, even if your calling system doesn’t meet the federal ATDS definition under Duguid, other TCPA provisions — including those governing prerecorded messages — may still apply regardless of how the call is initiated.
The safest compliance posture is to treat any automated or semi-automated outbound calling system as subject to TCPA requirements until you’ve confirmed with qualified legal counsel that your specific technology and use case fall outside the statute’s reach.
Consent Requirements for Outbound Calls
Like SMS, TCPA-governed voice calls require prior express consent before a business may contact a consumer. However, the level of consent required depends on the nature of the call.
For informational or transactional calls — such as appointment reminders, fraud alerts, or account notifications — delivered via autodialer or prerecorded message to a mobile number, the TCPA requires prior express consent. This is a lower bar than the written consent required for marketing, but it still requires that the consumer have provided their number in the context of the transaction or relationship and with the understanding that they may be contacted.
For marketing or promotional calls delivered via autodialer or prerecorded message to a mobile number, the TCPA requires prior express written consent. This is the same standard applied to marketing SMS messages — the consumer must have agreed in writing (including electronic writing) to receive calls, and that agreement must clearly authorize calls from your organization for marketing purposes.
Calls to residential landlines using a prerecorded message for marketing purposes also require prior express written consent. Calls to residential landlines using a live agent have somewhat different rules, primarily governed by Do Not Call Registry compliance rather than the autodialer-specific provisions.
Critically, consent obtained for one purpose does not automatically extend to another. A consumer who provides their phone number to receive order confirmations has not thereby consented to receive promotional calls. Scope and specificity of consent matter — and vague or overly broad consent language is increasingly challenged in litigation.
Ringless Voicemail: Where It Fits in the TCPA Framework
Ringless voicemail — also known as a voicemail drop or direct-to-voicemail delivery — is a technology that allows businesses to deposit a pre-recorded audio message directly into a consumer’s voicemail box without the phone ringing. The pitch to marketers has always been that it delivers a voice message without disrupting the consumer with an actual call, leading some to argue that it should be treated differently than a traditional phone call under TCPA.
That argument has not fared well legally. The FCC and multiple federal courts have taken the position that ringless voicemail constitutes a “call” for purposes of the TCPA. The method by which the voicemail is delivered — whether it triggers a ring or goes directly to the voicemail system — does not change the underlying act of using automated technology to deliver a message to a consumer’s phone number without their consent.
This means that ringless voicemail drops are subject to the same TCPA consent requirements as any other automated call. If you’re delivering a marketing voicemail drop, you need prior express written consent from each recipient. If you’re delivering a transactional or informational voicemail drop, you need prior express consent. Deploying ringless voicemail without appropriate consent because it “doesn’t really ring” is not a defensible compliance position — and businesses that have operated on that assumption have faced significant TCPA exposure.
There is ongoing regulatory activity around ringless voicemail, and the FCC has continued to receive petitions from both industry groups seeking clearer exemptions and consumer advocates seeking stronger restrictions. Businesses using this technology should monitor regulatory developments closely and ensure their consent practices are aligned with current FCC guidance.
The Do Not Call Registry and Internal DNC Lists
Separate from the autodialer and consent provisions, the TCPA’s Do Not Call rules create another layer of compliance obligation for outbound calling programs. The National Do Not Call Registry allows consumers to register their residential phone numbers to opt out of unsolicited telemarketing calls. Businesses making telemarketing calls are required to check their calling lists against the registry and honor registrations within a specified timeframe.
Beyond the national registry, the TCPA also requires businesses to maintain an internal Do Not Call list and to honor consumer opt-out requests promptly. If a consumer asks to be removed from your calling list, that request must be honored regardless of whether their number appears on the national registry. Calling a number that has opted out of your internal list — even once — is a violation.
For SMS programs, maintaining a suppression list for opt-outs is standard practice. The same discipline needs to apply to voice outreach. If your organization operates both an SMS program and an outbound call program, these suppression lists should ideally be integrated, so that an opt-out from one channel is reflected across all phone-based outreach.
How Call Compliance Connects to Your SMS Strategy
If you’re already managing TCPA compliance for an SMS program, the infrastructure you’ve built — consent capture and documentation, suppression list management, audit trails, and regulatory monitoring — is directly applicable to your voice and voicemail programs. The underlying legal framework is the same statute, the consent requirements follow similar logic, and the documentation standards that protect you in an SMS audit will protect you in a call-related audit as well.
The key is to avoid treating your calling program as a separate compliance silo. Businesses that manage SMS and voice compliance independently often end up with inconsistent consent records, fragmented suppression lists, and gaps in their documentation that create unnecessary exposure. A unified compliance approach — where consent is captured and documented consistently across all phone-based channels, and where suppression decisions propagate across every touchpoint — is both more efficient and more defensible.
State Laws and the TCPA Patchwork
Federal TCPA compliance is the floor, not the ceiling. A number of states have enacted their own telephone solicitation and robocall laws that impose stricter requirements than the federal statute. Florida’s Telephone Solicitation Act, for example, has been a particularly active source of litigation in recent years, with provisions that go beyond federal TCPA requirements in several respects. California, Texas, and other states have their own telemarketing regulations that businesses operating nationally must account for.
Multi-state calling programs should be reviewed against the laws of each state in which consumers are being contacted — not just against the federal TCPA. The combination of federal and state exposure is one of the primary reasons that phone-based outreach, like SMS, demands a serious, ongoing compliance investment rather than a one-time review.
Building a Phone Compliance Program That Holds Up
The businesses best positioned to use phone-based outreach at scale are those that treat compliance as infrastructure rather than an afterthought. That means capturing consent in a documented, auditable way before any call is placed. It means checking your calling lists against the DNC Registry on a regular cadence. It means maintaining and cross-referencing internal suppression lists across every channel. It means training staff on what they can and cannot say when using prerecorded messages or automated systems. And it means staying current on FCC rulemaking and litigation developments that can shift the compliance landscape with relatively little notice.
The stakes are high — but so is the opportunity. Businesses that invest in compliant, well-structured call programs can still use the phone as a powerful, personal, high-converting communication channel. The goal of compliance isn’t to stop you from using the phone. It’s to make sure that when you do, you’re doing it on a foundation that protects your business and respects your customers.
Stay Current on TCPA Compliance and A2P Best Practices
TCPA compliance for calls, ringless voicemail, and SMS is a moving target — and staying ahead of regulatory changes is one of the best investments a business can make. Subscribe to the mytcrplus.com YouTube channel for ongoing updates on SMS compliance, 10DLC registration, call compliance, A2P best practices, and everything your business needs to run phone-based communications the right way.
Whether you’re evaluating your current calling program or building one from the ground up, understanding the full scope of TCPA obligations — across every channel where you pick up the phone — is the foundation every compliant outreach strategy is built on.
