Bulk Broadcast Checklist: Send Email, SMS, and WhatsApp Reliably

A bulk broadcast is a planned message sent to many people, usually from a campaign rather than from a one-to-one conversation. It can be an email newsletter, an SMS promotion, a WhatsApp template message, or a coordinated send across two or more channels. The channel changes the delivery rules and recipient expectations, but the operator's job is the same: confirm who should receive it, why they should receive it, and whether the send can finish without damaging the next one.

This checklist is for the shutdown review before a broadcast leaves Devotel Orbit. Use the Campaigns dashboard or Outbound campaigns to review the send, and use Audience to confirm the segment behind it. A bulk broadcast is not a substitute for consent, a list-cleaning process, or a channel-specific sending identity.

1. Decide what kind of bulk send you are making

Start by naming the message class for each channel. A single campaign can include email, SMS, and WhatsApp, but each channel still needs its own audience eligibility and suppression check.

Bulk email

Bulk email is one message or template sent to a list on the sender's schedule. Newsletters, product announcements, event invitations, and promotions are common examples. It is different from transactional email, which is triggered by a recipient action such as a purchase, password reset, or account event.

For US recipients, CAN-SPAM is the baseline for commercial email. Your tenant-owned checklist should include:

• Identify the message as commercial when its primary purpose is commercial.
• Use accurate sender and routing information and a subject that matches the message.
• Include a working unsubscribe method that does not require a recipient to explain why they are leaving.
• Honor opt-outs promptly and keep unsubscribed addresses out of later campaigns.
• Keep a record of the sender, audience source, template version, and send time.

Mailbox-provider requirements can be stricter than the statutory baseline. If your volume qualifies as bulk traffic at Gmail or Yahoo, review the Gmail and Yahoo bulk-sender requirements before sending. Keep promotional traffic separate from transactional traffic when your sending identity and reputation plan call for it.

SMS broadcast

An SMS broadcast sends a common or templated text to many contacts without turning the recipients into one group conversation. The Bulk SMS glossary entry covers the delivery pattern and terminology; this checklist focuses on the send decision.

Before a tenant sends a commercial SMS broadcast, confirm that:

• The audience source records the permission or relationship that supports the message in the recipient's jurisdiction.
• The sender identity is appropriate for the destination and message type, including any registration or brand requirements that apply to the tenant.
• The message identifies the sender when the recipient could reasonably be unsure who is texting.
• The message includes the tenant's working opt-out instruction where required, and replies or opt-outs are suppressed from later sends.
• The message is useful at the time it arrives; frequency and quiet hours are part of the consent experience, not an afterthought.

The TCPA, state laws, carrier policies, and local rules can impose different duties based on the recipient, sender, content, and dialing method. Orbit surfaces tenant controls; it does not turn a campaign into legal advice or make a tenant's consent posture compliant for them.

WhatsApp broadcast

WhatsApp broadcasts are governed by the recipient's expectation of the channel, the tenant's relationship with that recipient, and WhatsApp's business messaging rules. A template approval or an available channel does not by itself establish permission to contact everyone in a list.

Review these tenant-owned questions before launch:

• Did the recipient opt in to WhatsApp messages from this business, or does the tenant have another documented basis for the planned message?
• Is the selected template accurate for the message and current for the intended use?
• Can the recipient understand who is contacting them and how to stop future messages?
• Does the tenant have a process for handling replies, requests to stop, and contacts who should no longer be messaged?
• If a recipient cannot receive WhatsApp, is the fallback channel separately eligible rather than silently assumed to be allowed?

Treat channel fallback as a new eligibility decision. An SMS fallback is not automatically covered by a WhatsApp opt-in, and an email opt-out is not automatically an SMS opt-out unless the tenant's own policy makes it cross-channel.

2. Select and validate the audience

Open Audience before opening the send review. A segment is a decision about recipients, not just a saved filter. Give it a name that records the purpose and date, then check the conditions that make a contact eligible for this channel.

Run this audience review in order:

