Quick answer: Meta moved WhatsApp Business Platform billing from per-conversation to per-message across 2025-2026. The old model charged once when a business opened a 24-hour conversation window, whatever happened inside it; the new model prices each template message individually by category — marketing, utility, or authentication — while customer-initiated service conversations stay free. In parallel, Meta widened the no-charge path: customers who reach you from a Click-to-WhatsApp ad or a Facebook Page call-to-action open a free entry-point window, and inbound service conversations have no per-message fee. For a business, spend now tracks which template categories you send, not just how many conversations you open — so template discipline and volitional engagement decide the invoice.
What changed
The legacy model priced conversations. A template send or an inbound message opened a 24-hour window billed per category: marketing at the top rate, utility lower, authentication lowest, service (the reply window) tiered separately. Everything that followed inside the window was covered by the initial charge, so the economics favored packing exchanges into one window.
The shifted model prices template messages individually. Each template send draws its category's per-message rate from Meta's rate card, whether or not a window is open. Four boundary changes follow:
- Per-message template pricing. A template is billable on delivery, priced by its assigned category. Sending five utility templates to one customer costs five utility messages, not one utility conversation.
- Service conversations stay free. Replies typed inside the customer-initiated 24-hour window carry no Meta charge, same as before — inbound service traffic is still the zero-cost lane.
- Free entry points widened. When a customer writes in from a Click-to-WhatsApp ad or a Facebook Page call-to-action, Meta opens a free entry-point window, and business responses inside it are not charged. Volitional traffic from owned or paid entry points costs nothing at the messaging layer.
- Category reassignment is the new variance. Meta re-scores template categories as it reviews them; a template that reads as marketing content gets the marketing rate regardless of the label it was submitted under. Re-classification is where a forecast drifts — utility intent written like promotion bills at marketing rates.
Meta's published rate card per category and market remains the source of truth; Orbit passes Meta's own fees through at zero platform markup, so the shift lands on the Meta side of the bill, not on ours.
What it changes for your bill
Three moves decide spend under per-message pricing:
- Route to the free lane first. A customer who messages in opens a service window — replies there cost nothing. Frequent, high-turnover exchanges (delivery updates, support threads) belong in that lane; a template is reserved for re-contacting the customer outside the window.
- Watch category, not just volume. Marketing is the premium lane, so marketing volume is where growth multiplies. Utility and authentication rates are the cheap lanes — keep transactional templates clean of promotional copy or Meta's reviewers re-tag them at marketing rates.
- Exploit the free entry points. Campaigns deep-linked into WhatsApp from ads or a Facebook Page CTA open free windows. Shifting acquisition traffic onto those entry points removes the per-message charge for the re-engagement it generates.
How Orbit's tenant-owned controls interplay
The pricing model is Meta's; what you let send, and when, is your call. Orbit exposes the levers and the enforcement points; the posture is tenant-owned.
- Templates and category hygiene. You submit and manage templates under Channels → WhatsApp → Templates, where each template's Meta-assigned category stays visible — so a re-classified template surfaces before it bills at the wrong rate. The WhatsApp channel docs cover template management end to end.
- Session-window logic. Orbit enforces Meta's 24-hour rule at send time, and a window-status endpoint answers whether a recipient is still inside the window before you compose. Under per-message pricing that check has a second use: within the window, prefer the free form of a session message; outside it, decide whether the template is worth its category's charge.
- Frequency caps. Tenant-configured frequency caps limit how often outbound templates reach a given contact. Under per-message billing, a cap is a spend ceiling as much as a courtesy — a runaway campaign burns per message now, not once per conversation.
- Consent tracking. Consent and opt-in state is recorded on the contact profile, and every send pipeline checks it before dispatch. Charging per message widens the cost of a non-consented send from a policy breach to a billable breach — the gate holds either way.
- Per-category spend visibility. Messaging analytics split channel spend by template category, so the marketing lane is visible as its own line rather than an aggregate — the split the new model makes load-bearing.
None of these is a pricing guarantee; Meta owns the rate card. What changes is that the controls above now decide real money per send, and they remain yours to set.
Frequently asked questions
What changed in WhatsApp Business Platform pricing?
Meta moved billing from per-conversation to per-message: each template message is priced individually by category (marketing, utility, authentication) rather than one conversation window covering unlimited sends. Customer-initiated service conversations remain free.
Are inbound-initiated conversations charged under the new model?
No. Service conversations — your free-form replies inside the 24-hour window a customer's inbound message opened — carry no Meta charge, same as before. The per-message charge applies to template sends.
What are the free entry-point windows?
When a customer messages you from a Click-to-WhatsApp ad or a Facebook Page call-to-action, Meta opens a free entry-point window and responses inside it are not charged. Traffic from those entry points costs nothing at the messaging layer.
How do template categories affect cost now?
More than before. Under per-message pricing, every send draws its category's rate, and Meta re-scores categories on review — utility intent written like promotion bills at marketing rates. Keeping transactional templates clean of promotional copy is now a direct cost control.
What does Orbit charge on top of Meta's fees?
Nothing at the messaging layer: Orbit passes Meta's per-message fees through at zero platform markup. The template, window, frequency-cap, and consent controls above are tenant-owned settings on the platform, not billable add-ons.
Resources
- WhatsApp Business API guide for 2026 — the product explainer this pricing shift sits on.
- WhatsApp calling GA analysis — the channel's other 2025-2026 shift, into voice.
- WhatsApp channel docs — templates, session windows, and broadcast mechanics as shipped.
- Messaging on Orbit — WhatsApp, SMS, RCS, and the rest on one bill.
Published 30 August 2026.