WhatsApp Onboarding Options Explained: WABA, Coexistence, and More
A practical comparison of how businesses connect WhatsApp — from the Business app alone to Cloud API with a new WABA, coexistence on an existing number, or migration from another provider.
Most UAE businesses already chat with customers on WhatsApp. The hard part is not “should we use WhatsApp?” — it is how to connect so the same number can support a team, templates, campaigns, AI, and CRM without breaking day-to-day conversations.
Meta’s WhatsApp Business Platform supports several onboarding paths. The right one depends on whether you already use the WhatsApp Business app, whether you can spare a new number, and whether you are switching providers.
This guide compares the main options, their features and trade-offs, and how Commbots helps you pick a path that matches your operations.
Why the onboarding option matters
Onboarding is not only a technical checkbox. It decides whether you keep your existing chat history and phone number, whether agents can work in a shared inbox, and how quickly you can send approved templates at scale.
Choosing the wrong path can mean re-registering a number, confusing customers with a new line, or delaying go-live while you migrate templates and permissions.
For a broader UAE setup overview, see our WhatsApp Business API UAE guide.
The four paths at a glance
WhatsApp Business app only
One device (or limited linked devices). Fine for a solo founder — not built for multi-agent inbox, Cloud API automation, or high-volume templates.
New WABA (Cloud API)
Create a WhatsApp Business Account and register a number for Cloud API through Embedded Signup. Best when you can use a new or unused number.
Coexistence (existing app)
Keep using the WhatsApp Business app on the same number while connecting Cloud API for teams, templates, and platforms like Commbots.
Migrate from another BSP
Move an existing Cloud API / WABA setup from another solution partner to Commbots — preserve the number and rebuild operations on a better stack.
Option 1: WhatsApp Business app only
The WhatsApp Business app is the familiar green-icon app on a phone. It is ideal for very small teams that answer chats personally and do not need CRM sync, AI bots, or multi-agent assignment.
Limitations show up quickly: one primary device mindset, weak team collaboration, and no official Cloud API access for automation, webhooks, or large template campaigns.
Many UAE businesses start here — then outgrow it when sales and support need the same number at the same time.
Best when:
- You are a solo operator or tiny team
- Volume is low and personal replies are enough
- You are not ready for Meta Business verification and templates yet
Trade-offs:
- No shared inbox with assignment and reporting
- No native Cloud API for AI, CRM webhooks, or bulk campaigns
- Hard to scale without risking account quality or chaotic handovers
Option 2: New WABA via Embedded Signup (Cloud API)
A WhatsApp Business Account (WABA) on the Meta Business Platform is the foundation for Cloud API. Through Embedded Signup, a partner such as Commbots guides you to create or select a WABA, attach a phone number, and grant messaging permissions.
This path typically uses a new number or a number that is not already active on the WhatsApp Business app as your production Cloud API line. After go-live you get templates, webhooks, multi-agent access, and platform features such as a shared inbox, AI chatbot, and WhatsApp campaigns.
It is usually the cleanest setup when brand identity can live on a dedicated business number.
Features and benefits:
- Official Cloud API messaging with approved templates
- Multi-agent access without sharing a single phone
- Automation, AI, and CRM integrations on one number
- Clear ownership inside Meta Business Manager / Portfolio
- Easier long-term scaling for UAE sales and support teams
Watch-outs:
- Customers must be told if you change to a new number
- Display name and Business verification may be required
- Templates need approval before marketing or utility blasts
Option 3: Coexistence — keep the Business app, add Cloud API
Coexistence (Meta also calls this onboarding WhatsApp Business app users) lets you connect an existing WhatsApp Business app account and phone number to Cloud API.
After a successful coexistence onboarding, your team can send higher-volume and automated messages through a platform like Commbots, while still using the WhatsApp Business app for one-to-one chats. Messaging history can stay in sync between the app and the API-connected tools.
This is the preferred path when your customers already know a number and you cannot afford downtime or a number change.
Features and benefits:
- Keep the phone number customers already save and message
- Continue using the Business app for personal or owner chats
- Unlock Cloud API for teams, templates, AI, and campaigns
- Reduce customer confusion versus launching a brand-new number
- Bridge “app-only” operations into a full platform workspace
Watch-outs:
- Not every number or app version is eligible — validate first
- Teams must agree who replies in the app vs the shared inbox
- Sync and webhook setup must be completed carefully after signup
- Governance matters: clear rules prevent duplicate replies
Option 4: Migrate an existing WABA from another BSP
If you already run Cloud API with another Business Solution Provider, you may not need a new number — you need a partner migration (or host migration) onto Commbots.
The goal is to keep the same WhatsApp number and WABA assets where Meta allows, while moving day-to-day operations — inbox, campaigns, AI, and integrations — to Commbots.
This path is common for UAE teams that outgrew their first BSP’s inbox, pricing, or support model.
Features and benefits:
- Preserve customer-facing number continuity
- Move to Commbots shared inbox, AI, and CRM-ready workflows
- Often faster than educating customers on a new line
- Chance to clean up templates, agents, and routing rules
Watch-outs:
- Migration steps depend on Meta and the current partner
- Plan a cutover window so agents know where to reply
- Re-test templates, webhooks, and quality ratings after move
New WABA vs coexistence — quick contrast
New WABA (new / free number)
- Cleanest Cloud API start
- Best if a new brand number is acceptable
- No need to keep the Business app on that line
- Customers may need a number update
Coexistence (existing Business app)
- Keep the number customers already use
- App + API can run together
- Ideal when brand equity is on the current line
- Needs eligibility checks and reply governance
Side-by-side: features you unlock with Cloud API
Whether you choose a new WABA or coexistence, Cloud API is what unlocks platform features. The Business app alone cannot match this stack.
What Commbots adds after you connect
Shared team inbox
Multiple agents, assignment, history, and supervision on one official number.
Approved templates & campaigns
Utility, marketing, and service journeys with measurable delivery and replies.
AI chatbot + handover
Bilingual first response with clean transfer to humans when needed.
CRM and ERP integrations
Push leads and conversation context into HubSpot, Odoo, or your stack.
How to choose the right onboarding path
Use this decision order with your Commbots specialist:
- 1
Inventory your current number
Is it on WhatsApp Business app, personal WhatsApp, another BSP, or unused? Eligibility differs for each case.
- 2
Decide if the number is sacred
If customers already save it and ads point to it, prioritise coexistence or BSP migration over a brand-new line.
- 3
Confirm Meta Business readiness
Portfolio access, display name, and verification status affect how fast Embedded Signup completes.
- 4
Pick the operational model
Define who replies in the app (if coexistence) versus the Commbots inbox, plus AI and campaign owners.
- 5
Go live with templates and training
Submit core templates, connect inbox users, and run a short pilot before full marketing volume.
How Commbots supports each option
Commbots is built for UAE and GCC teams that need official WhatsApp connectivity plus day-to-day operations — not raw credentials alone.
Whether you start with a new WABA, coexistence on an existing Business app number, or a partner migration, our team maps the Meta steps, then configures inbox, templates, AI, and integrations so go-live is usable on day one.
Explore the product surface on WhatsApp Business API, or view plans when you are ready to purchase.
Frequently asked questions
What is a WABA?+
A WhatsApp Business Account (WABA) lives in your Meta Business Portfolio and holds your WhatsApp Business assets — phone numbers, templates, and Cloud API access — used by platforms like Commbots.
What does coexistence mean?+
Coexistence lets you connect an existing WhatsApp Business app number to Cloud API so you can keep using the app for one-to-one chats while also running team inbox, templates, and automation through a partner platform.
Can I keep my current WhatsApp Business app number?+
Often yes, via coexistence if the number and app version are eligible. If coexistence is not available, you may need a new number for Cloud API or a structured migration plan with your partner.
Is Embedded Signup required?+
For most modern partner onboarding, yes. Embedded Signup is Meta’s guided flow to create or connect a WABA and grant the partner permission to message on your behalf.
What if we already use another WhatsApp BSP?+
You can usually plan a migration to Commbots to keep the same customer-facing number while moving inbox, AI, and campaigns. Timing depends on Meta rules and your current provider.
Which option is best for UAE SMEs?+
If customers already message your Business app number, start by checking coexistence. If you are launching a dedicated support or sales line, a new WABA is often faster and cleaner.
Does Commbots help choose the path?+
Yes. Book a demo and our Dubai team will review your current number, Meta assets, and goals — then recommend new WABA, coexistence, or migration before you change anything.
Keep exploring Commbots
Not sure which onboarding path fits you?
Commbots helps UAE teams choose between a new WABA, coexistence on your current Business app number, or a partner migration — then go live with inbox, templates, and AI.