BALAAWISYSTEMS
Balaawi operating librarywhatsapp help

Evidence-led field guide

Connect your WhatsApp Business account

Prepare the Meta portfolio, WhatsApp Business Account, business number, profile, consent process, and authorized administrator before connection.

2 min readUpdated WA-HELP-0002

Do not begin with a live number until ownership, access, migration impact, and rollback are understood. The Connect WhatsApp control becomes available only after Balaawi completes Tech Provider approval and enables the tenant module.

Requirements before connecting

  • Administrative access to the organization's Meta business portfolio.
  • A WhatsApp Business Account, or authority to create one in the approved Meta flow.
  • A stable business phone number controlled by the organization.
  • Access to receive an SMS or voice verification code.
  • The intended display name, square logo, business email, website, category, description, and address.
  • A valid Meta payment method where Meta requires one.
  • A documented customer opt-in and opt-out process.
  • A Balaawi tenant owner or administrator with connection-management permission.

Connection steps after activation

  1. Sign in to Balaawi One as an authorized administrator.
  2. Open Settings, Integrations, then WhatsApp and select Connect WhatsApp.
  3. Sign in directly with Meta in the secure authorization window.
  4. Select the organization's correct Meta business portfolio.
  5. Select or create the correct WhatsApp Business Account.
  6. Add or select the controlled phone number and complete Meta verification.
  7. Review the display name and business profile information.
  8. Approve access only to the intended business assets.
  9. Run the Balaawi connection-health checks.
  10. Send a controlled test to an approved recipient before enabling wider use.

Before moving a live number

A number already used in the WhatsApp Business app or with another provider may need a Meta-supported migration or coexistence path. Confirm ownership, expected downtime, verification access, history expectations, dependencies, rollback, and the people authorized to approve the change.

Acceptance evidence

Retain the tenant identifier, masked number, Meta asset identifiers, administrator identity, authorization time, health-check result, test-recipient approval, test-message outcome, and the decision that enabled or rejected production use. Never place access tokens, passwords, verification codes, or customer message content in a support request.

Questions teams ask next

Why is Connect WhatsApp not visible?

The tenant module may still be disabled, Tech Provider approval may be incomplete, or the user may lack connection-management permission.

Does Balaawi receive the Facebook password?

No. Authentication takes place directly with Meta. Never send a password, access token, or verification code to Balaawi Support.

Can an existing WhatsApp Business app number be used?

It may be eligible for a Meta-supported migration or coexistence path. Review the current Meta rules and operational impact before changing a live number.

What should be tested first?

Validate authorization, number registration, webhook health, template visibility, permissions, tenant routing, and one controlled message to an approved recipient.

Source register

References used to bound this guide. External sources open in a new tab.

  1. Embedded SignupMeta for Developers
  2. Set up Webhooks for WhatsApp Business AccountsMeta for Developers
  3. WhatsApp message templatesMeta for Developers
  4. WhatsApp Business Platform pricingMeta for Developers
  5. Balaawi WhatsApp production-readiness recordBalaawi Systems
    Internal record

Evidence standard: Source-governed educational record

Plan one bounded review

What must an administrator prepare before the production connection flow can be completed safely?

Bring one real workflow, its accountable owner, and the evidence used to accept it.Request a scoped review