voicemail-drop-optimization
Installation
SKILL.md
Voicemail Drop Optimization
You are an expert in voicemail drop strategy for sales automation. Your goal is to help developers create systems that leave effective, well-timed voicemails that drive callbacks.
Voicemail Drop Fundamentals
Types of Voicemail Drops
- Ringless Voicemail (RVM): Delivers directly to voicemail without ringing
- Traditional Voicemail: Left after unanswered call
- Hybrid: Attempt call, drop VM if no answer
Compliance Requirements
- TCPA: Requires consent for autodialed calls/messages
- State laws: Some states have additional restrictions
- Do Not Call: Must honor DNC lists
- Time restrictions: Generally 8am-9pm local time
Optimal Voicemail Timing
Best Times to Drop
Day Analysis:
- Tuesday-Thursday: Highest callback rates
- Monday: People are catching up
- Friday: People are wrapping up
Time Analysis:
- 7:30-8:30 AM: Before work rush
- 11:30 AM-12:30 PM: Pre-lunch check
- 4:30-5:30 PM: End of day review
- Avoid: 9-11 AM (meeting heavy)
Trigger-Based Timing
Drop voicemail when:
- Email opened but not replied (2-4 hours later)
- Proposal viewed (within 1 hour)
- Website visit detected (same day)
- After missed call from prospect
Sequence Timing
VM Drop 1: Day 1 (initial outreach)
VM Drop 2: Day 4 (follow-up)
VM Drop 3: Day 8 (persistence)
VM Drop 4: Day 15 (final attempt)
Maximum: 4 voicemails per prospect per month
Crafting Effective Voicemails
The 20-Second Rule
Ideal length: 18-22 seconds
Maximum: 30 seconds
Over 30 seconds: Delete rate increases 50%
Structure Template
[3 sec] Hook/Relevance
[5 sec] Who you are + why calling
[7 sec] Value/reason to call back
[5 sec] Clear CTA + callback number
Total: ~20 seconds
Example Scripts
Initial Outreach
"Hi [Name], this is [Rep] with [Company].
I noticed [Company] is [relevant observation].
I have an idea that helped [similar company] [achieve result].
Worth a quick chat—call me at [number]. Again, [number]."
Follow-Up
"Hi [Name], [Rep] again from [Company].
Following up on my email about [topic].
I'll be available [time window] if you want to connect.
[Number]—looking forward to hearing from you."
Post-Engagement
"Hi [Name], [Rep] here.
I saw you checked out [content/page] on our site.
Happy to answer any questions—I'm at [number].
Talk soon."
Final Attempt
"Hi [Name], [Rep] from [Company].
I've reached out a few times about [problem you solve].
If the timing isn't right, no problem—but if it is,
my number is [number]. Hope to connect either way."
Personalization at Scale
Dynamic Elements
Variables to personalize:
- [Prospect name]
- [Company name]
- [Industry]
- [Trigger event]
- [Relevant metric/result]
- [Time-specific reference]
Recording Strategy
Option A: Fully pre-recorded (most scalable)
- Record 5-10 variations
- Rotate to avoid repetition
- Less personal but consistent
Option B: Hybrid (personalized intro)
- Pre-record main message
- Dynamically add name/company
- Good balance of scale + personal
Option C: AI-generated (most personal)
- Generate unique for each prospect
- Highest personalization
- Quality control needed
Voice Quality Standards
Audio requirements:
- Clear, professional recording
- Minimal background noise
- Consistent volume levels
- Natural speech pattern (not read)
- Slight smile in voice
Avoid:
- Overly salesy tone
- Rushed delivery
- Monotone reading
- Echo or phone quality
Callback Optimization
Make Number Easy
Always:
- State number clearly
- Repeat number at end
- Speak slowly for digits
- Consider callback button (RVM)
"My number is 5-5-5, 1-2-3, 4-5-6-7.
Again, that's 555-123-4567."
Callback Tracking
Track:
- Which voicemail version
- What day/time dropped
- Callback rate by version
- Time to callback
- Conversion from callback
Optimize based on data.
Handling Callbacks
Prepare for callback:
- Have context ready
- Know what VM they received
- Reference the voicemail
- Don't make them repeat info
"Thanks for calling back! I mentioned [topic] in my message—
did that resonate with what you're working on?"
A/B Testing Voicemails
Elements to Test
Test one element at a time:
Subject of call:
A: "Calling about your [problem]"
B: "Calling about [result] for [company type]"
Value proposition:
A: "Save 20% on [process]"
B: "Help your team [achieve outcome]"
Call to action:
A: "Call me back at [number]"
B: "I'll try you again tomorrow"
Tone:
A: Professional/formal
B: Casual/friendly
Measuring Success
Primary metrics:
- Callback rate
- Time to callback
- Callback quality (leads to conversation)
Secondary metrics:
- Listen-through rate (if trackable)
- Delete rate
- Complaint rate
Integration with Other Channels
Multi-Touch Sequence
Day 1: Email (morning)
Day 1: Voicemail (afternoon) ← Reference email
Day 3: Email follow-up
Day 4: Voicemail (different message)
Day 7: LinkedIn touch
Day 8: Voicemail (final)
Cross-Channel Messaging
Voicemail after email:
"Hi [Name], I sent you an email earlier about [topic].
Wanted to follow up personally because [reason].
Give me a call at [number]—or reply to that email, either works."
Voicemail after no-show:
"Hi [Name], I was on our call at [time] but didn't see you join.
No worries if something came up—let me know a better time.
[Number]."
Compliance & Best Practices
Opt-Out Handling
Always:
- Honor opt-out requests immediately
- Remove from voicemail lists
- Document the opt-out
- Don't call back
Track opt-out sources:
- "Stop calling" in callback
- Email unsubscribe
- Website form
- Verbal request
Frequency Limits
Maximum contact attempts:
- 1 voicemail per week per prospect
- 4 voicemails total in a sequence
- 30+ days before re-engaging
- Respect "don't call" forever
Quality Assurance
Review voicemails for:
- Accurate information
- Appropriate claims
- Professional tone
- Compliance language
- Clear callback number
Weekly Installs
6
Repository
louisblythe/salesskillsGitHub Stars
11
First Seen
Mar 18, 2026
Security Audits