Broadcasts

A broadcast is a one-shot, scheduled send. You pick a moment in time + a filter + a payload (flow or template) and Wexio fires it exactly once for everyone who matches.

Use a broadcast whenever you want a bounded, auditable one-shot send:

• "Notify everyone tagged vip 30 minutes before the webinar starts."
• "Send the seasonal-sale WhatsApp template to all customers in Spain on Thursday at 9am."
• "Run the post-checkout follow-up flow for everyone who bought in the last 7 days, this Friday."
• "Re-engage cold leads on the first of each month" (created as a series of one-shot broadcasts).

Two Kinds

Every broadcast is one of two kinds, picked at creation time:

When to use which:

• Flow — branched, conversational, captures responses, mixes channels. Optionally attach WhatsApp template fallbacks so contacts the flow can't reach (typically a closed WA 24h window) still receive something.
• Template — static announcement, promotion, or notification. Configure one or more template routes — (template, integration) pairs — and the system picks the right route per contact. Each route is itself window-safe; no fallback is needed.

How Broadcasts Differ From Schedule Triggers

Same execution plumbing under the hood — different lifecycle and ownership.

Reach for a broadcast for bounded, one-shot sends with a per-run audit trail. Reach for a scheduled trigger for ongoing automations that fire whenever a clock or contact date matches.

What Broadcasts Are Not

• Not recurring. Each broadcast fires once. To repeat, create another broadcast (or use a recurring scheduled trigger).
• Not a trigger. Triggers fire in response to an event (message received, field changed, webhook received). Broadcasts fire at a clock time.
• Not transactional. Broadcasts are bulk. For 1:1 receipts, OTPs, or order-status messages, send templates from a flow or webhook handler.
• Not a campaign manager. No A/B split, no journey, no funnel dashboard — just delivered/skipped/failed counts. Cohorting and experimentation belong in the flow editor.
• Not throttled by user-set rate limits. Dispatch speed is paced by the messaging provider (e.g. WhatsApp Business API tier), not by broadcast configuration.

Common Sections

Glossary

• Audience filter — the list of conditions that defines who receives the broadcast.
• Audience size estimate — the count shown in the wizard, computed against the live directory at the moment you're editing.
• Audience size actual — the count computed at fire time, when the audience is re-resolved.
• Template route — a (template, integration) pair used by template-mode broadcasts to direct delivery through the right WhatsApp number.
• Fire time — the moment the worker dispatches the broadcast (within seconds of the scheduled time).
• Dispatch — the act of sending the flow or template to a single contact during the SENDING phase.
• Retry of a broadcast — a new broadcast targeting only the failed contacts of a prior one, linked via the source's history.