Skip to main content
Different outbound use cases require different campaign structures. The underlying architecture may stay the same, but the timing, retry logic, and workflow design should reflect the goal of the campaign. Below are the most common patterns used with RapidCall.

​
Lead Follow-Up

This pattern is built for speed-to-contact. It is typically used for new leads coming from:
  • Meta ads,
  • website forms,
  • CRM triggers,
  • or other live enquiry sources.
The workflow triggers the first call within minutes of the lead arriving. If the lead does not answer, a second attempt follows a few hours later. If there is still no connection, a fallback touchpoint such as an email or SMS is sent automatically. This pattern works best when the lead is fresh and response speed has a direct impact on conversion.

​
Database Re-Engagement

This pattern is used for large batches of dormant leads, old enquiries, or previous customers. Instead of calling the full list at once, the workflow processes the data in daily batches. Each contact typically receives two attempts across different calling windows, such as morning and afternoon. Results are written back into the reporting system so the team can identify:
  • who is still interested,
  • who needs a follow-up,
  • who should be excluded,
  • and who should be routed to a human.
This pattern is well suited to reactivation campaigns where the goal is to surface live opportunities from older data.

​
Recurring Outreach

This pattern is designed for workflows where new contacts enter the system continuously. Examples include:
  • debt collection,
  • payment reminders,
  • appointment reminders,
  • recurring customer outreach,
  • and operational follow-up flows.
The workflow runs on a fixed schedule, usually two or three times per day, and processes whatever contacts are currently waiting in the queue. Once a contact has been reached or completed the intended outcome, they are excluded from future runs. This creates a steady, automated calling pipeline without needing to launch manual batches each day.

​
A/B Testing

This pattern is used to compare different agent versions in a structured way. Two versions of the same agent are created with one meaningful difference, such as:
  • prompt wording,
  • voice choice,
  • model selection,
  • or call flow structure.
The workflow splits the contact list into separate groups and routes each group to one version of the agent. Outcomes are then logged separately so you can compare performance across the two versions. Useful comparison points include:
  • conversion rate,
  • answer rate,
  • sentiment,
  • average duration,
  • and transfer rate.
This is the most reliable way to improve agents over time. Instead of guessing which version is better, you test both under similar conditions and compare the results directly.

​
Best practice

Choose the campaign pattern that matches the operational reality of your use case. Use:
  • Lead Follow-Up for fresh inbound leads,
  • Database Re-Engagement for older lists,
  • Recurring Outreach for ongoing operational queues,
  • and A/B Testing when you want to improve performance systematically.
The structure of the campaign should always support the goal of the workflow, not the other way around.