The four things worth remembering
Meta's price is the same however you integrate. Direct or through a provider, Meta charges per message at the published rates. What a provider charges for its software is a separate line; keep the two apart when you read an invoice.
The billed price arrives after delivery. You can estimate a cost at send time, but the status webhook carries the price that matches the invoice.
Rate is category times country. Meta decides the category and can change it under you, and the country that counts is the recipient's, not yours.
From October 1, 2026, service messages are billable. Their rate is flat at every volume, so at scale service becomes the part of the bill that doesn't get cheaper.
The checklist
- Find out what share of your outbound volume is currently free: the estimate from Chapter 1.2, or your project's Usage screen if you're on Kapso.
- Tell whoever owns the budget, with a number attached.
- Audit your longest conversation flows for messages that exist only because the previous one was incomplete.
- Check that the template categories you're being billed for match the ones you think you registered.
Where to go next
If reducing turns is your biggest lever, the WhatsApp Flows documentation covers building the forms that replace message-by-message questions.
If you resell WhatsApp to your own customers, the next problem is attribution: working out which customer's traffic generated which part of the bill. We'll publish a separate guide on it.