Understanding the WhatsApp Business API: per-category and per-country pricing, free messages, BSP role and integration with Versatik AI agents.
The WhatsApp Business API is Meta's official interface that allows businesses to connect WhatsApp to their tools, CRM and AI agents to automate support, lead qualification, notifications and customer exchanges at scale. It is the essential technical building block to deploy a WhatsApp chatbot or a WhatsApp voicebot. Check out our complete WhatsApp AI automation guide.
Replies sent within conversations initiated by your customers are not billed by Meta. A key advantage for high-volume inbound support.
Confirmations, appointment reminders, order updates: charged only outside the 24-hour window or outside a direct customer reply.
OTP, account validation and security messages. They follow a separate pricing logic, distinct from other categories.
Promotions, commercial follow-ups, offers and campaigns. Proactive messages with a commercial purpose — the highest-priced category.
The WhatsApp Business API, also known as the WhatsApp Business Platform, is an interface designed for businesses that want to use WhatsApp in a professional, automated and integrated way. Unlike the WhatsApp Business app, it is not designed for manual management on a single phone, but for structured use cases: customer support, transactional notifications, campaigns, integrations and AI agents.
In practice, the API allows an external system to read, send, classify and process WhatsApp messages according to business rules. It is what allows an AI agent to automatically reply to a customer, send an appointment reminder, qualify a lead or hand off a conversation to a human advisor.
| Criterion | WhatsApp Business app | WhatsApp Business API |
|---|---|---|
| Usage | 1 user, manual replies | Multi-user, full automation |
| Automation | Quick replies, basic away messages | AI chatbot, voicebot, advanced scenarios |
| Integrations | None | CRM, ERP, calendar, ticketing |
| WhatsApp calls | Personal only | Inbound and outbound via API |
| Pricing | Free | Meta per-message fees + platform |
| For whom | Small businesses, freelancers | SMEs, mid-market, high-volume companies |
Automate inbound and outbound messages with an AI chatbot: lead qualification, 24/7 replies, appointment booking without human intervention.
Handle voice calls on WhatsApp with an AI voicebot: answer inbound calls, initiate outbound ones, transfer to a human when needed.
Connect WhatsApp to your CRM, helpdesk, calendar or ERP to centralise exchanges and eliminate manual re-entry.
Appointment reminders, confirmations, order updates — automatically, at the right time, in the right context.
Yes, messages received from your customers do not incur Meta charges as incoming messages. Meta states that it does not charge for service messages, nor for utility messages sent in response to a customer within the 24-hour window. In practice, a large share of inbound support exchanges can be very low cost, or even free on Meta's side.
You should, however, distinguish Meta charges (which can be zero in some cases) from provider / BSP charges (which may bill the platform, API usage or a per-message fee).
Meta charges based on three main factors: the message category, the recipient's country, and whether the message is sent within a free window or not. The dominant logic is per-delivered-message pricing, with free-tier rules depending on the conversation context.
For an appointment reminder (category Utility, outside the free window), here are approximate figures for Meta's share only:
| Recipient country | Approx. Utility cost | Note |
|---|---|---|
| France | ~€0.035 | Western Europe level |
| Spain | ~€0.023 | Lower than France |
| Germany | ~€0.054 | Among the highest in Europe |
| United Kingdom | ~€0.019 | Lower than France |
| Morocco | ~€0.0046 | Very low cost |
These figures correspond to Meta's share only and may change. They do not include your API provider's fees.
For 1,000 messages sent outside the free window:
| Country | Estimated Meta cost |
|---|---|
| France | ~€35 |
| Spain | ~€23 |
| Germany | ~€54 |
| United Kingdom | ~€19 |
| Morocco | ~€4.60 |
For an international business, it is useful to segment costs by market and distinguish transactional campaigns from marketing use cases.
The appointment reminder is one of the strongest use cases on the WhatsApp Business API: an expected message, high operational value, low cost compared to the time saved and appointments secured.
With Versatik, this flow can be integrated into a wider AI agent that books the appointment, sends the confirmation, automatically follows up before the deadline, then hands off to a human or a WhatsApp voicebot if the customer replies with a specific request.
Yes. To use the WhatsApp Business API, you must go through a provider / BSP that acts as a technical intermediary with Meta. This provider handles API access, templates, routing and sometimes a management interface. Total pricing therefore combines Meta charges (based on category and country) and provider charges (based on their own pricing model).
Meta enforces a strict framework for business conversations:
Versatik helps you set up the opt-in and consent journey to ensure your campaigns are compliant.
It is Meta's official interface that allows businesses to use WhatsApp in an integrated, automated way connected to their business tools.
The app is designed for manual, simple use. The API is used to automate, integrate and scale WhatsApp exchanges with systems such as a CRM or an AI agent.
Inbound messages do not generate Meta charges as such, and Meta does not charge for service messages or utility templates sent in response within the 24-hour window. Your provider may apply its own fees.
Yes, in the vast majority of cases. It falls into the category of transactional messages useful to the customer.
Meta applies per-market pricing: the price depends on the recipient's country and the message category. This is why the same reminder costs more in Germany than in Morocco.
Yes, access goes through a provider / BSP or a platform that relies on one.
Yes, that is actually one of the main benefits of the API. It can feed an AI agent that handles text, voice or both.
Compliance depends on the provider chosen, the technical architecture and how data is stored and processed. This needs to be addressed from the outset.