WhatsApp Business Platform review

WhatsApp Business Platform is a hosted business messaging service, rather than a library, CLI or self-hosted server. It puts WhatsApp customer conversations into a business's communications stack; the homepage positions it as a way to reach customers globally, showcase products and services, increase sales and build customer relationships.

The pricing model is pay-as-you-go, with charges based on delivered messages. That makes it a channel to integrate into a product or customer-support workflow, with usage costs that move with message volume and destination. A Reddit post about OpenBSP describes the open-source project as connecting directly to Meta's Cloud API; that is a separate tool, not a self-hosted version of Meta's platform.

The homepage also describes voice and video calls, group conversations and end-to-end encryption for personal messages and calls. Those consumer-facing claims should not be treated as guarantees about business API capabilities or message encryption. Confirm the business API's supported message types, security model and operating requirements in Meta's developer documentation before choosing an architecture.

The integration surface is WhatsApp Business Platform and, as described in a Reddit post about OpenBSP, Meta's Cloud API. The homepage's business copy covers customer messaging and product showcases, but not API endpoints, authentication, webhook behavior, SDKs, supported languages, a CLI or example integrations. Developers should verify those details in Meta's developer documentation before estimating implementation work; confirm SDK support for the languages in your stack rather than assuming a particular client library.

The practical work is not only sending messages. A Reddit commenter says approvals, rejections and templates are hard to work with, and another reports difficulty verifying a phone number while onboarding. Treat template setup, number verification, account approvals and error handling as integration risks to validate early. The homepage's claims about voice and video calls and end-to-end encryption refer to WhatsApp generally; confirm whether they apply to the specific business API workflow you plan to build. Scope your integration around the documented API and a fallback customer channel.

The WhatsApp Business Platform (Pay-as-you-go) has no monthly base subscription or annual price. The pricing information lists 1,000 free service messages per phone number each calendar month, plus free messaging for 72 hours after a Click-to-WhatsApp ad entry point. There is no free plan or published starting price; bills are based on delivered messages.

After free allowances, paid rates vary by destination country and message category. The pricing notes cite $0.0034 for utility, authentication or service messages to North American (+1) numbers; confirm the applicable rate for your category and destination. The platform also lists tier limits of 1,000, 10,000, 100,000 or unlimited unique customers per rolling 24 hours. These are customer limits, not message-volume price tiers.

Meta Business Agent is listed at $2 per 1 million tokens. WhatsApp does not publish seat costs; seats are managed and billed through third-party Business Solution Providers. Budget separately for provider charges and check the current rate card before projecting production spend.

WhatsApp Business Platform is a hosted Meta service, not an open-source server that you can run yourself. The available information does not give the Platform a software licence or describe a customer-data export path; ask Meta or your Business Solution Provider how to export message and contact data, and what remains accessible after an account or number change.

OpenBSP is a separate, open-source project that its Reddit post describes as self-hostable and connected to Meta's Cloud API. The post does not name its licence, so check the repository before using or modifying it. Self-hosting that layer does not remove reliance on Meta's API, account approvals, phone numbers or messaging rules. To reduce lock-in, keep customer records and message workflows in systems you control, and design a fallback channel. Verify export formats and migration steps before making WhatsApp the only customer contact route.

Before production, verify the current message rates for each destination and category, the free-message eligibility rules, and which rolling 24-hour customer tier applies to your account. The published tier options run from 1,000 to unlimited unique customers per rolling 24 hours; confirm how tier changes are handled and what happens when traffic reaches a limit. Build monitoring around delivery outcomes, spend and account status, and keep another way to reach customers.

A Reddit thread about WhatsApp Business reports account lockouts and difficulty getting support; a commenter also describes losing access to chats after changing phones. These are user reports about WhatsApp Business experiences, not proof that the Platform API behaves the same way. Another commenter warns that number verification and onboarding can take work. Plan for account recovery, number ownership and customer-data continuity, and get support and escalation terms from Meta or your provider in writing. Do not infer that personal-message encryption claims automatically cover business API traffic.