Integration & setup errors
This number is registered to an existing WhatsApp account
This error appears when the phone number was previously used with another WhatsApp Business API provider or with the WhatsApp mobile/business app. If the number was used in the standard WhatsApp app, you must disconnect it before connecting it to Intercom.
If used with another API provider:
Follow the onboarding flow for migrating an existing WhatsApp phone number, and exit the embedded onboarding after Step 2.
If used with a mobile WhatsApp app:
Follow the steps under the Learn more link shown in the error to disconnect the number from that WhatsApp account, then you should be able to retry our onboarding process successfully.
Note: Disconnecting a WhatsApp account deletes chat history unless backed up.
If neither applies, contact Support with your:
WhatsApp Account ID
Phone number
We can attempt a manual connection.
Code couldn't be sent
Check your browser console for additional detail.
If this occurred during migration:
The migration may already have succeeded. Try using the “I’m integrating WhatsApp for the first time” flow and select the newly created accounts.
Tip: This error often resolves by simply switching to the first-time setup path.
If still failing, contact Support.
500 error in console during signup
If you are unable to save your business profile settings and are receiving a 500 error back in your browser console, it's likely a validation error returned to us by WhatsApp on the profile setting you are trying to update. There are some details on the restrictions such as maximum number of characters here.
Cannot Migrate Phone Number. The WhatsApp account that this number is registered isn’t set up correctly
Check:
The phone number is fully verified in Meta.
It is not still connected to the WhatsApp Business app.
If both checks fail: Sending Support a screenshot of the verified number in Business Manager helps speed up resolution.
Provide Support with your:
Verified screenshot
Phone number
WABA ID
WhatsApp Business Account access not shared
Contact Intercom customer support for help with this error.
Cannot create certificate. Please ensure two-factor authentication is disabled
Ensure your WhatsApp number is connected on the installation page.
Note: Two-factor authentication must be disabled in WhatsApp for certificate creation.
Please make sure you fully authorize access to your WhatsApp Business Account
Verify the phone number is fully approved in Meta.
Tip: Delays between Meta approval and Intercom syncing can sometimes cause this temporarily. Wait a few minutes and retry.
Please retry in some time or reach support to get issue fixed
This typically occurs due to restricted or disallowed words in the title or description fields.
Note: Meta strictly enforces naming rules. Avoid political, medical, or sensitive terms. This Facebook developers post might be worth checking out.
WABA inputted (ID xxxx) is already using a payment method
This often occurs for numbers provisioned by third-party providers. Try the migration onboarding steps again. If unsuccessful, contact Intercom Support.
We can't verify the Meta business account that you selected…
This error must be resolved by Meta Support and cannot be fixed within Intercom.
Unsupported get request. Object with ID XXXXXXXXXXXX does not exist, cannot be loaded due to missing permissions, or does not support this operation
When you try to connect a number, make sure the code which is shown to you is a WhatsApp account ID.
Tip: WhatsApp Account IDs differ from Business Manager IDs—double check which you’re entering. You can find them here.
Error code (#100) Invalid parameter
This is usually flagged by Meta due to any phone migration error. Check the Meta docs for more details.
Additionally, if you encounter the following error: Type: OAuthException Code: 1 Error_subcode: 23881 Message: Invalid parameter Error_user_title: Cannot Create Certificate Error_user_msg: Your business doesn’t meet WhatsApp’s policy requirements. If you believe your business qualifies, reach out to Meta Business Suite Support. Official documentation can be found here.
If you encounter an error message like "(#1) Parameter Error" while connecting your WhatsApp number: Take a screenshot of the error message. Often, resolving this requires Meta support. Confirm that all settings in Meta and Intercom are configured correctly before reaching out.
OAuthException errors
Examples:
Type: OAuthException
Code: 1
Error_subcode: 23881
"Cannot Create Certificate"
"Your business doesn’t meet WhatsApp’s policy requirements"
These errors indicate your business may not meet WhatsApp’s policy standards. If you believe your business qualifies, reach out to Meta Business Suite Support. Official documentation can be found here.
“(#1) Parameter Error” while connecting your number
Take a screenshot and check your settings. Most parameter errors originate from Meta’s side and must be resolved via Meta Support.
Error connecting WhatsApp account: code: 1, error_subcode: 99, message: An unknown error occurred [HTTP 500]
Follow these steps:
Go to WhatsApp app settings.
Choose “I’m migrating from an existing WhatsApp…”
Select Create a new WhatsApp Business Account.
Close the popup after the WhatsApp Business Account is created but before adding the phone number.
You will be prompted in Intercom to introduce the ID of the new WhatsApp Business Account you have created - you can find it in your WhatsApp Business Account.
You can then keep following the instructions in our help article to complete the migration process.
Note: Closing the popup at the correct moment is essential to avoid this error. This is the window that you should close 👇
WhatsApp message template issues
Templates not appearing in Intercom
Check:
Template contains only plain text or quick reply buttons.
No media or unsupported variables.
Template is fully approved in Meta.
Language matches Intercom settings.
Intercom has been refreshed.
Tip: Meta approval can take minutes to hours, sync issues often resolve with time.
Variable formatting in WhatsApp message templates
Intercom requires templates to use numerical placeholders (e.g., ##{{1}}) rather than descriptive ones like ##{{sf_full_name}}. Example: Hi ##{{1}}, your order ##{{2}} has been shipped.
If your templates using variables like ##{{sf_full_name}} fail, edit your template in Meta to replace descriptive placeholders with numerical ones and map these in Intercom. This ensures compatibility between WhatsApp and Intercom by mapping variables directly to Intercom attributes.
Preventing template reclassification as “Marketing”
To ensure templates remain non-marketing:
Avoid promotional language.
Avoid excessive personalization.
Don’t include media unless required.
Specify the support or transactional purpose clearly when submitting. Make it explicit and non-marketing.
Useful resources:
WhatsApp message send issues
Receiver is incapable of receiving this message / Message is undeliverable
WhatsApp couldn’t deliver this message because the recipient’s WhatsApp account isn’t currently able to receive messages. This can happen if the phone number isn’t registered with WhatsApp, if the recipient hasn’t accepted WhatsApp’s latest Terms of Service or Privacy Policy, or if they’re using an outdated version of the WhatsApp app (minimum required versions include Android/SMBA 2.21.15.15, iOS/SMBI 2.21.170.4, KaiOS 2.2130.10, and Web 2.2132.6).
To resolve the issue, ask the recipient via another communication channel (such as SMS, email, or phone) to confirm they can send a message to your WhatsApp Business number, accept any pending Terms of Service prompts by going to Settings > Help or Settings > Application information, and update their WhatsApp client to the latest version.
Once they complete these steps, WhatsApp should be able to deliver your messages successfully.
This message couldn't be delivered due to WhatsApp's messaging frequency limits
This message was not delivered because WhatsApp blocked it to maintain healthy ecosystem engagement, which usually means the recipient has reached a limit on how many marketing template messages they can receive within a certain period.
If you suspect this is the cause, the best action is to wait at least 24 hours before attempting to resend the template message. Sending it again sooner will likely result in the same error, as the limit can remain active for varying lengths of time.
Tip: For more details on how these limits work and when they reset, see WhatsApp’s Per-User Marketing Template Message Limits documentation.
This message couldn't be delivered because the recipient's phone number is part of a WhatsApp experiment
This message was not sent as part of an experiment. For more details on experiments, see WhatsApp’s Marketing Message Experiment documentation.
Media type is not supported by WhatsApp
This message couldn’t be delivered because WhatsApp was unable to upload the media included in it, which typically occurs when the file uses an unsupported format or doesn’t meet WhatsApp’s media requirements.
To resolve this, review the media file you’re trying to send and confirm that its format and size are supported by WhatsApp. Once the media meets WhatsApp’s requirements, you should be able to resend the message successfully.
This message can't be sent
This message couldn’t be delivered because more than 24 hours have passed since the recipient last replied to your WhatsApp number, and WhatsApp only allows free-form messages within that active 24-hour conversation window. This error can also occur if the recipient’s phone number changed during the conversation, which effectively resets the session.
To continue messaging, you’ll need to send a WhatsApp-approved template message instead. Once the recipient replies, the 24-hour window will reopen and regular free-form messages can be sent again.
WhatsApp Business Account has been locked
This message couldn’t be delivered because the WhatsApp Business Account connected to your app has been restricted or disabled. This typically happens when WhatsApp detects a violation of their platform policies, or when details in the request can’t be verified against the account’s configuration—for example, an incorrect two-step verification PIN.
To resolve this, review WhatsApp’s Policy Enforcement guidelines to understand the type of violation and the steps required to restore the account. You can also check the WhatsApp Health Status API for more specific insight into why the account was locked or restricted. Once the underlying issue is addressed, message delivery should resume normally.
Need more help? Get support from our Community Forum
Find answers and get help from Intercom Support and Community Experts