1. Define the purpose. Write the offer, update, or service reason in one sentence. If the purpose is unclear, the audience will be unclear too.
2. Choose the source. Prefer a tenant-owned contact list, signup source, or segment with a known collection date and owner. Do not merge an old export into a current segment without reconciling opt-outs.
3. Filter for channel eligibility. Require a deliverable email address, mobile number, or WhatsApp-eligible contact field as appropriate. Do not treat a populated field as permission.
4. Apply suppression. Exclude hard bounces, spam complaints, unsubscribes, invalid numbers, blocked contacts, and channel-specific opt-outs. Check the suppression result after every audience edit.
5. Remove duplicates. Deduplicate by the channel identity used for sending. One person with two records should not receive two copies because the CRM used two contact ids.
6. Check recency and scope. Exclude contacts outside the intended geography, customer status, language, or relationship window. Document why the filter is present so a teammate can review it.
7. Preview the count. Compare the current count with the last approved count. A sharp increase is a reason to stop and inspect the source, not a reason to celebrate reach.
8. Save the segment snapshot. Keep the final audience definition and the rendered count with the campaign review. The list can change after approval; the operator should know which population was actually approved.

For a cross-channel send, create a separate eligibility view for each channel or make the channel branches explicit. A contact eligible for email may be suppressed for SMS. A contact who opted out of WhatsApp should not re-enter through a fallback path.

3. Protect deliverability before you queue the broadcast

Deliverability is a sender practice, not a promise made by a platform. Read the email deliverability playbook for SPF, DKIM, DMARC, warmup, bounce handling, and suppression. For the identity details behind transactional and bulk email, see Transactional email sending identities.

Use this channel-by-channel review:

Email deliverability

• Send bulk traffic from the tenant's intended marketing identity or stream, not the identity reserved for password resets and receipts.
• Confirm SPF and DKIM pass and align with the visible From domain; keep DMARC reporting under the tenant's control.
• Check the unsubscribe path in a rendered test message, including mobile view.
• Remove hard bounces and complaints before the send, and set a bounded retry policy for temporary failures.
• Warm a new domain or identity gradually. Do not use a first campaign as a volume test.
• Send a small preview to internal recipients and inspect links, personalization, sender name, reply-to, and plain-text fallback.

SMS deliverability

• Check the sender identity, destination mix, message length, encoding, and expected segments before approval.
• Keep the copy recognizably from the tenant and make the next action clear.
• Remove invalid numbers and contacts suppressed by prior opt-outs or carrier feedback.
• Avoid sudden volume spikes from a new sender. Start with a measured cohort and compare delivery, failure, and opt-out rates before widening the audience.
• Keep the opt-out response path working and monitor replies after launch.

The Bulk SMS glossary entry is a useful companion when the team needs to align on throughput, API or SMPP terminology, and the difference between a one-to-many broadcast and a one-to-one text.

WhatsApp deliverability

• Use the approved template that matches the message purpose and language.
• Check that the audience is eligible for the tenant's WhatsApp program and that the tenant has a reply-handling plan.
• Review recent delivery, read, failure, and quality signals before increasing the next wave.
• Keep the first wave narrow when the number or template is new. A large failure can make later sends harder even when the copy is unchanged.
• Never treat a failed WhatsApp delivery as permission to contact the same person on another channel.

4. Pace the queue and respect quiet hours

A reliable broadcast is paced for the tenant's sender, channel, audience, and expected retry load. Do not confuse the maximum rate shown by a provider or plan with a rate the tenant should use for every campaign.

Before scheduling, calculate:

• Recipients per channel: the approved count after deduplication and suppression.
• Available send rate: the lower of the tenant's configured limit, the sender or route limit, and the channel's current allowance.
• Retry headroom: capacity reserved for temporary failures, throttles, and provider retries. A queue filled to its ceiling leaves no room to recover cleanly.
• Completion window: the time required to finish the wave without crossing a recipient's quiet hours.

