Somebody tells you that the real setup needs the WhatsApp Business API, and every search result seems to confirm it. The articles that come up are competent and they are all about money: the per-message rates, the platform fee on top, the tactics for shrinking the bill. Read three of them and you will know roughly what a thousand messages costs you.
None of them asks the question you walked in with. You wanted to know whether you need this at all, and that answer is missing for a structural reason rather than a dishonest one. Those pages are published by companies whose software connects to the Platform. The Platform is the floor they stand on, so whether you need a floor is not a question they can take up.
I read Meta's own documentation for this on November 9, 2026, and the interesting finding was not the price. It is that the Platform makes a specific promise about what you are allowed to write, and for the kind of selling that happens in DMs, that promise runs the wrong way. The pricing pages move fastest, so those are the ones worth rereading if you find this much later.
The three names behind one product
Half the confusion on this subject is vocabulary, so that is worth clearing before anything else.
The WhatsApp Business API, the WhatsApp Business Platform and the Cloud API all point at the same thing. Meta renamed it along the way and the older name is what people still type into a search bar, which is why guides written a year apart appear to describe different products. There is one product, and it is the one outside software talks to.
What it is not is an app. You cannot download it, open it and look at your conversations. It is a developer product that another piece of software operates on your behalf, and your number has to be registered to it before anything happens. If what you are actually weighing is the ordinary account choice, which app to put your number on, that decision is a separate one and the comparison between the two WhatsApp apps handles it on its own terms.
What it asks of you before the first message
Start at Meta's getting started guide and you can see the shape of the thing from the table of contents. Before a single message leaves, you register as a developer, create a Meta app, attach a business portfolio, connect a messaging account, add a sending number, then replace your temporary access token with a permanent one issued to a system user holding three named permissions.
A vendor will do most of that for you, and the honest version of this section says so. Nobody expects a coach to generate their own tokens. The point is what the checklist reveals about the intended customer, because every step of it assumes a person whose job is building software, and none of it assumes a person whose job is talking to clients.
Two of the requirements stay yours no matter who handles the setup. The first is the number. Meta's page on business phone numbers is blunt about what registration does to it:
Registered numbers can still be used for everyday purposes, such as calling and text messages, but cannot be used with WhatsApp.
Your number keeps ringing, and it leaves the app your conversations live in. The same page adds a ceiling that matters to anyone holding numbers for clients: a new business portfolio starts out allowed two registered numbers, rising to twenty once the business is verified or once it has climbed to a messaging limit of two thousand.
Backing out is slower than going in. WhatsApp's page on deleting a number from the Business Platform restricts the deletion to admins of the WhatsApp Business app, blocks it entirely if the account has sent any chargeable message in the last 30 days, and warns that removing the number also erases all of its Platform data. That is not a setting you flip on a Tuesday to see how it feels.
Outside the 24-hour window, you cannot write your own sentence
This is the section the money articles skip, and it decides the whole question.
The Platform splits your messages in two using a timer. Meta's documentation on sending messages describes how the timer starts:
When a WhatsApp user messages you or calls you, a 24-hour timer called a customer service window starts.
While that window is open you can write whatever you like, in your own words, and the page confirms that these free-form replies need no clearance beforehand: "Unlike template messages, service messages do not require pre-approval." Every new message from the person resets the clock. So a live back-and-forth with someone who is answering you feels completely normal.
Then the clock runs out, and the rules change entirely:
When the window closes, you can only send pre-approved template messages.
Meta's template fundamentals page states the same restriction from the other direction, and adds what a template has to go through first. Templates are reviewed automatically when you create or edit them, review can take up to 24 hours, and nothing can be sent until the status reads approved. The page is equally specific about what a template is permitted to be:
Each template must be categorized as authentication, marketing, or utility.
Read that list again with your own inbox in mind. A woman asked your price in March, said she needed to talk it over with her husband, and went quiet. The message that reopens that conversation is not authentication, it is not a utility notification, and calling it marketing is both a stretch and an invitation to be rejected. There is no category for the only thing you want to send.
WhatsApp's Business Policy closes the gap from the compliance side, and the two lines that matter are short. "You may only initiate conversations using an approved Message Template," and:
We have the right to review, approve, pause and reject any Message Template at any time.
So on the Platform, your follow-ups are a fixed library of pre-cleared text that someone else can pause. A follow-up that earns a reply works precisely because it could not have been written for anybody else, which is the whole argument in reviving conversations that already happened, and it is the one shape a template system cannot hold.
The policy also requires an opt-in before you message anyone: the person has to have given you their number and confirmed that they want to hear from you. For a stock of old leads, that is a second condition nobody checks until they have already paid for the first.
The free app is not subject to any of it
The fact that settles this question sits in Meta's documentation, and almost nobody writing about pricing quotes it.
Meta documents a route it calls Coexistence, where a number runs on both the app and the Platform at once, and the page describing onboarding WhatsApp Business app users explains what happens to messages you send from the app:
Messages sent from the WhatsApp Business app are not subject to the customer service window
The same page says those messages "do not create, extend, or affect Cloud API conversation windows or Cloud API pricing," and that businesses "can still send messages on a one-to-one basis using the WhatsApp Business app," where sending stays free. Messages are mirrored between the two.
Take the measure of that. Meta's own design for a business that already uses the app keeps one-to-one conversations in the app, outside the window and outside the meter, and reserves the Platform for the messages that go out in bulk. The timer and the template library were never meant to govern the conversation you are having with one person. They govern notifications.
Which means the answer to your question is written into the product. If your sending is one human writing to another human about something that human already asked you, you are in the half that the app covers and the Platform was not built for.
The limits tell you who the Platform was designed for
The messaging limit settles any remaining doubt about the intended customer. Meta's page on messaging limits defines it as the number of distinct people you can deliver to in a rolling day, counting only messages sent outside a customer service window, and sets the starting point:
Newly created business portfolios have a messaging limit of 250.
From there the documented ladder runs to two thousand by completing a scaling path, then ten thousand, then a hundred thousand, then unlimited through automatic scaling. Climbing it requires templates carrying a high quality rating and, for the later steps, using at least half your current allowance over the preceding week. Quality ratings are assigned per number and per template, and they go down as well as up.
An architecture like that answers a real problem, and it is not yours. Somebody is trying to get from two hundred and fifty notifications a day to a hundred thousand, with a team watching rejection rates. A coach sending a handful of considered follow-ups each morning would sit at the bottom rung forever, paying a per-message bill the whole time, measured on an axis that has nothing to do with how their business works.
The bill itself is almost a footnote by this point. Meta's pricing documentation says billing moved to a per-message basis on July 1, 2025, that "Businesses are only charged when a message is delivered," and that the rate follows the category of the message and the country code of the person receiving it. There is a monthly allowance of service messages for each business number. Work out your own arithmetic there if you like, but the meter is the smaller cost. The larger one is that your follow-ups stop being yours to write.
When the API is the right answer
None of the above makes the Platform a bad product. It makes it a product for a different job, and that job is common enough that plenty of readers here genuinely need it.
Register your number if you send structured notifications that nobody needs to reply to: order confirmations, appointment reminders, shipping updates, a code to finish a login. Those fit the template categories cleanly because that is what the categories were drawn around, and the approval process stops being an obstacle when your text really is the same every time.
Register it if several people answer one business number all day, at volumes a phone in somebody's pocket cannot carry. Shared inboxes, routing, handoffs between agents and reporting across a team are the things the Platform does that no app does.
Register it if your message count is high enough that the ladder above reads as a plan rather than a wall, or if you need something the app simply does not expose, such as deep links into software your team already lives in.
| What you are doing | What that calls for |
|---|---|
| Reminders and confirmations at volume | The Platform, with templates |
| A team of agents on one business number | The Platform, for the shared inbox |
| Reopening old one-to-one conversations | The app, writing your own words |
| Sending the identical text to many people | Neither, and the reasons are in the broadcast rules |
That last line has its own article, because the shortcut most people try first is a broadcast, and who actually receives a WhatsApp broadcast is narrower than anyone expects.
What to use instead when you sell in conversations
If your real problem is that eighty conversations stopped without an answer and you cannot face scrolling back through them, that is a different problem from the one the Platform solves, and it has a different solution.
Ficiel connects to the WhatsApp account you already have. There is nothing to register, no number that leaves the app, no template to submit and no per-message meter, because it works inside conversations the other person opened. The Essentiel plan connects one account per channel, rereads 24 months of your history and includes 2 seats, at $117/mo with money back within 10 days. Connecting the three channels is three separate jobs, and what each one asks of you at setup goes through them one at a time.
Kord is Ficiel's AI assistant: it rereads your conversations, finds the leads who went quiet, drafts follow-ups in your own voice, and a human always approves before anything is sent. On this channel that means a thread which died on a question you asked comes back to the top of your list with a draft built from that exchange, waiting for you to read it:
You mentioned in March you wanted to run this past your husband before committing. Did the two of you land anywhere?
That sentence belongs to one conversation and could not be reused in a second one, which is both why it works and why no template library could hold it. Whether an approval step like that is real work or theater is a fair thing to ask, and we put it to the test in human in the loop.
One honest limit to end on. Nothing here makes your account safer than it was, and the published rules belong to WhatsApp rather than to any tool you buy. What changes is narrower: you keep the number you have, you keep the conversations behind it, and the message you send to someone who asked you a question eight months ago is a message you wrote.
FAQ
What is Ficiel?
Ficiel is an AI inbox for coaches and setters: it surfaces old Instagram, WhatsApp and LinkedIn conversations worth following up, drafts the message, and nothing is sent without your approval. On this subject it means there is no registration involved: it reads the WhatsApp account you already use, and the follow-up it prepares is free text rather than a pre-cleared template.
Do I need the WhatsApp Business API to send follow-ups?
No. One-to-one sending from the free WhatsApp Business app is what Meta's own documentation points app users toward, and messages sent that way sit outside the customer service window and outside per-message billing. The Platform becomes necessary when you are sending structured notifications at volume or running a team of agents on one number.
Can I send a normal message with the WhatsApp Business API?
Only while a customer service window is open, which happens when the person has messaged or called you in the preceding day. After that, Meta's documentation allows nothing but pre-approved template messages, categorized as authentication, marketing or utility, each one reviewed before it can be sent and liable to be paused or rejected later.
Does registering my number take it off the WhatsApp Business app?
In the standard route, yes. Meta states that a registered number still works for calls and texts but cannot be used with WhatsApp. There is also a Coexistence route where the app and the Platform share a number and messages are mirrored, which is worth asking any vendor about by name before you agree to anything.
What does the WhatsApp Business API cost?
Meta bills per message rather than per conversation since July 2025, charges only on delivery, and sets the rate by message category and by the recipient's country code, with a monthly allowance of service messages per business number. Published third-party rate tables go stale quickly, so read Meta's pricing page rather than a summary of it.
Is the WhatsApp Business API worth it for a coach or a solo setter?
Rarely. A new business portfolio starts with a cap of 250 recipients a day outside the customer service window and has to climb from there, which is a problem you only have if you are sending notifications in bulk. Against that you take on a registration, a bill, and a template library in place of writing your own follow-ups.
Will a follow-up tool make me register my number?
Some will, because they were built on the Platform and cannot reach your messages any other way. That constraint is theirs rather than yours, and it brings the number question and the per-message bill along with it. Ask before you pay, since the answer decides whether your existing conversations come with you.
