Templates & campaigns
Templates are pre-approved messages; campaigns send them to a list of recipients.
Message templates
To message someone outside the 24-hour service window, you use an approved template (e.g. marketing or utility). Templates are reviewed by Meta and move through these states:
draft— created locally, not yet submitted.submitted/pending— sent to Meta, awaiting review.approved— ready to use in campaigns.rejected— refused by Meta, with a reason shown in the dashboard.disabled— paused or flagged by Meta.
Each template has a category (MARKETING, UTILITY, AUTHENTICATION), a language, and a
set of components (header, body, footer, buttons).
Status updates are automatic
When Meta approves or rejects a template, the change is pushed to the platform and reflected in your dashboard within seconds — no manual refresh needed.
Campaigns
A campaign sends a chosen template to a list of recipients from one connection. Each recipient is tracked individually with a delivery status:
pending— queued, not yet sent.sent→delivered→read— normal progression.failed— with the failure reason returned by Meta.
Genuka is a Meta Tech Provider, not a BSP — Meta bills your own WABA directly, so we never debit
credits per message. Instead, every recipient counts against your plan's monthly message allowance
(the numbers you pay for × the tier's per-number quota), exactly like a single
POST /api/v1/messages send does. The whole recipient list is checked before the first send, so a
launch that wouldn't fit returns 402 plan_limit_messages up front rather than stopping half-way;
add numbers or move up a tier to raise the allowance. See Plans & billing.
Quality matters
Sending to recipients who haven't opted in, or high block/report rates, can lower a number's quality rating and lead Meta to restrict it. Monitor quality on the number's page in the dashboard.