By Siddharth GangalA sales voicemail script should reduce the listener’s work. They need to understand who called, why the call relates to them, and what to do next without replaying a miniature pitch. The ten scripts below are adaptable starting points, not tested conversion winners and not legal-safe templates for every campaign.
Replace every bracket with a verified fact. Delete any sentence you cannot support. Read the finished script aloud, because copy that looks compact on a screen can sound crowded, artificial, or ambiguous through a phone speaker.
What a useful sales voicemail must do
Direct answer. A useful sales voicemail does four things: identifies the caller truthfully, names one contextual reason for the call, offers one proportionate next action, and ends cleanly. It does not need a full product explanation, several benefits, manufactured urgency, or a claim that “companies like yours” achieved an unsupported result.
The intended next action changes the script. A cold outbound message may point to a follow-up email where the evidence is easier to inspect. An inbound request should make returning the call simple. A post-demo message should refer to the buyer’s stated decision or open question. Choose the action before writing the words.
Keep software selection separate from message quality. The sales voicemail tools guide covers delivery modes, controls, mailbox tests, and tool economics. This page covers what a rep says and how a manager evaluates it.
Fill this context card before choosing a script
Complete this context card before selecting a script. A blank field is a signal to research, not permission to improvise.
| Field | What to write | Reject when |
|---|---|---|
| Listener | Name, role, company, relationship, and preferred language | The number or owner is uncertain |
| Reason now | A dated event, request, meeting statement, referral, contract point, or open task | It is generic, inferred as fact, stale, or private without permission |
| Relevant problem | One hypothesis or buyer-stated issue, labeled accurately | The script pretends an unverified pain is known |
| Next action | Review an email, answer one question, confirm a time, or return a call | There are several competing asks |
| Proof or resource | A real link, document, example, or result the rep is authorized to share | The proof is vague, confidential, inflated, or unavailable |
| Eligibility | Current policy decision, suppression result, approved technology, time, and jurisdiction | Any required evidence is missing |
For cold accounts, use the cold-call prospect research workflow to verify the role, trigger, and company context. Gangly’s Call Prep Engine can assemble supported account and contact context, but the rep still decides whether a fact is relevant and appropriate to say.
Cold outbound voicemail scripts
Cold scripts should make the reason legible without pretending a relationship exists. The first three templates cover a verified trigger, a problem hypothesis, and a first-touch message paired with email.
1. Verified trigger voicemail
Use when: a current, public business event directly relates to the category you sell.
“Hi [Name], this is [Rep] with [Company]. I’m calling because [verified event and date]. Teams handling [specific resulting job] often have to decide [neutral decision]. I’m sending a short email with [useful resource or question]. If it is relevant, reply there and I’ll keep it specific.”
Adaptation rule: name the event, not a dramatic interpretation. “You posted three implementation roles Tuesday” is verifiable; “your rollout is failing” is not.
2. Problem-hypothesis voicemail
Use when: the account fits the ICP but no fresh trigger exists.
“Hi [Name], [Rep] from [Company]. This is a hypothesis, not something I know about your team: [role or operating model] can make [specific job] difficult when [condition]. I’ll email the two questions we use to check whether that is actually present. If it is not, no need to respond.”
Adaptation rule: keep “hypothesis” language. Do not convert firmographic fit into a claim about the buyer’s pain.
3. Email-paired first-touch voicemail
Use when: the email contains the detail, evidence, and low-friction reply path.
“Hi [Name], this is [Rep] at [Company]. I just sent a note with the subject ‘[exact subject]’ about [one topic]. The useful part is [specific diagram, checklist, or question], not a general brochure. If that job is on your list, the easiest response is to reply to the email.”
Adaptation rule: send the promised note immediately and log both touches once. The phone-plus-email workflow explains how to coordinate the channels without repeating the whole pitch.
Warm and triggered voicemail scripts
Warm messages can use more context because the listener created or accepted a connection. Keep the context exact; “warm” does not permit exaggerating the relationship.
4. Inbound request voicemail
Use when: the person submitted a form, requested a demo, or asked for contact.
“Hi [Name], [Rep] from [Company], returning your request about [exact request]. I have [specific question] so I can route the next conversation correctly. You can reach me at [number, spoken slowly], or reply to the confirmation email with [short answer].”
Adaptation rule: say what they requested and when. Do not call an unrelated content download a demo request.
5. Referral voicemail
Use when: a real person explicitly authorized the introduction.
“Hi [Name], this is [Rep] with [Company]. [Referrer’s full name] suggested I contact you about [specific job] and said I could mention them. I’ll send the context they shared, without anything confidential. If you are the right owner, would you prefer [option A] or [option B]?”
Adaptation rule: confirm permission before naming the referrer. Never imply a referral from a person who merely accepted a connection request.
6. Event or webinar follow-up voicemail
Use when: attendance or participation is known and campaign policy permits follow-up.
“Hi [Name], [Rep] from [Company], following up on [event name] on [date]. Your [question, poll response, or attended session] related to [topic]. I’m emailing [specific resource] and one question about how you handle it today. Reply there if you want the [template, recording section, or example].”
Adaptation rule: distinguish registration from attendance and attendance from active participation. Do not say someone asked a question unless the record proves it.
Active-deal and customer voicemail scripts
Active-deal and customer messages should preserve commitments already made. They are not opportunities to introduce surprise pressure.
7. Post-demo open-question voicemail
Use when: the meeting ended with a specific unresolved question.
“Hi [Name], [Rep] from [Company]. On [meeting date], you asked [accurate question]. I now have [answer, document, or named owner]. I’ll put it in the recap email so your team can review it. If the answer changes the next step we discussed, call me at [number] or reply to the thread.”
Adaptation rule: quote the substance, not invented words. If the answer is incomplete, say what remains unresolved.
8. Stalled-deal reset voicemail
Use when: the buyer missed an agreed next step or stopped responding after an active evaluation.
“Hi [Name], [Rep] from [Company]. We had [agreed next step] set for [date], and I have not been able to confirm whether it still matters. I’m sending a note with three clean options: continue, move the date, or close this out. Any one-line answer is useful.”
Adaptation rule: do not claim an emergency or expiring term unless it is real. For more recovery patterns, see the guide to handling ghosting in active deals.
9. Renewal or expansion voicemail
Use when: an existing customer has a real review date, renewal milestone, or requested expansion discussion.
“Hi [Name], this is [Rep] from [Company]. I’m calling ahead of [contract or review date] to confirm [one decision or dependency]. I’ll email the current facts we have—[usage scope, seats, deliverable, or open item]—and mark anything that needs your correction. Could you reply with the owner for that decision?”
Adaptation rule: use contractual dates and measured account facts. Do not manufacture scarcity or imply service loss outside the agreement.
10. Close-the-loop voicemail
Use when: the approved cadence has ended and the rep will genuinely stop the current outreach.
“Hi [Name], [Rep] from [Company]. I have tried to reach you about [specific topic], and I’m closing this outreach after today. I’ll send one final email with [resource or concise question], then stop. If the timing changes later, you can reply to that thread.”
Adaptation rule: honor the promise. Do not send a “final” message and restart the same cadence two days later. Coordinate timing with the cold-call cadence guide and the team’s suppression policy.
Adapt each script without inventing relevance
Adapt the evidence, not just the name. Read the draft once with every bracket visible, once after substitution, and once as if you were the buyer. Remove any word that creates certainty beyond the source.
- Verify identity. Confirm the phone belongs to the intended person or approved business destination.
- Label inference. Change “you are struggling with” to “teams with this structure sometimes encounter” unless the buyer stated the issue.
- Use one reason. Funding, hiring, a post, and a technology change in one voicemail sound like surveillance, not relevance.
- Choose one action. Do not ask for a callback, an email reply, a calendar booking, and a document review together.
- Remove decorative proof. Use a customer or result only when it is accurate, shareable, comparable, and useful to this decision.
- Read the number aloud. If a callback is desired, slow down and repeat only when policy and local convention support it.
- Fulfill the promise. Queue the exact email, document, answer, or owner before dialing.
A script library is a control surface, not a set of magic words. Store each approved version with scenario, owner, evidence requirements, allowed claims, prohibited claims, delivery modes, jurisdictions, language, version, approval date, and retirement date.
Handle prerecorded voicemail and compliance carefully
A manually left message, agent-triggered recording, answering-machine-detected drop, and ringless voicemail are not automatically the same legal or operational workflow. This article is not legal advice. Have qualified counsel approve the exact campaign, audience, numbers, jurisdictions, technology, content, timing, consent or other basis, suppression, disclosures, opt-out, frequency, retention, and audit trail.
The FTC’s official Telemarketing Sales Rule guidance says most B2B solicitation calls are exempt from that rule, but it describes important exceptions and warns that other rules—including FCC and state requirements—can apply. The FTC’s 2024 amendments also added protections against material misrepresentations in B2B telemarketing. Never treat “B2B” as permission to mislead or ignore an entity-specific stop request.
The FCC’s ringless voicemail ruling states that ringless voicemail to wireless numbers is a call using an artificial or prerecorded voice subject to TCPA requirements. Ringless delivery is not a loophole.
Operationally, maintain approved caller identity, current eligibility evidence, internal suppression, correct local time, truthful claims, versioned recordings, callback routing, complaints, opt-outs, incidents, retention, and an owner empowered to stop the campaign. Fail closed when the suppression or audit system is unavailable.
Test scripts with this 100-point listening rubric
Do not select a script because the team likes how it sounds. Run a blind listening test with people who did not write it. Score each criterion from one to five, multiply by the frozen weight, add the results, and divide by five for a score out of 100.
| Criterion | Weight | Pass evidence |
|---|---|---|
| Truthful identity and context | 20 | Caller, company, relationship, event, and claim are accurate and current. |
| Reason relevance | 20 | The listener can explain why this message is for them after one playback. |
| Clarity and brevity | 15 | One subject, ordinary language, audible pace, no compressed feature list. |
| Next action | 15 | One proportionate action with a clear channel and owner. |
| Delivery quality | 10 | No clipped opening, awkward placeholder, noise, rushed number, or cut-off ending. |
| Sequence continuity | 10 | The promised email, callback, resource, or follow-up exists and is logged. |
| Compliance evidence | 10 | Eligibility, suppression, identity, approval, technology, and audit requirements pass. |
| Total | 100 | Keep false identity, unsupported claim, prohibited recipient, or missing required disclosure as knockout failures. |
After one playback, ask the listener to write the caller, company, reason, useful detail, next action, and callback number if included. Score what they heard, not what the script writer intended. Record on the actual headset, phone system, microphone, compression path, and voicemail workflow used in production.
Build a controlled voicemail experiment
Test one variable at a time on an authorized audience. A useful experiment can compare a trigger-led opening with a hypothesis-led opening while holding list, rep group, timing, delivery mode, next action, and paired email constant.
- Define the eligible population and obtain policy, legal, and operational approval.
- Freeze the two script versions, context requirements, delivery mode, follow-up, sample plan, and stop conditions.
- Train representative reps and run seeded mailboxes first to catch clipping, wrong recordings, bad callbacks, and logging errors.
- Randomly assign eligible records where practical and prevent the same person from receiving both versions.
- Measure verified delivery, comprehension sample, email reply, qualified callback, correct routing, next-action completion, opt-out, complaint, CRM association, correction time, and cost.
- Review results by segment and failure type. Do not declare a universal winner from a small, short, or changing cohort.
The output should be a version decision with evidence: keep, revise, restrict, or retire. Save the recording, context card, approvals, delivery evidence, follow-up artifact, results, exceptions, and decision date. Ten adaptable scripts are useful only when the team knows which one applies, verifies every fact, and stops using versions that fail.