Use a staged schedule when any of those values is uncertain: internal preview, small cohort, measured expansion, then the remaining audience. Watch delivery and failure rates between stages. Pause the expansion if failures, opt-outs, complaints, or provider throttles move sharply in the wrong direction.

Quiet hours should be evaluated against the recipient's local time when the tenant has a reliable timezone. If the tenant cannot resolve a recipient's timezone, follow the tenant's documented fallback policy instead of pretending the time is known. The policy may differ by channel and jurisdiction; Orbit exposes tenant-owned controls and does not choose a universal commercial-send window for every tenant.

For cross-channel broadcasts, quiet hours apply to each attempted channel and to each fallback. A contact who receives an email at a reasonable hour should not immediately receive an SMS because the email event was delayed. Add a frequency cap or a deliberate channel priority so one campaign does not become three unexpected interruptions.

At the stop point, record who can pause the campaign and what signal triggers the pause. A broadcast should have a named operator, an observable queue, and a rollback or suppression action that does not depend on the original campaign author being online.

5. Final shutdown checklist

Run this list immediately before scheduling or pressing send:

• [ ] The campaign purpose and message class are recorded for each channel.
• [ ] The audience came from a tenant-owned source and has a current owner.
• [ ] Each channel has its own eligibility, consent, suppression, and fallback review.
• [ ] Duplicate contacts, hard bounces, complaints, invalid numbers, and opt-outs are excluded.
• [ ] Email authentication, sending identity, unsubscribe path, and test rendering are confirmed.
• [ ] SMS sender, message length, registration posture, opt-out path, and destination mix are confirmed.
• [ ] WhatsApp template, opt-in posture, reply handling, and current quality signals are confirmed.
• [ ] The staged rate, retry headroom, completion window, and recipient quiet-hours policy are documented.
• [ ] The campaign has a stop owner and a monitoring plan for delivery, failure, complaint, and opt-out signals.
• [ ] The approved audience count and message version are captured for later review.

After the send, compare results with the approved baseline. A delivery report answers whether the message reached a channel; it does not answer whether the audience was appropriate or whether the next campaign should use the same volume. Feed those decisions back into the tenant's audience and suppression process.

Frequently asked questions

What is the difference between a bulk broadcast and a mass text?

A bulk broadcast is the broader pattern: one planned message sent to many recipients. A mass text is the SMS-only version. This checklist covers email, SMS, and WhatsApp together, including the channel-specific eligibility and deliverability decisions a cross-channel send requires.

Can I use one audience for email, SMS, and WhatsApp?

You can start from one business segment, but you should not assume one eligible audience. Each channel needs its own contact field, permission or relationship basis, suppression scope, message rules, and fallback decision. Build or preview channel branches before approval.

Does an email unsubscribe stop SMS and WhatsApp too?

Not automatically. Suppression scope is a tenant-owned policy and can be channel-specific or broader. Honor the scope the recipient was given, and choose a broader cross-channel policy when that is how the tenant represents a recipient's request to stop.

How fast should a bulk broadcast send?

Use the slowest applicable limit with room for retries, then stage the send. A rate that looks acceptable on paper can still create a poor experience when a new sender, a large audience, or a provider throttle adds retries. Measure the first cohort before expanding.

What should I do if the first wave starts failing?

Pause expansion, preserve the send and audience snapshot, and inspect the failure mix by channel. Check sender identity, destination quality, template or content, rate limits, and suppression handling. Do not switch every failed recipient to another channel automatically; confirm that the fallback is eligible and expected.

Is this checklist legal advice?

No. CAN-SPAM, TCPA, carrier rules, WhatsApp business messaging rules, and local requirements can depend on the recipient, sender, content, relationship, and jurisdiction. Devotel Orbit provides tenant-owned campaign, audience, sending, and suppression controls; the tenant is responsible for selecting and documenting its compliance posture with qualified advice.

Where do I run this review in Devotel Orbit?

Build or inspect the segment in Audience, then review the send in Campaigns or Outbound campaigns. Keep the final audience count, message version, channel branches, pacing plan, and stop owner with the campaign record.