Is Ringless Voicemail Legal for Insurance Leads in 2026?

Yes, it’s legal, but only under the same consent rules that already govern an automated or prerecorded call, and a lot of the agencies using it don’t realize that. Ringless voicemail drops a prerecorded message straight into someone’s voicemail box without the phone ever ringing, and for years vendors sold it as a way around the Telephone Consumer Protection Act on exactly that basis: no ring, no call, no consent required. The FCC closed that argument in November 2022. A Wisconsin insurance agent has already sued another insurance marketing firm over it. This article covers what the FCC actually decided, what a violation costs an agency that gets it wrong, and how to use ringless voicemail, if you use it at all, without turning a cheap outreach tactic into a five-figure demand letter.

What Ringless Voicemail Actually Is, and Why It Feels Like a Loophole

Ringless voicemail, often shortened to RVM, is a prerecorded audio message deposited directly into a recipient’s cell phone voicemail box using a technical process that bypasses the normal ringing step. The recipient’s phone never rings and shows no missed call; they simply see a voicemail notification and, when they check it, hear a message that was never actually “called in.” The vendor that fought the FCC over this technology described its own process, in its 2017 petition, as creating what it called “a landline to landline session directly to the telephone company’s voicemail server,” specifically arguing that because no call is placed to the recipient’s actual phone number in the traditional sense, the TCPA’s call restrictions shouldn’t apply.

That argument is the entire reason ringless voicemail got marketed to insurance agents, real estate agents, and debt collectors as a compliance workaround for years. If it’s not a “call,” the thinking went, then none of the consent rules built around calls, cell phones, and autodialers apply to it. Agencies could blast a list at scale, at a fraction of what a live dial costs, without triggering the same exposure a robocall or an autodialed campaign would.

The problem with the “not a call” argument was that it asked regulators to focus on the delivery mechanism, ringing versus not ringing, instead of on what actually lands on the recipient’s phone: an artificial or prerecorded voice message, delivered to a wireless number, that the recipient didn’t ask for. That’s precisely the category of contact Congress wrote Section 227(b)(1)(A)(iii) of the TCPA to require consent for in 1991, years before ringless voicemail existed as a technology. The FCC had to decide whether a new delivery method could sidestep an old consent requirement just because it was engineered around the letter of “the phone rings.”

The FCC Already Answered This: Ringless Voicemail Is a “Call”

The petition that forced the FCC’s hand came from All About the Message, LLC (AATM), a ringless voicemail provider, filed March 31, 2017. AATM asked the Commission to declare that its service falls outside the TCPA entirely and, failing that, to grant a retroactive waiver of the rules for any past use of the technology. The Consumer and Governmental Affairs Bureau opened the petition for public comment and received more than 8,000 responses, almost all opposed. AATM tried to withdraw the petition in June 2017, but because it had already drawn attention from commenters and members of Congress, the Commission kept the docket open and eventually ruled on the merits anyway.

The ruling came down as FCC 22-85, a Declaratory Ruling and Order in CG Docket No. 02-278, adopted by the Commission on November 14, 2022 and released November 21, 2022. The holding is stated in the ruling’s own opening paragraph: “we find that ‘ringless voicemail’ to wireless phones requires consumer consent because it is a ‘call’ made using an artificial or prerecorded voice and thus is covered by section 227(b)(1)(A)(iii) of the 1991 Telephone Consumer Protection Act.” The Commission denied AATM’s petition to declare ringless voicemail exempt, and separately denied its request for a retroactive waiver.

Two things about that ruling matter for how it applies to your agency specifically. First, it isn’t limited to AATM or to the particular technology AATM used. The ruling applies to any entity that delivers a ringless voicemail to a wireless number, regardless of which vendor’s software does the delivery. Second, it didn’t invent a new rule; it clarified that an existing one, the consent requirement in Section 227(b)(1)(A)(iii), already covered this delivery method. That distinction matters because it means the ruling isn’t a novel restriction agencies can plausibly claim they didn’t know about going forward. As of late 2022, “ringless voicemail isn’t really a call” stopped being a good-faith legal position for anyone paying attention to FCC guidance.

What a Violation Actually Costs

Run the actual statute. Section 227(b)(3) of the TCPA gives a person receiving a non-compliant automated or prerecorded call, which now includes an unconsented ringless voicemail per FCC 22-85, a private right of action to recover actual monetary loss or $500 in damages for each violation, whichever is greater. A court can increase that award to as much as three times the base amount, up to $1,500 per violation, if it finds the defendant willfully or knowingly violated the rule. Because a ringless voicemail campaign typically sends the same message to thousands of numbers at once, and because the statute counts each message as its own violation, the exposure scales directly with list size, not with how many people actually complain.

