Home / Blog / Template vs. Session Messages: Getting WhatsApp Pricing Right
WhatsApp APIMay 23, 2026·2 min read

Template vs. Session Messages: Getting WhatsApp Pricing Right

WhatsApp billing is built around conversation categories and the 24-hour window. Here's how to model your costs before you scale.

When teams plan a WhatsApp rollout, the first question is usually "what does it cost?" The honest answer: it depends on how you message — and the pricing model rewards businesses that understand the 24-hour session window.

Conversations, not messages

WhatsApp doesn't bill per message. It bills per conversation — a 24-hour thread between you and a customer. Within one conversation you can exchange many messages for a single charge. This is a crucial planning insight: the cost driver is how many conversations you open, not how chatty you are inside them.

Conversations fall into categories — typically utility, authentication, marketing, and service — and each is priced differently by country. Authentication (OTP) and utility (order updates) are generally cheaper than marketing.

The 24-hour window changes your math

Here's the lever most teams miss. When a customer messages you, a free-form service window opens for 24 hours. Within it, your replies don't require templates, and in many pricing schemes customer-initiated service conversations are the cheapest category — sometimes free up to a monthly allowance.

So a support flow where customers reach out first is dramatically cheaper than a marketing flow where you're always the initiator. If you can design interactions so customers start the conversation — a "message us" button, a QR code on a receipt — you shift volume into the cheaper category.

A simple cost model

To estimate monthly spend, you only need three numbers:

  1. Conversations opened per month, split by who initiates.
  2. The category mix — what share is authentication vs. utility vs. marketing.
  3. Your country's per-category rate.

Multiply and sum. Notice that sending ten messages inside one conversation costs the same as sending one — so batching updates into an existing thread is free efficiency.

Practical takeaways

Model this before you scale, and WhatsApp stays predictable. Skip it, and a marketing-heavy strategy can get expensive fast.

Build with Abati Technology

We build software that ships — WhatsApp API, developer tools, POS, and mobile apps. Let's talk about your project.

Get in Touch →