// Decision guide
Short answer: if one or two people reply by hand from one phone and you only answer customers who write first, stay on the WhatsApp Business app. If several staff share the number, or you need reminders, an AI agent, CRM sync or approved template messages, move to the WhatsApp Business Platform (Cloud API), usually through a provider that supplies the inbox, or directly through a developer when the integration is the point. If you want both, keep answering from the phone app while software automates the rest on the same number, and ask a provider for coexistence. The matrix below compares the setups dimension by dimension. Every Meta fact on this page was checked against Meta's and WhatsApp's own documentation on November 2, 2026, and is linked in the sources.
Most comparisons frame this as app versus API. In practice a small business picks one of four routes: the WhatsApp Business app on a phone; the WhatsApp Business Platform through a provider (often called a BSP, Solution Partner or Tech Provider) that gives you an inbox; the Cloud API connected directly by a developer; or coexistence, where one number runs on the app and the Cloud API at the same time.
The app is a product for people. WhatsApp describes it as built with the small business owner in mind, with a business profile, product showcase, and greeting and away messages. The Cloud API is a product for software: Meta's documentation describes it as a way to programmatically message and call on WhatsApp, sending through the Graph API and receiving through webhooks. It has no team inbox of its own; Meta's WhatsApp Manager is for managing accounts, numbers, templates and analytics, not for replying to customers. The Lebanon-specific setup checklist is in the companion answer at tarekrjeily.com/answers/whatsapp-business-api-lebanon.
| WhatsApp Business app | Business Platform (Cloud API via a provider or direct) | |
|---|---|---|
| Who it suits | An owner or a small team replying by hand from one number | Teams that share a number, automate messages, or connect WhatsApp to other software |
| Setup steps | Install the app, register the number, complete the business profile | Business portfolio, WhatsApp account, number verification and display name; through a provider's Embedded Signup or a developer's direct connection |
| Meta business verification | Not part of everyday app use | Optional to start; verification factors into higher throughput, Official Business Account status, and higher message and phone-number limits |
| Number handling | The number lives in the app on the owner's phone | A number already on WhatsApp must be deleted there before registration, unless you use coexistence; new portfolios start with two registered numbers |
| Multi-user inbox | Designed around the owner and their devices, not a staffed team inbox | No inbox in the API itself; a provider supplies one or a developer builds one |
| Automation and AI agents | Greeting and away messages; no programmable access for your own software | Webhooks and templates allow reminders, routing and AI agents; automated replies need a clear path to a human, and general-purpose AI assistants as the main product are prohibited |
| CRM integration | No official connection; records are copied or retyped by hand | Every message arrives by webhook, so it can be written to your CRM or a provider's integration |
| Template messages | Not applicable; you message people by hand | Required outside the 24-hour customer-service window; approved by Meta and categorised as marketing, utility or authentication |
| Cost layers | Meta's per-message Platform fees do not apply; check WhatsApp's pages for any paid app features | Meta's per-delivered-message fees by category and recipient country, plus provider fees, any build work, and maintenance |
| Arabic and English | Type in any language; every reply is manual | Template languages include a general Arabic code plus regional codes such as ar_AE and ar_LB; Meta does not translate template text, so you write each language version |
| Risk of number bans | Terms require opt-in, ban spam and unapproved apps that interact with the app; WhatsApp can throttle, suspend or terminate the account | Documented escalation: warnings, template blocks, timed messaging blocks, account locks and disablement; opt-in required |
| What breaks | One phone becomes the bottleneck; history and follow-ups depend on whoever holds it | Without an inbox or integration there is nothing to reply from; tokens, webhooks and templates need ongoing maintenance |
| Coexistence (both on one number) | Keep the app for one-to-one chats; groups are not synced and broadcast lists are disabled | Automation runs alongside the app at a fixed 20 messages per second; set up only through a Solution Partner or Tech Provider |
One or two people reply from one phone, and you only answer customers who write first: the WhatsApp Business app. Moving earlier adds setup and fees without a clear benefit.
Several staff need the same number, with shared history and handover: the Business Platform through a provider whose inbox fits your team. If its inbox, templates and reports cover the job, you do not need a developer.
Reminders, confirmations, follow-ups or an AI agent must run without a person pressing send: the Business Platform. Approved template messages and webhooks are what make that possible.
Conversations must become structured CRM records, with Arabic and English fields or business-specific logic: the Cloud API with a custom integration, either directly or next to a provider's inbox.
You want to keep replying from the phone app you already use and automate the rest on the same number: coexistence, through a provider that supports it.
You plan to message people who never opted in, such as a bought list: none of them. Both the app terms and the Platform policy require opt-in, and the Platform's enforcement escalates to account locks.
Both routes reach the same Meta platform. A provider onboards you through Meta's Embedded Signup flow: you select or create a business portfolio and a WhatsApp account, verify your business phone number, and enter a display name, then work in the provider's software. A direct connection avoids the provider's fee, but you or your developer must supply the interface, store access tokens securely, handle webhooks, and maintain the integration when Meta changes something.
A common middle path is a provider's inbox for the people plus a custom integration for the CRM or the AI agent. Before signing, ask any provider whether Meta's message fees are passed through at cost or marked up, whether you can export your conversations and contacts, and who controls the business portfolio and the number.
As of November 2, 2026, Meta's documentation describes coexistence as onboarding an existing WhatsApp Business app account and number to the Cloud API, so the business keeps using the app for one-to-one chats while software sends higher-volume messages. It needs app version 2.24.17 or later and is set up through a Solution Partner or Tech Provider. Contacts can be synchronized, along with one-to-one chat history from the 180 days before onboarding if the business agrees to share it.
The trade-offs are specific. Group chats do not sync, broadcast lists are disabled, and disappearing messages, view-once and live location are turned off for one-to-one chats. The number gets a fixed throughput of 20 messages per second, and Meta notes the connection can drop if the primary phone is inactive for about 14 days. If any of those features run your business today, test before you switch.
Meta's messaging fees apply to the Business Platform. As of November 2, 2026, Meta charges per delivered message, priced by category (marketing, utility, authentication or service) and by the recipient's country calling code; messages customers send you are not charged. Marketing, utility and authentication messages are templates that can be sent at any time once approved. Free-form replies, whether written by a person or a third-party AI, are service messages and can only be sent inside the 24-hour customer-service window that each customer message opens or resets. From October 1, 2026, Meta lists 1,000 free service messages per business phone number per month, with charges beyond that. Messages sent inside a free entry point window, which opens when someone writes from a click-to-WhatsApp ad and can last up to 7 days, are not charged.
The market matters in this region. Meta's pricing page lists Saudi Arabia (+966) and the UAE (+971) as markets with their own rates, while Lebanon (+961) is billed at the Rest of Middle East rate. Meta changes rates only on the first day of a quarter, with at least one month's notice for rate card updates, so this page quotes no figures: open Meta's rate card for the current numbers, using the country of the people you message. The other layers are the provider's subscription or seat fee, any build or integration work, and maintenance. The fee layers are explained one by one at tarekrjeily.com/answers/whatsapp-business-api-fees.
On the app, WhatsApp's terms as of November 2026 require opt-in from the people you message, prohibit spam and the use of applications that interact with the Business App without WhatsApp's written consent, and give WhatsApp the right to limit, throttle, suspend or terminate an account. Unofficial bulk-sending tools and bots attached to the app are therefore a real risk to the number itself.
On the Platform, enforcement is documented step by step: warnings, 1- or 3-day blocks on template messages, 5-, 7- or 30-day blocks on all messaging, indefinite account locks that only an appeal can lift, and permanent disablement after repeated violations. Severe violations can mean immediate offboarding. Meta's Business Messaging Policy requires opt-in, and when you automate replies it requires a prompt, clear path to a human.
Two limits surprise new users. A new business portfolio can message 250 unique people outside the customer-service window per rolling 24 hours and can register two phone numbers; business verification is one route to raising both. And Meta's Platform terms prohibit providers of general-purpose AI assistants from using the platform when AI is the primary functionality, so an AI agent on WhatsApp should serve your business's customers, not act as an open-ended chatbot.
Tarek Abou Rjeily, an AI consultant & builder in Beirut, builds WhatsApp automations, AI agents and CRMs for businesses in Lebanon and the Gulf. Invisible CRM, built for a Beirut brokerage owner, is the published example of forwarded messages and voice notes becoming client records. If a provider's ready inbox and templates already cover what you need, you do not need Tarek or any other developer: you pay Meta and the provider.
Yes. As of November 2026, Meta's documentation shows no size requirement and no Lebanon-specific restriction; what a business needs is a Meta business portfolio, a phone number, and a provider or developer to connect the API, because the API has no inbox of its own. Business verification is optional to start and raises limits later.
Yes, through coexistence, which keeps the same number on the app and the Cloud API and is set up through a Solution Partner or Tech Provider. Without coexistence, Meta's documentation says a number already in use with WhatsApp must be deleted there before it can be registered on the API.
Meta charges per delivered message, by category and by the recipient's country calling code. As of November 2, 2026, the UAE and Saudi Arabia have their own rates and Lebanon is billed at the Rest of Middle East rate. Use Meta's current rate card for figures, then add any provider fee, build work and maintenance.
Yes, if it serves your own customers. Meta's Platform terms prohibit providers of general-purpose AI assistants when AI is the primary functionality, and the Business Messaging Policy requires a clear path to a human when you automate replies. Replies written by a third-party AI inside the customer-service window count as service messages.
Not if a provider's inbox, templates and reports cover your needs. A developer is worth it when messages must become structured CRM records, when an AI agent needs your business data, or when you want to own the integration logic.
Product facts can change. These primary sources were checked on the guide's update date; verify plan details again before buying.
A quick question on WhatsApp is always free. Most engagements start with the diagnostic: three working days, ending in an honest build, buy or fix-by-hand recommendation. Message me on WhatsApp or email tar@tarekrjeily.com.