Bulk WhatsApp broadcasts, sent safely and tracked to every reply.

WAPI's broadcast scheduler is wired into the kernel automation engine, the kernel customer registry, and the WAPI inbox — all the parts that need to know what got sent.

You pick a segment (dynamic, so its members are refreshed on a schedule as contacts change) or a static list. You pick a Meta-approved template (or write one and submit it for approval in the same place; Flaxxa picks up Meta's verdict). You send now or schedule a time, and Flaxxa sends in batches at a steady pace within Meta's limits. Contacts who opted out are left out. The scheduler records every message id and brings delivery, read and reply events back into the same inbox where the conversation lives.

The results update while the campaign is running, not nightly and not via a CSV. When a recipient replies, the reply lands in the shared inbox on their conversation, so the agent picking it up sees the broadcast they're answering.

What the marketing + CX teams actually feel.

• Marketing sees broadcast results in Flaxxa instead of waiting for CSV exports.
• Sends are paced by default, which helps protect your number's quality rating.
• Per-campaign reply rate becomes a tracked metric — you stop guessing whether the broadcast worked.
• Agents can handle broadcast-day replies, because each reply sits on the conversation under the message it answers.
• The offer actually gets seen, because WhatsApp messages have a 98% open rate.