Is Ringless Voicemail Legal? FCC Rules, State Laws and a Checklist

A marketing manager has a list of mobile numbers, a short promotion ready to record, and a familiar concern: a traditional call may interrupt people, while a ringless voicemail drop seems more considerate. A healthcare communicator may face a similar choice when sending a reminder or follow-up. The message goes directly to voicemail, so it can feel like a quiet shortcut around the normal rules.

That assumption creates the first compliance problem. Avoiding the ring doesn't remove the communication from federal robocalling rules. Ringless voicemail compliance depends on permission, message routing, suppression, and records, not on whether the recipient hears the phone ring.

The practical path is manageable. You need to understand how ringless delivery works, identify the consent required for your use case, stop messages when a recipient opts out, control timing, and preserve evidence that connects permission to the destination number and campaign purpose. Healthcare organizations also need to protect patient information and fit voicemail workflows into their HIPAA safeguards.

Jump to the rules at a glance, state laws, what changed since 2022, the pre-send checklist or the frequently asked questions.

Introduction to Compliant Ringless Voicemail Outreach

A sales team may want to notify prospects about an offer without filling their call logs with missed calls. A clinic may want to remind patients about an upcoming appointment without asking staff to dial each number manually. In both situations, ringless voicemail appears efficient because the recipient receives a message without the handset ringing.

The temptation is to treat that quiet delivery as a different category of outreach. A marketer might think, “We aren't calling the person, we're only placing a message in voicemail.” That reasoning is precisely what creates exposure when the destination is a wireless number and the message uses an artificial or prerecorded voice.

The safer approach treats compliance as a workflow design problem. The campaign should check permission before dispatch, apply suppression rules before routing, and retain records that explain why the message was eligible to send. A compliance review after delivery is too late, because the risky event has already occurred.

The mistake behind the shortcut

Suppose a contact once downloaded a guide but never agreed to receive automated marketing calls. The number is added to a ringless voicemail list, the recording identifies the business, and the message is delivered without a ring. The quiet experience may feel less intrusive, but the missing consent still matters.

An informational message can raise different questions from a promotional offer, yet the sender shouldn't assume that calling something a reminder solves every compliance issue. Purpose, permission, recipient type, content, timing, and opt-out history all need to align.

This guide focuses on the operating details that make ringless voicemail safer:

• Permission: Capture consent in a form that can be tied to the number and intended use.
• Routing: Prevent ineligible contacts from entering the send path.
• Suppression: Honor opt-outs and do-not-call controls before every campaign.
• Records: Preserve the evidence needed to explain the decision to send.
• Healthcare safeguards: Keep protected health information out of insecure messages and systems.

Compliant outreach isn't about finding a clever exception. It's about building a process in which the platform refuses to send when the required conditions aren't satisfied.

How Ringless Voicemail Works and Why It Counts as a Call

Think of ordinary calling as knocking on a door and waiting for someone to answer. Ringless delivery is closer to placing a note directly into the mailbox. The recipient may not hear a knock, but a sender still intentionally delivered a communication to that person's address.

A ringless voicemail system routes an audio message to a voicemail destination without causing the handset to ring in the usual way. The technical path changes the recipient's experience, not the sender's responsibility. For a wireless number, the Federal Communications Commission treats ringless voicemail as a “call” using an artificial or prerecorded voice under the TCPA, as described in FCC Declaratory Ruling and Order FCC 22-85. The FCC also noted that the phone "may signal that there is a voicemail message and may ring once before the message is delivered," and that its ruling covers any ringless voicemail technology that uses the person's mobile number to reach their phone (FCC 22-85, para. 16 and footnote 51).

What happens before the message drops

A responsible routing flow usually looks like this:

1. A number enters the audience. The system stores the number, contact source, consent status, and permitted communication purpose.
2. The campaign identifies its purpose. A sales promotion, appointment reminder, account notice, and service update shouldn't automatically share the same eligibility rule.
3. The platform checks suppression data. Opt-outs, do-not-call records, invalid numbers, and internal exclusions need to be applied before dispatch.
4. The system validates the destination. Wireless and landline handling may differ operationally, so the campaign should retain the destination type and routing decision.
5. The message is delivered. Only contacts that pass the campaign's rules should reach the voicemail-drop queue.

This is why ringless voicemail compliance belongs at the message-routing layer, not only at the dialing layer. A clean dialer doesn't help if a contact with revoked permission can still enter a prerecorded campaign.

Marketing and informational messages

