Meta ships two distinct things under the WhatsApp Business name. They are not tiers of one product. They are built for different situations, and the decision between them is mostly about whether a human is going to read every message.
#The WhatsApp Business app
A free app, installed on a phone, used by people. It adds business features on top of ordinary WhatsApp: a business profile, a product catalogue, labels for organising chats, saved quick replies, greeting and away messages, and the ability to link a handful of additional devices so more than one person can answer.
It is the right answer for a great many businesses. If your message volume is something a person can comfortably read, and your replies genuinely need a person's judgement, the app is enough, and anything more is overhead.
Where it runs out
- It has no real automation. Greeting and away messages are canned text, not answers.
- It cannot reach into your systems. It does not know your stock levels, your calendar, or your CRM.
- It is bound to devices and to people's attention. Volume that outruns the people is volume that waits.
- Reporting is thin — you cannot easily see what customers asked or where conversations died.
#The WhatsApp Business Platform
Not an app at all. It is an interface your own systems talk to, so messages can be received and sent by software. There is no inbox unless you build or buy one. You connect either through Meta's Cloud API directly, or through a solution provider that handles the plumbing and support on top of it.
That is what makes everything else possible: an agent that answers instantly, a booking written straight into a real calendar, a stock check against real inventory, a lead logged to your CRM with the transcript attached.
Rules you should know before you commit
- Business-initiated messages need pre-approved templates. You cannot freely message someone out of the blue in whatever words you like.
- You need opt-in. Consent to be messaged has to be collected and recorded.
- There is a customer service window. Once someone messages you, free-form replies are allowed for a limited period — after it closes, you are back to templates.
- It is paid, and Meta sets the rates. Pricing is metered by Meta, varies by country and by message category, and has been restructured more than once.
- A phone number used on the Platform cannot also be used in the Business app. Moving a number across is a migration, not a toggle.
#How to tell which one you need
Three questions settle it for most businesses.
- Can a person read every message within a few minutes, including evenings and weekends? If yes, the app is probably enough.
- Do your answers depend on data in another system — stock, availability, prices, order status? If yes, the app cannot reach it, and you need the Platform.
- Does missing a message at 21:40 cost you a sale? If yes, the constraint is human attention, and only the Platform removes it.
A fourth, quieter test: if you already pay someone to do nothing but answer repeated questions during business hours, you have already decided the volume justifies automation — you are just paying for it in salary rather than software.
#The part people underestimate
Getting onto the Platform is the easy half. The work is in what the agent is allowed to say, what it does when it does not know, and what happens to the conversation afterwards — whether it lands in a record a human can pick up, or evaporates. A connection to WhatsApp is not a system. It is a pipe; the value is what you put behind it.
The modules describe what we put behind it, and packages explains how the volume maps to a plan.
Where to go next