Skip to main content
A broadcast sends one approved WhatsApp template to a list of recipients, and tracks delivery, reads, and replies for each one. Broadcasts are template-only. Meta requires an approved template to open a conversation, so free-form text cannot be broadcast.

​
Lifecycle

Two paths through it:
  • draft → sending → completed, failed, or stopped
  • draft → scheduled → sending → …
The transitions are enforced:
  • Scheduling requires a scheduled_at timestamp
  • Recipients can only be added or cleared while draft or scheduled
  • Cancelling only works while scheduled, and returns the broadcast to draft
  • Stopping only works while sending. Pending recipients stay pending and are not sent

​
Add recipients

Two ways, and they produce the same result:

CSV upload

Upload a spreadsheet in the dashboard. No code.

Broadcasts API

Create and send programmatically.
The API accepts up to 1000 recipients per request. Send more by repeating the call.

​
Metrics

Every broadcast exposes running counts: Per-recipient status, timestamps, and error messages are available through List individual recipients.

​
Delivery pacing

Kapso batches sends automatically and paces them to stay within WhatsApp’s throughput limits. Batch size scales with the size of the list, so you do not need to throttle your own requests or split large lists.