A promotional recording that encourages a recipient to buy, renew, upgrade, or schedule a sales conversation deserves strict scrutiny. An informational message may have a different purpose, but that distinction doesn't eliminate the need for permission, clear identification, suppression, and appropriate records.

Readers who need a plain-language overview of the technology can review what ringless voicemail means and how it works. The important operational lesson is simple: no ring doesn't mean no call.

Current Federal Rules for Ringless Voicemail in the United States

A campaign can pass through a routing system in seconds, yet the legal decision happens before delivery. On November 21, 2022, the FCC issued Declaratory Ruling and Order FCC 22-85, stating that ringless voicemail to wireless phones is a “call” under the TCPA because it uses an artificial or prerecorded voice. Bypassing the ring does not place the message outside the statute, as stated in the FCC's official order and announcement.

For businesses, the practical rule is direct: ringless voicemail sent to mobile numbers requires consumer consent before delivery. If the message advertises something or is telemarketing, that consent must be prior express written consent: a signed agreement (an electronic signature counts) that authorizes the seller to deliver such messages to a specific phone number (47 CFR 64.1200(a)(2) and (f)(9)). The campaign should apply the same permission, suppression, and recordkeeping controls used for other prerecorded or automated marketing calls.

The Federal Rules at a Glance

These are the US federal rules that apply to a ringless voicemail once it counts as a prerecorded call, from the rule text (47 CFR 64.1200, checked October 19, 2026).

For the consent details, see our guides to express written consent and do-not-call list compliance.

What Changed: Ringless Voicemail Rules Timeline

• March 31, 2017: All About the Message, LLC asks the FCC to declare that ringless voicemail is not covered by the TCPA (FCC 22-85, fn. 2).
• November 21, 2022: the FCC denies the petition and the requested waiver: ringless voicemail to wireless phones is a "call" that needs consent, effective on release (FCC 22-85).
• February 8, 2024: the FCC confirms that AI-generated voices are "artificial" voices under the TCPA (FCC 24-17).
• April 11, 2025: consent revocation rules take effect: any reasonable method, honored within 10 business days (47 CFR 64.1200(a)(10); effective date per FCC 26-67, fn. 7).
• September 30, 2026: the FCC adopts new revocation rules (FCC 26-67): callers may designate an exclusive revocation method and treat some revocations as limited to one category of informational calls. They take effect 30 days after Federal Register publication, so check the current rule (FCC 26-67, paras. 2 and 24).

What the ruling means for message routing

The FCC's position turns compliance into a workflow design task. Before a message reaches the voicemail-drop queue, the system should:

• Verify permission: Confirm that legally sufficient consent covers the specific number and message purpose.
• Identify the destination: Retain whether the number is wireless or landline and record the routing decision.
• Apply suppression rules: Remove opt-outs, do-not-call records, invalid numbers, and internal exclusions before dispatch.
• Preserve evidence: Connect the consent record to the number, campaign, communication method, and relevant timestamp.
• Control the queue: Prevent a later opt-out from being overridden by an earlier opt-in.

A consent field without provenance is like a key without a label. It may exist, but the team cannot tell which door it opens. Healthcare campaigns also need HIPAA review at this layer. Patient information should not enter a voicemail workflow unless the message, recipient, authorization, vendor access, and disclosure settings fit the organization's privacy controls.

Teams can turn these requirements into assigned campaign controls with a practical TCPA compliance checklist, covering consent, timing, opt-outs, and documentation.

Consent, timing, and local requirements

Federal rules place ringless voicemail alongside other prerecorded-call controls. Consent, quiet-hours practices, and recordkeeping still require attention, while the exact review may depend on the message, recipient, industry, and applicable state law. A national campaign should therefore treat federal compliance as the baseline, not the entire approval process. For example, Florida bars commercial telephone solicitation calls, including recorded messages, before 8 a.m. or after 8 p.m. in the called person's time zone, and limits them to three per 24 hours on the same subject (Florida Statutes 501.616(6), checked October 19, 2026).

The communication channel also affects the controls. The same business purpose can face different rules by channel: a prerecorded voicemail to a cell phone needs consent under the TCPA, while telemarketing to residential lines with a prerecorded voice needs prior express written consent (47 CFR 64.1200(a)(3)). The principle remains consistent: permission must match the channel and purpose.

State Laws That Add to the Federal Rules

