Sent is not delivered
For seven weeks this summer, every ringless voicemail drop we sent showed as sent. Twenty-four drops, to twenty-four different property owners. Not one was ever confirmed delivered, and nothing on any screen said anything was wrong.
This post is how we found it, what was actually broken, and the checks we run now, so you can find out in ten minutes whether your own drops are reaching anyone.
(If you want to see how much of your list you can reach at all, the free Pipeline Grader reads your actual list rather than a questionnaire. We never store it, sell it, or message anyone on it.)
How we found it
We were deciding whether voicemail drops were worth keeping in our follow-up. The obvious first number to look at was how many had been delivered. There was no such number. Every drop had a "sent" status. None had a delivery.
Zero delivered did not look alarming before that day, because nobody had ever looked for it. Zero is what "not measured yet" looks like, too.
What was actually wrong
Our first guess was that delivery confirmations were not switched on, so the drops were landing and we simply never heard back. That guess was wrong.
The real problem was in our own requests. They were malformed in two small ways: the account credentials were sent somewhere the service did not read them, and the phone numbers went out without the country code. The service accepted every request anyway and answered "queued." Queued reads like success. Nothing was ever placed.
The fix took an afternoon. The first drop after it was confirmed delivered about a minute after it went out.
Four checks that prove your drops are landing
1. Find the delivered number, not the sent number. Your provider's report should separate queued, sent, delivered and failed. If you can only find "sent," you do not know whether anything arrived.
2. Make sure failures exist. On a real list, some drops fail: the number is not reachable, or there is no voicemail box to drop into. A report with zero failures over weeks is not a clean list. It is a report that is not hearing back.
3. Drop one to your own phone. Not a test inside the tool. A real drop to a real phone you are holding, through the same path as your campaign. If it does not arrive, nothing else did either.
4. Check it every day, automatically. We now run a morning check that goes red if a drop sits without a delivery confirmation for a day, or if queued drops are not going out at all. It is the check that would have caught our seven weeks on day two.
Why this matters more than voicemail
Every automated channel has the same weak spot. The tool tells you what it did, and what it did is not what happened. Mail gets returned. Texts fail at the carrier. Email lands in spam while the dashboard says delivered.
The question to ask of any follow-up you automate is not "did it send?" It is "how would I know if the other person never got it?" If you cannot answer that, you are running a system on faith.
Common questions
What is a good ringless voicemail delivery rate? We are not going to quote one from a handful of drops. What we can say is that a report with no failures at all, over weeks, is a warning sign, not a good rate.
Why would a voicemail drop show as sent but never deliver? The request can be accepted and queued without ever being placed. Ours were malformed and still accepted. Only a delivery confirmation proves the message reached a voicemail box.
How do I test whether my drops are working? Send one to your own phone through the exact campaign path, then check that your report shows it delivered with a timestamp.
Stop counting what you sent. Count what they received.