Troubleshoot WhatsApp connection and messaging

Possible causes include incomplete Tech Provider approval, a tenant module that has not been activated, or a user without connection-management permission. Ask the tenant owner to confirm the approved rollout and role. Do not grant broad administration merely to make a button appear.

Allow popups for Balaawi, refresh an expired session, use a current supported browser, and confirm that privacy or network controls are not blocking the Meta window. Verify that the correct Meta business portfolio is selected. If authorization was revoked, an approved administrator must reconnect.

Confirm international number format, control of SMS or voice verification, current registration, provider ownership, and retry limits. For a pending or rejected display name, align the name and profile with the legal or publicly recognized business identity and follow the action shown by Meta.

Review the exact status for payment readiness, authorization, recipient validity, consent, service-window state, template approval and variables, quality restrictions, role permission, and temporary provider errors. Correct the named requirement before retrying. Never use repeated sends as a health check.

Confirm the masked connected number, tenant status, authorization, webhook health, event subscription, and the time range. A platform operator should use connection metadata and safe event identifiers to diagnose routing while preserving tenant boundaries and customer privacy.

Provide the tenant name or approved identifier, masked phone number, safe error code, approximate time and timezone, browser version for authorization issues, expected action, observed result, and whether the issue affects all authorized users. Exclude secrets, full customer numbers, message bodies, and unnecessary personal data.