Embedded Signup is a Meta flow shown inside a provider's onboarding experience. It lets your business authorize account and number setup without handing the provider your personal Meta login.
Who should start Embedded Signup?
Use the Meta login for the business portfolio owner or an administrator with permission to manage its WhatsApp assets. The person completing the flow approves what the provider can connect.
Keep the administrator in control of the Meta account. Asking a provider to impersonate that administrator risks losing control of the assets and permissions. The business owner should review the assets, permissions and terms in the Meta dialog before confirming.
Which assets does the flow connect?
The flow can connect a Meta business portfolio, a WhatsApp Business Account and a phone number to the provider's integration. The exact choices depend on whether you create a new account or select an existing one.
| Asset | Confirm before continuing |
|---|---|
| Business portfolio | The legal business and administrator are correct |
| WhatsApp Business Account | The account is the one your team intends to operate |
| Phone number | The number is available for the selected WhatsApp setup |
| Provider connection | The provider and workspace receiving the connection are correct |
The provider can operate the connected assets. Your business remains responsible for the account's policies, customer permission and message content. Review Meta's WhatsApp Business policy before authorizing access.
What happens during the flow?
The provider opens Meta's Embedded Signup dialog in its dashboard. You sign in, choose or create the business assets, provide the requested business details, and authorize the provider connection.
Phone verification can be a separate step. Follow the number checks in Bird's WhatsApp number guide before starting if you are unsure whether the candidate number can connect.
What is still incomplete when the dialog closes?
When the dialog closes, verification, connection and sending may still be incomplete. The browser flow has returned, but Meta may still be processing the assets.
Bird's completion operation is dashboard-only. A backend request cannot reproduce the administrator's consent and asset selection, so do not build a public API integration around it.
In Bird, read the connected number's status and next fields. status can report pending, connected, failed or error. While signup awaits a browser step, next carries that guidance. Poll the resource after completing the flow instead of treating the redirect as a successful send test.
How do I check signup readiness?
Before the flow, confirm:
- The administrator can access the correct Meta business portfolio.
- The business details and account ownership are ready for review.
- The phone number is available for this connection path.
- The provider workspace is the one that should receive the account.
After the flow, confirm the account, number status, verification result and a real test send. Keep the Meta account owner and provider support contact recorded for recovery.
In short
Bring the right administrator.
The owner or an administrator of the Meta business portfolio must complete the consent and asset steps.
Prepare the number and business.
Have the business portfolio, WhatsApp Business Account details and a number ready for the provider's connection flow.
Expect work after signup.
Closing the dialog does not prove verification, number connection or send readiness. Follow the reported status.
Keep ownership clear.
Confirm which business portfolio, account and number the provider connects before you authorize the flow.