Federal rules are the floor. Florida, Oklahoma and Maryland go further for sales calls, and all three name prerecorded voicemail in their definition of prior express written consent. Each also lets a person sue for $500 per violation or actual damages, whichever is greater, and up to three times that if the violation was willful or knowing.

Other states have their own telemarketing, registration and do-not-call rules, and they change. For a national list, the simple approach is to apply the strictest window that fits your contacts (for these three states, 8 a.m. to 8 p.m. in the recipient's time zone), keep written consent that names voicemail, and check the states where your contacts live with your lawyer.

The TCPA lets a person sue for $500 in damages for each violation (or the actual monetary loss, if greater), and a court may increase the award to up to three times that amount, up to $1,500, if the violation was willful or knowing (47 U.S.C. 227(b)(3)). These are statutory damages in private lawsuits, not fines; the FCC can separately impose forfeiture penalties (47 U.S.C. 227(b)(4)). That exposure makes each pre-queue routing decision part of the compliance record.

Key Risks and Case Law Lessons Every Sender Should Know

The largest mistake is treating compliance as a document someone checks after a campaign. A sender may have a polished recording, a carefully segmented audience, and a reputable delivery provider, yet still lack proof that every destination number was authorized for that exact type of outreach.

The financial exposure is calculated per violation. If a message is sent without the required consent, the statute provides $500 for each violation, which a court may increase up to $1,500 when the violation was willful or knowing (47 U.S.C. 227(b)(3)). A high-volume campaign can therefore turn one flawed audience rule into a serious liability event.

Where campaigns usually break

Legal commentary on the FCC's ruling repeatedly emphasizes the same operational themes. The sender needs evidence of permission, a reliable opt-out process, and records that survive staff changes and system migrations. The FCC's treatment also rejects the idea that avoiding the ringing step changes the message's legal status, as explained in this analysis of ringless voicemail consent requirements.

What the FCC and Courts Have Said

The 2022 ruling is the main lesson, because it answered the arguments senders used to rely on. The FCC rejected each of these (FCC 22-85, paras. 14 to 20):

Courts have also let ringless voicemail lawsuits proceed. In Dickson v. Direct Energy, LP, 69 F.4th 338 (6th Cir. June 1, 2023), the district court had dismissed a TCPA class action because the plaintiff received only one ringless voicemail. The Sixth Circuit reversed: "regardless of the number of RVMs Dickson received," the injury was concrete enough to sue (opinion, 6th Cir.). In other words, even a single unwanted voicemail drop can support a claim.

Common failure points include:

• Consent without provenance: The database says “opted in,” but can't show when, where, or for what purpose.
• Purpose mismatch: A contact agreed to service notifications, then receives a sales promotion.
• Suppression lag: An opt-out is recorded in one system but not synchronized with the send platform.
• Shared audience contamination: A list approved for one client, brand, or campaign is reused elsewhere.
• Weak audit trails: The business can't reconstruct the audience, recording, schedule, and eligibility decision.

A simple risk example

Suppose a sender releases a campaign to a large audience without checking whether previous opt-outs were suppressed. Each disputed message may be evaluated separately, rather than treated as one indivisible campaign mistake. The risk therefore grows with the number of messages that fail the eligibility test, while the operational cost includes investigation, list reconstruction, complaint handling, and possible campaign suspension.

The most useful response isn't panic. It's prevention. Build the send process so that the system requires a valid consent record, checks current suppression status, and preserves the decision before it hands the message to the delivery layer.

Your Ringless Voicemail Compliance Checklist and Best Practices

A compliant workflow follows a contact from acquisition through delivery. Start with the person, number, purpose, and permission before creating the recording. This order matters because routing rules can stop an ineligible message before it reaches the delivery provider.

Start with consent provenance

Capture the consent source, destination number, date or event that created permission, and communication purpose. Preserve the language or form context that explains what the recipient accepted. A generic “yes” field cannot show whether the permission covered marketing, service communication, or another use.

Marketing campaigns need the clearest internal gate. Require documented consent for the intended automated outreach. If the record does not identify the authorized purpose, keep the number out of the ringless voicemail audience until someone resolves it.

Write for identification and restraint

The recording should identify the sender and explain its purpose without making the recipient guess who left the message. The rules are specific: state the business name clearly at the beginning of the message and a callback telephone number during or after it (47 CFR 64.1200(b)(1) and (b)(2)). Avoid sensitive details, especially when a shared phone, family member, or workplace device could expose the content.

Give recipients a practical way to stop future messages. For marketing messages this is required: an automated opt-out mechanism explained within two seconds of the identification and, when the message is left on voicemail, a toll-free number that connects to that mechanism (47 CFR 64.1200(b)(3)). State the opt-out instruction clearly, then send the resulting request to the suppression record before another campaign can route to that number. The routing layer should treat suppression like a closed gate, not a note for someone to review later.

Control timing and suppression

Use the recipient's local time instead of relying on the campaign manager's time zone. Federal rules bar telephone solicitations before 8 a.m. or after 9 p.m. at the called party's location (47 CFR 64.1200(c)(1)), and some states set a shorter window. Before dispatch, apply internal do-not-call lists, campaign exclusions, prior opt-outs, and invalid-number results. A message should not reach the provider first and become compliant afterward.

Review eligibility in this order:

1. Verify identity and purpose. Confirm the sender, campaign type, audience, and intended message.
2. Check consent. Match the number to a documented permission record.
3. Run suppression. Remove opt-outs, do-not-call entries, and other blocked contacts.
4. Apply timing controls. Hold messages outside the approved window.
5. Record the decision. Store the audience version, message version, eligibility result, and delivery event.

Compare the control environment

Healthcare organizations must connect ringless voicemail controls with HIPAA safeguards. A voicemail should disclose no more patient information than necessary. HHS says the HIPAA Privacy Rule does not prohibit leaving messages on answering machines, but providers "should take care to limit the amount of information disclosed," for example leaving only their name and number and other information needed to confirm an appointment, or asking the person to call back (HHS HIPAA FAQ 198). Systems handling contact data need secure access, appropriate safeguards, and controlled integrations. HIPAA also makes workflow boundaries important: the team should decide what may be left in the recording before routing patient-related outreach.

Broadcast provides ringless voicemail delivery, consent and suppression controls, do-not-call screening, scheduling, recordings, analytics, and integrations with systems such as ActiveCampaign, HubSpot, Keap, and Zapier. Teams can evaluate those functions against their consent, routing, privacy, and recordkeeping requirements.

How Platform Features and Workflows Reduce Compliance Risk

A platform doesn't make an unlawful campaign lawful by itself. It can, however, turn policy into repeatable decisions that staff don't have to reconstruct manually for every send.

The most valuable feature is a pre-dispatch eligibility layer. Consent capture can begin with a web form, a double opt-in process, or a text-to-join keyword. The resulting record should travel with the contact, including the number, source, purpose, and status. Segmentation then separates marketing audiences from informational audiences instead of placing both in one broad list.

Put suppression in the send path

Do-not-call management, opt-out handling, number validation, and campaign exclusions should run before routing. If a recipient replies with an opt-out request, that status needs to reach every relevant sequence, not just the campaign that received the request.

Scheduling controls support the same principle. A campaign can use recipient-aware timing, approval steps, and pauses between messages so a contact doesn't move automatically from one channel into another after becoming ineligible.

Broadcast provides ringless voicemail delivery, consent and suppression controls, do-not-call screening, scheduling, recordings, analytics, and integrations that can connect outreach with systems such as ActiveCampaign, HubSpot, Keap, and Zapier. Teams evaluating those functions can review its ringless voicemail feature as one platform option.

On Broadcast, a ringless voicemail drop uses 2 credits per delivered drop, from the same credits as texts and calls, and plans start at $15. For the consent, opt-out and do-not-call tools across texts, voicemail drops and calls, see compliance.

HIPAA needs a separate review

Healthcare teams should avoid placing diagnoses, treatment details, appointment specifics, or other protected health information into a voicemail unless the communication and safeguards have been carefully reviewed. A safer message may identify the organization and ask the patient to return a call through an approved channel, rather than disclosing the reason in detail.

The TCPA also has health care specific rules. Health care messages from a HIPAA covered entity or its business associate are exempt from the written-consent requirement for marketing calls (47 CFR 64.1200(a)(2)). A separate exemption lets healthcare providers send certain free-to-the-patient calls to the number the patient provided, such as appointment reminders, lab results and prescription notifications, under strict conditions: no marketing or billing content, generally one minute or less, one per day and three per week at most, and a toll-free opt-out number on voicemail (47 CFR 64.1200(a)(9)(iv)). For patient messaging more broadly, see our guide to HIPAA compliant patient communication.

Integrations can reduce manual copying, but every connection becomes part of the privacy review. Confirm access permissions, data flow, retention, and vendor responsibilities before linking a CRM, scheduling system, automation tool, or patient workflow to a voicemail campaign.

Analytics should support reconstruction, not just marketing measurement. Keep the campaign version, audience criteria, recording, consent state, suppression result, schedule, and delivery status so an internal reviewer can understand what happened without relying on memory.

Building a Sustainable and Compliant Outreach Strategy

A healthcare office schedules a reminder, but the patient's consent record is incomplete. A marketing team imports an old list, while a recent opt-out remains in another system. In both cases, the risk begins before delivery. A sustainable program treats compliance as routing logic that decides whether a message may proceed.

The operating rule is simple: permission must reach the dispatch decision. Consent records should identify the approved purpose, the recording should stay within that purpose, and suppression status should be checked again when the route is created. If any required value is missing or stale, the system should hold the message for review instead of sending it.

A short decision tree helps staff act consistently:

1. Proceed when consent is documented for the campaign purpose, suppression data is current, and the recording has passed privacy review.
2. Hold when a record is incomplete, conflicting, outdated, or linked to an uncertain healthcare workflow.
3. Cancel or remove the recipient when an opt-out, do-not-call restriction, or privacy concern makes eligibility unacceptable.
4. Reassess after changing the audience, script, vendor connection, or routing rule. A new workflow can change the compliance decision.

Healthcare teams should use a minimal voicemail script, such as identifying the organization and asking the patient to return the call through an approved channel. The recording should avoid diagnoses, treatment details, appointment specifics, and other protected health information unless the communication and safeguards have been reviewed.

Keep records that explain the decision, including the campaign version, consent state, suppression result, script, routing outcome, and delivery status. This creates an audit trail without relying on staff memory.

For the basics of the channel before you plan a campaign, see ringless voicemail for business.

Broadcast supports SMS, voice broadcasting, and ringless voicemail workflows with consent capture, suppression tools, scheduling, recordings, and campaign analytics. Review Broadcast to assess whether its workflow fits permission-based outreach and existing team systems.

Ringless Voicemail Compliance FAQ

Is ringless voicemail legal?

Yes, with consent. The FCC ruled in November 2022 that ringless voicemail to wireless phones is a call made with a prerecorded voice, so it needs the recipient's prior express consent, and prior express written consent when it is marketing (FCC 22-85; 47 CFR 64.1200(a)(2)).

Which states have their own ringless voicemail rules?

Florida, Oklahoma and Maryland require prior express written consent for sales calls that use a recorded message, and their definitions name prerecorded voicemail. All three limit those calls to 8 a.m. to 8 p.m. in the recipient's time zone and to three in 24 hours on the same subject (see state laws). Other states have their own rules.

Does ringless voicemail require written consent?

Only when the message advertises something or is telemarketing. Informational messages, such as an account notice, still need prior express consent, just not the written form (47 CFR 64.1200(a)(1)(iii) and (a)(2)).

Does the Do Not Call Registry apply to ringless voicemail?

Yes, for telephone solicitations. The national do-not-call and calling-hour rules apply to telemarketing calls to wireless numbers too, and you must keep your own do-not-call list and honor requests within 10 business days (47 CFR 64.1200(c), (d) and (e)).

What must a ringless voicemail say?

The name of the business at the beginning and a callback number during or after the message. Marketing messages also need an automated opt-out and, when left on voicemail, a toll-free number that reaches it (47 CFR 64.1200(b)).

Can I use an AI voice for ringless voicemail?

An AI-generated voice counts as an "artificial" voice under the TCPA, so the same consent rules apply as for a recorded human voice (FCC 24-17).

What are the penalties for ringless voicemail violations?

A person can sue for $500 per violation or the actual loss, whichever is greater, and a court may triple it if the violation was willful or knowing; the FCC can also impose forfeitures (47 U.S.C. 227(b)(3) and (b)(4)).

Does ringless voicemail to a landline need consent?

FCC 22-85 addresses messages sent to wireless numbers. For residential landlines, prerecorded telemarketing messages already need prior express written consent, with limited exemptions (47 CFR 64.1200(a)(3)).

Can healthcare providers leave voicemails for patients?

Yes. HHS says HIPAA does not prohibit leaving messages on answering machines, as long as the information is limited, for example the provider's name and number or a request to call back (HHS FAQ 198). The TCPA rules above still apply to prerecorded calls.

How long should I keep ringless voicemail records?

The rules require do-not-call requests to be honored for 5 years from the request (47 CFR 64.1200(d)(6)). Keep proof of consent for as long as you rely on it, and check your lawyer's guidance on retention.