Skip to content
Start a Project
WhatsApp

WhatsApp Business App vs WhatsApp Business Platform

One is a free app you install on a phone. The other is an API you build against. Choosing the wrong one usually shows up as a migration six months later.

Illustration generated in code — replace with a project screenshot or photograph where one exists.

WhatsApp offers two products for businesses and the naming does very little to distinguish them. The practical differences are substantial.

WhatsApp Business App

A free mobile application, installed on a phone, tied to one number. It adds a business profile, labels for organising chats, saved quick replies, an away message and a simple product catalogue.

It suits a business where a small number of people handle messages and the volume is manageable by hand. The limits are structural rather than arbitrary: it is a phone app, so simultaneous access by a team is constrained, and it does not connect to other systems.

WhatsApp Business Platform

An API. There is no interface — you either build one or use a provider that supplies it. It is designed for businesses that need to send and receive messages programmatically, route them to multiple agents, and connect the conversation to a CRM, helpdesk or order system.

Access is through a solution provider or directly via Meta. Messages are priced per conversation rather than per message, and business-initiated conversations require pre-approved message templates.

Side by side

Business AppBusiness Platform
InterfaceMobile app providedNone — you build or buy one
CostFreePer conversation, plus provider fees
Team accessLimitedDesigned for it
AutomationAway and greeting messagesFull programmatic control
System integrationNoneCore purpose
Setup effortMinutesDays to weeks

Which one

The app is right if messages are answered by one or two people, volume is low enough to handle manually, and the conversation does not need to appear in any other system.

The platform becomes necessary when any of these is true: several agents need the same inbox simultaneously; messages must create or update records elsewhere; notifications need to be triggered by events in your own systems; or volume has passed the point where manual handling is reliable.

The migration cost

A number registered to the Business App can be migrated to the Platform, but chat history does not transfer. Starting on the app is still usually correct — just be aware that the history stays behind.

Templates and the 24-hour window

This catches out most teams new to the Platform. Once a customer messages you, there is a 24-hour window in which you can reply freely. Outside that window, you can only send a pre-approved template message.

Templates are submitted to Meta for review and are approved or rejected based on content and category. Getting a template rejected on the day of a campaign is a common and avoidable problem — submit them well in advance.

If you are building on it

Three things are worth getting right from the start:

  • Webhook idempotency. Delivery notifications can arrive more than once. Handle each event by its identifier, not by its arrival.
  • Template versioning. Templates change and need re-approval. Keep them in version control alongside the code that sends them.
  • A human handoff path. Any automated conversation needs a reliable way to reach a person. It is also increasingly a regulatory expectation.

Pricing, template categories and rate limits change periodically. Check Meta's current documentation before committing to a cost model.

Keep reading