Send campaigns, broadcasts and cascades

Use a broadcast when the message is driven by an owner rather than an automatic event.

Quick composer and campaigns

The Overview composer supports free-form email, in-app, push and SMS when those channels are available. It deliberately excludes WhatsApp because a cold WhatsApp broadcast needs approved template handling.

For a saved broadcast, open Campaigns → New campaign. Choose the audience, channel, subject where applicable, message and whether to save, send or schedule it. A single-channel campaign creates one campaign record and queues one eligible message per recipient.

When All channels is used as a multi-channel send, JollyBee creates a separate campaign for each selected channel. The same person can therefore receive the message more than once—once on each eligible channel. Use that only when broad repetition is intentional.

Cascade mode

A cascade tries channels in the order configured under Communications Settings and stops after the first successful send attempt for each person. It is an immediate waterfall, not a scheduled queue strategy. It is useful when you want one best-effort contact per person rather than one copy per channel.

The current cascade is limited to 2,000 resolved people. It tries a person's preferred channel first when one is available, then the configured order. “Successful” means the channel sender accepted that attempt; it does not promise the person read it. Cascade applies member opt-outs but does not consult the separate address-suppression table.

An inline cascade writes its own cascade and recipient records. It does not create an ordinary Campaign and its attempts do not appear in the current Message log. Use the result shown after the cascade and its cascade records when auditing it; do not look for a matching campaign row.

The web Overview cascade currently selects email, in-app, push and SMS only. Cascade email uses the platform sender rather than the community SMTP override. Other cascade callers can request WhatsApp, but that path requires community-owned credentials and sends free text, so it depends on an open customer-service window.

Scheduling and audience resolution

Campaign messages are processed by the queue worker, normally within about five minutes of becoming due. A scheduled campaign resolves its segment when it sends, so a dynamic segment can contain different people from the estimate shown when it was scheduled.

Preferences and missing addresses are applied per channel. Campaign suppression records are checked for email addresses, but the same suppression table is not applied to every phone channel. The segment count is not the promised delivery count; maintain the member's SMS and WhatsApp preferences instead of assuming an email suppression blocks them.

Read campaign status correctly

Campaign status Sent normally means the original queue drained. A retry from Message log can create queued work without reopening the Campaign, and Sent can still include failed or bounced rows. Inspect the campaign detail and outbound log before reporting reach. Likewise, a provider-accepted SMS or email is not the same as confirmed handset or inbox delivery.