Meta WhatsApp

Meta WhatsApp connects your WhatsApp Business Account (WABA) to Zyelra using Meta Embedded Signup. Phone number ID and WABA identifiers are obtained through the connection flow — you do not invent them.

• Outbound WhatsApp from Messaging (templates outside the customer-service window).
• Inbound customer messages and delivery status via Meta webhooks.
• Zyelra template mappings that point at Meta-approved WhatsApp templates.

• A Meta Business portfolio and WhatsApp Business setup eligibility for your business.
• Ability to complete Meta Embedded Signup (business verification may be required for production limits).
• Permission to manage Settings → Messaging & Delivery → WhatsApp.

• Meta Embedded Signup (official) ↗
• WhatsApp message templates (official) ↗

1. Step 1In provider

   Prepare Meta Business & WhatsApp

   Ensure you can access Meta Business Manager / WhatsApp Business assets for the brand that will own the number. Have business details ready for Embedded Signup.

2. Step 2In Zyelra

   Start WhatsApp connection

   Go to Settings → Messaging & Delivery → WhatsApp and start Connect / Embedded Signup for Meta.

3. Step 3In provider

   Complete Embedded Signup

   In Meta’s Embedded Signup UI, create or select the WhatsApp Business Account and phone number. Zyelra stores phone number ID and WABA ID from this flow — do not paste random IDs.

4. Step 4In provider

   Approve message templates in Meta

   Create and submit WhatsApp message templates in Meta Business / WhatsApp Manager. Wait until status is Approved before relying on them in production.

5. Step 5In Zyelra

   Map Zyelra templates to Meta templates

   In Settings → Messaging & Delivery → WhatsApp, sync Meta templates and map Zyelra message types to Meta-approved templates. Mapping is not the same as Meta approval.

6. Step 6In provider

   Confirm webhook subscription (platform)

   Meta must call Zyelra at GET (verify) and POST {your Zyelra API base URL}/api/v1/webhooks/communications/meta. POST payloads are verified with Meta app secret HMAC (X-Hub-Signature-256). Agencies typically inherit platform webhook configuration — do not invent verify tokens.

7. Step 7In Zyelra

   Test inbound, outbound, and status

   Send a test WhatsApp message, reply from a customer phone to open a service window, and confirm delivery statuses update in Messaging.

GET  {your Zyelra API base URL}/api/v1/webhooks/communications/meta  (verification challenge)
POST {your Zyelra API base URL}/api/v1/webhooks/communications/meta  (HMAC-signed events)

1. WhatsApp shows connected with WABA / phone number on file in Settings → Messaging & Delivery → WhatsApp.
2. At least one template mapping is Ready with Meta approved.
3. Outbound test sends; inbound reply appears in Messaging; statuses update.

• Embedded Signup cancelled — restart Connect from Zyelra; do not manually invent phone_number_id values.
• Template send rejected — template not Approved in Meta, or mapping points at the wrong language/name.
• Outside customer-service window — free-form text may be blocked; use an approved template.
• Webhook verify fails — platform Meta app verify token / callback URL must match Zyelra’s meta webhook path.
• HMAC failures — app secret mismatch between Meta app and Zyelra platform configuration (Super Admin / platform ops).