What is the WhatsApp Business API, and does my business need it?
The WhatsApp Business API lets software send and receive WhatsApp messages automatically, which the free WhatsApp Business app cannot do. You need it once messages have to be sent by a system rather than typed by a person — appointment reminders, order updates, payment confirmations — or once more than one person has to answer them.
- Written by
- MyFloww
- Published
- Updated
- Reading time
- 8 min read
In India, WhatsApp is where a customer actually reads the message and replies to it. An email goes unread, an SMS goes unanswered, and a WhatsApp message gets a reply — which is why almost every Indian business eventually asks how to send them automatically.
The answer is the WhatsApp Business API, and most of the confusion around it comes from three separate things sharing a name.
Three different WhatsApps
- WhatsApp Messenger
- The personal app. Not licensed for business messaging at any scale, and using it for bulk sending is the fastest way to get a number banned.
- The WhatsApp Business app
- Free, runs on one phone, and is genuinely enough while one person can answer every message by hand. It offers a catalogue, labels, quick replies and away messages — but no way for your software to send anything.
- The WhatsApp Business API
- Not an app at all. It is an interface your systems talk to, so a booking made in your software can trigger the confirmation, the reminder and the follow-up without anyone typing them. Your team answers from a shared inbox rather than from one phone.
Which one you need
| What decides it | The free Business app | The Business API |
|---|---|---|
| Who sends the message | A person, typing it, on one phone. | Your software, triggered by a booking, an order or a payment. |
| How many people can reply | Effectively one device at a time. | Your whole team, in a shared inbox, with history attached to the customer. |
| Connecting to your systems | Not possible. The phone is the system. | The entire point of it — your CRM, booking system or ERP triggers and receives messages. |
| Automated replies | Canned greetings and away messages. | An AI chat bot answering from your own content, with handover to a person. |
| What it costs | Free. | Meta charges per conversation at its own published rates, plus whatever the automation itself costs to build. |
How the pricing actually works
Meta charges per conversation template category, not per message typed, and the category matters far more than the volume does. This is the part that surprises people, and getting it wrong is what turns a small bill into a large one.
- Utility
- Messages about something that already happened: an appointment confirmation, an order update, a payment receipt, a delivery notification. This is the cheapest category by a wide margin, and it is the category almost every message a clinic or a service business needs to send.
- Authentication
- One-time passcodes. Priced separately, and only relevant if you are logging people in.
- Marketing
- Promotions, offers, re-engagement, anything sent to create demand rather than to service it. Several times the price of a utility message, and the category Meta scrutinises most closely.
- Service
- Your replies inside a window the customer opened by messaging you first. Answering a customer who wrote to you is not the expensive part.
Two practical consequences follow. First, an appointment reminder written as a utility template costs a fraction of the same words sent as a marketing template — so the template you register decides your bill, not the message you write. Second, a business whose messages are almost all utility can run meaningful automation for a very small monthly spend, which is not the impression most vendor pricing pages give.
We do not restate Meta's current per-message rates here, and you should be sceptical of any page that does without a date on it. They are set by Meta, they are published by Meta, they differ by country, and they have changed more than once. What is stable is the structure above — and GST applies on top in India.
Do you need a provider, or can you go direct?
You can access Meta's Cloud API directly, and you can also go through a Business Solution Provider that wraps it in a dashboard and charges a platform fee on top. Both are legitimate; they suit different situations.
- A ready-made provider makes sense if you want a dashboard today, your team will send campaigns by hand, and you are not connecting WhatsApp to anything else.
- Going direct makes sense when WhatsApp has to be wired into software you already run — or software being built for you — and you would rather not pay a platform fee forever for a layer you do not use.
- The question worth asking any provider is what the platform fee buys you on top of Meta's own charge, and whether you would still be paying it in year three.
What appointment-driven businesses actually send
Most published advice about WhatsApp automation is written for e-commerce — carts, catalogues, abandoned checkouts. Clinics, salons, diagnostic labs, gyms, coaching centres and veterinary practices have a different and much simpler list.
- The booking confirmation, sent the moment the appointment is made.
- The reminder the day before, with a way to confirm or reschedule in the same thread.
- The follow-up afterwards — the home exercise programme, the aftercare note, the next step.
- The payment receipt or the outstanding-balance nudge.
- The review request, asked once, at the right moment, with a direct link.
For a clinic, the second of those is the one that pays for everything else. A reminder that arrives where the patient already reads, with a reply that reschedules rather than cancels, removes both reasons appointments get missed — see how a physiotherapy clinic can reduce patient no-shows for where it sits among the other two changes that matter.
What not to put in a reminder
A WhatsApp message lands on a phone that other people can see, and a template is stored and reviewed by Meta. That makes restraint a design requirement rather than a nicety, particularly for a healthcare practice.
- Keep the diagnosis, the condition and the clinical detail out of the reminder. "Your session with Dr Rao is at 11:00 tomorrow" says everything the message needs to.
- Collect consent to message the person, and keep a record of when and how you collected it. Handling personal data under India's Digital Personal Data Protection Act 2023 means collecting what is needed, using it for the purpose it was given, and being able to show that.
- Give people a way to stop, and honour it immediately.
- Do not send a marketing template to someone who gave you their number to book an appointment. It is a worse experience and a more expensive message.
Where automation becomes useful rather than annoying
The difference between automation a customer tolerates and automation they resent is almost always whether the message knows anything. A reminder sent from a separate list is a broadcast. A reminder sent because the appointment exists in the system — and a reschedule that writes back to that same system — is service.
That is why WhatsApp automation is worth connecting to the software that already holds the answer, rather than running beside it. We build WhatsApp automation that way, and where the system it should connect to does not exist yet, that is a custom software build quoted alongside it.
Questions
Related questions
Can I use my existing WhatsApp number for the Business API?
Usually yes, but not while it is still active on the WhatsApp Business app or WhatsApp Messenger — a number lives on one of them at a time, and moving it means the message history on the phone does not come with it.
Many businesses use a second number for automation and keep the original phone for the conversations staff already handle by hand. That is often the least disruptive route.
How long does WhatsApp Business API approval take?
It depends on Meta's business verification, which is the step that takes the time — the technical setup is comparatively quick.
The delays are almost always documentation: the business name on the account has to match your registration, and the display name has to satisfy Meta's naming rules. Getting those right first is what makes the difference.
Is WhatsApp automation allowed for a clinic in India?
Yes, sending appointment reminders and confirmations on WhatsApp is a normal, permitted use — the care needed is in what the message contains and whether the patient agreed to be contacted.
Keep clinical detail out of the message, collect and record consent, and give people a way to stop. This is general guidance on how we build, not legal advice; a practice with a specific compliance question should take its own.
Can a WhatsApp chat bot answer questions as well as send messages?
Yes. An AI chat bot on WhatsApp can answer customer questions from your own content and hand the conversation to a person the moment it is out of its depth.
That handover rule is not optional in the agents we build. An agent that improvises about a medical service, a price or a delivery date is a liability.
What does WhatsApp automation cost to set up?
The automation is quoted per project, and Meta's per-conversation charges are separate and go to Meta rather than to us.
What moves the build cost is not the messages — it is what has to be connected. Sending a reminder from a list is simple; sending one because an appointment exists in your booking system, and writing the reschedule back to it, is the part with the work in it.