Meta Embedded Signup

Connect WhatsApp without technical setup

Lead to Deal uses Meta Embedded Signup so each developer or brokerage connects its own WhatsApp Business number. The company admin grants access in Facebook, and the platform handles tokens, webhooks, channel health, and AI routing.

Get started

Before you start

What the company admin needs

Correct Facebook admin

Log in with a Facebook user who can manage the customer business portfolio, WhatsApp Business Account, and phone number.

Business phone access

The phone number must be able to receive an SMS or voice call if Meta asks for verification. If the number is already connected elsewhere, that provider may need to release it.

Six-digit PIN if requested

For Cloud API registration, Meta may ask for the phone number's two-step verification PIN. Use the existing PIN or set a new one in Meta.

Meta permissions

During signup, approve WhatsApp business management and messaging permissions so Lead to Deal can subscribe the channel and send approved replies.

Choose the right path

Two supported setup modes

Default

Cloud API number

Use this for a new WhatsApp Business Platform number, a migrated number, or a number dedicated to AI sales automation.

When available

WhatsApp Business App coexistence

Use this when the company already works from the WhatsApp Business mobile app and Meta enables coexistence for that account and number.

What happens in the app

Connection walkthrough

  1. 1

    Choose whether the number is a Cloud API number or an existing WhatsApp Business App number.

  2. 2

    Add a readable label and optionally dedicate the number to one project.

  3. 3

    Click Connect WhatsApp via Facebook and complete Meta Embedded Signup in the popup.

  4. 4

    Select the customer's business portfolio, WhatsApp Business Account, and phone number.

  5. 5

    Approve the requested WhatsApp permissions. Lead to Deal exchanges the temporary code on the server and stores customer secrets securely.

  6. 6

    Send a test WhatsApp message to the connected number, then confirm inbound and outbound health from Settings.

Handled by Lead to Deal

What the platform does automatically

  • Exchanges Meta's temporary authorization code on the server, not in the browser.
  • Stores customer channel credentials securely and keeps tokens out of the UI.
  • Subscribes the customer WhatsApp Business Account to the platform webhook.
  • Routes every inbound message by phone number ID to the correct tenant, inventory, dialect, and human handoff rules.
  • Tracks channel health, last inbound, last outbound, webhook status, and reconnect warnings.

After connection

What to test before go-live

  • Send a real inbound WhatsApp message from a personal phone and confirm it appears in the inbox.
  • Send a safe outbound test message and check the customer receives it.
  • Confirm the AI only recommends uploaded projects, units, prices, payment plans, images, offices, and agents.
  • Run one Arabic and one English conversation if the company sells across Egypt and the GCC.
  • Submit the company setup for platform approval before routing paid campaign traffic.

Common blockers

If Meta stops the flow

Wrong Facebook account

Ask the business owner to add the current user as an admin on the business portfolio and WhatsApp assets, then retry.

Number already connected

Check whether the number is still linked to another BSP, Cloud API app, or Business App setup that does not support coexistence.

No verification code

Confirm the SIM, landline, IVR, or call forwarding setup can receive Meta's SMS or voice call during the session.

Coexistence missing

Use the standard Cloud API setup if Meta does not show Business App coexistence for that customer, region, or number.

Reconnect warning

Reconnect from Settings if token health, webhook subscription, or channel permissions are no longer valid.

Quality or rate limits

Review Meta quality signals, message volume limits, and template policy before scaling paid campaigns.

Source material

Official Meta references