Two different products with one name
"WhatsApp Business" covers two separate things. The WhatsApp Business app is a free app you download on your phone, much like regular WhatsApp, with extra tools for a shop or a small team. The WhatsApp Business Platform, which most people call "the API", is software that other systems plug into. It has no app of its own. You use it through a dashboard or chatbot tool, and Meta charges for certain messages.
What the free app already does
Much of this sits unused in the Business Tools menu.
- A catalogue, so customers can browse products and prices inside the chat and you can share a single item instead of sending ten photos.
- Quick replies. You save answers you type every day (address, timings, delivery charges, UPI ID) and call them up with a "/" shortcut.
- Labels, so you can tag chats as "new enquiry", "paid", "to deliver" or "follow up". Customers cannot see them.
- A greeting message for people messaging you for the first time, and an away message for when the shop is closed.
- A business profile with your address, hours, website and category.
- Linked devices. You can run the same account on your main phone plus a few more devices, such as a laptop at the counter. WhatsApp currently allows up to four linked devices, but check its help pages because this has changed before.
For a shop handling a few dozen chats a day with one or two people replying, this covers most of what you need.
Where the app runs out
The first is staff. Linked devices let three or four people see the same inbox, but nobody "owns" a chat. Two people reply to the same customer, or each assumes the other did. The app has no assignment and no record of who said what.
The second is automation. Greeting and away messages are the only automatic replies. The app cannot read "what is the price of the blue kurta in M" and answer from your catalogue, take an order step by step, or remind someone that payment is due tomorrow.
The third is connecting to other tools. Orders, payments and stock live somewhere else, such as a sheet, your billing software or your website. Every enquiry gets copied across by hand.
What the Business Platform (API) adds
- Automated flows and chatbots that answer common questions, show products, collect order details and hand the chat to a person when needed.
- Connections to your other systems, such as a store, payment links, CRM or Google Sheet, so an order on WhatsApp shows up in your order list without retyping.
- A shared inbox, through most providers, where many staff can work on one number with chats assigned to each person.
- Template messages. These are pre-approved message formats you can send to customers who have opted in, even if they have not messaged you recently: order updates, payment reminders, appointment confirmations, offers.
What the API costs and needs, in general terms
There are three kinds of cost.
The first is Meta's message charges. Since 1 July 2025 Meta charges per template message delivered, not per conversation. Templates fall into categories (marketing, utility and authentication), and marketing ones cost the most. Rates depend on the recipient's country and your volume. Ordinary replies inside the 24-hour window after a customer messages you are free, and so are utility templates sent inside that window. Rates and rules change, so check Meta's current pricing page before you budget.
The second is the provider's fee. Few small businesses connect to the API directly, because that needs a developer. Most sign up through one of Meta's partners (often called a Business Solution Provider), which gives you the inbox, chatbot builder and integrations. Providers charge a monthly fee on top of Meta's charges, and some add a markup per message.
The third is setup work. You need a Meta business account, a verified business for higher sending limits, templates written and approved, and flows built and tested. Somebody has to own this.
Can you keep your number on both?
For years the answer was no. A number registered on the API could not also be used in the Business app, so moving meant giving up the app on that number. Meta now has an option often called "coexistence", where a number already on the Business app can also be connected to the API through a supporting partner, with chats synced between the two. It comes with conditions: a recent app version, supported countries, some app features that stop working on those chats, and the app must stay installed and active. Not every provider supports it. Ask your provider directly, and confirm against Meta's documentation, before you move a number that customers already know.
Which one fits your situation
| Your situation | Start with | Why |
|---|---|---|
| One owner replying, under about 50 chats a day | App | Catalogue, quick replies and labels cover it, at no cost. |
| Two or three people sharing replies, chats sometimes missed | App, with a clear rota and labels | Fix the process first. Software does not fix "nobody knows whose chat this is". |
| Same ten questions all day, staff copying answers | API, or app with good quick replies | If quick replies still eat hours, a chatbot pays for itself. |
| Orders typed by hand into a sheet or billing software | API | Integration removes the retyping and the errors. |
| You need reminders and order updates sent to many customers | API | Template messages are built for this. Broadcasts from the app only reach people who saved your number, and mass-sending risks blocks. |
| Five or more people on one number | API with a shared inbox | You need assignment and a record of who replied. |
A festival-season test
Say you run a sweets shop in Lucknow. For most of the year you get 20 to 30 WhatsApp enquiries a day and handle them on the app between customers. Then Diwali arrives. For three weeks you get hundreds of messages a day: box sizes, prices, corporate orders, delivery dates, "has my order left?".
On the app, you and two staff work three linked devices. Corporate orders are tracked on a paper pad, someone misses a payment screenshot, and a 40-box order goes out a day late. Nothing broke because of the app. It broke because the volume needed structure the app does not have.
On the API, a flow answers box sizes and prices from the catalogue, collects the order and address, sends a payment link, and drops the order into one sheet. Anything unusual goes to a person. You pay Meta's charges and a provider fee for those weeks, and in return you get your evenings back.
The question to ask yourself is whether last festival season cost you orders or customers. If it did, the API is probably worth it. If you coped, stay on the app and tidy your quick replies and labels.
A rule of thumb
Start with the app. Move to the API when any one of these is true for more than a month or two: more than two people regularly reply on one number, you or your staff spend over an hour a day typing the same answers, orders are being copied by hand from chat into another system, or you need to send updates or reminders to customers who have not messaged you in the last day.
If none of those apply, you will get more from setting up the app properly. That means a full catalogue, ten good quick replies, labels everyone uses the same way, and a same-day reply habit.
If you have outgrown the app and want the order flow built and run with you through a busy season, see how we automate orders and follow-up.