A WhatsApp message needs two independent checks: whether the business may send it and how delivery will be charged. An open customer service window permits certain non-template replies; it no longer means every reply is free. Build these checks into the sending workflow rather than leaving them to an operator's memory.
This guide covers ordinary business messaging through the platform. Specialized AI Provider rules, eligibility exemptions, provider fees, and account contracts require their own review.
Separate permission from price
A template is approved content with a defined category and structure. Non-template service messages allow a business to respond more freely during the supported customer service window.
Under the current Business Messaging Policy, that window lasts 24 hours and opens or resets when the user sends a message. Outside it, the business must use an approved template. A business sending another message does not by itself extend that window.
Keep the latest qualifying inbound timestamp in the application. Recheck it when a queued message is about to send, not only when staff first compose the reply. A notification waiting behind an outage may cross the boundary before execution.
Opt-in and suppression are additional checks. A usable template and an open window do not create permission to contact someone who has opted out. The CRM integration guide explains where to retain that operational evidence.
What changed in October 2026
Last verified: October 2026. Meta's current developer documentation says that from October 1, 2026, service replies and utility templates inside the service window are chargeable on delivery, subject to applicable allowances and exemptions. This replaces older guidance describing universally free service replies and in-window utility templates. Policy and rates can change.
The following points are verified against the current pricing overview, rather than an old conversation-pricing calculator:
- Billing is based on delivered business-to-user messages, with category and recipient market affecting the rate.
- Each business phone number has 1,000 free service messages monthly, with no rollover; charges start after that allowance.
- A qualifying click-to-WhatsApp entry and response can open a free entry point window lasting up to seven days.
- Eligible government/non-profit treatment and specialized AI Provider rules have separate scope.
Last verified: October 2026. These are platform rules, not a rate quote. No India, USD, INR, or other country/currency unit rates are quoted here because the current downloadable rate cards were not independently retrieved for this article. Select the actual recipient market, account currency, category, and effective date before budgeting.
The public WhatsApp pricing landing page retrieved during research still described the older free-service behavior. Use the current dated developer overview and account billing evidence when reconciling this discrepancy. Do not combine an old free allowance or window duration with a newer rate card.
Understand the template categories
| Category | Intended purpose | Illustrative business example |
|---|---|---|
| Utility | Specific non-promotional updates related to a user action, request, account, or essential need | Confirming a particular appointment change |
| Authentication | Identity verification through the supported authentication template format | Delivering a login verification code |
| Marketing | Promotional or other marketing objectives | Offering an upgrade or discount |
Meta's categorization documentation says mixed utility and promotional content is marketing. A transaction reference does not turn an upsell into a utility message. For example, combining an appointment confirmation with an unrelated discount changes the content that must be evaluated.
Treat examples as illustrations rather than approval promises. Meta can categorize and review the actual submitted content, and current documentation describes automatic category updates. Keep the category and approval state synchronized with the account instead of assuming they are permanent application constants.
Give templates stable internal purposes. Application code should request an appointment confirmation, then resolve the approved template, language, and supported parameters. It should not choose a template by searching for the cheapest category.
Keep the free entry point separate
The free entry point window and customer service window answer different questions. One concerns a qualifying entry source and charging treatment; the other limits when a non-template response is allowed.
Do not infer that a longer charging exception permits unrestricted non-template replies after the customer service window closes. Check the supported message type before every send. Retain the entry-source evidence supplied by the integration and use documented eligibility rules rather than marking every ad-attributed contact as free.
Meta Business Agent is also distinct from a third-party chatbot. Current non-template pricing documentation describes its own token-based billing. A third-party AI reply does not acquire that billing model merely because an AI wrote it. Include the external AI supplier's charges separately in the operating budget.
Model a month with explicit assumptions
Use a worksheet containing the business number, Messaging account, recipient market, currency, category, delivered count, applicable free treatment, and provider fee. Preserve the effective date of every selected rate.
Consider an illustrative ordinary business with one number and 2,500 delivered service messages during a month, no qualifying free entry point messages, and no special exemption. Applying the verified monthly service allowance leaves 1,500 service messages to price. This is arithmetic under stated assumptions, not a forecast or a unit-rate quote.
Add billable utility, authentication, and marketing deliveries using their applicable rates and tier rules. Do not price the whole month as conversations or multiply all categories by one blended rate without retaining the underlying mix.
Keep Meta charges separate from BSP seats, automation, markup, engineering, and third-party AI. The Cloud API vs BSP guide uses that separation to compare operating models.
Build an auditable send decision
Store the business event, recipient identity, consent evidence, suppression state, latest inbound timestamp, selected template and language, current category, and outbound operation ID. Keep the resulting provider message ID and status evidence with the operation.
Check eligibility again just before sending. A template can become unavailable, the user can opt out, or an agent can resolve the underlying issue while a job waits. Cancelling stale work is better than delivering a technically valid but unwanted message.
Track accepted, delivered, failed, and unknown states separately. A successful API request is not a delivery receipt. If the response is lost, reconciliation is an engineering concern; avoid assuming that another send attempt is necessarily safe.
Review both customer experience and cost
Monitor how many messages a workflow produces and whether each helps the customer act. Multiple short automated replies can add noise and increase delivered-message volume. Combine information when it remains clear, while preserving the ability to reach a human.
Review template state, sending failures, suppression behavior, usage, and invoices together. A sudden cost change can come from message mix or eligibility, not only customer growth. Keep the integration implementation explicit about those state changes so staff can investigate an individual send.