WhatsApp Business Cloud: “Invalid detach account” + support form stays blank

Questions
1

:bullseye: What is your goal?

Connect my existing WhatsApp Business app number to Make while keeping the mobile app active, and successfully create a Watch Events webhook.

:thinking: What is the problem & what have you tried?

In WhatsApp Business Cloud → Watch Events, saving a webhook fails with “Invalid detach account.”

I tried recreating the connection and disabling Safari’s pop-up blocker, but the error persists. My Make region is EU1.

I also cannot submit a support ticket. The “Get help” form stays blank in both Safari and Chrome on my iPhone, using either mobile data or Wi-Fi. Refreshing and signing into the support portal did not help. “New support ticket” returns me to the same support page, and Merlin has not responded.

How can I fix the connection or contact technical support?

:clipboard: Error messages or input/output bundles

Invalid detach account.

2

Invalid detach account is not really a Make error, and it is not about Safari’s pop-up blocker. It is Meta refusing to attach your number because the number is still attached somewhere else. Coexistence has to take the number from wherever it currently lives and hand it to the partner. If a previous attachment is still on record, the detach step fails, and Make surfaces Meta’s rejection with that wording.

The usual culprits, most common first:

An earlier Cloud API registration of the same number. If that number was ever registered on the Cloud API, even in a test or abandoned app, it has to be deregistered before it can be attached again.

A leftover WABA from an earlier onboarding attempt. Look in WhatsApp Manager for a second WhatsApp Business Account you had forgotten about, with your number still listed under it. Remove the number there first. Two WABAs in play is extremely common with Coexistence, and it is behind at least one other open thread here.

A previous BSP or partner still holding the number. If the number was ever run through another provider, that partner link has to be removed in Business Settings before Make can take it.

So: WhatsApp Manager, Phone numbers, find every place your number appears, and remove it from all of them except where you want it to end up. Then run Coexistence onboarding again from a clean state. If none of that applies and the number appears nowhere else, then it is a stuck record on Meta’s side and only Meta can release it.

On support: that form is broken on iPhone, which is why it stays blank for you in both Safari and Chrome. Two ways around it. Use a desktop browser, where the form generally does load. Or skip the form and email support directly, which avoids the reCAPTCHA entirely. Someone else here hit the same expiring-reCAPTCHA wall today, so it is not your setup.

The part worth being honest about: untangling a number that is attached in two places, without deregistering the wrong one and losing your existing WhatsApp Business chat history, is fiddly and not very forgiving. The order of operations matters, and the mistake people make is deregistering before checking where the number actually sits, which costs them the history. If you want it handled rather than talked through, my profile has how to reach me. Otherwise, start with the WhatsApp Manager audit above, since that alone tells you whether you have a simple leftover WABA or something Meta has to release.

Kane