WhatsApp costs are two separate bills: one from Meta, one from your provider. They're calculated on different units and arrive on different cycles.
Meta's charges
Meta charges per message. The rate is set by two things: the category of the message and the country your recipient is in. Your plan, your account and your negotiating position don't enter into it, beyond the volume tiers that apply to some categories.
This is the bill that moves with what you send, and it's the one this guide is about.
Partner charges
Everything else comes from whoever you send through, whether that's Kapso or another provider. That's a charge for software rather than for messages, so it's calculated on a different unit and billed on its own cycle.
The thing worth checking on your own invoice is whether your provider passes Meta's price through at cost or adds a margin to it. Kapso passes Meta's published USD price through without a markup, so the Meta line on a Kapso invoice is Meta's number. Not every provider works that way, and it's a common reason two quotes for the same traffic don't match.
What's changing
The rule until now has been simple: templates cost money, replies are free. That stops on October 1, 2026, when the free-form replies you send inside a customer conversation start being billed per message.
For a business that answers a lot of support, that can move a large share of outbound volume from free to paid without anything about its messaging changing. Section 2 works out how much, and what to do about it.
What this guide covers
- Which category a message is billed under, and who decides it.
- How to read the pricing object on a status webhook and say what the message cost.
- What October 1, 2026 does to your own bill, estimated from your message history.
- The four changes that most reduce spend.
Throughout the guide we use a single fictional company, Vera Market, so every concept comes with a number attached.