WhatsApp Embedded Signup & Tech Provider Onboarding: Connecting Client Numbers at Scale
If your platform needs to connect dozens or hundreds of client WhatsApp numbers, the basic Cloud API setup is not enough. You need the Tech Provider program and Embedded Signup — and that is where most SaaS projects get stuck.
Connecting a single WhatsApp number to the Cloud API is one thing. Onboarding many client numbers through your own product — so each customer keeps ownership of their WhatsApp Business Account while your platform sends and receives on their behalf — is a completely different setup. This is what the Tech Provider program and Embedded Signup are built for, and it carries real configuration and review hurdles that a basic setup guide never mentions.
Two pieces that work together
Tech Provider program
Meta's program for software companies (ISVs/SaaS) that onboard other businesses onto WhatsApp. It lets your business act on behalf of your clients, each on their own WhatsApp Business Account, instead of forcing every client to build their own integration.
Embedded Signup
The "Login with Facebook" popup flow you embed in your product. The client signs in, creates or selects a Meta Business Portfolio, picks or adds a phone number, accepts terms, and your app receives the credentials — all without leaving your UI. If a client already uses the WhatsApp Business app on the number, WhatsApp Coexistence lets the app and Cloud API run together during onboarding.
Why this is harder than a single-number setup
Business Verification dependency
Higher messaging limits and Official Business Account status depend on Meta Business Verification — for your own business and, often, your clients'. An unverified portfolio caps what the integration can do.
The configuration ID
Embedded Signup runs against a configuration (config_id) you set up in the App Dashboard. Get the permission set or the configuration wrong and the popup either fails or onboards clients with the wrong access.
Permissions & tokens
The flow needs the correct WhatsApp business permissions selected — and the right token strategy (such as system-user access) so onboarded numbers keep working past short-lived user tokens.
On-behalf-of ownership
Clients must retain ownership of their own WhatsApp Business Account while your app operates it. Getting the OBO relationship right matters for trust, billing, and access revocation.
What the onboarding flow involves (high level)
Register as a Tech Provider
Set up your Meta app and business correctly for the Tech Provider use case before any client onboarding.
Configure Embedded Signup
Create the configuration, select the correct WhatsApp business permissions, and capture the configuration ID Meta provides. Embedded Signup runs against a config_id instead of classic scopes, and our Facebook Login for Business vs Facebook Login guide explains why business apps use config_id.
Embed the signup button in your product
Add the launch button and handle the callback so your app receives the account and phone number details when a client finishes the flow.
Handle credentials & tokens
Exchange and store the credentials securely so each onboarded number keeps sending and receiving reliably. Onboarded numbers keep working past short-lived user tokens only with the right token strategy, and our Meta system user access tokens guide explains admin, employee, and BISU tokens.
Resolve Business Verification
Ensure verification is in place so messaging limits and account status are not stuck at the lowest tier.
We deliberately keep the exact configuration values, permission combinations, and token handling out of this article — those details are where onboarding breaks, and getting them wrong can lock you out or onboard clients incorrectly. That precise implementation is the work we do for you.
The end result
A working Embedded Signup flow inside your product where clients connect their own WhatsApp number in a few clicks, your platform sends and receives on their behalf, and ownership and verification are set up cleanly — instead of a half-finished integration that stalls at verification or token errors.
Where these projects most often stall
- Trying to scale client onboarding on a basic single-number Cloud API setup instead of the Tech Provider model.
- Business Verification not completed, so messaging limits and account status stay capped.
- Wrong permissions selected in the Embedded Signup configuration, breaking the popup or onboarding the wrong access.
- Short-lived tokens used where a durable token strategy is required, so numbers stop working after a while.
- Phone number assignment and ownership handled incorrectly, creating access and billing confusion later.
Note: WhatsApp and Meta control program eligibility, verification outcomes, and account status. This is review-preparation and technical implementation support — not a guaranteed outcome, and not an official partnership claim.
Related reading on this site: the WhatsApp Business API setup guide for single-number basics, the Meta Business Verification guide for the verification gate, and the WhatsApp App Review service page for done-for-you support.