I need urgent help from the HighLevel WhatsApp/LeadConnector technical team with a WABA-to-Location association issue that has been unresolved since September 3, 2026.

WABA: Daniel Angiología

Phone: +52 1 564 004 0818

WRONG / PREVIOUS LOCATION ID:

FIeNTIwTLYotvgncpnhp

CORRECT CLIENT LOCATION ID:

OqrPOrmo4bQ9DhXRgnG

HighLevel continues to show this error:

“This WABA is already onboarded at location Id: FIeNTIwTLYotvgncpnhp”

The previous Location has already been checked. There is no visible WhatsApp connection and no option to disconnect the WABA from that Location.

Meanwhile, Meta shows the WABA and phone number as active and connected to LeadConnector.

This issue has already been escalated through HighLevel Support and is documented under:

Ticket #6281712

Related ticket #6290177

I have been requesting assistance through both chat and email since September 3. The case has been escalated and marked as high priority, but I continue receiving generic responses stating that the case is still in queue.

The issue remains completely unresolved and is blocking a paid client implementation that must be delivered today, September 7, 2026.

I am NOT requesting another onboarding tutorial. I do NOT want to create another WABA, change the phone number, or repeat the same troubleshooting steps.

I need the WhatsApp/LeadConnector technical or backend team to review the WABA-to-Location association, release the stale association from the previous Location FIeNTIwTLYotvgncpnhp, and correctly associate the WABA with the client Location OqrPOrmo4bQ9DhXRgnG.

The Conversation AI phone selector currently shows “No data” because the WhatsApp asset is not properly available in the correct Location.

All relevant information and screenshots have already been provided to Support.

Please have someone with actual backend access review this issue and provide a concrete technical resolution today. I do not need another generic escalation status. I need the underlying WABA-to-Location association fixed.