WhatsApp Cloud API vs a BSP: What UAE Businesses Actually Pay For

What are the two ways a UAE business actually gets onto WhatsApp?

There is exactly one platform underneath every legitimate WhatsApp business integration: Meta's own WhatsApp Cloud API. Every message a business sends, whether it goes through a slick third-party inbox or a line of code a developer wrote themselves, travels through that same infrastructure. The choice a UAE business actually makes is not which WhatsApp to use, it is whether to connect to that platform directly or pay a Business Solution Provider (BSP) to sit in between.

That distinction gets lost in most vendor pitches, because a BSP's product is usually described as "WhatsApp for business" without mentioning that the same underlying access is available at no extra charge. It is worth being precise about what each path involves before signing anything.

What does a Business Solution Provider actually do, and charge for?

A BSP handles the Meta-side setup on a business's behalf: registering the app, submitting templates for approval, and giving the business a hosted inbox to manage conversations from, often bundled with a chatbot builder, a shared team inbox, or integrations into other tools. In exchange, a BSP typically charges a recurring subscription fee, a per-conversation markup on top of Meta's own usage, or both.

None of that is dishonest. A managed inbox and a faster path through Meta's approval process has real value for a business that does not want to touch a developer console. The point worth understanding before paying for it is that the underlying access a BSP resells is the same Cloud API a business can connect to directly, at no additional charge from Meta for the connection itself.

What does connecting directly to the Cloud API actually require?

Going direct is a one-time setup, not an ongoing subscription. It needs, in order:

1. A Meta Business Manager for the company, if one does not already exist from running Meta ads.
2. A Meta app registered under that Business Manager, used purely as the technical container for the WhatsApp connection.
3. The WhatsApp product added to that app, with the business's own number connected and verified.
4. A permanent system-user access token generated against that app, which is what authenticates every message sent through the API without needing a person to stay logged in.
5. Message templates submitted for Meta's review under the correct category, before any of them can be used outside an open conversation window.

None of these steps involve a BSP. A business that already runs Meta ads usually has the Business Manager in place already, which makes the remaining setup closer to an afternoon's work than a specialist project.

What is the 250-contacts-a-day limit, and does the BSP-vs-direct choice change it?

Meta caps how many unique customers an unverified WhatsApp Business number can message within a rolling 24-hour period, described in its own messaging limits documentation. MAJ Leads' default tier for a newly connected client number reflects that limit at 250 unique contacts within 24 hours, until the business completes Meta's own business verification process.

This limit applies at the Meta platform level, not the connection method. A number reached through a BSP is subject to exactly the same cap as one connected directly, because both ultimately run on the same Cloud API infrastructure. Choosing a BSP does not raise this ceiling; completing verification does.

Why does the utility-vs-marketing template category matter for the bill?

Every template a business submits is reviewed and approved under a category. A utility template supports a transaction or request the customer already initiated, a booking confirmation or a status update. A marketing template promotes an offer, and carries stricter opt-in requirements and a lower approval rate. Meta's own conversation-based pricing, described on its WhatsApp Business Platform pricing page, treats these categories differently, and rates vary by market and change over time, so a business should check that page directly for current figures rather than relying on a number quoted secondhand.

For lead follow-up specifically, this is not a technicality to work around. A booking confirmation or a missed-call notice is a genuine utility message tied to something the lead already did, and treating it as anything else invites a rejected template and a delayed launch.

How does the 24-hour service window affect what actually goes out?

Once a customer messages a business on WhatsApp, that business can reply freely, without a template, for the next 24 hours. Outside that window, without a new message from the customer, an outbound message has to be a pre-approved template again. This mechanic sits underneath both the BSP and direct paths identically, since it is a Meta platform rule rather than something either side layers on top.

In practice this is what makes WhatsApp follow-up feel responsive rather than robotic: a lead who replies to a booking confirmation reopens a normal, free-form conversation, and a lead who goes quiet simply moves back outside the window until the next templated message reaches them.

So what is the actual cost difference between the two paths?

There are two layers of cost in either scenario. The first is Meta's own usage-based pricing for conversations, which applies identically whether the connection is direct or through a BSP, because both send messages through the same Cloud API. The second is the BSP's own fee, a subscription, a markup on conversations, or both, which exists only if a BSP is involved at all. Going direct removes that second layer entirely. What it costs instead is the setup work described above, and the ongoing responsibility of managing the Business Manager, the templates, and the access token in-house.

How does MAJ Leads handle this for a client?

MAJ Leads connects every client directly to the Cloud API, using that client's own Meta Business Manager, WhatsApp product, number and permanent system-user token. There is no BSP in the chain and no markup added on top of Meta's own usage. Six approved templates cover the lead journey end to end, four to the lead and two to the client's team, and a reply from a lead reopens the 24-hour window and continues as a normal thread inside the console. The full template list and the reasoning behind each one is covered in WhatsApp CRM in the UAE: Rules, Templates and the 24-Hour Window.

Both MAJ Leads plans include 500 WhatsApp conversations as part of the subscription, which covers the templated messages and the free-form replies they generate for the large majority of UAE SMEs and brokerages.

Is there a case where a BSP still makes sense?

Yes, honestly. A business that has no interest in managing a Meta app or a Business Manager, or that needs one inbox spanning WhatsApp alongside several other messaging channels for reasons unrelated to lead follow-up, gets real value from a BSP's managed setup, in exchange for the fee it charges. The point of this comparison is not that a BSP is a bad choice, it is that the fee buys convenience on top of an access layer that is otherwise free to connect to directly.

What's the bottom line for a UAE business choosing between the two?

The Cloud API itself, the messaging limits, the template categories and the 24-hour window are identical whichever path a business takes, because they are all Meta platform rules, not vendor features. The genuine choice is whether to pay a BSP for managed setup and an inbox, or connect directly and keep that fee. See the full mechanics on the WhatsApp CRM page, compare AI Mode against Team Mode, and check current pricing, Team Mode starts from AED 299 per month, on the pricing page.