Chatflow — incoming messages with BSUID-only identity (WhatsApp usernames) never reach the inbox

We run a WhatsApp funnel on Chatflow (Cloud API, single business number, Spain + Latam markets).

We have started receiving messages from users who have adopted WhatsApp usernames. For these contacts, nothing appears in the Chatflow inbox at all — no conversation, no contact record, no error entry. The flow never triggers. The message is silently dropped.

Per Meta's documentation (https://developers.facebook.com/documentation/business-messaging/whatsapp/business-scoped-user-ids/), when a user adopts a username the wa_id and from fields are omitted from the incoming messages webhook, and the user is identified only by user_id (BSUID, format CC.alphanumeric, e.g. ES.13491208655302741918). BSUID has been present in all message webhooks since April 2026, and Meta states that supporting it is required for all partners and directly-integrated businesses.

Could you confirm the following, specifically:

1. Does Chatflow currently ingest incoming message webhooks where wa_id / from are absent and only user_id (BSUID) is present? Our observation is that it does not, and that the drop is silent — no inbox entry and no error logged. Please confirm or correct this.

2. Are user_id (BSUID) and profile.username exposed inside flows as usable variables, and are they forwarded to API Request nodes and to Pabbly Connect?

3. Does POST https://chatflow.pabbly.com/api/v1/messages accept a BSUID recipient (Meta's recipient parameter) as an alternative to to?

4. Does Chatflow support sending Meta's request_contact_info interactive message, or the REQUEST_CONTACT_INFO template button, so we can ask a user to share their phone number in-thread?

5. For anything not yet supported: what is the target date? Meta's username rollout reaches the rest of the world from September 2026, which includes our markets.

Meta provides a webhook test tool that simulates the scenario "user has adopted a username and phone number is unavailable" (App Dashboard > WhatsApp > Configuration > messages webhook > Test). Could you run that against Chatflow's endpoint and share the result? That would settle question 1 definitively.

This is currently causing silent lead loss at the entry point of our funnel. A clear answer — including "not supported yet, no date" — is more useful to us than a workaround.

Thank you.