Evidence-led field guide
Connect WhatsApp Business Platform to Balaawi One
Understand ownership, tenant isolation, permissions, security boundaries, and the activation status of the Balaawi One WhatsApp integration.
The WhatsApp integration foundation is prepared for organizations to connect their own Meta business assets to Balaawi One. Live connection and messaging are not yet publicly active. Balaawi must first complete Meta Tech Provider approval and then enable the module for the specific tenant.
Your organization remains in control
- Your organization owns and administers its Meta business portfolio and WhatsApp Business Account.
- Your organization obtains, verifies, and controls its business phone number.
- Customers see the organization's approved display name and number, not Balaawi's identity.
- The tenant manages customer consent, opt-outs, message purpose, and Meta billing.
- Meta sign-in happens directly with Meta. Balaawi does not ask for a Facebook password.
What the prepared integration is designed to provide
After approval, configuration, and a controlled test, permitted employees can work from a tenant-isolated inbox, use approved templates, inspect delivery states, and prepare operational notifications. Phone-number routing, connection records, and message records stay scoped to the owning tenant.
Permission boundaries
Connection management is separate from reading conversations, sending messages, managing templates, configuring automations, viewing analytics, and using AI-assisted drafts. Granting send access must never grant authority to reconnect or disconnect Meta business assets.
Security and privacy
Provider credentials remain server-side and are not returned to tenant interfaces. Sensitive connection changes require an authorized administrator. Platform operations should expose masked connection health and identifiers, not customer conversation content. AI-assisted reply drafts require authorized human review unless a separately approved automation policy explicitly allows sending.
Activation sequence
- Balaawi completes Meta Tech Provider approval.
- Balaawi configures approved production credentials and callback settings.
- The tenant owner confirms the correct Meta portfolio, account, number, consent process, and administrators.
- An authorized administrator completes Meta authorization.
- Balaawi and the tenant run connection-health and controlled messaging tests.
- The module is enabled only after the acceptance checks pass.
Questions teams ask next
Is WhatsApp live in Balaawi One now?
The production foundation is prepared, but live connection and sending remain disabled until Meta Tech Provider approval, production configuration, tenant activation, and controlled acceptance testing are complete.
Does Balaawi own the tenant's WhatsApp Business Account?
No. The organization owns and administers its Meta business assets and grants only the approved access needed for the integration.
Can regular employees connect or disconnect WhatsApp?
No. Connection management is reserved for a tenant owner or an explicitly authorized administrator. Other WhatsApp capabilities use separate permissions.
Are messages separated between tenants?
The prepared architecture scopes connection and messaging records to the owning tenant. Tenant-isolation checks are part of activation acceptance.
Source register
References used to bound this guide. External sources open in a new tab.
- Embedded SignupMeta for Developers
- Set up Webhooks for WhatsApp Business AccountsMeta for Developers
- WhatsApp message templatesMeta for Developers
- WhatsApp Business Platform pricingMeta for Developers
- Balaawi WhatsApp production-readiness recordBalaawi SystemsInternal record
Evidence standard: Source-governed educational record
Plan one bounded review