Campaigns

1. 1Campaigns send WhatsApp templates, not free-form message bodies. In Campaigns → Templates, select a positional template whose Meta status is Approved.
2. 2Meta decides template approval in Meta’s own process and on Meta’s own timetable. Fluenta cannot control or accelerate that decision, so do not promise an approval duration to a recipient or stakeholder.
3. 3At launch, Fluenta rejects a locally mirrored template whose status is not APPROVED. A template that has never been mirrored locally is permitted because Fluenta cannot validate its status; that is not approval evidence. Verify unknown templates in Meta before scheduling them.
4. 4Fluenta excludes contacts with a recorded marketing opt-out. It does not capture or verify positive opt-in, so the operator must target only contacts with documented marketing consent. The absence of an opt-out is not consent.

1. 1Choose New campaign, give the draft a recognizable name, select the approved template, and fill its positional body parameters. Use the supported {{name}} and {{phone}} tokens only where they belong in the template.
2. 2Build the audience with activity windows, conversation outcomes, unresolved signals, and/or an explicit phone list. The filters are combined, and recorded marketing opt-outs remain excluded.
3. 3Select Preview audience before launch to inspect the matching count and sample. Recheck consent for that exact audience before sending.
4. 4Choose Send immediately on launch or enter a scheduled time, save the draft, then choose Launch. The audience is resolved when the scheduled campaign fans out, so review the segment again if the schedule is far in the future.

Fluenta applies its own per-message platform-credit rate from the Meta pricing category reported with delivery status:

• marketing: 1,500 micro-credits (0.0015 credits) per message
• utility: 800 micro-credits (0.0008 credits) per message
• authentication: 600 micro-credits (0.0006 credits) per message
• service: 400 micro-credits (0.0004 credits) per message
• free: 0 micro-credits (0 credits) per message

Before a delivery status reports a category, Fluenta uses a 1,000-micro-credit placeholder and reconciles the platform charge once Meta reports the category.

These Fluenta credits are separate from Meta’s own conversation charges. Because you connect your own WhatsApp Business account, Meta bills those charges directly to your Meta Business account; Fluenta does not resell, mark up, or pass through them.

Review pricing and usage for Fluenta credit usage, and follow WhatsApp onboarding to connect the customer-owned Meta credentials.

No template appears in the campaign picker

Campaigns show approved positional templates. Submit or sync the template, then wait for Meta’s decision; Fluenta cannot promise when Meta will approve it. Named-parameter templates are not available in the campaign picker.

A contact is missing from the audience

Review the activity, outcome, signal, and explicit-phone filters, then check whether the contact has a recorded marketing opt-out. Do not remove an opt-out merely to make a campaign send; obtain and document new consent first.

Launch rejects the selected template

A locally mirrored template that is not APPROVED cannot launch. Correct the template or wait for Meta to decide its status; there is no Fluenta-controlled approval timeline.

A Meta charge does not match Fluenta credit usage

Treat them as separate bills. Fluenta applies the platform rate above from Meta’s reported category, while Meta bills conversation charges directly to the connected Meta Business account.