WhatsApp common issues
Troubleshoot phone registration, missing Meta access, verification codes, and connected numbers that do not reply.
Start with the symptom below. For a first connection, follow Connecting WhatsApp and check the Requirements.
Meta says the number is already registered
Check whether the number is in the regular WhatsApp app, the WhatsApp Business app, or an existing API provider. Even an unfinished business profile can follow completed phone registration.
Send Octocom the exact error and the number's current setup. An app number and a provider migration need different procedures. Do not delete the account or repeatedly register it in different products while troubleshooting. Simultaneous use of the Business app and API requires a supported coexistence setup; do not assume it is enabled for your connection.
The business portfolio or WhatsApp account is missing
Confirm that the Facebook account used in the login has full admin access to the owning Meta Business Portfolio and access to the intended WABA. Check that the correct portfolio was selected and that the WhatsApp account was shared with Octocom. A Page role alone is not enough.
Retry the login with the authorized admin and grant access to the intended account. If Meta shows an account restriction or verification requirement, resolve that in Meta's business settings. Avoid creating duplicate portfolios or WhatsApp accounts to work around missing access.
The SMS or verification call does not arrive
Check the country code and number. Confirm that the SIM or line is active and can receive the selected verification method. For calls, check IVR menus, forwarding, spam blocking, and whether international calls can reach the line.
Use the alternative verification method if Meta offers one. Respect any retry timer shown by Meta rather than requesting codes repeatedly. Enter the code only in Meta's signup screen; do not send it to support.
WhatsApp shows Needs attention
Octocom shows Needs attention on the WhatsApp card when Meta refused to register a number, Octocom could not connect to its messages, or Meta reports that a number can't send or receive messages. Messages to that number will not arrive until it is fixed. Open the card to see which number is affected and what Meta reported. Settings → Channels → WhatsApp shows each number's status from Meta, with Meta's reason and suggested fix when a number isn't live.
- Meta reports a number isn't live. A number still pending registration or offline usually needs Continue with Facebook again for that number. If Meta reports a restriction, the account's Meta admin needs to resolve it or request a review in WhatsApp Manager; only Meta can lift it.
- Meta still refuses registration after a PIN reset. When Meta refuses a number's two-step PIN, Octocom sets a new PIN and tries once more. A failed retry does not establish an account restriction. If Meta reports an account lock, check the WhatsApp Business Account in WhatsApp Manager for a restriction or policy warning. If there is one, the account's Meta admin needs to resolve it or request a review; only Meta can lift it. If there is none, contact Octocom support.
- Meta still rejects the two-step PIN after a reset. Contact Octocom support to finish connecting the number. This error alone does not indicate an account restriction.
- Octocom couldn't reset the two-step PIN. Contact Octocom support before changing two-step verification, so the number can be recovered without interrupting it.
- Octocom lacks permission for the account. Reconnect with an admin of the Meta Business Portfolio and share the WhatsApp account with Octocom during signup.
- Meta needs to verify the number again. A number that was offline can need a new verification code before it can connect again, and Octocom can't request that code from the dashboard yet. Contact Octocom support.
- Too many attempts, or the number was just removed from WhatsApp. Meta pauses registration after too many attempts (for 72 hours after 10 registrations of the same number) or briefly after a number is removed. Wait as shown, then reconnect.
If Octocom reset the PIN but setup still failed, the error message says so and explains the remaining step. You can set your own PIN in WhatsApp Manager at any time.
After fixing the cause, click Continue with Facebook again for the same number. The card returns to Connected once the number is registered, its messages are connected and Meta reports it live. Then send a test message as described in Connecting WhatsApp.
Octocom cannot verify the existing WhatsApp numbers
Click Retry. If it keeps failing, contact Octocom support to check access to your existing WhatsApp account. Octocom pauses setup at this step to preserve existing reply settings. If the error appears after returning from Meta, reopen the WhatsApp connection window and start again.
Facebook login finishes, but the number is missing in Octocom
Return to the correct Octocom business and open Settings → Channels → WhatsApp. If Meta refused to register the number, Octocom shows an error after the signup and the WhatsApp card shows Needs attention; see the section above.
Check that you finished the full signup and shared the WABA containing that number. If it remains missing, send Octocom the error or final screen, business name, phone number, and time of the attempt. If available, include the WABA ID and phone number ID from WhatsApp Manager. Support can check registration and webhook setup.
The number is connected, but the AI does not reply
- Check the number under Connected phone numbers. If it shows Not live, Meta can't deliver its messages; see WhatsApp shows Needs attention. Otherwise check its switch: newly connected numbers start disabled, so enable the intended number in the correct business.
- Send a fresh message from another WhatsApp account and allow for the configured Reply delay.
- Check whether the message appears in Octocom. If it does, inspect the conversation's status and human escalation settings. A conversation handed to a human may correctly wait for an agent.
- If the message is missing, check that you sent it to the correct number and business. Send support the test time and destination number so the inbound connection can be checked.
- If a reply fails to send, capture the exact delivery error and check WhatsApp Manager for restrictions or billing requirements. Follow Meta's messaging requirements if the error says the reply is outside its allowed messaging window. Changing Octocom's Reopen window does not change Meta's sending rules.
If the page says Routed through Zendesk, phone numbers and accounts are managed in Zendesk. Investigate the help desk's WhatsApp connection as well as Octocom's handling settings.
Messages appear under the wrong business
Check the business selected during connection and the per-number reply settings. A shared WABA can expose several numbers to more than one connected Octocom business. Enable each number only in the business that should handle it. Contact support if an existing connection needs to be reassigned.
Meta shows pending review, a rejected name, or a restriction
Open WhatsApp Manager or Meta's business settings and follow the specific review or verification request. Check the submitted business information and display name against the public business identity. Share the exact Meta message with Octocom if you need help interpreting it.
Phone verification, business verification, and display-name review are different checks. Repeating phone verification does not resolve an unrelated business review or policy restriction. Keep launch plans conditional on a successful inbound-message and reply test.
What to send support
Include the Octocom business, destination phone number with country code, exact error or screenshot, time of the attempt with timezone, and whether the number is new, app-registered, or connected through another provider. For message-delivery issues, include the Octocom conversation link if one exists.
Never share passwords, access tokens, SMS codes, or two-step verification PINs. Crop or redact credentials from screenshots.