WhatsApp Business Platform

Meta-hosted Embedded Signup

Embedded Signup lets an eligible business authenticate with Meta and connect supported WhatsApp assets through a hosted onboarding experience.

Secure boundary: authentication happens with Meta. Team Supreme configures the server-side flow; never invent a URI or place secrets in frontend code.

Embedded Signup: step-by-step

  1. Confirm the invite: Team Supreme confirms the use case, business, assets, phone plan, and configured Meta-hosted flow.
  2. Start securely: use a current/private browser session where the client signs in as the authorized Meta administrator. Do not share a password.
  3. Review permissions: check the business, WABA, phone, and requested permissions. Stop if assets or the redirect destination are unexpected.
  4. Select assets: choose an eligible existing business/WABA or complete the available create flow. Meta may request verification details.
  5. Finish every screen: a closed tab or skipped step may leave a partial connection.
  6. Confirm the return: Team Supreme records only required non-secret identifiers and confirms the next task.
Pause rule: if the business, permissions, phone, or destination looks wrong, cancel and contact support. Never paste tokens into chat.

What to have ready

  • Admin access to the relevant Meta Business.
  • Phone number meeting current Meta requirements.
  • Business details and display-name context.
  • Privacy, opt-in, and support process.
  • Technical owner for webhook events.
  • Agreement to applicable Meta and Team Supreme terms.

After signup: verify the handoff

  1. Confirm expected business, WABA, phone, and environment identifiers using redacted values in tickets.
  2. Confirm server connectivity and required WABA/webhook subscriptions.
  3. Register/verify the phone, display name, messaging limits, and test recipient.
  4. Submit templates, run controlled messages, and inspect inbound/status events.
  5. Write down owner, revocation path, support contact, and production go/no-go.

Signup is a connection step, not production readiness. Verification, billing, permissions, webhooks, phone registration, template review, testing, and policy checks may still apply.