Hello Meta developer community,

I am the legal owner of a Mexican business and I have been blocked for several days from administering a WhatsApp Business Account (WABA) that lives inside my own Business Portfolio. I am posting here because two Direct Support tickets on this exact issue have been auto-closed by the Meta AI Agent within seconds, without any human review, despite providing complete ownership documentation.

I am asking the community (and any Meta engineer who may be monitoring this forum) for guidance on how to escalate this case to a human reviewer.

═══════════════════════════════════════════════════ PROBLEM ═══════════════════════════════════════════════════

Inside my Business Portfolio "Nichiboku Querétaro" (BM ID: 496836770171931) there is a WABA called "Nichiboku Nippori" (WABA ID: 1334748968204825) that contains my business phone number +52 744 819 0251.

This number is actively used for: - Customer support with current students - Receiving leads from active Click-to-WhatsApp ad campaigns

The original administrator of this WABA is no longer associated with my business and cannot be contacted. As a result, my user has lost admin permissions on the WABA, even though:

• I am the legal owner of the business
• I am full admin of the parent Business Portfolio
• The WABA appears listed inside my Business Portfolio
• The phone number is registered to my name and RFC

When I open WhatsApp Manager for this WABA, I get the error: "You don't have access to WhatsApp Business account 1334748968204825. Contact the account owner to request access."

This blocks me from migrating the number, connecting it to a new app for Cloud API integration, or performing any administrative action.

═══════════════════════════════════════════════════ WHAT I HAVE TRIED ═══════════════════════════════════════════════════

1. Direct Support ticket #1 (April 8, 2026) — closed within minutes by Meta AI Agent with a generic templated response asking for documentation. No way to upload anything or reply.

2. Direct Support ticket #2 (April 8, 2026, 7:23 PM) — submitted with ALL ownership documents attached upfront, marked as human escalation request. Closed in the same minute by Meta AI Agent with another templated response asking me to "confirm I attached the documents that were already attached and visible in the case panel."

3. I have NOT touched the phone in WhatsApp Business app, to avoid losing the customer chat history or pausing my live ad campaigns.

═══════════════════════════════════════════════════ WHAT I AM ASKING ═══════════════════════════════════════════════════

1. Is there a working escalation path for "lost WABA admin access — original admin no longer available" that bypasses the AI Agent auto-close loop?

2. Has anyone in this community recently recovered admin access to a WABA in similar circumstances? What worked for you?

3. If a Meta engineer is reading this: would it be possible to route case ID 27222089484061524 to a human reviewer? All ownership documentation is already attached in that case.

I am willing to provide any additional documentation or proof of ownership through any channel a Meta employee can suggest.

Thank you in advance for any guidance.

— Juan Pablo Chacón Merino Owner, Nichiboku Querétaro Business Portfolio ID: 496836770171931 Affected WABA ID: 1334748968204825