Fix GoHighLevel WhatsApp Onboarding Failure
If you work with ClickUp and GoHighLevel together to manage client operations, you may sometimes see a WhatsApp onboarding error that says you must create a new WhatsApp Business account because a payment method is already attached. This guide explains what that message means and how to resolve it step by step so you can successfully connect WhatsApp to your GoHighLevel account.
Understanding the GoHighLevel WhatsApp Onboarding Error
When you attempt to connect WhatsApp inside GoHighLevel, Facebook may show an onboarding failure message similar to:
- “Please create a new WhatsApp Business Account since a payment method already exists in this account”
This message appears during the Facebook/Meta Business extension flow when you are trying to configure WhatsApp for your GoHighLevel sub-account. It typically indicates a problem with the existing WhatsApp Business Account (WABA) or the payment configuration tied to it.
The core issue is that the current WABA already has a payment method attached, or the configuration does not meet Meta’s requirements for the extension integration that GoHighLevel uses.
Main Causes of the GoHighLevel WhatsApp Failure
The error is not generated by GoHighLevel directly. It comes from Meta’s systems and is related to one of the following issues:
- A payment method is already attached to the existing WhatsApp Business Account.
- The WhatsApp Business Account was created previously outside the GoHighLevel flow.
- There are legacy or incomplete WhatsApp settings in your Facebook Business Manager.
- The account is not compatible with the embedded onboarding used by GoHighLevel.
Because of this, the preferred solution is usually to create a new WhatsApp Business Account while following the correct onboarding process from inside GoHighLevel.
Before You Start: Requirements for GoHighLevel WhatsApp Setup
Before you try to fix the onboarding error, check that you have:
- Admin access to the connected Facebook Business Manager.
- The phone number you want to use for WhatsApp (not already registered on WhatsApp Business API elsewhere).
- Access to SMS or call verification for that phone number.
- Your active GoHighLevel account with permissions to set up WhatsApp inside the sub-account.
Having these prerequisites ready helps avoid repeated failures when reconnecting the extension.
Step-by-Step: Fix the GoHighLevel WhatsApp Onboarding Failure
Use the steps below to work through the Meta error and complete the connection inside GoHighLevel.
Step 1: Start the WhatsApp Setup inside GoHighLevel
- Log in to your GoHighLevel account.
- Open the sub-account where you want to enable WhatsApp.
- Navigate to the settings area where WhatsApp integration is offered (under the Twilio/WhatsApp or conversations-related settings, depending on your plan and UI version).
- Click the option to connect WhatsApp via Facebook/Meta. This will launch the embedded onboarding flow in a pop-up or new window.
Always begin from within GoHighLevel so the correct Business App and extension are used.
Step 2: Review the Error During Meta Onboarding
- Proceed through the Facebook login prompt with the correct admin account.
- Select the Facebook Business Manager that owns or will own the WhatsApp configuration.
- When you see the message about creating a new WhatsApp Business Account because a payment method already exists, stop and note the exact wording.
This message confirms that Meta wants you to create a new WABA under the Business Manager for compatibility with the GoHighLevel embedded flow.
Step 3: Create a New WhatsApp Business Account (WABA)
The official resolution recommended by Meta and reflected in the original instructions is to create a new WhatsApp Business Account instead of trying to reuse the old one.
- When prompted by the embedded setup, choose the option to create a new WhatsApp Business Account.
- Provide the required business details (name, business information, and region) as requested by Meta.
- Confirm and save your selections.
Creating the new WABA ensures there is no conflicting payment method tied to an older configuration that is blocking GoHighLevel from finishing onboarding.
Step 4: Add or Confirm a Payment Method in Meta
Meta sometimes requires a payment method for message templates or usage billing. During or after WABA creation:
- Follow any on-screen prompts to add or review a payment method for the new account.
- Use a valid card or payment profile that matches Meta’s policies.
- Make sure the payment method is correctly associated with the new WhatsApp Business Account, not the legacy one.
If you previously had a payment method on another WABA, Meta’s recommendation is to separate this new account to avoid the specific error you received inside GoHighLevel.
Step 5: Connect the Phone Number to the New WABA
- Still in the embedded Meta flow, select the phone number you want to attach to WhatsApp.
- If the number is already in use by a different WhatsApp (mobile or Business app), remove it from that app first, then return to the flow.
- Choose the verification method (SMS or call) and enter the code when you receive it.
- Wait for Meta to confirm that the number is now linked to the new WhatsApp Business Account.
Once verified, GoHighLevel should see this phone number as available and approved for WhatsApp Business API usage.
Step 6: Complete the GoHighLevel WhatsApp Integration
- Allow the embedded extension to finish all steps until you see a success confirmation.
- Return to your GoHighLevel settings page.
- Refresh or reopen the WhatsApp configuration screen.
- Confirm that the new WhatsApp number and Business Account appear as connected or active.
At this point, you should be able to send and receive WhatsApp messages from GoHighLevel as long as your Meta account and payment method remain in good standing.
What If the GoHighLevel Error Still Appears?
If you continue to see the same onboarding error after creating a new WABA, try the following checks:
- Ensure you used the same Facebook Business Manager in both attempts.
- Confirm that you actually selected the new WABA and not the old one during onboarding.
- Clear browser cache or use an incognito window and restart the flow from GoHighLevel.
- Verify that the phone number is not registered to any other WhatsApp Business API provider.
If none of these steps fix the issue, contact GoHighLevel support with screenshots of the full error message and details about the Business Manager and WABA you created. Their support team can confirm whether there is any platform-side configuration required.
Best Practices for Managing WhatsApp in GoHighLevel
To avoid future onboarding problems and keep your messaging stable inside GoHighLevel, follow these best practices:
- Always initiate WhatsApp onboarding from the GoHighLevel interface, not directly from Facebook’s dashboard.
- Keep a record of which WABA is tied to which GoHighLevel sub-account.
- Avoid reusing a WABA that is heavily customized or tied to another provider.
- Monitor your Meta payment method to prevent billing or policy issues that could interrupt service.
If you are building complex automations, funnels, or AI-enhanced workflows around WhatsApp messaging, consider documenting each step in tools such as ClickUp and aligning that documentation with your GoHighLevel setup for easier troubleshooting.
Additional Resources for GoHighLevel Users
For more technical growth strategies, CRM optimization tips, and done-for-you implementations around platforms like GoHighLevel, you can visit Consultevo for consulting and implementation services.
To review the original help documentation that this article is based on and see any latest updates directly from the platform, refer to the official page here: GoHighLevel WhatsApp Onboarding Failure Help Article.
By following the steps above and creating a new WhatsApp Business Account when prompted, you can reliably resolve this Meta payment method conflict and finish connecting WhatsApp to your GoHighLevel account.
Need Help With ClickUp?
If you want expert help building, automating, or scaling your GHL , work with ConsultEvo — trusted GoHighLevel Partners.
“`
