The Voicemail Nobody Deletes: A 20-Second Script and the Text That Follows It
Most reps either skip voicemail or leave a 45-second infomercial. Here is the 20-second structure, three worked examples, and the follow-up message that goes with it.
Two ways to waste a dial
There are two things most reps do with voicemail, and both of them are wrong.
The first is skipping it entirely. The reasoning goes: nobody listens to voicemail, so why bother. The rep hears the beep, hangs up, marks the activity, moves on. Feels efficient. It isn't.
The second is worse. The rep leaves forty-five seconds of company positioning, a value proposition with three clauses in it, a rushed phone number at the end, and an apology somewhere in the middle. Nobody finishes that message. But here is the thing people miss: they don't have to finish it for it to hurt you.
Run the maths on a single dial. You researched the account. You found the direct line. You waited through four rings. All of that cost is sunk by the time the beep happens. Leaving a message costs you twenty more seconds on a dial you have already paid for. So the question is never "is voicemail worth it." The question is whether the twenty seconds you spend earns a callback or poisons the next attempt.
I can't tell you what share of voicemails get returned. Nobody's attribution on that is clean, and anyone quoting you a precise figure is guessing. What I can tell you is what I have watched happen on hundreds of call reviews: the reps who leave short, specific, oddly calm voicemails get answered on the second dial far more often than the reps who leave nothing. Not because the prospect called back. Because the prospect recognised the name.
What a bad voicemail actually costs you
Voicemail is not neutral. This is the part reps don't model.
When you leave a rambling message, you have done three things to yourself. You have taught the prospect that your number belongs to a salesperson. You have taught them what your calls sound like. And you have used up the one novelty you get with a stranger — the first time your name lands in front of them.
Caller ID makes this concrete. Most desk phones and every mobile show the number, and plenty of prospects screen against a list in their head. If your first message was a pitch, the second dial is being screened by someone who already knows the answer. If your first message was twenty seconds of specifics about their plant, their claims backlog, their ramping headcount, then the second dial is being screened by someone who is mildly curious.
So voicemail is the first impression that happens without you in the room. Treat it that way and the structure writes itself.
The twenty-second structure
Five parts. In order. Nothing else in the message.
- Your name and company, once, at normal speed.
- The reason you called this specific person.
- One number, and it should be theirs, not yours.
- One question, left hanging.
- Your callback number, said twice, slowly.
Twenty seconds is not arbitrary. It is roughly the amount of time a person will hold the phone to their ear before their thumb starts moving toward delete. You are not trying to persuade anyone inside twenty seconds. You are trying to be identifiable and specific enough that deleting it feels slightly premature.
Your name and company, once
"Hi, it's Timothy from DrillCall." That's it. No "my name is," no "I'm a senior account executive with," no "I hope I'm not catching you at a bad time" — you are talking to a machine, you cannot catch a machine at a bad time.
Say it at normal conversational speed. The instinct on voicemail is to speak faster because you feel the clock. Fight it. A rep who sounds rushed sounds like a rep. A rep who sounds unhurried sounds like a peer who has other things going on today.
The reason you called this specific person
This is the whole message, really. Everything else is scaffolding.
The test is simple: could this sentence be left for anyone else with the same job title? If yes, rewrite it. "I'm calling because you run operations for a mid-market manufacturer" fails the test. "I'm calling because you're bringing the second line at the Rockford site up in Q1" passes it.
Where does that come from? Job postings, the plant tour video on their website, a LinkedIn post the VP made about a reorg, an earnings call transcript, the local business journal. It takes three or four minutes per account and it is the only part of the voicemail that does any work. If you have not found something specific, skip the message and dial again tomorrow. A generic voicemail is worse than silence.
One number, and it should be theirs
Here is where almost every rep gets themselves into trouble, and it's the same trouble that gets marketing copy thrown out. They reach for a benchmark. "Companies like yours typically see a thirty per cent reduction in" — stop. If you cannot name the source of a figure in the same breath, do not say it. Executives who have been sold to for twenty years hear an unsourced percentage as noise at best, and as a tell at worst.
Use a number from their world instead. The number of open adjuster roles on their careers page. The three plants listed on their site. The eleven SDRs you counted on LinkedIn against the four AEs. The date of the acquisition. These are verifiable, they are specific to the account, and crucially, they prove you did work before you dialled. That proof is what a benchmark statistic was pretending to do anyway.
If you genuinely have a customer result you are allowed to quote, name the customer and the situation. "A three-plant fabricator in Ohio" beats "our customers see." Vaguer and true always beats precise and invented.
One question, left hanging
One. Not a list of pain points. A single question that the prospect can answer in their head while they're listening, and that they cannot answer comfortably.
"I wanted to ask how you're covering the second shift while you're still four techs short." "I wanted to ask what happens to the FNOL queue when volume spikes in storm season." "I wanted to ask whether the new AEs are ramping on the same timeline the first cohort did."
Notice these are not yes/no. Notice none of them mention a product. The question is doing one job: making the prospect think about something slightly uncomfortable while your name is still in their ear.
The callback number, twice, slowly
This is the most commonly botched twelve digits in sales. The rep says the number once, at the speed of someone reading their own phone number, which is the fastest anyone ever says anything.
Say it twice. Say it slowly enough to write down. Pause between the groups. And say it at the end of the message, not the start, because the prospect who is going to write it down is the one who already decided to, and they decided during the question.
One more thing on the ending: do not say "I'll try you again." It sounds like a threat and it removes the reason to call you back. Do not say "if now's not a good time." Do not apologise. End on the number and hang up.
Three that work
The plant manager
"Hi, it's Timothy from DrillCall. I'm calling because I saw you've got four maintenance tech roles open at the Rockford site and one of them's been posted since August. I wanted to ask what you're doing about PM coverage on nights while those seats are empty, because the two other plant managers I spoke to this month are both running the same gap and handling it completely differently. My number is 555 0142 — that's 555 0142. Thanks."
Twenty seconds, out loud, timed. The specific detail is the August posting. The number is theirs — four roles, one since August. The question is operational, not commercial. There is no mention of what DrillCall does, which is fine, because a plant manager does not return a call to learn about a product. He returns a call because someone noticed the thing that has been annoying him since August.
If he does pick up on the second dial, you had better be ready for the conversation that follows, and that is a different piece of preparation entirely — I have written up how that call goes in the manufacturing cold call script for earning twenty minutes with a plant manager.
The claims leader
"Hi, it's Timothy from DrillCall. I'm calling because you posted about the Southeast expansion in October and I counted seven adjuster roles across three states on your careers page. I wanted to ask how you're holding cycle time while you're onboarding that many people at once, because that's usually where it slips. My number is 555 0142 — again, 555 0142. Thanks."
The post and the seven roles are both verifiable in about two minutes. "That's usually where it slips" is a judgement, not a statistic, and it is the kind of judgement a claims VP will either agree with or want to argue about — both of which are callbacks. The tone matters more in insurance than almost anywhere; the insurance cold call script for keeping a claims leader on the phone goes deeper on why the operational framing outperforms the risk framing.
The VP of Sales
"Hi, it's Timothy from DrillCall. I'm calling because I counted nine SDRs and three AEs on your team on LinkedIn, and six of the SDRs started in the last quarter. I wanted to ask what the ramp looks like for that cohort compared to the group before it. My number is 555 0142 — 555 0142. Thanks."
A VP of Sales gets more voicemails than anyone on this list and deletes almost all of them within four seconds. The thing that stops the thumb is hearing a number about her own org that she has not said out loud yet. She is not returning the call to hear a pitch. She is returning it because she wants to know how you counted and what you concluded. Have an answer ready. The SaaS cold call script for CROs, VPs of Sales and RevOps leaders covers the first sixty seconds of that conversation, which is a harder sixty seconds than the voicemail was.
The message that follows, and the one rule about it
Send something within two minutes of hanging up. Not the next morning. Two minutes, while the voicemail notification is still on their lock screen.
The rule: reference the voicemail, never repeat it. If your email is a transcript of what you just said, you have wasted both. The email's job is to be the written half of a single message, and to be shorter than the voicemail was.
Email, for the plant manager:
Subject: nights coverage, Rockford
Left you a voicemail about the four open tech roles.
The short version of what I wanted to ask: who's covering PM on nights right now, and is that a supervisor doing double duty?
If it's the supervisor, I've got two examples worth ten minutes. If it isn't, ignore this.
Timothy
That's it. Under sixty words. The "if it isn't, ignore this" line does more work than any CTA I have ever written — it gives the prospect a clean exit, which is exactly why they don't take it.
If you have a mobile number and you are on the right side of the rules in your market, a text is stronger than the email, and it should be shorter still: "Timothy from DrillCall — left you a voicemail about the four open tech roles at Rockford. Question was who's covering PM on nights. Happy to be told it's handled." Get advice on consent and local regulations before you make texting part of a sequence; I am not going to pretend that's uniform across markets.
What neither message should contain: a calendar link on the first touch, a deck, a case study PDF, or the phrase "just following up." You are following up on a voicemail you left ninety seconds ago. Everyone can see that.
When to stop leaving them
Attempt one: leave a voicemail.
Attempt two: leave a voicemail, different angle, different question. Do not re-run the first message with a "me again" on the front. If the first one was about the open roles, the second one is about the shift pattern or the acquisition or the new line. You are demonstrating that you have kept paying attention, which is rarer than persistence.
Attempt three onward: stop. Dial silently. Vary the time of day — early, late, the top of the hour when meetings break. The reason to stop is not politeness. It's that a third and fourth message tell the prospect you are working a sequence rather than working an account, and the moment they conclude that, every future dial is screened.
The two voicemails you already left keep working while you dial silently. That is the point.
Voicemail as permission, not a message in a bottle
Here is the shift that changed how I think about this. Stop treating voicemail as a callback mechanism. Treat it as a permission asset for the next live conversation.
When they do pick up on attempt three, you do not open cold. You open like this:
"Hi, it's Timothy from DrillCall — I left you a voicemail last Tuesday about the four open tech roles at Rockford. Is now a bad time?"
That sentence is doing something a genuinely cold opener cannot. It establishes that you have been polite and patient. It reminds them of a specific detail they may half-remember. And it makes the call feel like a continuation rather than an intrusion, which changes what they permit you in the first fifteen seconds.
I sold inside AWS and Dell before I built companies of my own, and the reps who consistently got past the opener were almost never the ones with the cleverest hook. They were the ones whose name already meant something small and non-annoying by the time the prospect picked up. Two good voicemails do that for you.
What I'd do this week
Record yourself leaving all three of the messages above, substituting your own accounts. Time them. Almost every rep I have listened to comes in over thirty seconds on the first take and hates the sound of their own callback number. Cut until you hit twenty, then say the number slower than feels natural.
That is the part that needs reps rather than reading, and it is the reason I built DrillCall — so you can run the same twenty seconds twenty times against a plant manager, a claims leader and a VP of Sales before you spend a real dial on any of them. If you'd rather do it with a colleague and a stopwatch, do it that way. Just do it before Monday, because the voicemail you leave badly this week is the dial you lose next month.