Key Takeaways
- Meta renamed the thing you are searching for. The current docs call it the WhatsApp Business Platform, so guides using the old name usually describe the old rules too.
- Connecting takes an afternoon. Running it takes a process. Template approval, messaging limits and quality rating are ongoing duties, not setup steps.
- You start at 250 recipients a day, not unlimited. New business portfolios open at a 250-person messaging limit, and climbing out needs verification or 2,000 delivered messages at a high quality rating.
- Answering customers is no longer free. Since October 1, 2026, service replies bill beyond 1,000 per number per month, and utility replies inside an open window bill too.
Search for the WhatsApp Business API and you will find setup guides describing a product Meta no longer documents under that name. Meta's own platform overview calls the whole surface the WhatsApp Business Platform, with the Cloud API as the part your software talks to, and the phrase WhatsApp Business API appears nowhere on the overview, pricing or get-started pages (checked 2026-10-24).
That is more than vocabulary. Guides still using the old name tend to describe the old self-hosted route and the old billing model, and both are gone. Getting connected is the easy half. What teams underestimate is the three things that run forever after: an approval queue for every template, a daily sending cap tied to your quality rating, and since October 1, 2026, a charge for answering the customers who wrote to you.
What the WhatsApp Business API Is Now
Two products carry the WhatsApp Business name, and the gap between them decides whether you need any of this.
| WhatsApp Business app | WhatsApp Business Platform (Cloud API) | |
|---|---|---|
Built for | One person on one phone | A team and your own software |
Built for WhatsApp Business appOne person on one phone WhatsApp Business Platform (Cloud API)A team and your own software | ||
Sending | By hand, from the device | Programmatically, from your systems |
Sending WhatsApp Business appBy hand, from the device WhatsApp Business Platform (Cloud API)Programmatically, from your systems | ||
Message templates | Not used | Required outside an open conversation |
Message templates WhatsApp Business appNot used WhatsApp Business Platform (Cloud API)Required outside an open conversation | ||
Reaching someone who never wrote you | Not workable at volume | Supported, through approved templates |
Reaching someone who never wrote you WhatsApp Business appNot workable at volume WhatsApp Business Platform (Cloud API)Supported, through approved templates | ||
Cost | Free | Billed per message delivered |
Cost WhatsApp Business appFree WhatsApp Business Platform (Cloud API)Billed per message delivered | ||
The self-hosted option is no longer a choice to weigh. Meta's On-Premises API sunset notice records that numbers could only be registered for the Cloud API from July 1, 2024, and that the final On-Premises client expired on October 23, 2025, after which numbers still registered there stopped delivering. Anything describing a self-hosted WhatsApp client is describing 2024.
Pick Your Route In: Direct or Through a Provider
Meta supports two ways in, and the choice is about who maintains the integration, not which features you get.
Direct integration means you create a Meta app, generate a system user token and call the Cloud API yourself. You hold the account, the webhooks and the template library. A 30-comment thread in r/WhatsAppBusiness_API follows a small business owner weighing this move off the free app, and the recurring answer is that direct is cheapest and also the route that leaves you owning every integration bug.
Through a solution provider means a Partner or Tech Provider onboards you, usually with a hosted inbox and template editor on top. You pay their layer plus Meta's message charges. The 70-comment provider comparison in r/whatsapp is a useful check on how little that market differentiates on capability and how much on price and support.
One detail before you shop: a provider who onboards you can verify your business on your behalf, which is one of the three routes out of the starting messaging limit. That is a real reason to use one beyond convenience.
You Can Keep the App on the Same Number
The old warning that going to the API costs you your phone number is out of date. Coexistence runs the Cloud API and the app on one number at once, with messages mirroring between them, and a 10-comment thread in r/WhatsappBusinessAPI covers what that changed for people who had avoided the migration for years.
What Onboarding Actually Requires
Meta's Cloud API get-started guide lists three prerequisites: a Facebook or managed Meta account, a developer registration, and a WhatsApp-enabled device for test messages. Everything else is a step, not a precondition.
- Create or select a business portfolio. Meta states you cannot use the platform without one. Your messaging limit is set at this level and shared by every number inside it, so the choice matters more than it looks.
- Create a Meta app with the WhatsApp use case, attached to that portfolio.
- Connect a Messaging account. Pick an existing one or create a WhatsApp Business account during setup. A new portfolio may generate one for you.
- Register the business phone number and confirm it with a six-digit PIN until it reads as connected.
- Generate credentials. The test token expires fast. Production needs a system user and a permanent token carrying the business management, messaging and WhatsApp management permissions.
- Add a payment method. Meta's pricing documentation tells businesses to keep one in Billing Hub, because service message delivery stops without it.
- Submit your first templates and wait for review before sending.
Note what is missing. You do not need a company registration to get a sandbox working, which is the question behind a 20-comment thread in r/WhatsappBusinessAPI from someone building a personal notification project. You do need a verified business to grow past the starting send limit, so a hobby integration works and a hobby rollout does not.
Verification is optional in the narrow sense: Meta's wording is that portfolios can be verified, and that verification status factors into improved functionality such as higher throughput and Official Business Account status. Read that as optional on day one and unavoidable by month two.
The Operational Work Nobody Budgets For
This is the part that decides whether your rollout holds up, and it is absent from most setup guides.
Template Approval Is a Standing Queue
Every message to someone outside an open conversation has to be an approved template, and Meta's documentation is explicit that templates generally require approval first. Opt-in is a hard requirement too, and it has to name your business and say what you intend to send.
Meta publishes no turnaround commitment for review. Plan on a rejected template costing you a cycle, and keep a library of approved variants rather than writing a fresh one per campaign.
Messaging Limits Start Low
Your messaging limit is the number of unique recipients you can message outside an open conversation per rolling 24 hours, and Meta's messaging limits documentation states that new business portfolios begin at 250.
| Messaging limit level | Unique recipients per 24 hours |
|---|---|
Starting level | 250 |
Messaging limit levelStarting level Unique recipients per 24 hours250 | |
Second level | 2,000 |
Messaging limit levelSecond level Unique recipients per 24 hours2,000 | |
Third level | 10,000 |
Messaging limit levelThird level Unique recipients per 24 hours10,000 | |
Fourth level | 100,000 |
Messaging limit levelFourth level Unique recipients per 24 hours100,000 | |
Top level | Unlimited |
Messaging limit levelTop level Unique recipients per 24 hoursUnlimited | |
Three paths move you from 250 to 2,000: verify your business, have the partner who onboarded you verify it, or deliver 2,000 messages outside conversation windows to unique numbers within a rolling 30 days using high-quality-rated templates. Meta then reviews quality and either approves automatic scaling or denies it and names the alternative path in an account alert.
Above 2,000, scaling is automatic within about six hours, but only while quality stays high across your numbers and templates and you used at least half your current limit in the last seven days. A cap you never fill is a cap you keep.
That rating is assigned per business phone number and per template. The technical ceilings sit well above most teams' needs, at 80 messages per second per number and one message every six seconds to the same person, so your real ceiling is the quality rating rather than the throughput number.
What It Costs Now That October Has Passed
Billing moved to per-message on July 1, 2025, and the conversation-based model is gone. Meta's pricing documentation carries a notice that the page reflects pricing updates effective as of October 1, 2026, by Messaging account timezone, and that Meta resumed charging per message for messages that were previously free.
Five categories, split by whether they need a template.
| Category | Template required | How it bills today |
|---|---|---|
Marketing | Yes | Charged on delivery, no volume tiers |
CategoryMarketing Template requiredYes How it bills todayCharged on delivery, no volume tiers | ||
Utility | Yes | Charged, including in-window replies since October 1, 2026 |
CategoryUtility Template requiredYes How it bills todayCharged, including in-window replies since October 1, 2026 | ||
Authentication | Yes | Charged, volume tiers available |
CategoryAuthentication Template requiredYes How it bills todayCharged, volume tiers available | ||
Service | No | Charged beyond 1,000 free messages per number per month |
CategoryService Template requiredNo How it bills todayCharged beyond 1,000 free messages per number per month | ||
Meta Business Agent | No | Charged per token, one global rate |
CategoryMeta Business Agent Template requiredNo How it bills todayCharged per token, one global rate | ||
Two mechanics shelter you. A 24-hour customer service window opens when someone messages or calls you, and resets each time they write again. A free entry point window, which Meta says may stay open for up to seven days, covers marketing, utility, authentication and service messages when the contact arrived through an ad or page button. Meta Business Agent messages keep billing inside it, at two US dollars per million tokens.
The exposure runs against intuition. Rates follow the recipient's country code and move as often as quarterly, and the teams hit hardest by the October change are the ones answering support fast inside an open window, which is the behaviour WhatsApp rewards everywhere else. A 200-comment thread in r/IndiaTech from three weeks ago shows how that landed with high-volume senders. Our WhatsApp Business API pricing breakdown runs a sample month.
Running It Inside a Scheduling Platform
meetergo is a Cologne-built platform where WhatsApp sits alongside scheduling, CRM and forms rather than as a standalone messaging subscription, with dedicated pages for sales, talent, healthcare and other verticals. For support teams the relevant piece is that approved templates fire from the workflows that already run your bookings.
Its WhatsApp Business integration connects to Meta's platform directly, and you build and submit templates from inside meetergo rather than in Meta's business tools. Setup follows the path above: sign in with Facebook, pick or create the WhatsApp Business account, enter the number and register it with the six-digit PIN. If the number already runs in the WhatsApp Business app, coexistence keeps the app working while meetergo sends in the background.
Workflow-driven templates
Templates become steps in a workflow, so appointment confirmations and appointment reminders carry reschedule and cancel links and reach guests who never messaged you first.
One number, unlimited seats
Team members share a single WhatsApp number with conversations assigned between them, and separate numbers can run per location or service line.
An AI agent that books
The conversational AI agent answers from your knowledge base, detects the customer's language, handles lead qualification into the CRM and books into your calendar inside the chat, then hands over to a person.
European processing
The agent runs on Mistral in France and Melious in Germany with no US cloud in the path, and prompts are processed to generate the reply, then neither stored nor used for training, which keeps data sovereignty intact.
Where this falls short. WhatsApp is a per-number add-on from €39 per number per month, and the integration page lists WhatsApp Business as included in the Premium plan (both checked 2026-10-24), so a team that wants messaging and nothing else is buying a scheduling suite to get it. Meta's charges land on your account either way, and the approval queue is Meta's. Tier prices sit on the pricing page. If your need is a shared inbox on your website instead, live chat is cheaper.
See what the scheduling side looks like first. No credit card required.
Common Mistakes
- Registering your team's number without coexistence. This used to mean losing the app, and it no longer has to. Check the coexistence path first, or read up on getting a separate number for WhatsApp if you want clean separation.
- Treating template approval as a setup task. Teams book a campaign, then find the template still in review. Build the library before the calendar.
- Planning volume against the limit you want. A campaign sized for 10,000 contacts fails at 250 on day one. Verify the business early, because that is the fastest route up.
- Budgeting by contact count. The bill follows message categories and recipient country codes, not list size. Two companies sending identical volumes to different markets get different invoices.
- Expecting a provider to absorb Meta's charges. The provider layer adds an inbox and a template editor. The per-message charges stay yours, which makes speed to lead a cost question now and not only a conversion one.
Who Should Adopt It, and Who Should Not
Adopt it if you send transactional messages at volume to customers who expect them, if your market treats WhatsApp as the default messaging app, and if someone owns the template library as a standing job. Those three conditions make the channel pay, and they are organisational rather than technical.
Skip it below a few thousand messages a month: the free app covers the same ground and your effort goes into Meta's review queue instead of your customers. Skip it for cold outbound too, because marketing rates apply to every send with no window to shelter behind, and a list that never opted in damages the quality rating you need to grow. If you want automated replies rather than outbound reach, a chatbot on your own site carries none of this overhead.
The API part of the WhatsApp Business API is the least interesting part of the decision. Pick your route, verify the business in week one, and staff the template queue. Then price a month of answering customers under the new rules, because that number is larger than it was in September.
Booking + video conferencing in one tool.
Booking + video conferencing in one tool.
FAQs
Is the WhatsApp Business API free to use?
No licence fee for access. Delivered messages bill individually, and since October 1, 2026 that includes service replies beyond 1,000 per number per month and utility replies inside an open window.
Do I need a registered company to get access?
Not for a test integration. You do need a business portfolio, and a verified business to pass the 250-recipient starting limit, so an unverified setup stays a sandbox.
Can I keep using the WhatsApp Business app on the same number?
Yes. Coexistence runs the app and the Cloud API on one number with messages mirroring between them, so your team keeps answering on the phone while automation sends alongside.
How long does template review take?
Meta publishes no turnaround commitment. Treat approval as a dependency of unknown duration and submit well before the campaign that needs it.
Do I have to go through a Business Service Provider?
No. Direct integration is supported and documented. A provider earns its fee if you want a hosted inbox, or want it to verify your business so you reach the 2,000-recipient level sooner.
Is the On-Premises API still an option?
No. The last client version expired on October 23, 2025, and numbers still registered to it stopped delivering. The Cloud API is the only route.
What is the quickest way to send WhatsApp reminders without building anything?
Connect the number through a platform that already holds your calendar. WhatsApp automation covers the five flows most teams build first; confirmations and a 24-hour reminder pay back quickest.
