Connect through Meta Embedded Signup
Customers use one official Meta-hosted popup. They do not need to copy App IDs, WABA IDs, Phone Number IDs or access tokens into the dashboard.
Have these ready before onboarding
The technical Meta app configuration belongs to the platform owner, not each customer.
Facebook access
Use a Facebook account that can access the correct Meta Business Portfolio for the business.
Business details
Keep the business name, website, email and other business information accurate and consistent in case Meta requests verification.
A phone number you control
Use a number eligible for the onboarding path Meta presents. Existing numbers may require Meta's current migration or coexistence option.
Verification access
Be ready to receive any SMS, voice or in-product verification Meta requests for the selected number.
One Connect WhatsApp button
This is the only normal customer onboarding path in the dashboard.
Open your dashboard
Sign in to Codecraft Messaging Hub and tap Connect WhatsApp.
Meta popup opens
Continue with Facebook inside Meta's hosted Embedded Signup window.
Choose business assets
Select or create the correct Business Portfolio, WhatsApp Business Account and phone number.
Complete Meta checks
Finish any OTP, business verification, number eligibility or permission step Meta requires.
Connection finishes automatically
The platform receives Meta's authorization result, subscribes the WABA webhook and attempts Cloud API phone registration. Your dashboard then shows Connected or Activation Pending.
What CodeCraft Marketing configures once
These are administrator/provider requirements. Customers should not have to perform them for every connection.
Meta App + Embedded Signup configuration
The platform owner configures the Meta Business app, Facebook Login for Business / Embedded Signup configuration, App ID, Config ID and App Secret once for the SaaS.
App Review / Advanced Access
Before broad production release, request the Meta permissions and Advanced Access required by the provider flow, including business_management and whatsapp_business_management where applicable.
WhatsApp messaging permission
The operational token used for phone registration and messaging needs the WhatsApp messaging permission required by Meta for those operations.
Provider System User
When provider mode is enabled, configure the provider Business ID, System User and server-side tokens needed to manage connected customer WABAs.
Webhook configuration
Configure the Meta Webhooks product and verify callback so each connected WABA can deliver inbound messages and delivery/read events to the platform.
Billing model
If Meta provider credit-line billing is used, configure it only after that commercial model is approved. Otherwise keep credit-line mode disabled.
Common setup questions
Embedded Signup finished but dashboard says Activation Pending
Meta returned the WABA and phone IDs but final phone registration did not complete. Check permissions, number eligibility, verification and provider credentials before starting another signup, so you do not create duplicate WABAs.
The number already uses WhatsApp or WhatsApp Business
Do not delete the existing account automatically. Use the migration or coexistence option Meta currently offers for that number and business during onboarding.
Can customers send bulk marketing to any uploaded list?
No. Campaigns require recorded marketing opt-in and Meta-approved templates when applicable. Contacts marked Do Not Message are automatically excluded.
Does Embedded Signup guarantee instant approval?
No. It streamlines the connection process, but Meta still controls App Review, business verification, number eligibility, messaging limits and other account-specific requirements.