Voicemails That Get Called Back: A Three-Message Sequence That Isn't Begging

Nobody is going to call you back because you asked nicely

There are two kinds of reps on voicemail. The first kind hangs up the second they hear the beep, because they decided years ago that voicemail is dead. The second kind talks for forty-five seconds, gets nervous around the twelve second mark, and starts explaining the value proposition to an empty room. Both of them are doing the same thing: treating voicemail as a place where nothing happens.

I have left a lot of voicemails. Selling inside AWS and Dell, and then building my own companies, I have had stretches where voicemail was the only surface I could actually control. The prospect decides whether to pick up. The gatekeeper decides whether to transfer. But nobody can stop you from leaving a message, and nobody can make you leave a bad one.

Here is the reframe that changed it for me. A voicemail is not a request for a callback. It is a piece of context that makes the next thing you do land differently. The email that arrives sixty seconds later reads differently because they heard your voice first. The third dial gets answered because your name is already sitting in their head as a real person with a specific question, not an unknown number. Treat voicemail as a standalone ask and it will disappoint you forever. Treat it as the setup, and it starts paying.

What follows is a three-message sequence across a two-week window. It is the closest thing I have to a repeatable sales voicemail script, and the last message in it is the one that does the most work.

Twenty seconds, and I mean twenty

Before any of the wording matters, fix the length. Under twenty seconds. Not "short." Not "concise." Twenty seconds, timed with a stopwatch on your desk while you practice.

The reason is not that people have short attention spans. The reason is what happens to you after twenty seconds. Past that mark you have said everything you planned to say and you are now improvising, and improvised voicemail is where reps start hedging. That is where "I just wanted to reach out" lives. That is where "I know you're incredibly busy" lives. That is where you start explaining what your company does, which is the single fastest way to make a voicemail sound like a recording.

Twenty seconds is enough for four things: who you are, your number, why you are calling this specific person, and what happens next. That is the whole architecture. Anything else you want to include belongs in the email.

A practical test. Write your voicemail out and read it at the pace you would use telling a colleague something mildly urgent. Not the pace you use presenting. If you cannot get through it comfortably in twenty seconds, you have not written a voicemail, you have written a paragraph.

Say the number first, and say it like you are reading it off a card

Most reps put their phone number at the very end, mumble it at double speed, and hang up. I do the opposite twice: number near the front, number again at the end, both times slowed way down.

Front-loading it matters because of how people actually consume voicemail. Half of them are reading a transcript on a phone screen while walking somewhere. Transcripts mangle things, but they mangle the middle worst, and a number that shows up in the first line survives better than one buried in the last. The other half are listening with a thumb hovering over delete. If the number is at the front, they have it before they decide.

Saying it at the end too is not redundancy for its own sake. It is for the person who half-listened, decided at second fifteen that this is worth a callback, and now needs the digits without replaying the whole thing.

The delivery trick: write the number down on paper as you say it out loud. Physically writing forces you to the pace of someone taking dictation, which is exactly the pace the listener needs. I still do this. My handwriting is terrible and my callbacks are better.

And yes, leave your number even though it is sitting in their call log. Voicemails get forwarded. Voicemails get listened to from a desk phone when the call came to a mobile. Voicemails get saved and returned three days later from a different device. The number in the message is the only one you control.

Tell them you are about to email, then email

This is the smallest change with the biggest effect, and almost nobody does it.

End the voicemail by naming the email that is coming and giving them the subject line. "I'm sending you an email in the next minute, subject line is 'site startup.'" Then send it. Immediately. Not in your afternoon batch — inside sixty seconds, while your voice is still in their ear.

Three things happen. First, you have converted an unread cold email into an expected one, and an expected email with a subject line they already heard out loud is a different object in the inbox. Second, you have given them a reply channel that costs them nothing. A lot of people will not call a stranger back but will type four words into an email. Third, and this is the underrated one, you have made yourself a person who does what they said they would do, which is a surprisingly rare signal at the top of a funnel.

The email should be shorter than the voicemail felt. Two or three sentences, the same problem stated the same way, one question. Do not restate the voicemail in full. Do not attach a deck. The email exists to be easy to reply to.

The three messages

Message one: the problem and the reason you are calling this person

Message one has exactly one job: establish that you called for a reason that has to do with them and not with your quota.

The structure is name, your name and number, the problem in one clause, why you thought it might be theirs, and the email handoff. No company boilerplate. No "we help companies like yours." You do not need to say what you sell in message one, and in my experience saying it makes things worse, because the moment you name a category the listener files you and stops listening.

Name the problem the way an operator would say it internally, not the way it appears on your website. "Site startup timelines" instead of "clinical trial acceleration solutions." "Truck rolls that didn't need to happen" instead of "field service optimization." If your problem statement could be read aloud in their Monday meeting without anybody flinching, it is written correctly.

Message two: something only they would recognize

Message two lands about a week later, and it has to prove you are still here for a reason. This is where you use something specific to their business: a job posting, a line from an earnings call, a new market they announced, a conference talk, a regulatory deadline that hits their segment.

The bar is that the detail should be impossible to have said to anybody else. "I saw you're growing" fails. "I saw the two field roles you posted in the Northeast" passes. Specificity is the entire point of message two, because it is the message that separates you from the automated sequence they assume you are running.

