Broadcasts
Send WhatsApp, SMS and email to a list — scheduled or now — and see what was sent and what failed.
A broadcast sends one message to many people: renewal reminders for the month, a festival greeting, a newsletter. Broadcasts live under Inbox → Broadcasts. Replies come back into the inbox like any other conversation.
Anatomy of a broadcast#
| Part | What you choose |
|---|---|
| Channel | WhatsApp, SMS or email |
| Audience | A list — dynamic or frozen |
| Message | A template, with merge fields filled per recipient |
| Timing | Send now, or schedule a date and time |
The broadcasts table shows each one's channel, audience, status and delivery, for example:
| Broadcast | Channel | Status | Sent / failed |
|---|---|---|---|
| Renewal reminder — September | Sent | 27 sent · 3 failed | |
| Dasara greetings | Scheduled | — | |
| Premium due | SMS | Draft | — |
Choosing the audience#
- Use a dynamic list for recurring sends. Motor renewals due always holds the customers whose renewals are coming up, so the next month's broadcast needs no rebuilding.
- Use a frozen list for one-off sends where you want a permanent record of who was targeted.
WhatsApp broadcasts#
WhatsApp broadcasts must use a template Meta has approved (see Templates). Merge fields — {{contact.firstName}}, {{policy.expiry_date}} — are resolved per recipient, so each person gets their own details. When a customer replies, the conversation lands in the inbox and follows your normal assignment and SLA rules.
After it's sent#
Check the sent and failed counts. Failures usually mean an invalid number or address, or a customer who has opted out. Fix the underlying record and it'll be included next time a dynamic list runs.
Through the API#
The klerc API doesn't currently include broadcast endpoints. You can prepare audiences through the lists API and schedule the broadcast in the console.