WhatsApp Business messages only arrive from the admin's own number — Advanced Access granted, still broken

[RolandGraf]

Hi all,

We've been stuck on this for over two weeks and have run out of things to check ourselves. Hoping someone here has seen this before.

Setup:

• 3CX PRO Edition v20
• WhatsApp Business number: 058 000 00 00 (Meta App "3cx-WA", App-ID *************)
• Routed via Queue (Trunks & Chat → WhatsApp → Standard route)

Symptom:
Incoming WhatsApp messages only arrive in 3CX when sent from the account owner's own (admin) phone number. Messages from any other number — tested repeatedly with a colleague's phone, a genuine customer number — simply never arrive. No error, no bounce, nothing. The chat just never appears in 3CX.

Root cause we found (but fixing it didn't help):
Under Meta App Dashboard → App Review → Permissions and Features, whatsapp_business_messaging was set to Standard Access (no App Review requested). With Standard Access, a WhatsApp Business app can only exchange messages with people who have a role on the app (Admin/Developer/Tester) — which explained why only the admin's own number worked.

We submitted an App Review request on 21.07.2026 for Advanced Access, including a screen recording of the full flow (WhatsApp message to our number → arrival in 3CX). It was approved on 04.08.2026 (App Review Submissions page shows "Einreichung genehmigt", whatsapp_business_messaging = Approved, no outstanding items).

Problem: identical symptom persists after Advanced Access was granted. A fresh test today (05.08.2026) from a non-admin number still doesn't arrive in 3CX — same as before the grant.

What we've additionally ruled out:

• License: PRO edition, includes WhatsApp + Queues ✓
• Meta App Mode: Live and publicly available (since 09.02.2026) ✓
• Webhook subscription: "messages" field correctly subscribed ✓
• Server reachability: webhook URL responds HTTP 400 externally (not a timeout) ✓
• Phone Number ID: identical between Meta and 3CX config ✓
• Routing: confirmed Queue, not Ring Group ✓
• No stale/stuck test chats (archived) ✓
• Not a Meta test number (058 000 00 00 is the real registered number, no test-number flag, no recipient allow-list) ✓
• Business Verification: completed since 09.02.2026 ✓
• Meta Activity Log: no configuration changes around the time of the Advanced Access grant — so nothing seems to have been silently reset ✓

Our 3CX reseller (PCETERA) couldn't help beyond suggesting a license upgrade (which we already have — PRO).

Has anyone run into WhatsApp messages from external numbers being silently dropped even with Advanced Access granted? Is there a propagation delay we're missing, or a separate setting (e.g. at the WABA / phone number level, not the app level) that also needs to be flipped?

Any pointers greatly appreciated — this number is on all our active maintenance contracts, so it really needs to work reliably.

Thanks in advance!

 

[CXBridge Ops]

Hi @RolandGraf

Check this: https://developers.facebook.com/documentation/business-messaging/whatsapp/support/health-status

 

[RolandGraf]

**Thanks for the pointer to the health_status feature — followed up on this today:**

1. Checked `health_status` via Graph API Explorer for our phone number. Result: `can_send_message: LIMITED`, but the reason given is "display name has not been approved yet" — an unrelated outbound-messaging limit, not a receiving issue. WABA/Business/App all show `AVAILABLE`.

2. Checked WhatsApp Manager → Phone Numbers → Insights: our number shows **14 received messages** in the last 30 days. So Meta is clearly registering inbound messages — this contradicts a full block on external numbers at Meta's level.

3. Decisive test: used the Webhook Field Sample tool in the App Dashboard (`messages` field, v25.0) with the built-in "Incoming Message" sample (from a foreign test number, not our own). Sent it to our server — result: **"Webhook field messages v25.0 was successfully tested"** at the timestamp. So Meta successfully delivers a simulated incoming-message payload from a foreign number to our 3CX webhook endpoint, and 3CX responds with success (HTTP 200).

**Conclusion:** This points away from Meta entirely. The webhook is received successfully by 3CX even for unknown/foreign numbers — so the issue must be in how 3CX processes the payload *after* receiving it (e.g. some filter/routing logic that only surfaces messages as a visible chat for numbers with an existing contact/role, silently dropping others). Would appreciate any insight into how 3CX's WhatsApp integration decides whether to create/display a chat from an incoming webhook payload.

 

[RolandGraf]

Hi all — following up again on this thread. It's now been over 3 weeks since we first reported this (webhook delivery confirmed successful via Meta's own test tool, HTTP 200 from 3CX, yet messages from any number other than the account owner's own still don't appear in 3CX). If anyone else has run into the exact same "only my own WhatsApp number gets through" symptom, we'd really appreciate hearing how you resolved it. Happy to share our full diagnostic writeup if useful.

 

[CXBridge Ops]

It’s interesting that Meta shows all messages as successfully received, while they do not appear in 3CX. Please perform the following tests and check whether the logs provide any key information.

First, set the 3CX logging level to Verbose, and then run these two separate tests:

TEST A

• Sender: Administrator’s number
• Expected result: The chat appears in 3CX

TEST B

• Sender: External customer
• Current expected result: The chat does not appear in 3CX

Please let me know what you are able to capture in the logs for each scenario, particularly for Test B and any entries related to WhatsApp.