Sending broadcasts
Last updated August 29, 2026
In short. A broadcast sends one email to a whole list through the platform channel. Suppressed and opted-out contacts are skipped and counted, results finalize from queued to sent, and opens and clicks always track.
A broadcast is one email to a whole list (or a single contact) in one action, and it's the platform channel's flagship use: bulk mail on infrastructure built for it, metered against your monthly send pool, never through your personal mailbox. Broadcasts need a paid plan or trial; the sending-channels guide explains the split.
What happens when I hit send?
The broadcast fans out asynchronously: recipients queue, sends process in the background, and the results page updates itself without a manual reload. Status moves from queued to sending to a terminal sent, or partial if some recipients failed. Each recipient becomes an individual send record stamped with the broadcast, so the sends list and each contact's history show exactly what went out.
Who gets skipped?
Every recipient passes the same gate as any other send: suppressed contacts, opt-outs, and invalid email addresses are skipped, not attempted, and the results page counts them under Skipped so list totals always reconcile. A large skipped count is information, not a bug; it usually means an imported list carried opt-outs, which is exactly what the suppression check is for.
Which limits apply?
Three can come into play. The broadcast draws from your monthly platform pool (7,500 to 200,000 sends depending on tier), and pool exhaustion pauses the remainder rather than failing it, resuming after an upgrade or a bank top-up. If you're sending from a custom domain still in warmup, the day's warmup allowance caps how much of the broadcast goes out per day, with the rest rolling to the next day. And the bounce-rate guardrails apply in full, so a broadcast to a stale list is the classic way to meet the 5% throttle mid-send. The deliverability guide is worth reading before your first large one.
What tracking do broadcasts get?
Always the full set: open pixel, rewritten click-tracked links, and per-recipient open and click counts on the results page. Unlike the mailbox channel there's no opt-out from tracking here, since bulk mail is where the numbers are meaningful and expected. The usual open-rate caveats still apply.
Can I test two versions against each other?
Yes, that's the composer's holdout option: try two subject lines or two templates on a slice of the list, then send the winner to the rest automatically. It has its own guide: A/B testing broadcasts.
Can I send the same broadcast again?
Duplicate, on any broadcast's results page, opens the composer already filled in with the same template, from-address, subject, and list. If the original was an A/B test, its variants and holdout settings come through too. The name arrives as "Copy of" the original.
Nothing sends until you click Send. Creating a broadcast in SEMAOS is sending it, so there is no half-made copy waiting in a drafts list. Duplicate hands you a filled-in composer and you decide what goes out. Swap the list, rewrite the subject, or send it as it stands.
If something the original used has since been deleted, the composer names it at the top of the form and leaves the replacement to you rather than substituting one quietly. That covers a deleted list, a deleted template, and a sending address that is no longer verified. One case it cannot cover: a broadcast sent to a hand-picked set of contacts rather than a saved list has no audience to carry across, since the composer sends to lists, so you will be asked to pick one.