Skip to main content
Most outbound calls do not connect on the first attempt. Voicemail, no answer, and busy signals are normal outcomes in outbound operations. A strong campaign does not treat those as failures. It plans for them with a clear retry structure.

​
How many attempts?

For most campaigns, two to three attempts per contact is the standard. More than three attempts usually adds little value and increases the risk of irritating the contact. The right number depends on the use case:
  • debt collection and payment reminders can often justify three attempts within a day,
  • lead qualification and appointment setting usually perform best with two attempts spread across different times.

​
How to space attempts

The most effective retry pattern changes the time of day between attempts. For example:
  • if the first call was in the morning, place the second in the afternoon,
  • if both attempts fail, place the third on the next business day at a different time.
This increases the chance of reaching the contact when they are actually available. Repeating attempts too close together usually produces more voicemails, fewer answers, and a worse experience.

​
Voicemail strategy

Decide in advance whether the agent should leave a voicemail, and if so, on which attempt. A common structure is:
  • leave a voicemail on the first unanswered attempt,
  • do not leave a voicemail on later attempts.
This gives the contact a clear first touchpoint without repeatedly filling their voicemail inbox. It also helps protect number reputation and keeps follow-up cleaner. If your workflow supports it, use a variable such as voicemailDropped to track whether voicemail has already been left and control this behaviour across attempts.

​
Exclusion logic

Once a contact has been reached, they should usually be removed from the retry queue. That includes both positive and negative outcomes. If someone has already booked, declined, requested removal, or completed the intended conversation, they should not be called again through the standard retry flow. Your workflow should check the result after each attempt and exclude connected contacts from further retries where appropriate.

​
Callback handling

If a contact asks to be called back at a specific time, that request should override the standard retry cadence. In that case, the agent should capture the preferred callback time, and the workflow should schedule the next attempt around that request rather than using the normal retry logic. This keeps the experience more natural and avoids calling the contact at the wrong time after they have already given a preference.

​
Best practice

A good retry system should:
  • limit total attempts,
  • vary the timing of each attempt,
  • avoid repeated voicemail drops,
  • stop retrying once the contact has been reached,
  • and respect requested callback times when provided.
That is what turns repeat calling into a controlled campaign rather than noise.