Put those figures against a realistic list size instead of a worst case. An agency that sends 5,000 ringless voicemails to a purchased or scraped list, one it never separately confirmed had valid consent for automated or prerecorded messages, is looking at a theoretical exposure of $2,500,000 at the base $500 figure, or $7,500,000 if the conduct is found willful. Most cases never settle anywhere near the statutory ceiling. But that ceiling is what a plaintiff’s attorney negotiates against from the opening position, and settlements built off multi-thousand-message campaigns still land in real money: National Law Review’s coverage of a 2026 TCPA class action against National Retail Solutions (NRS Pay), resolved over ringless voicemails sent using VoiceLogic’s service, reports a $6.5 million settlement covering a class period from January 8, 2020 through final approval, with more than 50,000 class members each receiving over $100.

None of this means every agency that has ever used ringless voicemail is sitting on a multimillion-dollar liability. It means the statute counts by the message, the FCC has already foreclosed the “it’s not a call” defense, and the gap between what a compliant campaign costs and what a non-compliant one can cost is not a rounding error at any real list size.

A Real Case: What Happened When an Insurance Marketing Firm Used Ringless Voicemail on Agents

The clearest illustration of this exposure applied to the insurance industry specifically is Van Elzen v. Advisors Ignite USA LLC, No. 1:22-cv-00859, filed in the U.S. District Court for the Eastern District of Wisconsin. According to National Law Review’s and TCPAWorld’s coverage of the case, the plaintiff, an insurance agent named Van Elzen, alleged that Advisors Ignite USA used SlyBroadcast’s ringless voicemail technology to send more than 15,000 prerecorded messages to insurance agents, advertising marketing events the defendant said could help recipients “substantially increase” their income. The recipients were, notably, not consumers being sold insurance; they were other insurance agents being marketed a business opportunity, sourced from what the coverage describes as an industry data provider list.

Van Elzen sought to represent a class of everyone who received similar messages. On January 18, 2024, Judge William C. Griesbach denied class certification. The court’s reasoning wasn’t that ringless voicemail is exempt from the TCPA, or that the underlying allegations lacked merit; it turned on Rule 23’s class-action mechanics specifically. Per the coverage, the court found that whether class members suffered a real injury from receiving the messages was too individualized a question to resolve on a class-wide basis, since some recipients may have found the marketing message unwelcome while others may have viewed it as a beneficial business tip, undermining predominance, typicality, and superiority.

The detail worth sitting with is who the recipients were: insurance agents, marketed by another firm in the same industry, off a purchased data list. It’s the exact pattern a lot of agencies run in reverse, marketing to consumers instead of to other agents, using the same technology and the same “we bought a list, we didn’t call them, we just dropped a voicemail” logic. The case doesn’t need a favorable outcome for the plaintiff to make the point: this fact pattern, purchased list plus mass ringless voicemail plus no documented consent, is the one that ends up in federal court.

How to Use Ringless Voicemail Without Getting Sued, or Decide Not To

Give this away completely, because none of it requires buying a different product; it requires building a consent record before the message goes out, which is the same discipline any compliant automated or prerecorded outreach needs.

1. Confirm what kind of consent standard applies to your message. If the ringless voicemail advertises anything, a quote, a policy, an event, a callback offer, it’s advertising or telemarketing under 47 CFR Section 64.1200(a)(2), which means it needs prior express written consent, not the lower prior-express-consent standard that covers some non-marketing calls. Assume the stricter standard applies to anything your agency would actually send.
2. Never send ringless voicemail to a purchased or scraped list without separately verifying consent for that specific channel. A list vendor’s assurance that leads “opted in” to being contacted isn’t the same as a signed, specific authorization to receive automated or prerecorded messages at that number. Ask the vendor directly what the consent language said, when it was captured, and whether it named your agency or was a blanket authorization to unnamed third parties; a blanket authorization to “partners” generally doesn’t satisfy the specific-seller requirement in 47 CFR Section 64.1200(f)(9).
3. Capture and store the consent record itself, not just a checkbox result. A timestamped certificate showing exactly what language the consumer agreed to, and when, is the difference between a defensible record and a guess if a complaint arrives years later. The TCPA’s lookback period for a private claim runs years, not weeks, so a consent record that only lives in a vendor’s dashboard you no longer have access to isn’t a record you can actually produce.
4. Identify your business and provide a real opt-out mechanism in every message. Every ringless voicemail should say who’s calling and give a clear, working way to stop future messages, whether that’s a callback number, a reply-STOP text option, or both. An opt-out that goes nowhere is close to the same problem as no opt-out at all.
5. Honor every opt-out immediately, and apply it across channels. A consumer who opts out of ringless voicemail messages has revoked consent for that contact method going forward; treat a revocation as covering related automated contact from the same campaign, not just future ringless voicemail specifically, and stop promptly rather than on the next scheduled list pull.
6. Reserve ringless voicemail for numbers where consent already exists for another reason. The lowest-risk use case is a warm list: existing clients or leads who already gave prior express written consent for automated contact as part of an application, quote request, or account relationship. That’s a narrower and smaller list than a purchased one, but it’s the one the statute was written to allow.
7. If your agency can’t answer exactly what consent record exists for a given list, don’t send to it. That’s not overly cautious; it’s the standard the statute already sets. “We assumed the list was clean” is not a defense once FCC 22-85 has told every business in the country that ringless voicemail needs the same consent a live automated call needs.

