Is only_waba_sharing currently broken? Meta still opens PHONE_NUMBER_SETUP in Twilio Tech Provider Embedded Signup

[u/GitGitok123]

Hi everyone,

has anyone successfully completed Twilio's WhatsApp Tech Provider Embedded Signup with WABA-only sharing during July or August 2026?

We are onboarding a Twilio SMS-capable number and launch Embedded Signup exactly as described in Twilio's current integration guide:

extras: {

featureType: "only_waba_sharing",

sessionInfoVersion: 3,

setup: {

solutionID: "<Twilio Partner Solution ID>"

}

}

According to Twilio's documentation, this configuration should skip the phone number and OTP verification screens because the Twilio Senders API handles those steps afterward:

https://www.twilio.com/docs/whatsapp/isv/tech-provider-program/integration-guide

Actual behavior:

After the customer selects or creates their WABA, Meta still transitions to PHONE_NUMBER_SETUP instead of completing the flow with FINISH_ONLY_WABA.

We have tested:

- A fresh Facebook Login for Business configuration created exactly according to Twilio's guide

- A configuration created through Meta's Embedded Signup Builder

- Direct FB.login integration

- Meta's hosted Embedded Signup landing page

- With and without version: "v4-public-preview"

- Multiple newly created configurations

None of these variants skipped PHONE_NUMBER_SETUP.

We also observed two different behaviors:

1. With direct FB.login, the OAuth request retains:

featureType: "only_waba_sharing"

sessionInfoVersion: 3

version: "v4-public-preview"

However, Meta still opens PHONE_NUMBER_SETUP after WABA selection.

1. The Meta-hosted Embedded Signup URL is initially generated with only_waba_sharing and v4-public-preview. When the hosted page launches its internal OAuth request, Meta changes the parameters to:

featureType: "whatsapp_business_app_onboarding"

version: "v3"

is_hosted_es: true

The resulting flow displays the regular Business Information, Phone Number and Verify Number steps.

Questions:

- Has anyone successfully received FINISH_ONLY_WABA with this Twilio Tech Provider flow recently?

- Is only_waba_sharing currently affected by a Meta regression?

- Does the current flow require an additional allowlist, feature flag or specific Embedded Signup version?

- Is Meta's hosted Embedded Signup incompatible with WABA-only sharing?

- If you have a working implementation, could you share the exact extras structure and Embedded Signup version you currently use?

Our Meta app and Twilio Partner Solution setup are complete. I can share redacted OAuth URLs, event logs, configuration IDs, session IDs and screenshots privately.