To send a WhatsApp broadcast, create a campaign, choose your audience (a contact list, a segment, or a CSV import), and select an approved message template. Stravax Engage checks each contact's opt-in status, fills in any per-recipient variables you've mapped, and queues the messages, sending them right away or at a time you schedule.
A broadcast's audience is either a saved contact list, a segment, or a CSV file you import at send time, not more than one of these at once. If you import a CSV, you map its columns to contact fields as part of setting up the campaign.
If you're sending to a segment, Stravax Engage resolves who's actually in it at the moment the campaign goes out, not when you built the segment. That matters if someone's status changes in between: a contact who withdraws marketing consent after you set up the segment but before send time is still skipped for missing consent, they don't get swept in just because the segment counted them earlier.
Yes. Broadcasts only send over WhatsApp templates that Meta has already approved, you can't send free-form text as a broadcast. Which contacts are eligible also depends on the template's category: marketing templates go only to contacts who've given marketing opt-in, while utility or authentication templates only require message opt-in.
Yes. Map a contact field, or a column from your CSV, to each numbered placeholder in the template body ({{1}}, {{2}}, and so on), and every recipient gets their own values filled in. The number of variables you map has to match the number of placeholders the template actually has, Stravax Engage checks this when you create the campaign so a mismatch never reaches the send queue.
Yes. Set a send time and the campaign stays in a scheduled state until then, it won't fire early. Stravax Engage checks for due scheduled broadcasts on an hourly cycle and fans them out automatically once their time arrives.
A per-contact frequency cap applies across all of your broadcasts and sequences (drip campaigns) together, so one contact can't be hit repeatedly just because they're on several lists. When a contact is skipped for being over the cap, that skip is counted and shown in the campaign's results, it's never a silent drop.
Each recipient's message is queued and sent individually, metered, and threaded into that contact's conversation in your inbox. Sending also respects the number's current broadcast limit, so a large campaign paces itself rather than firing all at once. See Throttling, quality rating and messaging tiers for why.