WhatsApp Setting

WhatsApp Setting configures Meta WhatsApp business credentials, phone/account identity, template sync, sender setup, webhook handling, and delivery health.

What this page is for

WhatsApp Setting configures Meta WhatsApp business credentials, phone/account identity, template sync, sender setup, webhook handling, and delivery health.

Who should use it

Owner, communications admin, platform admin

Where to find it

/admin/whatsapp-settings

Before you start

In Meta Business/Developers, collect the WhatsApp Business Account ID, phone number ID, business phone display number, app ID, app secret, and a long-lived or system-user access token approved for the WABA.
In Meta Developers WhatsApp API setup, the phone number ID and WhatsApp Business Account ID are shown in the WhatsApp product setup/API configuration area. Copy them exactly; they are not the display phone number.
Register and verify the WhatsApp business phone number in Meta before using it as a SquareOS sender.
Configure the webhook callback URL and verify token supplied by SquareOS/platform in the Meta app webhook settings, then subscribe to WhatsApp message/status events so inbound messages and delivery statuses can sync.
Create a system user or approved token flow in Meta Business Settings, grant the app/WABA required WhatsApp permissions, and paste only the approved credential/token reference into SquareOS.
WhatsApp requires provider account, phone/business identity, credential reference, approved templates, webhook readiness, template sync, and sender readiness.
Use approved template names/languages and component variables exactly as Meta expects. Placeholder mismatch can block sends.
WhatsApp template fields in Message template are External template ID, Language code, Category, Header parameter keys, Body parameter keys, Name, Event key, Sender account, Provider account, Body template, and Description.
Header parameter keys and Body parameter keys must match Meta placeholder order exactly so approved-template sends can build Meta template components instead of falling back to text.
In SquareOS Channel Account, choose WhatsApp, provider Meta WhatsApp, Account name, External account id as WABA/phone identity reference, credential/token reference, and Safe/fake provider mode only for sandbox testing.
After saving, Verify the provider, Sync channel account, Sync templates, then create sender account whose sender value is the approved display phone number or phone number ID reference.
Inbox, profile activity, class group messaging, campaigns, and automations should stay disabled until readiness is true.
Current backend contract: WhatsApp provider setup, sender/template records, template submit/sync state, inbound message intake, queueing, opt-out/consent checks, delivery attempts, Meta Cloud API text-message dispatch, approved-template payload dispatch, and signed Meta WhatsApp webhook handling exist. GET /engagement/meta-whatsapp/webhook verifies the Meta challenge, and POST /engagement/meta-whatsapp/webhook validates x-hub-signature-256, updates message delivery/read state, and ingests inbound replies into Inbox/profile activity.
When a WhatsApp render snapshot is linked to an approved template with an external template id, the worker sends Meta type template with template name, language, and ordered body/header parameters from stored template design or body placeholders. Safe/fake provider mode or simulated delivery attempt IDs are not proof of Meta WhatsApp delivery. Production proof requires a real Meta provider message id, signed status callback, and inbound reply mapped into Inbox/profile activity.

Daily workflow

In SquareOS, open Admin, WhatsApp Setting, enter provider Meta WhatsApp, account name, WABA/business ID, phone number ID, display phone number, credential reference/access token, app ID/app secret where required, webhook verify token, and template sync status.
Create sender account for the approved business phone number, sync approved templates, and check template approval/sync status before campaign or automation use.
Send a template test to an internal opted-in phone, reply from that phone, and verify the inbound reply appears in Inbox/profile activity.
Use WhatsApp for customer follow-up only when consent and template rules are satisfied.
Review delivery failures before assuming the customer received a message.

Watch out

Do not use WhatsApp for untracked payment instructions when a generated payment link exists.

Use the left menu to open related pages in Integrations.
Use Ask Docs for questions that are already covered in this public documentation.