Almost everyone shopping for a WhatsApp AI agent hits the same wall in the first week. The demo looks great, the pricing makes sense, and then someone says "you will need the API" and the conversation turns into acronyms: WABA, BSP, business verification, template categories, the 24-hour window. None of it is hard, it is just unfamiliar, and most vendors skip it because explaining it feels like friction. Here it is in plain language, including the parts that will slow you down.
What is the difference between WhatsApp Business, the app, and the API?
WhatsApp Business is the free app you download on a phone. It gives you a business profile, labels, quick replies and an away message, and one person answers by hand from that device. It is genuinely good for a small operation, and it is also a closed box: no other software can read your incoming messages or send replies for you.
The WhatsApp Business API is the opposite. It has no interface at all. It is an endpoint that receives messages as data and sends messages as calls, so everything you see on top of it (an inbox, a CRM, an AI agent) is built by someone else. That is what unlocks several operators on one number, integrations with your calendar or payment provider, and automation that runs while nobody is watching.
The part that matters for your decision: an AI agent can only run on the API. Anything claiming to put artificial intelligence inside the free app is either a person typing or an unofficial workaround that risks getting your number blocked, and losing the number your customers have saved is not a recoverable mistake.
What do you actually need to get access?
Five things. In practice you will collect them in this order.
A Meta Business account. The free container that owns your business assets: your Facebook page, your ad accounts and, eventually, your WhatsApp Business Account. If you have ever run Meta ads, you already have one. The WhatsApp Business Account (written as WABA) lives inside it and holds your phone numbers and your message templates.
Business verification. Meta confirms your business is a real, identifiable entity. You submit your legal name, address and contact details, plus a supporting document such as a business registration certificate, a tax document or a utility bill. The most common cause of delay is inconsistency: the name on the document has to match the name you typed, which has to match what is publicly visible about your company. You can test before you are verified, but you cannot grow your messaging limits without it.
A phone number that is not active on WhatsApp. The number you register cannot be in use in the WhatsApp app or the WhatsApp Business app at the same time, because a number lives in one place. It has to receive a verification code by SMS or voice call, so a landline works if someone can pick it up. If the number you want is already running in the app, you delete that account inside the app first, which also deletes that chat history from the device. Many businesses avoid the disruption by starting the agent on a new number.
A display name. What customers see at the top of the chat instead of a raw phone number. Meta reviews it against a display name policy: it has to reflect your actual business, it cannot be a generic word, and it cannot imply something you are not. Changing it later goes through review again.
A provider or platform. Meta hosts the Cloud API itself and a developer can connect directly, but the raw API gives you nothing to work with: no inbox, no history, no logic. Most businesses go through a Business Solution Provider or a platform that handles number registration, webhooks, template submission and delivery. Check ownership before signing anything: the WhatsApp Business Account and the number should sit inside your own Meta Business account, not the provider's.
Why message templates exist, and what the 24-hour window changes
WhatsApp is a private inbox, so Meta gates the messages a business starts. That gate is the message template: a pre-written structure with variable placeholders, submitted for review and sendable only once approved.
Templates are approved in three categories. Marketing covers promotions, offers and anything that brings a quiet contact back. Utility covers messages tied to a transaction the customer already has with you: an appointment confirmation, a reschedule, an order update. Authentication covers one-time codes. A fourth word appears in Meta's documentation, service, and the difference matters: service is not a category you submit a template for. It labels the free-form replies you send while a customer service window is open.
That window shapes every agent design. Each time a customer sends you a message, a 24-hour customer service window opens. Inside it, your agent writes whatever the conversation calls for, with no template and no pre-approval. When the window closes, free-form messages stop going through and the only way back to that person is an approved template.
A well-built agent treats that clock as part of its logic. HeySetter's follow-ups at 2 hours and 8 hours land inside the open window as normal messages. The one at 48 hours cannot, so it goes out as a re-engagement template. Same intent, different mechanism, because the window closed in between.
Turn WhatsApp chats into paid bookings, automatically.
Start freeHow much does the API itself cost?
Since July 1, 2025, Meta charges per delivered template message rather than per conversation. Replies your agent sends inside an open customer service window are not charged. Rates for template messages vary by the recipient's country and by the template category, so the same text costs different amounts depending on who receives it and how it is classified. Meta bills those fees directly to your own Meta Business account, separate from whatever the platform you use costs.
No one can honestly quote you a single figure, because your bill depends on which countries you message and how much of your volume is template-initiated rather than in-window. Meta publishes the rate card that applies to you, and it is the only source worth citing. What you control is the mix: an agent that replies fast enough to keep conversations inside the window sends far fewer paid templates than one that lets leads go cold and then chases them.
The mistakes that stall most connections
Using a number that is still live in the WhatsApp app. The leading cause of a failed registration, and the fix is not a setting: the account has to be deleted from the app first, and that step erases the chat history on that device. It should be a decision, not a surprise.
A display name that gets rejected. Names that are generic, that describe a category rather than a business, or that match no public trace of your company tend to come back rejected. Use your legal or commercial name and you rarely have a problem.
Templates written as marketing when the correct category is utility. People write "we would love to see you again, check out our offers" for what is really an appointment reminder. Meta reviews category assignment and can reclassify a template, changing what you pay and how it performs. Write the message for what it is: a specific, transactional update to someone who already deals with you.
Trying to raise messaging limits before business verification. New numbers start with a limited number of unique customers they can message in a rolling 24 hours, and that ceiling rises in steps as you build a history of quality sends. Verification is a prerequisite for that climb, not an optional badge. Leave it for later and you meet the limit on the day you most need volume.
How HeySetter handles this part
Connecting WhatsApp is step 3 of a 6-step guided setup, and it is the step we walk through with you, because it involves Meta rather than us. You end up on the official WhatsApp Business API, on your own number, with your own display name.
Ownership does not move. The Meta Business account, the WhatsApp Business Account, the number and the conversation history are yours. If you ever leave, you disconnect the platform and keep the asset your customers already have saved in their phones.
Frequently asked questions
No. A number can only be registered in one place at a time, so once it moves to the API the app stops working for it. Your team keeps answering, but from the dashboard instead of the phone, and several people can work the same number at once.
Not strictly, but verification works by matching what you declare against what is publicly checkable about your company. A live site with your legal name, address and contact details, consistent with your submitted documents, removes most of the friction. Mismatched or outdated information is the usual reason a review comes back.
It varies by country, by how complete your documents are, and by review volume at the time. Some businesses clear everything in a single sitting, others wait several days on a verification round trip. Plan a buffer before any launch date you have committed to, and prepare your documents before you start.
You edit and resubmit. Rejections are usually about wording rather than intent: a category mismatch, a placeholder in a position Meta does not accept, or promotional language in a message meant to be transactional. Nothing else about your account is affected, and your existing approved templates keep working.
No. The number and the WhatsApp Business Account stay inside your own Meta Business account, so you disconnect the platform and connect a different one. That is worth verifying with any vendor you evaluate, because setups where the provider owns the asset are hard to unwind. Ready to skip the guesswork? Start your 7-day free trial with no card, and we will walk you through the Meta connection step by step.
