Broadcasts & bulk actions

There’s no separate “Broadcasts” screen. A broadcast is just one kind of bulk action — the Send message kind — and every bulk action follows the same three beats:

1. 1Select who it applies to — from your Contacts or Leads table, by ticking rows or filtering and selecting all pages.
2. 2Choose one operation from the toolbar that appears, and configure it (a message, a workflow, a field, a tag).
3. 3Exabloom runs it in batches you pace, while you watch the live counts from the Bulk Actions page.

Tick contacts in the table and a violet selection toolbar slides up from the bottom. It shows your count and every action you’re allowed to run. Buttons you don’t have permission for are greyed out with a tooltip — bulk actions are permission-gated per role.

To act on more than the page you’re looking at, filter the table first, then use the select-all control. You’ll be asked whether to select this page only or all pages that match the filter:

One selection, one operation. From the toolbar you can run any of these (the code names in grey are what you’ll see in a run’s Type column):

The rest of this guide follows the Send message broadcast in full — it’s the richest of the six. Most of what you learn (pacing, days/hours window, monitoring, reports) applies equally to Add to workflow, which shares the same scheduling panel.

Choose Send message and you first pick the channel to send from — one of your connected numbers. (No channel connected? You’ll be sent to Settings → Social Channels to add one first.)

What comes next depends on the channel. Official WhatsApp numbers walk you through three tabs — Select template → Configure → Schedule — because WhatsApp requires pre-approved templates for outbound campaigns. Every other channel (Telegram, non-official WhatsApp) skips straight to a free-text composer with attachments, then the same schedule panel.

On the Schedule step you set the pacing and timing. The top of the panel confirms how many contacts will actually receive it — contacts with no valid phone number are dropped automatically and called out here.

A broadcast doesn’t fire all at once. You control the rhythm with two fields, and a delivery window:

• Batch quantity — how many messages go out per batch. Defaults to 1 and is capped at 5 (the form rejects anything higher).
• Time interval per batch — the gap between batches, in minutes or hours. Defaults to 5 minutes.
• Days & hours window — which weekdays it may send, and between which times. Defaults to all 7 days, 08:00–20:00. Outside the window, the run waits.

On an Official WhatsApp Cloud API number you’ll also see a high throughput toggle. Switch it on to remove the throttle entirely and send as fast as the API allows.

You can also exclude people from past campaigns: open “Don’t send to contacts from past campaigns”, pick earlier bulk actions, and filter by their outcome (e.g. exclude anyone with Success — they already got it). It’s the clean way to avoid double-messaging across a sequence of broadcasts.

Once created, a run moves through a fixed set of states. The UI collapses the raw internal statuses into three friendly labels, so “Creating” covers both the queueing and the contact-resolving phases:

Creating is where the filter is turned into a concrete recipient list (this is also when invalid numbers and your exclusions are dropped). Processing is the actual batched send. A run you intervene on shows Paused or Cancelled instead, and a finished one shows Completed.

The Bulk Actions page is a paged table (10 per page) of every run, showing its name, type, status, created date, who started it, and completion time. The kebab menu on each row is where the controls live:

The menu adapts to the run:

• Pause / Resume / Cancel — pause or cancel only while a run is still active; resume only a paused one. The menu hides the ones that don’t apply.
• Show stats — a quick Total / Success / Errors breakdown with percentages.
• View contacts — jump back to the Contacts table filtered to this run, optionally narrowed to success, error, or pending contacts.
• Download report — a CSV of results, available for Send message runs (once a report URL exists) and finished Import runs.
• Rename and View details (the raw run payload) — always available.

Four common runs, each built from the pieces above. Adapt, don’t copy exactly.

• “All pages” means the filter, not the screen. Selecting all pages acts on everyone matching your filter — confirm the filter is right before you run anything destructive.
• Your recipient count can shrink. Invalid phone numbers and your exclusions are dropped during the “Creating” phase, so the final count is often lower than what you selected.
• Batch quantity tops out at 5. For real speed on Official WhatsApp Cloud API, use the high throughput toggle instead.
• Official WhatsApp needs an approved template. You can’t broadcast free text from an Official number — only templates that have cleared WhatsApp’s review.
• The send window pauses, it doesn’t cancel. Outside your days/hours window the run simply waits; it resumes when the window reopens.
• Pace cold lists, or risk your number. Exabloom’s throttle doesn’t protect you from WhatsApp’s spam controls — broadcast to people who expect you, and ramp up gradually.
• Reports only for some run types. A downloadable CSV exists for Send message and Import runs; for the others, use Show stats and View contacts.