Documentation
Send to many recipients at once with dynamic audiences, scheduling, recurring series, and paced delivery.
Broadcasts let you send one message to many recipients at once through a connected WhatsApp session — or through a bot, which spreads delivery across the bot's sessions. Use them for announcements, promotions, and updates. Audiences are dynamic: rather than freezing a recipient list the moment you create the broadcast, Neuron can resolve it live at send time, so contacts added, removed, or opted out before it goes out are always reflected.
Create a broadcast in a few steps:
Choose a sender
Send from a connected WhatsApp session, or from a bot. If you skip session selection, Neuron auto-resolves your organization's default session (or the first connected one). When you send from a bot, delivery is load-balanced across the bot's sessions with sticky routing, falling back to a fixed session if needed.
Compose your message
Write the message text and, optionally, attach media — an image, audio, video, or a document.
Pick your audience
Choose All contacts, Lists & groups, or a hand-picked Selected set. Live audiences (all / lists / groups) are resolved at send time; hand-picked recipients are fixed when you create the broadcast.
Pace and schedule (optional)
Send now, schedule for later, or set up a recurring series. Optionally deliver in batches with a cooldown so a large send is spread out instead of firing all at once.
Review and send
Review the audience estimate and message preview, then send. Messages are queued and delivered in the background — you can leave the page.
A broadcast is defined by its audience sources, not a frozen list. When you pick a live audience, Neuron stores the sources and resolves them to concrete recipients only when the broadcast actually sends — so anyone added to a list or group in the meantime is included, and anyone opted out is dropped. There are three ways to choose recipients:
All contacts
Every contact in your organization at send time.
Lists & groups
One or more contact lists and/or WhatsApp groups on the sending session. Members are pulled live when the broadcast sends. The count shown while composing is an upper-bound estimate before duplicates are removed.
Selected contacts
A hand-picked set — search your contacts or type phone numbers directly. This set is fixed at creation and does not re-resolve.
Duplicate phone numbers are automatically removed across all sources, so a contact who is in a list and a group only receives the message once.
WhatsApp groups are the one source that needs a live, connected session at send time. If the session is disconnected when the broadcast fires, group members resolve to zero (logged as a warning) — schedule group broadcasts only when the session will be online.
Broadcasts support text-only messages, images (with optional caption), audio, video, and documents (PDF, etc.). Upload the media while composing; it is sent alongside your message text to every recipient.
Toggle "Schedule for later" and pick a date and time to queue a broadcast instead of sending immediately. Neuron checks for due broadcasts roughly every 30 seconds and sends them in the background, resolving live audiences at that moment. If a scheduled broadcast resolves to nobody (for example, an empty list), it is marked completed rather than left hanging.
A broadcast can repeat on a fixed cadence — every X hours, days, weeks, or months. The recurring broadcast acts as a template: it never sends its own message. Instead, each time it is due, Neuron creates a fresh child send that re-resolves your audience live, then advances the schedule to the next occurrence. This keeps each send's history clean and always targets the current audience.
Set the cadence
Choose an interval (e.g. every 2 weeks) and, if the worker was offline, elapsed occurrences are skipped rather than fired as a burst — the cadence stays anchored and drift-free.
Choose when it ends
Never, on a specific date, or after a set number of occurrences.
Pause, resume, or stop
Pause a series to hold it, resume to roll the schedule forward to the next future window, or stop to end it while keeping the full history of past sends.
Recurring is available only for live audiences (All contacts or Lists & groups) with a schedule — a hand-picked Selected set cannot recur, since the point of recurrence is to re-resolve a changing audience each time.
Blasting hundreds of messages in one burst from a number that was recently quiet is a classic spam-ban trigger. Enable "Deliver in batches" to pace a large send. You control:
Batch size
How many recipients go out per batch (default 50). After each batch, Neuron waits a cooldown before the next one.
Delay between messages
A gap between individual messages inside a batch (default a random 1–3 seconds), so sends don't land in a perfectly even, bot-like rhythm.
Deliver over a window
Instead of tuning batches by hand, pick a window — 1 hour, 6 hours, 24 hours, 3 days, 7 days, or a custom span — and Neuron spreads the whole broadcast evenly across it.
Worker slots are freed during cooldowns, and progress is saved as it goes — a restart resumes a paced broadcast from where it left off. On top of this, Neuron automatically paces the backlog that piles up while a session is offline, so a just-reconnected number doesn't suddenly flush a burst.
Some contacts should never receive a broadcast — people who asked to stop, partners, or report-risk numbers. Neuron removes them automatically at send time so you don't have to manage exclusions by hand:
Do-not-broadcast marker
Any contact flagged "do not broadcast" is subtracted from every broadcast, matched by phone number — so it applies even to raw numbers and group members.
Exclusion lists
Exclude specific lists from a broadcast, and set an organization-wide global exclusion list that is always removed.
Automatic opt-out (optional)
An opt-in organization setting can automatically flag contacts as do-not-broadcast when they reply to stop or unsubscribe, or react with hostility to being messaged. This only affects future broadcasts.
While a broadcast sends, the detail page auto-refreshes and shows each recipient's status — pending (queued), sent (handed off for delivery), or failed — along with running sent and failed counts. Note that "sent" means the message was handed to the delivery pipeline, not that WhatsApp has confirmed it. Failures that happen later, at the gateway (for example, a session drop mid-send), surface separately in Failed Messages, where they can be reviewed and retried.
After a broadcast finishes, or if you need to iterate:
Resend
Clone a completed or failed broadcast's recipients into a new broadcast, edit the name or message, and send again.
Duplicate
Copy a broadcast into a new draft. If the original used a live audience, the audience sources are carried forward and re-resolved next time; otherwise the concrete recipient list is copied.
Cancel
Stop a broadcast that is mid-send. Remaining queued recipients are marked failed and any pending delivery batches are removed.