Two features get sold with nearly identical marketing copy: "leave a voicemail without ringing the phone." They sound like the same thing. In the eyes of a plaintiff's attorney, they are not. One is a normal part of an agent making a call. The other has been argued in federal court as an unwanted "call" under the TCPA — and the difference between them is a single technical fact about how the audio reaches the mailbox.
Full disclosure: I work for ReadySMS, and our Power Dialer includes voicemail drop. So I have a stake in explaining this correctly rather than scaring you off outbound voice entirely. The honest version is more useful anyway: voicemail drop done right is fine, ringless voicemail done as a standalone product is where operators keep getting sued.
The one technical difference that decides everything
Here's the distinction courts have circled around, stripped of legalese.
Agent-initiated voicemail drop. A rep (or a dialer working a queue on the rep's behalf) places an actual outbound call to the number. The phone attempts to connect. It goes to voicemail — no answer, busy, whatever. At that point the rep drops a pre-recorded message into the mailbox instead of talking live. There was a real call. The call was made to a number the rep had a reason to dial. The voicemail is just how that call ended.
Server-to-server ringless voicemail (RVM). No call is placed to the handset. A server connects directly to the carrier's voicemail platform through a back-door route and deposits audio into the mailbox. The phone never rings — by design, it can't ring, because no call is being made to it. The mailbox is the target, not the person.
That second method is what plaintiffs' lawyers have gone after. Their argument, which several district courts have found plausible enough to survive a motion to dismiss: depositing audio into someone's voicemail is a call under the TCPA, because the recipient still has to retrieve and listen to it, and it still consumes their device and their voicemail storage. The FCC has never blessed RVM as exempt. A 2017 petition asking it to declare RVM outside the TCPA was withdrawn under public pressure. So the safe legal read today is: RVM lives in a gray zone that a well-funded litigator can drag into an expensive discovery fight.
Why the money is on the other side
TCPA statutory damages run $500 per violation, up to $1,500 for willful violations — per message, not per campaign. Send 5,000 RVMs to a list that includes a few dozen litigators and you're not looking at a nuisance. You're looking at a class-action theory, because RVM is by definition a bulk, automated, no-consent-check activity. It's the kind of fact pattern class-action firms actively shop for.
Agent-initiated calling doesn't remove TCPA risk — nothing does — but it sits in a far more defensible posture. You made a call. You have consent records or an established business relationship. The call happened to end in voicemail. That's ordinary business behavior a jury understands, not a scheme to bypass the phone ringing.
Where ReadySMS's voicemail drop sits
Our Power Dialer's voicemail drop is the agent-initiated kind. A rep is working a manual or queue dial, the call connects to the carrier, the recipient doesn't pick up, and the rep triggers a pre-recorded drop so they don't have to repeat the same 20-second message forty times an hour. The call was placed. The handset was dialed. The drop is a productivity feature layered on top of a real call — not a replacement for making one.
We do not offer standalone server-to-server RVM, and that's deliberate. If the only thing a product does is deposit audio without ever placing a call, you've bought the exact fact pattern the litigators want.
The rest of the Power Dialer feature set is built around real calls:
- Manual + queue dial, call recording, and voicemail drop on unanswered calls
- Transfer / barge / whisper for managers monitoring live reps
- Speed-to-lead auto-dial on new leads (Team plan)
- Minutes billed in 6-second increments, so a 14-second drop bills as 18 seconds, not a full minute
Plans, for reference:
| Plan | Price | Agents | Rate | Notable |
|---|---|---|---|---|
| Free | $0/mo | 1 | $0.06/min | 1 free number, 500 min/mo included |
| Pro | $29/agent/mo | up to 3 | $0.05/min | recording, voicemail drop |
| Team | $69/agent/mo | unlimited | $0.0375/min | speed-to-lead, routing, monitoring |
Full details live on the pricing page.
Configuring outbound so reps stay compliant
Using the compliant flavor of voicemail drop is necessary but not sufficient. The rest of your outbound setup is where reps quietly walk into trouble. Four things to lock down:
1. Scrub the list before you dial. A number can pass the national DNC and still belong to a serial TCPA plaintiff. Those are two different databases. Our standalone TCPA & DNC Litigator Scrub runs at $0.005 per contact and suppresses known litigators and DNC-complainers before the dialer ever queues them. That's a rounding error against $500–$1,500 per violation. If you're not clear on why DNC alone isn't enough, this breakdown covers it.
2. Re-scrub on a cadence. Litigator lists age. A number that was clean in January can join a complainer database by March. Treat scrubbing as a recurring job, not a one-time cleanse — here's how to build the cadence.
3. Respect quiet hours. The federal safe zone is 8am–9pm in the recipient's local time, and several states are stricter. A dialer that fires at 7:40am because your rep is in a different timezone is a documented violation waiting to happen. Our quiet-hours guidance applies to voice just as much as text.
4. Keep consent records. For an agent-initiated call ending in voicemail, your defense is "we had a reason to call this person." That reason needs to exist in writing — opt-in, prior business relationship, inbound request. No paper trail, no defense. The broader auto-dial checklist is in our TCPA outbound dialing guide.
The stronger play: SMS first, then dial
If your goal is "reach someone without demanding they answer live," a compliant SMS often beats any flavor of voicemail. It's opt-in by design, it lands in a channel people actually check, and the compliance rules around it are far more settled than the RVM gray zone.
A worked example. Say you've got 5,000 opted-in leads and you send a 150-character text — one segment. On our Starter tier that's:
5,000 × 1 × ($0.0155 + $0.0045) = $100 for the whole blast.
Then let the dialer chase only the people who reply or click, dropping a voicemail on the ones who don't pick up. You've replaced a legally risky 5,000-mailbox RVM dump with a compliant text plus real calls to warm, self-selected leads. That's cheaper and safer. For agencies splitting outreach across channels, this real-estate breakdown shows the same logic applied to cold vs. warm lists, and the speed-to-lead window post explains why pairing an instant text with a fast dial closes more than either alone.
What none of this makes you
It doesn't make you lawsuit-proof. Compliance is ultimately the sender's responsibility, and a determined plaintiff can file over almost anything. What the right setup does is move you from the fact pattern lawyers love to the fact pattern juries find boring: you had consent, you scrubbed the list, you called during permitted hours, you placed a real call, and the call happened to hit voicemail. Boring is what you want. Boring is defensible.
RVM as a standalone product optimizes for the opposite of boring. It exists to avoid the ring, which is precisely the behavior that reads as evasion.
The practical takeaway
- Voicemail drop after an agent-initiated call = normal outbound behavior, defensible.
- Server-to-server ringless voicemail = no call placed, legally contested, the thing class-action firms target.
- The difference is whether a real call was made to the handset — not whether the phone happened to ring.
- Scrub against litigator and DNC lists, re-scrub on a cadence, enforce quiet hours, keep consent records.
- When "don't make them answer" is the real goal, a compliant SMS usually beats any voicemail tactic on both cost and risk.
If you're running outbound voice and want the drop feature without the RVM exposure, the Power Dialer and the litigator scrub are built to work together. Start on the free tier, wire up a scrub-before-dial step, and you've handled the two things most operators skip.