Key takeaways
- The API is worth it when volume, multiple agents or system integration outgrow the free app.
- Build transactional flows before promotional ones — they are cheaper, welcomed, and drive repeat contact.
- Quality rating governs how much you can send; weak opt-in and irrelevant templates are what get numbers limited.
- The value is in the integration, not the messaging.
What the API gives you beyond the free app
The free Business app is a phone app with a catalogue attached. It works well up to a point, and that point is usually one of three things: too many conversations for one person, too many people needing access to one number, or the need for another system to send the message.
The API is a channel your systems can speak through. Practically, that means:
- Multiple agents on one number, with assignment, queues, tags and full history.
- Automated messages triggered by real events — an order, a payment, a dispatch, a renewal date.
- Integration with your CRM, ERP or website, so the conversation and the customer record are the same thing.
- Reporting on response times, resolution rates and revenue attributable to the channel.
- Rich message types — buttons, lists and flows — that reduce the amount of typing a customer has to do.
| Free Business app | Business API | |
|---|---|---|
| Agents on one number | One phone, limited linked devices | Unlimited, with routing |
| Automation | Away messages and quick replies | Event-driven messages from your systems |
| Integration | None | CRM, ERP, orders, support desk |
| Cost | Free | Per conversation or message, plus provider fees |
| Best for | Small volume, one operator | Volume, teams, and system-driven messaging |
The flows worth building first
Transactional messages are the ones customers actually want, and they cost less to send than marketing ones. They also keep the service window open, which makes support cheaper. Start here, in roughly this order:
- Order and payment confirmation, with the invoice attached, so the customer never has to ask whether it went through.
- Shipping and delivery updates, which replace the “where is my order” ticket entirely.
- Appointment reminders with reschedule and cancel buttons, which cut no-shows more effectively than SMS.
- Abandoned enquiry follow-up — one message, clearly opted in, sent while the intent is still warm.
- Renewal and re-order nudges for anything consumable or subscription-based.
- Post-delivery feedback, which is both useful and a natural reason for the customer to message you back.
Replacing status-check tickets with proactive updates is usually the fastest measurable return on the whole channel, because you can count the tickets that stop arriving.
The rules you need to design around
WhatsApp is a permissioned channel, and the constraints shape the design more than the technology does.
- Opt-in is mandatory, and you must be able to show where and when it was collected for each contact.
- Outside a 24-hour window from the customer’s last message, you can only send pre-approved template messages.
- Templates are categorised — utility, authentication and marketing — approved individually, and priced differently.
- Every number carries a quality rating driven by blocks and reports, which directly caps how many people you can message per day.
- A verified business name and profile improves both deliverability and the customer’s willingness to reply.
Design around this by treating marketing sends as the exception. A channel built on utility messages stays healthy almost automatically, because customers want those messages and never report them.
Connecting it to the rest of your stack
The value comes from the integration, not the messaging. Three connections matter most, and doing them properly is most of the project:
- Orders and payments, so confirmations and status updates fire without anyone pressing anything.
- CRM, so conversation history sits on the customer record your sales team already works from, and nobody has to check two places.
- Support, so a handover from automation to a human keeps the full thread and does not make the customer start again.
A fourth is worth planning for early even if you build it later: a single view of consent, so you can always answer where a given contact opted in and what they agreed to receive.
What gets numbers restricted
- Buying or scraping lists. It is the fastest route to a restricted number and there is no recovery argument to make.
- Promotional blasts to people who opted in only for order updates. Technically permitted by your form, experienced as spam, reported accordingly.
- Bots with no visible route to a human, which generate reports rather than resolutions.
- Slow replies inside the service window, which train customers to block you rather than wait.
- One number used for unrelated brands or business lines, which makes the messages feel unexpected.
The pattern is consistent: quality rating tracks whether people wanted the message. Every technical safeguard is downstream of that.
Frequently asked questions
Is the WhatsApp Business API free?
Access is; messages are not. You pay per conversation or message depending on category, plus whatever your provider charges on top. Utility messages cost less than marketing ones, which is another reason to start with transactional flows.
Can we keep our existing number?
Yes, if it is migrated properly. A number registered on the free app has to be moved across, and it cannot be used in both places at once — so plan the switch rather than discovering it mid-campaign.
Do we need a chatbot?
Not at the start. Automated transactional messages plus a well-staffed shared inbox delivers most of the value. Automating enquiry handling makes more sense once you can see the real distribution of questions.
How is this different from SMS?
Higher open rates, richer messages, two-way conversation and a permanent thread on the customer’s phone. The trade-off is stricter permission rules and per-message cost, which is why targeting matters more.
Related services