Campaigns

1. 1Campaigns → New campaign. Name it something you'll recognise in reports.
2. 2Pick the channel: WhatsApp, Email, SMS or RCS.
3. 3On WhatsApp, pick an approved template — drafts and pending templates aren't selectable. On the other channels, write the message body (plus a subject for email).
4. 4Choose the target segment with a contact tag; leave it blank to reach every opted-in contact.
5. 5Map variables — {{1}}, {{2}} — to contact fields like name or phone.
6. 6Send now, or schedule for a date and time in the workspace timezone.

Each campaign runs on one primary channel and can declare a fallback. If a message fails permanently on the primary channel, the queue waits the number of minutes you set and then re-sends the same text on the fallback channel — once, never in a chain.

• WhatsApp requires an approved template and a connected, verified number.
• Email, SMS and RCS require that channel to be connected on the Channels page, and send your body text with variables substituted.
• Email campaigns only reach contacts that have an email address; contacts without one are skipped.
• SMS and RCS use the contact's E.164 phone number; RCS falls back to SMS automatically when the handset can't receive RCS.
• Opted-out contacts are excluded on every channel.

Scheduled campaigns are picked up by the background queue worker. A running campaign can be paused; pausing stops new sends but doesn't recall messages already handed to Meta.

• Messages are enqueued, not sent in one burst, so a large campaign can't stall the app.
• The worker respects your Meta messaging tier (250 / 1k / 10k / 100k unique contacts per day).
• Failed sends are retried with backoff; permanent failures land in the dead-letter queue with the Meta error code.
• Business-hours restrictions, if configured, hold sends until the next allowed window.
• Email, SMS and RCS jobs go straight through their provider driver and are metered as usage events.