Handling Failed Calls
Improving your connection rate is crucial for campaign success. This guide covers why calls fail, how to configure retries effectively, and how to analyze your results.
Why calls fail
Understanding failure reasons helps you configure better retries:
Busy
Recipient on another call
Yes, likely
No Answer
Recipient unavailable
Yes, try different time
Rejected
Recipient declined call
Maybe, depends on reason
Voicemail
Machine answered
Depends on goal
Network Error
Technical issue
Yes, usually temporary
Measuring your baseline
Before optimizing, measure your current performance:
curl -X GET /program-executions/EXECUTION_ID \
-H "Authorization: Bearer YOUR_API_KEY"Calculate your connection rate:
Connection Rate = contactsCompleted / totalContacts × 100Typical benchmarks:
First attempt: 20-40% connection rate
With 1 retry: 30-50%
With 2-3 retries: 40-60%
Your results will vary based on audience, timing, and industry.
Choosing a retry strategy
No retries
Use when:
Testing flows
One-shot notifications
You'll handle retries externally
Very time-sensitive messages
Fixed delay
Use when:
Standard campaigns
Predictable retry timing needed
Consistent recipient behavior expected
Recommended settings:
High
15 min
3-4
4-5
Medium
30-60 min
2-3
3-4
Low
120+ min
1-2
2-3
Scheduled
Use when:
Different times of day might work better
Compliance requires specific timing
Multi-day campaigns
Weekend/weekday differences matter
Optimizing retry timing
Finding the best times
Track which retry times produce the best results:
Day of week patterns
Monday: Often busy, moderate answer rates
Tuesday-Thursday: Generally best days
Friday: Lower afternoon rates
Weekend: Varies widely by audience
Spacing your retries
This gives you coverage across different availability patterns.
Combining retries with pause windows
Retries respect pause windows. Configure them together:
This ensures retries don't happen during lunch or after hours.
Analyzing retry results
Call reports
Get detailed attempt information:
Response shows all attempts:
Metrics to track
Per-attempt metrics:
Connection rate per attempt number
Time of day correlation
Day of week correlation
Outcome distribution
Campaign metrics:
Overall connection rate
Average attempts needed
Retry conversion rate (failed → success)
Retry conversion analysis
Calculate how effective your retries are:
If your retry conversion rate is low (<10%), consider:
Different retry timing
Fewer retries (save resources)
Different audience segmentation
Handling persistent failures
Some contacts never connect. After exhausting retries:
Export failed contacts
Analyze patterns
Same phone number format?
Specific regions?
Certain times?
Take action
Remove invalid numbers
Try alternative channels (SMS, email)
Flag for manual follow-up
Identifying patterns
A/B testing retry strategies
Test different strategies to find what works:
Test setup
Split your audience into test groups
Create separate programs with different strategies
Run simultaneously
Compare results
Example comparison
Group A:
Group B:
Group C:
Measuring results
After campaigns complete, compare:
A
45%
1.8
180 calls
B
52%
2.4
240 calls
C
48%
2.1
210 calls
Choose based on your priorities (connection rate vs. efficiency).
Advanced techniques
Progressive retry spacing
Increase delay between attempts:
Useful when you don't want to seem aggressive.
Time-zone aware scheduling
For contacts across time zones:
Segment audience by region
Create separate programs
Schedule based on local time
Outcome-based routing
Use flow conditions to handle voicemail differently:
Best practices summary
Start with moderate retries - 2-3 retries, 30-60 minute delay
Use pause windows - Respect recipient time
Track your metrics - Measure before and after changes
Test different approaches - A/B test strategies
Analyze failures - Understand why contacts don't connect
Iterate - Continuously improve based on data
Common mistakes
Too many retries - Annoying recipients, wasting resources
Retrying too quickly - Situation hasn't changed
Ignoring time zones - Calling at inappropriate hours
Not measuring - Can't improve what you don't track
One strategy for all - Different audiences need different approaches
Next steps
Retry Strategies - Complete configuration reference
Pause Windows - Timing controls
Executions - Monitoring progress
Last updated