Do not gloat about the research. Do not say "I did some digging on your company." Just use the fact and move on, the way you would if you actually knew the business. And then hand off to the email again, with a new subject line.

Message three: the clean exit

This is the one. Message three lands at the end of the two-week window and it does not ask for a meeting. It asks for permission to stop calling.

Of the three, this is the one that has consistently pulled the most replies for me, and I do not think it is a trick. It works because it is the first message in the sequence that puts the prospect in control. Everything up to here has been you wanting something. Now you are offering them the fastest way to make you go away, and it costs them one word.

The mechanics matter. Say it is the last one. Mean it. Give them two or three plausible reasons you have not heard back and make all of them acceptable answers. Ask them to reply with any of them, or with a name if it belongs to someone else. Then actually stop calling, because if you say last message and then call again in a week, you have taught them that nothing you say is load-bearing.

What comes back is not always yes. A lot of it is "not this quarter" or "talk to Priya." Both are worth more than silence, and the referral to Priya is a completely different conversation than a cold one — that is a warm call, and you should handle it like one rather than reopening at the top.

Worked examples in two verticals

Clinical operations at a mid-size sponsor

Message one:

"Dana, it's Tim Yang, 512-555-0180. Calling about the stretch between site selection and first patient in, and specifically how much of that window is document chasing rather than anything clinical. I don't know if that's your problem or your CRO's, which is honestly why I'm calling. I'm sending an email in the next minute, subject line 'first patient in.' Tim Yang, 512-555-0180."

Message two, six days later:

"Dana, Tim Yang, 512-555-0180. Saw the two CRA postings you have open in the Northeast. That usually means either a new protocol or a retention problem, and both of them change the startup math. Same question as last week. Email coming now, subject line 'CRA postings.' Tim Yang, 512-555-0180."

Message three, day thirteen:

"Dana, Tim Yang, 512-555-0180, and this is the last one from me. Three calls over two weeks and no reply usually means it's not a priority, it's not your area, or the timing is bad. Any of those is a fine answer and I'd rather have it than keep guessing. Reply to my email with 'not now' or a name and I'll close the file. Tim Yang, 512-555-0180."

If Dana calls back, do not read her the voicemail again. She has heard it. Open the way you would open a live conversation with a clinical ops leader who has already given you the hardest thing to get, which is her attention — I wrote out how I handle that first thirty seconds in the pharma cold call script, and if the callback came from someone she pointed you to, the warm call script for pharma is the closer version of the same conversation.

Head of network operations at a regional carrier

Message one:

"Marcus, Tim Yang, 512-555-0180. Calling about truck rolls that get dispatched for something that could have been closed out remotely. I don't know whether that's noise at your footprint or a real number, which is why this is a question and not a pitch. Email's coming in the next minute, subject line 'truck rolls.' Tim Yang, 512-555-0180."

Message two:

"Marcus, Tim Yang, 512-555-0180. Heard your CFO talk about the fiber build in the southern markets on the last earnings call. New footprint tends to be where dispatch discipline shows up first. Same question as last week, email coming now, subject line 'southern markets.' Tim Yang, 512-555-0180."

Message three is the same clean exit, word for word, with the details swapped.

Network leaders return calls in a specific mood, which is mild suspicion, and the opening seconds have to survive it. The telecommunications cold call script is how I handle a CTO or head of network ops who did not ask to hear from me, and the same shape holds for an asset management leader at a utility if that is your patch — the energy and utilities version is built the same way.

How the calls sit around the messages

Three voicemails does not mean three dials. It means three dials that end in a message and several that do not.

Here is the shape I use. Day one, dial, leave message one, send the email. Day three, dial at a different time of day, no message. Day six, dial, message two, email. Day nine, dial, no message. Day thirteen, dial, message three, email. Then stop.

The silent dials matter. They vary the time of day so you are not always hitting the same standing meeting, and they give you a shot at a live pickup without burning a message on it. If you leave a voicemail every single time, the third one reads as pestering rather than persistence. The gap is what makes the messages feel deliberate.

One more thing on timing. Send the email while the voicemail is still unheard as often as it lands after. It does not matter which order they consume it in. What matters is that they arrive close enough together to be one event rather than two intrusions.

Say them out loud before you say them to a prospect

Everything above falls apart in delivery. The script can be perfect and you can still sound like you are reading it, and people hear reading instantly. The failure modes are all audible: rushing the number, apologizing at the front, letting your voice go up at the end of the sentence so a statement turns into a question, and running long because you got nervous in the pause.

The fix is reps, and not reps on live prospects. Record yourself leaving message one twenty times, listen back, and delete the words you did not need. Then do message three, which is harder than it looks because the tone has to be genuinely easy rather than passive-aggressive. "I'd rather have a no than keep guessing" sounds fine on paper and sounds like a guilt trip if you land on the wrong word.

That rehearsal loop is exactly what I built DrillCall for — if I were starting this week, I would drill the three messages against a timer until every one of them lands under twenty seconds without me thinking about it, then take them to the phone. The prospects you are calling are worth more than the practice you are getting on them.

Get the length right, put the number where it survives, promise the email and send it, and end the sequence by handing them the exit. That is the whole thing. It is not clever, and it does not beg.