Order updates
Would require an external order event, approved template, variable mapping, and idempotent one-contact dispatch.
WhatsApp Notifications
A reviewed template-send path — not a notification engine.
Wavy's campaign path can send an approved Meta template to resolved recipients and track provider receipts. There is no dedicated transactional-event API, notification scheduler, one-contact notification object, or automation-to-template send path yet.
Status: PartialApproved-template campaign sends exist; a dedicated transactional notification workflow does not.
Campaign path onlyThe rules and inbox send paths use text messages, not template-notification dispatch.
Campaign template gateCampaign launch and worker execution require the current template to be APPROVED.
How notifications work
The exact path from trigger to delivered notification.
A notification is not a special object — it is a template send. Here is how it flows through the existing backend.
- Create and submit a template — The templates API records LOCAL, PENDING, APPROVED, or REJECTED status and can submit through a configured WABA path.
- Create the campaign audience — Campaign creation resolves contacts from the selected segment and stores recipient rows at creation time.
- Review and launch — Owner or admin launch checks the campaign is still a draft and the current template is APPROVED before enqueueing work.
- Track provider receipts — The worker records provider message IDs and status webhooks update sent, delivered, read, or failed states. This is still a campaign workflow, not a dedicated event notification service.
What you need
Requirements for live notifications.
These are the same requirements as any template-based send — there is no separate notification setup.
- An approved template — The current campaign template must be APPROVED. The source does not provide a separate notification-template library or event schema.
- A configured WhatsApp channel — Server credentials and the correct phone-number ID are required. Unconfigured sends use explicit dry-run behavior.
- A verified webhook for receipts — Delivery and read receipts arrive through
/webhooks/meta; without it, later provider states cannot be confirmed. - A campaign trigger — The existing reviewed path is campaign creation and launch. Event-driven transactional triggers and a dedicated scheduler remain planned.
Safeguards
What keeps notifications honest.
- Campaign template gate — Campaign launch and worker execution check template status; LOCAL, PENDING, and REJECTED templates are blocked on that path. Direct WhatsAppClient template calls do not add the same database gate.
- Dry-run fallback — Unconfigured sends return synthetic IDs and do not call Meta. This means a misconfigured deployment cannot silently fail to deliver a critical notification while appearing to succeed.
- Status transparency — Each notification message carries a status field reflecting the real provider state. The UI does not fabricate a "delivered" state for a message that Meta has not confirmed.
- Workspace isolation — Templates, contacts, and channels are workspace-scoped. A notification in one workspace cannot use another workspace's template or channel.
- No fabricated delivery guarantees — Wavy does not claim 99.9% delivery rates, real-time delivery, or guaranteed read receipts. Delivery depends on Meta's infrastructure, the contact's device, and the webhook being configured.
Planned notification use cases
What a dedicated trigger layer could support.
Appointment reminders
Would require a calendar or booking source and a scheduled transactional-send path that is not implemented today.
OTP and verification
No OTP generation, verification, expiry, or dedicated authentication-template dispatch flow exists in Wavy.
Status alerts
Would require a trusted source event, approved template, and replay-safe delivery record.
Payment links
The current payment collection endpoint creates a link and sends plain conversation text; it is separate from template notifications.
Questions
WhatsApp notifications — straight answers.
Is there a separate notification engine or queue?
No. Notifications are template sends through the same WhatsAppClient as marketing campaigns. There is no dedicated notification microservice, no separate queue, and no notification-specific infrastructure.
Can I run an OTP flow through Wavy?
Not as a complete feature. Wavy has no OTP generation, verification, expiry, or dedicated authentication-template dispatch endpoint.
What happens if my channel is not configured?
The send returns a synthetic message ID and does not call Meta. No real notification is delivered. This is the dry-run fallback, and it prevents a misconfigured deployment from appearing to send successfully.
Does Wavy guarantee delivery?
No. Delivery depends on Meta's infrastructure, the contact's device, network conditions, and the webhook being configured for receipts. Wavy tracks the real provider state — queued, sent, delivered, read, failed — but does not fabricate delivery guarantees.
Can I schedule recurring notifications?
No recurring-notification builder or event scheduler is implemented. Campaign scheduling is a separate reviewed broadcast workflow, and automation rules are inbound-message triggers.
How are template statuses handled?
Wavy records each submitted template separately as LOCAL, PENDING, APPROVED, or REJECTED. Campaign launch requires its selected current template to be APPROVED.
Use reviewed campaigns today; treat notifications as planned.
The existing template-gated path is campaign launch. A dedicated event-triggered notification service still needs its own contract, idempotency, and tests.