Most enquiries now arrive on WhatsApp, and they all land on one phone. Someone at the counter answers when they can, the owner answers late at night, and a customer who asked about price on Tuesday is still waiting on Thursday. Then somebody mentions “the WhatsApp API” and it sounds like the fix, though nobody can quite say what it is.
There are two different products here, and they are built for different situations. This post explains what each one does, where each one stops being enough, and how to decide without paying for more than you need.
Two products with similar names
The WhatsApp Business app is a free app for Android and iPhone. It looks and works like normal WhatsApp, with extra tools for a business. You install it, register a number, and start replying. Nothing to build.
The WhatsApp Business Platform, which most people call the WhatsApp API, is not an app at all. It is a way for software to send and receive WhatsApp messages on behalf of your business. Meta offers it directly as the Cloud API, and many companies, usually called Business Solution Providers, resell access to it with their own shared inbox, chatbot builder and integrations on top. On its own, the API has no screen to type into. You either use a provider’s inbox or connect it to software you already run, such as a CRM, booking system or online store.
That surprises people. The API is not “WhatsApp, but bigger”. WhatsApp becomes part of your systems, and someone has to set those up.
What the free app already does well
A lot of businesses that think they have outgrown the app are not using half of it. Before looking at anything else, check whether these are set up:
- Business profile with your address, hours, website and a short description, so customers do not have to ask.
- Catalog of products or services with photos and prices, which you can send in a chat instead of typing the same details again.
- Quick replies, saved answers you insert with a shortcut, for questions like delivery areas, payment options or how to book.
- Labels such as “new enquiry”, “paid” or “follow up”, so you can filter chats and see what is still open.
- Greeting and away messages that go out automatically when someone writes for the first time or outside your hours.
- Linked devices, so the same account can be used on WhatsApp Web or the desktop app as well as the phone.
For a shop, salon, clinic or consultant where one or two people handle the chats, this covers most of what you need.
Where the app starts to strain
The limits show up in a few predictable ways:
- Several people need to answer. Linked devices help, but everyone is effectively logged into the same account. You cannot easily see who replied, assign a chat to one person, or stop two people answering the same customer differently.
- Messages should go out on their own. The app cannot send an order confirmation when someone pays on your website, or a reminder the day before an appointment. Someone has to do it by hand, and on a busy day it does not happen.
- Chats need to connect to records. If you want each conversation tied to an order, a lead in your CRM or a patient booking, the app has no way to pass that data anywhere.
- The phone is a single point of failure. If it is lost, broken or leaves with an employee, your customer conversations go with it.
Broadcast lists in the app are also narrower than people expect: a broadcast only reaches people who have saved your number in their contacts. That is a deliberate restriction, not a bug.
What the API adds, and what it asks of you
With the API, through Meta’s Cloud API or a provider, you can have many agents answering from one number in a shared inbox, with chats assigned and history kept. You can send automatic messages triggered by your website or software. You can add a chatbot for common questions, and connect WhatsApp to your store, CRM or booking system.
It also comes with rules that the app does not have:
- Template messages need approval. When you message a customer first, or reply after a period of silence, you must use a pre-written template that Meta has reviewed and approved. Templates are put into categories, such as utility messages (order and account updates) and marketing messages. Within a limited window after the customer writes to you, you can reply freely.
- Customers must opt in. Meta requires that people agree to receive messages from you on WhatsApp before you send them. A phone number collected for delivery is not, by itself, permission to send offers. Recording that consent properly also matters under India’s data protection rules, which our guide to keeping a privacy policy current in India touches on.
- Quality is watched. If many people block or report your messages, Meta can lower your number’s quality rating and restrict how many people you can message. New numbers also start with limits on how many customers they can contact, which rise over time.
- Some messages are charged by Meta. Meta charges for certain types of messages, and the rates differ by category and country. Pricing has changed several times, so check Meta’s current pricing for your country before you commit, and ask any provider to show their own fees separately from Meta’s.
- Business setup. You will need a Meta business account, an approved display name, and Meta may ask you to verify your business.
One more thing to ask a provider before you start: what happens to your existing number. Whether a number can stay on the app once it is connected to the API has changed over time and depends on the setup, so get a clear answer in writing.
Side by side
| WhatsApp Business app | WhatsApp Business Platform (API) | |
|---|---|---|
| Cost to use | Free | Meta charges for some message types; providers usually add their own fee |
| Setup | Install and register a number | Meta business account, provider or developer setup |
| Who answers | One account on a phone and linked devices | Many agents in a shared inbox |
| Automatic messages | Greeting and away messages only | Triggered by your store, CRM or booking system |
| Messaging customers first | Normal chats and broadcasts to saved contacts | Approved templates, to people who opted in |
| Integrations | None | Store, CRM, booking system, chatbot |
| Best for | One or two people handling chats by hand | A team, or messages that should send themselves |
An honest way to decide
Stay on the app if one or two people handle the chats, most conversations start with the customer, and nothing needs to be sent automatically. Set up the catalog, quick replies, labels and away message properly first.
Move to the API if you have a team answering, if customers expect automatic updates from your store or booking system, or if chats need to be recorded against orders or leads. Online stores, clinics taking appointments and businesses running a shared support desk are the usual cases.
Wait if the real problem is that nobody has time to reply. The API makes a well-run process faster. It does not create one, and a chatbot that gives wrong answers is worse than a slow human reply.
Whichever you choose, make WhatsApp easy to reach from your website: a clear chat button on mobile, with a pre-filled message so you know which page the customer came from. It works with both the app and the API. You can read more about where WhatsApp fits among other website features in what a business website needs now, and if you want an automated assistant answering on WhatsApp, our page on AI chatbots for small business websites explains what that involves.
If you only need the button, it is one of the small jobs on our website services list, with WhatsApp CTA integration from ₹999. If you are weighing up the API and want a second opinion on whether it suits your volume, tell us how your enquiries come in and we will say plainly whether the app is still enough.
Next in this series: Automatic WhatsApp Order Updates for WooCommerce Stores
