Bulk and scheduled sends

How a batch is shaped

Two decisions shape a bulk send: which contacts are in it, and which channel carries it.

• Adding contacts creates a batch, identified by a batch number. The batch is the unit you review and resend.
• A batch sends over one channel that you pick — the whole batch goes through that single provider, with its sender numbers still rotating by weight inside it.
• Pacing is applied per batch, so a large send does not exhaust the provider limits that your live traffic also depends on.

Run a bulk send

1. Prepare the recipients

   Use a list, or import contacts by CSV. Numbers must be E.164.

2. Compose the message

   Pick the batch and the channel it should send through, then write the content.

3. Choose immediate or scheduled

   Immediate sends start as soon as you launch; a scheduled send waits for the time you set.

4. Watch the batch

   The batch view reports sent, failed, skipped and suppressed counts as it progresses.

When a batch fails part-way

Resending a failed batch retries only the recipients that were never attempted. Contacts that were already sent, or that are suppressed, are not sent to again — so a reset does not turn into a duplicate blast.

Suppression counts as skipped, not failed

Recipients on the suppression list are counted separately from failures. A batch can therefore report a large skipped number and still be a healthy run — see "Opt-out and suppression" for why that is the correct outcome.

Keep reading