Coexistence Setup for WhatsApp Cloud API

# WhatsApp Cloud API — Tech Provider + Coexistence Setup (Embedded Signup, Self-Hosted)

## Project overview

We are a UAE-based B2B trading company. Our sales team currently chats with customers using the **WhatsApp Business app** on their phones, and we want to keep it that way. Our goal is to connect those existing numbers to the **WhatsApp Cloud API using Meta's Coexistence feature**, so that the reps keep using the app exactly as they do today, while every message is also mirrored to our own self-hosted backend for logging, monitoring and (in a later phase) CRM integration.

This is **not** a request to set up a BSP dashboard (Wati, Twilio, 360dialog, etc.). We are building this **directly with Meta** and want it owned by our own Meta Business account and infrastructure. You will help us become our own **Meta Tech Provider** and implement the **Embedded Signup coexistence onboarding** flow.

If you have only worked through reseller dashboards and have not implemented Embedded Signup / Tech Provider onboarding yourself, this project is not a fit.

## The outcome we want (Phase 1)

By the end of this engagement:

1. Our business is set up and approved as a **Meta Tech Provider** (business verification + App Review for advanced access to `whatsapp_business_messaging` and `whatsapp_business_management`).
2. A working **Embedded Signup flow with Coexistence enabled** (`featureType: whatsapp_business_app_onboarding`), either self-hosted or via Hosted Embedded Signup.
3. Our **~6 existing sales-rep numbers** (UAE, +971), currently active on the WhatsApp Business app, onboarded to the Cloud API **via coexistence — without removing them from the app.**
4. Webhooks delivering, to our self-hosted endpoint, the full message stream for each number: customer inbound messages, **`smb_message_echoes`** (messages reps send from the app), and the one-time **`history`** / **`smb_app_state_sync`** payloads on onboarding.
5. Verified ability to **send messages via the API** from each rep's number (template and, where applicable, session messages).
6. Clean documentation and a handover call so we can operate and extend it ourselves.

## Scope of work

- Guide us through and configure **Meta Business verification** and the **Tech Provider** setup in the Meta App Dashboard (Partner Solution, app configuration, required permissions).
- Prepare and submit the **App Review** for advanced access to the two WhatsApp permissions, including drafting the permission justifications and the screen-recording walkthroughs (we will record on our account with your script/guidance).
- Implement the **Embedded Signup coexistence flow**: the launch configuration, the page/host (we have a VPS available if self-hosting is needed), capturing the returned code, and the **server-to-server token exchange** for business tokens.
- Implement the **onboarding + synchronization orchestration**, respecting the **24-hour history-sync window** and the one-shot nature of the `smb_app_data` sync calls.
- Configure and verify **webhook subscriptions** (`messages`, `smb_message_echoes`, `history`, `smb_app_state_sync`) delivering to our endpoint, and confirm payloads are received and parseable.
- Prove the full chain on **one number in development mode first** (a paid early milestone), then roll out to the remaining numbers after App Review approval.
- Provide all **source code** (Embedded Signup page, token-exchange service, any helper scripts) in a Git repository, plus written documentation of the setup, tokens/IDs, and how to onboard an additional number in future.

## What we will provide

- Our **Meta Business account** and admin access; we will perform all account-bound actions (verification, App Review submission, screen recordings) ourselves with your step-by-step guidance.
- A **self-hosted automation/webhook environment** (n8n) and a **Linux VPS** for hosting the Embedded Signup page if required.
- The **~6 sales-rep phone numbers**, already active on the WhatsApp Business app (UAE).
- Prompt responses and availability for the account-bound steps and testing.

## Required experience (must-haves)

- Demonstrable, **hands-on WhatsApp Cloud API** integration experience built **directly on Meta**, not via a BSP dashboard.
- Specific experience with **Embedded Signup** implementation and **Tech Provider / Solution Partner onboarding**.
- Specific experience with **WhatsApp Coexistence** (Business app + Cloud API on the same number). This is the core of the project.
- Experience taking an app through **Meta App Review** for `whatsapp_business_messaging` and `whatsapp_business_management` advanced access.
- Solid grasp of **webhooks, the 24-hour customer service window, and template messaging**.
- Comfortable with server-side code for the token exchange and webhook handling. Familiarity with **n8n** is a strong plus.
- Clear written English and the ability to guide a technical client through the Meta-account steps.

## Screening questions (please answer in your proposal)

Proposals that skip these or answer them generically will not be considered.

1. Briefly describe a **WhatsApp Coexistence** project you personally implemented — what was the client's situation and how did you onboard their existing app number(s)?
2. In the Embedded Signup launch configuration, **what value do you set to enable coexistence onboarding**, and on which object?
3. Which **webhook fields** must be subscribed for coexistence, and which one carries messages that a rep sends from the WhatsApp Business app?
4. After a number completes the coexistence flow, what is the **time limit to synchronize messaging history**, and what happens if you miss it?
5. Have you taken an app through **App Review** for `whatsapp_business_management` advanced access? What did Meta require you to submit?

## Phase 2 (future, separate engagement — for context)

Once Phase 1 is stable, we will integrate the message stream with **Zoho CRM** (logging conversations to contact records, sending/follow-ups from within CRM, and automated daily summaries). This is mostly work on our own n8n/Zoho stack.

## Budget & engagement

Fixed-price, **milestone-based**. Suggested milestones:

- **M1 –** Tech Provider configured + business verification complete + App Review submitted.
- **M2 –** Working coexistence flow proven end-to-end on **one number in development mode** (webhooks receiving inbound + echoes; test send working).
- **M3 –** App Review **approved** (advanced access granted).
- **M4 –** All ~6 numbers onboarded to coexistence in production, webhooks verified, send-from-API verified, documentation + handover delivered.

Please propose your price per milestone and a realistic timeline, noting which steps depend on Meta's review queue.

## To apply

Answer the five screening questions, share **links or descriptions of comparable coexistence / Embedded Signup work**, and outline your proposed approach and milestone pricing. Thank you. Show More