Template + segment pairing
A campaign references one approved template and one filtered segment. This structure mirrors Meta's business-initiated conversation model.
WhatsApp Marketing
Broadcast campaigns built on approved templates and opted-in segments.
Wavy's campaign engine creates, schedules, and launches WhatsApp broadcasts. A campaign is a template-plus-segment pair: it references a Meta-approved template and a filtered contact segment, then enqueues recipient sends through the configured WhatsApp channel. Without an approved template, a configured channel, and opted-in contacts, a campaign cannot launch.
Status: Configuration-dependentCampaign routes exist. Launch requires an approved template, a configured channel, and opted-in recipients.
Template-gatedOnly Meta-APPROVED templates can be attached to a campaign. LOCAL, PENDING, and REJECTED templates are blocked.
Consent requiredContacts carry an opted_in flag. Broadcast marketing to non-opted-in contacts is not the intended workflow.
How a campaign works
The exact workflow from template approval to recipient enqueue.
This is the real campaign path in the backend — not a generic marketing description.
- Create or select an approved template — Templates are created locally then submitted to Meta. The templates API tracks status as LOCAL, PENDING, APPROVED, or REJECTED. A campaign launch checks the template status and rejects anything that is not APPROVED.
- Build a contact segment — Contacts are created manually, imported via CSV, or synced from Airtable. Segments filter contacts by attributes and lead stage. Each contact carries an opted_in flag; the intended broadcast audience is opted-in contacts matching the segment.
- Create the campaign — The campaigns API creates a campaign record that references the template ID and segment ID, sets a name, and optionally schedules a send time. The campaign starts in a draft state.
- Launch and enqueue — On launch, the worker enqueues CampaignRecipient rows for each contact in the segment. Each recipient is sent the template through the configured WhatsApp channel. Stats — queued, sent, delivered, read, failed — are aggregated back onto the campaign.
- Track results — The campaign record carries a stats object updated from recipient statuses and webhook receipts. The workspace UI shows per-campaign progress and per-recipient outcomes, not inflated aggregate metrics.
Requirements
What you need before a campaign can launch.
These are enforced by the backend, not just listed as best practice.
- At least one APPROVED template — The launch path queries the template and checks its status. LOCAL, PENDING, and REJECTED templates cannot be used. Meta approval is outside Wavy's control.
- A configured WhatsApp channel — The channel's WhatsAppClient must be configured (phone-number ID and access token set server-side). An unconfigured channel runs in dry-run mode and returns synthetic IDs.
- Opted-in contacts in a segment — Contacts must exist in the workspace and be grouped into a segment. The opted_in flag is the consent signal. Sending marketing broadcasts to non-opted-in contacts is not the intended path and may violate Meta's commerce and messaging policies.
- Provider webhook for receipts — Delivery, read, and failed receipts arrive via the Meta webhook. Without a verified webhook, statuses remain at "sent" and do not advance to delivered or read.
Safeguards
What prevents a bad broadcast from going out.
- Template status gate — The launch endpoint queries the template and rejects the campaign if the template is not APPROVED. This prevents sending unreviewed content to a segment.
- Workspace isolation — Campaigns, templates, segments, and contacts are all workspace-scoped. A campaign in one workspace cannot pull recipients from another.
- Dry-run channel fallback — If the channel is unconfigured, recipient sends return synthetic IDs and do not call Meta. The campaign still enqueues, but no real message leaves the system.
- Unsubscribe handling — A built-in automation rule suppresses contacts who reply with an unsubscribe keyword. The rules engine marks them as opted out so they are excluded from future segments.
- Per-recipient status transparency — Each CampaignRecipient carries its own status. The UI does not collapse failures into a single "sent" count or fabricate delivery numbers.
Campaign capabilities
What the campaign engine covers.
Scheduling
A campaign can be scheduled for a future send time or launched immediately. The worker processes the enqueue when the schedule fires.
Recipient-level tracking
Each contact in the segment becomes a CampaignRecipient with its own status, updated from Meta webhook receipts.
Aggregated stats
The campaign record carries a stats object — queued, sent, delivered, read, failed — rolled up from recipient statuses.
CSV import & Airtable sync
Contacts can be imported via CSV or synced from an Airtable base. Segments are built from the resulting contact pool.
Questions
WhatsApp marketing campaigns — straight answers.
Can I send a broadcast without an approved template?
No. The campaign launch path checks the template status and rejects any template that is not APPROVED. This is enforced in the backend, not just the UI.
Do I need consent before sending marketing messages?
Yes. Contacts carry an opted_in flag, and the intended broadcast audience is opted-in contacts matching the segment. Sending marketing to non-opted-in contacts is not the intended workflow and may violate Meta's messaging policies.
What happens if my WhatsApp channel is not configured?
The campaign still enqueues recipients, but each send returns a synthetic message ID and no real call is made to Meta. This is the dry-run fallback — it lets you test the campaign structure without sending live messages.
Does Wavy guarantee Meta template approval?
No. Wavy submits templates to Meta and tracks their status, but Meta governs approval. Automix does not claim to influence Meta's review or guarantee that any template will be approved.
Can I see delivery and read receipts?
Yes, when the Meta webhook is configured and verified. Receipts update each recipient's status. Without a webhook, statuses remain at sent and do not advance.
Are campaign metrics like open rate or CTR available?
The campaign tracks message-level statuses (queued, sent, delivered, read, failed). It does not fabricate click-through rates or engagement metrics that the WhatsApp API does not provide.
Build campaigns on approved templates, not guesswork.
The campaign engine enforces template approval and consent before a single recipient is enqueued. Configure your channel and get a template approved to start.