Connect your own WhatsApp Business account

Fluenta connects through Meta’s official WhatsApp Business Platform (Cloud API) on Graph API v25.0. It is not an unofficial bridge and does not use a scraped WhatsApp web client.

Fluenta does not provision, resell, or rent phone numbers. You connect a WhatsApp Business Account (WABA) and phone number that you own inside your own Meta Business Manager.

That ownership stays with you: if you leave Fluenta, you keep the number and the WABA in your Meta Business Manager.

• A Meta Business account.
• A WhatsApp Business Account with a phone number that is not already registered to the WhatsApp consumer or WhatsApp Business app.
• A Meta app with WhatsApp added.
• Four credentials to paste: a phone number ID, WABA ID, a system-user access token, and the app secret.

• Paste the four credentials into the bot's WhatsApp settings.
• Fluenta immediately verifies the credentials against Meta and tells you if they are wrong.
• Fluenta encrypts the token and app secret with AES-256-GCM before storing them.
• Fluenta subscribes to the webhook and verifies every inbound payload's HMAC-SHA256 signature.

For the connected number and WABA, Fluenta uses access that lets it:

• Send and receive messages on the connected number.
• Read message delivery statuses.
• Read and create message templates on the WABA.

Templates you create in Fluenta are submitted to Meta and mirrored locally. The mirror tracks Meta’s own statuses — PENDING, APPROVED, and REJECTED — plus LOCAL_DRAFT for a template you have not submitted.

A sync action reconciles Fluenta’s mirror with Meta’s authoritative template list. Approval is Meta’s decision on Meta’s timetable; Fluenta cannot promise a duration.

Business verification and display-name review are Meta processes run in your Meta Business Manager. Fluenta neither controls nor accelerates them, and it cannot promise a timeline.

Meta bills conversation charges directly to your own Meta Business account. Fluenta never resells, marks up, includes, or passes through Meta’s fees.

Fluenta’s separate platform charge is metered in credits per message:

• Marketing: $0.0015.
• Utility: $0.0008.
• Authentication: $0.0006.
• Service: $0.0004.
• $0.00 when Meta reports a conversation as non-billable.
• $0.001 provisionally until Meta’s delivery status reveals the category; Fluenta then reconciles the charge to the real rate.

See pricingfor Fluenta’s platform plans and credit allowances.

The built-in simulator runs every branch without a WhatsApp number or any Meta setup at all. Try the flow before you connect production credentials.

Open the live simulator.

• Credentials are rejected on save. Check the phone number ID and replace an expired system-user token, then paste the corrected credentials and save again.
• The number is already registered to a WhatsApp app. Resolve that existing app registration in Meta and use a number eligible for Cloud API registration before trying again.
• Webhook signatures do not match. Check that the app secret in Fluenta belongs to the same Meta app where the webhook is configured, then save the matching secret.
• Meta rejects a template.Review Meta’s rejection feedback in your Meta Business Manager, correct the template, and submit it again from Fluenta.

Need a person to help investigate? Visit support with the details of what you tried.