B2B Voicemail Scripts That Get Callbacks

Why most B2B voicemails get deleted in under 6 seconds

Busy B2B buyers wade through a steady drip of sales voicemails every week, and most get deleted within the first few seconds. That's not because prospects hate voicemail — it's because reps treat it as a monologue rather than a trigger. The voicemail that gets returned isn't the one with the slickest pitch; it's the one that creates a specific, time-bound reason for the prospect to pick up the phone.

Practitioner playbooks — including the cadence guidance built into platforms like SalesLoft — converge on the same three structural elements: (1) the rep's name and company appear in the first 4 seconds, (2) the message references something specific to the prospect's company or role, and (3) the message is between 18 and 25 seconds. Long, rambling voicemails almost never get returned; tight, personalized ones inside that window perform dramatically better.

Here's the insight most reps miss: a voicemail isn't a standalone outreach. It's the second touch in a one-two punch with email. A voicemail paired with an email sent within 5 minutes consistently outperforms voicemail alone — by a wide margin. The voicemail's job is to make the email get opened. That changes everything about how you write it.

The 22-second voicemail framework that actually drives callbacks

Across the voicemail teardowns and team playbooks sales practitioners have published, the structure that consistently outperforms looks like this:

Seconds 0–4: Name, company, and a pattern interrupt. Don't start with "Hi, this is..." Every rep does that. Start with the prospect's first name, then yours.

Seconds 5–12: A specific, researched reference. Not "I saw your LinkedIn." Reference a hire, a product launch, a 10-K mention, a podcast appearance, or an industry shift affecting their function.

Seconds 13–18: The reason for the call. One sentence. Tie the reference to a specific, measurable outcome you've delivered for someone in their seat.

Seconds 19–22: The bridge to email. "I just sent you a two-line email with the subject line [X] — easier to reply there than call back." This is the conversion mechanism.

Here are three illustrative scripts built on that framework — every name, company, and number in them is invented to show the structure, so swap in your own researched specifics. Each is engineered to convert into callbacks or email-reply rates:

Script 1: The trigger-event voicemail (SDR → VP Sales)

"Marcus — Jordan from Lattice. Saw you just hired three enterprise AEs out of Gong and Outreach in the last six weeks. When teams scale like that, ramp time usually stretches out fast. We cut ramp time meaningfully for Procore's enterprise org last quarter. Just sent you a two-line email — subject line 'Lattice + your new AE class.' Easier to reply there. Talk soon."

That's about 22 seconds. The trigger (hiring spree) is specific, the pain (ramp time) is named, and the proof point (Procore) is concrete.

Script 2: The competitive displacement voicemail (AE → Director of RevOps)

"Priya — this is Sam at Clari. I noticed your team's been on Salesforce forecasting since 2026 — and we just helped Snowflake's RevOps team kill 14 hours of weekly spreadsheet reconciliation by layering on top of their existing Salesforce instance. Not asking you to rip anything out. Sent you a 90-second Loom showing exactly how — subject line 'Clari + your forecast pipeline.' Worth a look."

Notice what's missing: there's no "I'd love to hop on a call." That phrase adds nothing the prospect wants and instantly marks the message as a generic pitch.

Script 3: The referral-anchored voicemail (AE → CFO)

"David — Alex from Ramp. Your CRO Maria suggested I reach out directly. Her finance team's been using us to close the books 5 days faster, and she thought you'd want to hear how before Q3 planning kicks off. Sent you the same one-pager I sent her — subject 'Per Maria — Ramp for finance ops.' Two-minute read."

The "per [referrer]" subject line construction borrows trust a cold subject line has to earn — referral-anchored subjects reliably outperform cold ones.

What to stop doing immediately

Stop leaving voicemails on the first touch. First-attempt voicemails almost never get returned — you're a stranger asking for a callback. Wait until attempt 3 or 4, after the prospect has seen your name in their inbox at least twice. Familiarity is what makes the voicemail get heard, not the script.

Stop saying your phone number. It's in the missed-call log. Repeating it eats 6 seconds and signals you expect a callback to your number — which they won't do anyway. The email is the conversion path.

Stop using "just" and "quick." "Just wanted to reach out" and "quick question" are filler that signals junior energy. Cut them. Both are the verbal equivalent of shrinking in the doorway, and both invite an early delete.

Stop pitching the product. Pitch the outcome, named customer, or trigger event. Product features in voicemail convert at near-zero. A reference to a customer in their industry does far more work than any feature mention.

Stop calling at the same time every day. Reps default to 9-11am Tuesday-Thursday. So does everyone else. The late-afternoon window — roughly 4:30-5:30pm local time — is chronically underused for both live pickups and voicemail callbacks, because executives are wrapping up and checking voicemails before leaving the office.

The takeaway

• Treat voicemail as a setup for email, not a standalone pitch. Send the email within 5 minutes of the voicemail, reference the subject line in the message, and make the email the easy reply path. This single change does more for combined response rates than any script tweak.
• Drop voicemails on touch 3 or later, never touch 1. Familiarity drives listen-through. Pair the voicemail with a specific trigger event — a hire, a launch, a 10-K mention, or a referrer's name — and keep the entire message between 18 and 25 seconds.
• Audit your team's voicemails this week. Pull 10 recent dialer recordings, time them, and flag any that exceed 25 seconds, repeat the phone number, or use "just/quick." Rewrite three to the framework above and A/B test against your current scripts over the next 30 days.