Setup Jobs

Distributed Jobs

A distributed job splits a broadcast into smaller batches sent at timed intervals — useful when you expect recipients to respond and want to manage replies at a steady rate.

When to Use It

If all recipients receive a message simultaneously and a significant number respond, your team can be overwhelmed with replies arriving at once. A distributed send staggers delivery so responses arrive in manageable waves.

Typical use cases include:

  • SMS or voice campaigns where recipients are expected to call back or reply
  • Surveys or polls with a high expected response rate
  • Appointment reminders where staff need time to handle confirmations between batches
Primarily for SMS & TTS Distributed sending is available on fax, SMS and text-to-speech broadcasts, but is most useful for SMS and TTS jobs where two-way responses are expected. For fax-only campaigns it is rarely needed.

How to Set It Up

The Send as Distributed Job option appears on the final review screen before you submit a broadcast. Check the box to enable it, then fill in the two fields:

FieldDescription
No. of jobs to split into How many equal batches your recipient list is divided into. WEL will split the list as evenly as possible.
Minutes between jobs How long WEL waits after one batch completes before starting the next.

Example

You have 500 recipients and set 5 jobs with 60 minutes between jobs:

  • Batch 1 — 100 recipients sent immediately
  • Batch 2 — 100 recipients sent 60 minutes later
  • Batch 3 — 100 recipients sent 120 minutes later
  • … and so on until all 500 are reached

Each batch appears as a separate job in your Broadcast History with its own job number and success report.

Things to Keep in Mind

  • Each batch job is independent — if a batch is cancelled, subsequent batches are not automatically stopped. Cancel each job separately from Broadcast History if needed.
  • You can combine a distributed send with a scheduled start time — set the schedule for when the first batch should go out.