I followed the official WhatsApp integration procedure documented here using "Authorize WhatsApp". During this process, Meta permanently restricted the newly created business because it detected prohibited automation. Before I attempt Manual Configuration using my own Meta Developer App, I need to know the recommended procedure in this situation. I don't want to create another Business Portfolio or WABA if Meta could consider that circumvention of the previous restriction. Can you confirm whether this is a known issue with the WhatsApp OAuth onboarding process and what procedure Botpress recommends after a Meta Business Portfolio has been permanently restricted during onboarding?

Yes, this is a Meta-side restriction rather than a normal Botpress configuration error. Meta documents cases where WhatsApp accounts become restricted during Embedded Signup/onboarding, including before a phone number is fully configured. I would not create another Business Portfolio/WABA to bypass the restriction. The safer route is to appeal/review the restricted Business Portfolio with Meta first. If Meta clears it, Botpress officially supports Manual Configuration with your own Meta Developer App, so we can proceed that way without creating a replacement business identity. I can help diagnose the restriction and set up the manual Botpress–WhatsApp configuration once Meta confirms the account is eligible. @microscopic-greece-72903

I got fed up with Meta too and I wasn't even using a bot just manually sending messages (about 5-10 strangers every day). And they kept restricting my WhatsApp cutting me off from the platform I trusted with to reach out to my friends and family. As a developer, I got really pissed and so Wazzup.im was invented. It's in very early stages but functional. Please buy early bird $5 premium to help me further my development including allowing unlimited bot access and unlimited backups.

Thanks for the clarification. The problem is that I have already appealed the restriction with Meta. Meta reviewed it and informed me that the decision is final and cannot be reversed. The Business Portfolio was newly created specifically for Alberto Coaching, and the restriction appeared during the WhatsApp/Botpress onboarding process. There was no spam, bulk messaging or previous WhatsApp automation activity. Since Meta says the restriction cannot be appealed any further, what would be the correct compliant next step? I specifically do not want to create another Business Portfolio or WABA if Meta could consider that circumvention. Is there any Meta support/escalation route you recommend for this specific Embedded Signup restriction, or any information/IDs from Botpress that I should provide to Meta so they can understand that the automation detected during onboarding was related to the official Botpress WhatsApp integration? If this Business Portfolio cannot ever be restored, what is the compliant way to proceed with the Botpress–WhatsApp integration without violating Meta’s policies?