Verified provider onboarding

Getting started with Meta integrations

Team Supreme is a verified Meta business and verified WhatsApp Tech Provider. Eligible clients can onboard under Team Supreme for supported Meta business workflows.

Important: provider status is not a guarantee of client verification, app review, template approval, delivery, capability access, or account restoration. Meta makes those decisions.

1. Prerequisites

Mark each item ready, blocked, or eeds Meta confirmation before sending a connection link.

  1. Business owner: identify the legal business, administrator, support contact, and person who can approve access changes.
  2. Assets: list the Meta Business, WABA, phone, Instagram professional account, Page, ad account, and domains. Record the owner of each.
  3. Use case: document the customer journey, markets, message categories, expected volume, opt-in source, opt-out wording, and retention needs.
  4. Technical owner: name the person responsible for HTTPS endpoints, secrets, webhook events, retries, logs, and incidents.
  5. Compliance materials: prepare business details, privacy notice, terms, data-processing explanation, and documents Meta may request.

2. Meta dashboard setup

  1. Open Meta Business Suite / Business Settings and confirm the correct business is selected.
  2. Review people, partners, system users, asset assignments, two-factor authentication, and billing contacts. Remove stale access.
  3. Open the relevant developer app, or create one only when the selected workflow requires it. Record the app/environment owner.
  4. Check WhatsApp, Instagram, Page, domain, and ad-account assets against the use-case map. Do not grant broad access “just in case”.
  5. Capture redacted evidence of the final configuration and keep original screenshots private.

3. Client onboarding process

  1. Intake: collect use case, assets, owners, markets, and safe contact details.
  2. Readiness review: resolve missing admin access, phone, domain, opt-in, permissions, or policy evidence.
  3. Guided connection: send the configured Meta-hosted flow; the client authenticates directly with Meta.
  4. Technical configuration: connect server-side credentials, WABA/phone, webhooks, templates, and test environments.
  5. Handover: document ownership, revocation, monitoring, support contacts, and the production go/no-go decision.

4. Readiness checklist

  • Admin access to the relevant Meta Business assets.
  • Eligible phone number and clear display name.
  • Verified domain, privacy notice, and terms where required.
  • Documented customer opt-in and opt-out process.
  • Named technical owner for webhooks and incidents.
  • Safe support process with no credential sharing.

Recommended lifecycle

  1. Discover: map use case, data, markets, assets, and ownership.
  2. Prepare: confirm roles, domains, phones, documents, and environments.
  3. Connect: authenticate directly with Meta through the hosted flow.
  4. Configure: set permissions, webhooks, phone registration, templates, and tests.
  5. Validate: test delivery, statuses, retries, opt-outs, revocation, and failures.
  6. Operate: monitor quality, policy changes, access, incidents, and escalation.

Never send access tokens, app secrets, system-user tokens, or unredacted customer data in a support request.