Ringless Voicemail vs. a Live Call: The Real Trade-off

Price is the reason ringless voicemail is attractive in the first place, so put the actual numbers side by side instead of an abstract comparison. Drop Cowboy, a named ringless voicemail vendor, publishes its own pricing: the Prime plan runs $125 a month for 62,762 messages a year, with overage priced at 2.1 cents per message and a separate $0.0031 per-message compliance fee, landing around two to three cents per drop at that tier. TheAffordableAI’s Single Account plan, a managed AI caller that places live, disclosed calls, runs $200 a month plus a $500 one-time setup at $0.20 a minute. On a strict per-touch basis, ringless voicemail is roughly ten times cheaper.

The trade-off isn’t really price versus safety, because both channels carry the same underlying consent obligation once a message markets something. The real difference is what happens when consent does exist. A ringless voicemail, even a fully compliant one, is a one-way broadcast: the recipient hears a recording and has to call back to reach anyone, which is exactly the mechanism our comparison of warm transfers against voicemail drops covers from the effectiveness side rather than the legal one. A live call from a managed AI caller can qualify the lead and warm-transfer them to a licensed agent in the same conversation, with no callback step and no second chance for the moment to go cold. Ringless voicemail is cheaper per touch. It’s also structurally worse at the one thing that actually closes a policy, getting a real person on the phone with your agent while they’re still interested.

Where Ringless Voicemail Is the Wrong Fix

Be straight about the limits here, because “just switch to live calling” isn’t automatically the right answer for every agency either. If your real problem is that you don’t have enough dial capacity to reach a large list at all, ringless voicemail on a properly consented warm list is a legitimate, inexpensive way to remind existing leads or clients you exist, and it’s a lot cheaper than trying to live-dial the same volume. If your real problem is that leads bought from a vendor never had documented consent for anything, the fix isn’t a different delivery channel; it’s fixing what you buy, and no amount of careful ringless voicemail practice solves a lead source that was never compliant in the first place.

And if your agency’s actual goal is reaching more prospects who haven’t already consented to anything, ringless voicemail isn’t a safer version of cold outreach. It’s the same TCPA exposure a cold robocall would carry, delivered through a channel that used to be marketed as exempt from that exposure and no longer is.

How TheAffordableAI Handles This

None of this replaces the consent work described above. A managed AI caller still needs a properly consented list to call, the same as a compliant ringless voicemail campaign would. What it changes is the shape of the follow-up: instead of a recording that waits for a callback, a real conversation happens the first time, with the disclosure and the opt-out built into the call itself. There’s a live demo call on the homepage if you want to hear what that actually sounds like before deciding anything. You can also build a compliant ringless voicemail program yourself with a vendor like the one priced above and your own documented consent process; plenty of agencies do exactly that, and it’s worth pricing against a managed live-calling platform before choosing either path.

What You Actually Get

Concretely: clarity on where the legal line actually sits, instead of relying on a vendor’s marketing copy about what counts as a “call.” A documented consent process turns ringless voicemail, or any automated outreach, from an open-ended liability into a bounded, ordinary compliance cost. It means an opt-out gets honored the moment it’s requested instead of on the next list refresh. It means if a complaint or a demand letter does show up, there’s a timestamped record to produce instead of a shrug and a vendor contract that promised compliance without proving it.

What it doesn’t do is make ringless voicemail, or any calling channel, risk-free by default. The consent obligation exists before the message goes out, not after, and no platform, prerecorded or live, removes that requirement or the licensed agent’s responsibility for it.

Ringless voicemail didn’t get more dangerous in 2026. It got clearly labeled in 2022, and a lot of agencies are still running campaigns as if the old “it’s not a call” pitch still holds up. It doesn’t. A documented consent record, a working opt-out, and an honest read of what you’re actually sending cost a fraction of what one demand letter over a purchased list would, and that’s true whether the message reaches a lead through a prerecorded drop or a live disclosed call.