WhatsApp Business API Free Tier:What's Actually Free and What Isn't

The 3-layer cost model nobody draws for you

Every BSP pricing article presents WhatsApp API costs as a single blurry number. They are not. There are three completely separate cost layers, each billed by a different entity, each with different free zones. Understanding the separation is how you stop overpaying.

What Meta actually charges — the July 2025 update

On July 1, 2025, Meta shifted the WhatsApp Business API from a per-conversation pricing model to a per-message pricing model. This is the biggest pricing change since the API launched, and most articles still describe the old model.

Under the old model, Meta charged per 24-hour conversation window regardless of how many messages were exchanged inside it. Under the new model, Meta charges for each individual template message sent. The implications differ significantly depending on how you use the API:

• High-volume broadcast operations (many short template messages) get slightly cheaper per-message charges on some categories
• Conversational operations (long back-and-forth exchanges) that previously paid once per conversation may now pay more if they send multiple template messages within the same session
• Inbound-heavy operations where customers initiate contact are largely unaffected — customer-initiated windows remain free

What Meta does not charge for: receiving inbound messages. When a customer sends your WhatsApp Business number a message, that event costs you nothing from Meta. The webhook fires to your endpoint at zero Meta cost. You pay your webhook infrastructure (Layer 3) — that's it.

The 4 message categories: free, cheap, and expensive

Every message on the WhatsApp Cloud API falls into one of four categories. The category determines what you pay. Rates vary by country — what follows is the structure, not country-specific rates, since Meta publishes these on their business pricing page and they change periodically.

The pattern is consistent: the more you initiate and the more promotional the message, the more you pay. The more you respond to customers who came to you, the less you pay — often nothing.

The 24-hour service window: the most valuable free zone

The service window is the mechanism that makes WhatsApp genuinely cost-effective for inbound-heavy operations. Here is exactly how it works:

When a customer sends a message to your WhatsApp Business number, Meta opens a 24-hour service window. During this window, every message you send back — text, image, document, interactive message, or rich media — falls into the Service category and costs nothing beyond the first 1,000 service conversations per month (covered below).

The window resets each time the customer sends a new message. So an active customer support conversation where the customer keeps responding extends the free window continuously. You only start paying Meta's fees when you initiate contact or the window expires and you follow up with a template message.

The Layer you pay on top: platform and BSP fees

Here is where the confusion lives. Most businesses hear "WhatsApp API pricing" and assume they are hearing Meta's fees. They are usually hearing a BSP's blended price — Meta's Layer 1 fees plus the BSP's own Layer 2 subscription rolled together.

These are genuinely separate costs. Meta's fees go to Meta. Your BSP's fees go to the BSP. They are invoiced separately, negotiated separately, and can be changed independently. The implication: switching BSPs does not change what you pay Meta. And building directly on the Cloud API does not make you pay Meta differently.

What BSPs charge for in Layer 2:

• Their shared team inbox and conversation management UI
• No-code chatbot builder and flow designer
• Campaign and broadcast management tools
• CRM integrations (pre-built connections to HubSpot, Salesforce, etc.)
• Analytics dashboards and reporting
• Managed onboarding and Meta account setup support

If you are building your own logic — a custom AI agent, your own CRM integration, your own automation — you do not need a BSP's product stack. You need a webhook layer to receive inbound events and an access token to send outbound messages. The BSP's subscription (Layer 2) becomes an optional extra cost you are paying for features you never use.

What a developer-built inbound operation actually costs per month

Let's make this concrete. Here is the actual monthly cost breakdown for a business handling 900 inbound customer conversations per month, responding within the service window, and using SocialHook to receive webhook events — without any BSP subscription:

Scale that same operation to 5,000 inbound conversations — beyond the 1,000 free quota but still all within service windows. Meta charges a low per-conversation rate for service conversations beyond the free quota (the exact rate varies by country — check Meta's Business Pricing page). SocialHook still costs $50 flat. No BSP subscription. No per-message markup from anyone. Your costs scale at Meta's official service conversation rate only.

Compare this to a BSP route for the same operation: Meta's service conversation fees plus $80–$300/month for a BSP subscription you use primarily as a webhook receiver. The BSP is charging Layer 2 fees for a product layer you are not actually using. SocialHook's Layer 3 fee — $50 flat — is all you need for the webhook delivery itself. See the full feature comparison at socialhook.io/en/pricing.