# Can't Connect WhatsApp to ZazzyAgent? Troubleshooting Guide If WhatsApp won't connect to ZazzyAgent, don't immediately restart the entire setup. Most connection problems can be narrowed down by checking the Meta business account, WABA, phone number, permissions and previous provider connection. ## 1\. Check your Meta Business access The Meta account you're using must have the appropriate access to the business and WhatsApp assets. If your Facebook account can access a Page but doesn't have sufficient Business/WABA permissions, the WhatsApp setup can fail. ## 2\. Check the WABA Make sure your WhatsApp number actually belongs to the WABA you're selecting. If you manage multiple businesses, it's easy to select the wrong business or WABA. ## 3\. Check the phone number Make sure you're selecting the correct phone number. If the number doesn't appear during setup, investigate the WABA and Meta configuration before creating another number. ## 4\. Was the number previously connected to another provider? This is a major check. If the number was previously connected to another WhatsApp API provider, the old provider relationship may still need to be removed. A previous provider connection can prevent the new provider connection from completing. See [Migrating a WhatsApp Number From Another Provider to ZazzyAgent](https://blog.zazzyagent.com/whatsapp-number-migrated-from-another-provider-zazzyagent). ## 5\. Check whether the number is already registered A WhatsApp number may already be associated with a WhatsApp registration. The correct next step depends on whether you're: * Connecting a new number. * Migrating an API number. * Moving between providers. * Moving from the WhatsApp application to the Business Platform. Don't delete accounts or numbers blindly. ## 6\. Check Meta permissions During Embedded Signup, approve the requested permissions. If permissions were denied or incomplete, the connection may fail. The current connection workflow explicitly identifies permission problems as a common cause of failed WhatsApp connections. ## 7\. Check whether Business verification is needed Some WhatsApp configurations depend on your Meta Business verification status. Open your Meta business settings and check the current status. If verification is pending or rejected, resolve that issue before assuming the problem is inside ZazzyAgent. For setup requirements, see [WhatsApp API Setup & Meta](https://blog.zazzyagent.com/series/whatsapp-api-setup-meta). ## 8\. Connection completed but account isn't appearing Sometimes the Meta connection can complete while the connected account isn't immediately reflected in the ZazzyAgent dashboard. Try: * Refreshing the page. * Signing out and back in. * Synchronizing the account where available. * Reconnecting if the account remains unavailable. Account synchronization issues are also identified in the current connection troubleshooting material. ## 9\. Browser problems A browser session can sometimes interfere with Meta's authorization flow. Try: * Private/incognito window * Hard refresh * Another browser * Clearing cached authentication/session data Don't start changing your Meta business configuration unless the browser test confirms the problem persists. ## 10\. Embedded Signup stops at Finish If the setup fails when you click the final confirmation: Check: * Required permissions * Business access * WABA selection * Phone verification * Meta account The current setup documentation identifies missing or denied permissions as a common cause. ## 11\. Phone registration problems If your number connects but registration needs attention, check the **Register Phone** workflow. It uses the WhatsApp two-step verification PIN. If you have never changed the automatically configured PIN, the setup instructions use: **123456** For a detailed explanation, see [What Is "Register Phone" in ZazzyAgent?](https://blog.zazzyagent.com/what-is-register-phone-zazzyagent). ## 12\. Indian number migrated from another provider If the number is: **+91** and was migrated from another WhatsApp provider, check whether **Local Storage (India Only)** should be enabled during registration. Don't enable it for every Indian number. See [Migrating a WhatsApp Number From Another Provider to ZazzyAgent](https://blog.zazzyagent.com/whatsapp-number-migrated-from-another-provider-zazzyagent). ## 13\. Don't reconnect repeatedly Reconnect only when there is a reason. Repeatedly reconnecting can make troubleshooting harder because you may change the state while trying to identify the original problem. First identify: **Meta** → **Business** → **WABA** → **Phone** → **Provider** → **Permissions** → **Registration** Then fix the specific problem. ## Connection troubleshooting checklist ### Meta * \[ \] Correct Meta account * \[ \] Correct Business * \[ \] Correct permissions * \[ \] Verification status checked ### WABA * \[ \] Correct WABA * \[ \] Correct phone number * \[ \] WABA accessible to your Meta account ### Phone * \[ \] Correct number * \[ \] Number eligible * \[ \] Existing registration checked ### Migration * \[ \] Previous provider identified * \[ \] Old provider relationship checked * \[ \] Migration requirements reviewed ### Registration * \[ \] Current 6-digit PIN known * \[ \] Local Storage checked if applicable * \[ \] Registration completed when required ## When to contact support If you've confirmed: * Correct Meta Business * Correct WABA * Correct phone number * Required permissions * Previous provider connection * Registration requirements and the number still won't connect, collect the exact error message and screenshots before contacting support. That gives the support team enough information to identify the failing step. ## The fastest way to diagnose a connection problem Don't treat "WhatsApp won't connect" as one problem. Break it down: > **Can Meta see my business?** ↓ > **Can Meta see my WABA?** ↓ > **Can Meta see my phone number?** ↓ > **Can ZazzyAgent access the business?** ↓ > **Does the number have an old provider connection?** ↓ > **Does phone registration need to be completed?** This approach is much faster than repeatedly restarting the onboarding process.