WhatsApp Business API pricing, and what you pay

Every quote you will be given for WhatsApp business messaging is two numbers stapled together, and most vendors only show you one of them. Meta charges for the messages. The software you use to send them charges for the software. They are set by different companies, they move for different reasons, and a comparison that mixes them tells you nothing.

This is what each side is charging for, and which parts of your own behaviour move the total.

The two bills

The first bill comes from Meta. It is attached to your WhatsApp Business Account, the container that holds your phone numbers and your approved templates. Whoever owns that account is the party Meta invoices. This is the single most consequential detail in the whole arrangement, and it is decided before you send a message: if the account sits inside your own Meta business, the charges are yours and so is the account. If a vendor holds it for you and resells access, you are buying messages from the vendor at whatever margin they set, and leaving means starting again.

The second bill comes from the platform you use to write, send, route, and answer those messages. That one is priced however the vendor decided: per seat, per contact, per message on top of Meta's rate, or as a monthly credit pool.

Ask which arrangement applies to you in plain words, before you sign anything. A vendor whose answer is long is telling you something.

What Meta charges for now

Meta has moved WhatsApp to per-message pricing. The unit is one delivered template message, and the price depends on two things: the template's category and the recipient's country.

That is a real change from the model most comparison articles still describe. Under the older conversation-based pricing, the first message opened a 24-hour conversation and everything inside it was covered by one charge, priced by category. Under per-message pricing, five template messages are five charges. If a page quotes you a "conversation rate", check what year it was written.

Three things are not billed as template messages:

• Free-form replies you send inside an open conversation window. These are service messages: the customer wrote to you, you answered, and the answer costs nothing at the template rate.
• Utility templates sent while that window is still open. Meta treats them as part of the service conversation rather than as a new outbound message.
• The customer's own messages. Inbound is free, always. This matters more than it sounds, and there is a section on it below.

Categories are the price

There are three template categories, and Meta decides which one your template belongs to, not you.

You submit a template with a category. Meta reviews it and may reclassify it. A promotional line inside an order update is the standard way a utility template becomes a marketing template, and the first sign is usually the bill rather than an email.

Country is the other half. Meta publishes rates per market, and the spread between markets is wide enough that the same campaign can cost several times more depending on where your customers are. If you sell in more than one country, an average rate is not a useful planning number. Price each market separately.

The number that tells you what you were actually charged

You do not have to infer any of this. When WhatsApp reports a message as delivered, the delivery receipt carries the billing decision Meta made:

"pricing": {
  "billable": false,
  "category": "utility"
}

The object also carries a type naming the specific rate that applied. That payload is authoritative in a way your own reasoning about categories is not: it is what Meta will invoice. A utility template that landed inside an open service window comes back marked as not billable, and a template you submitted as utility that Meta reclassified comes back as marketing.

Any platform worth paying for captures this per message and reports on it. If your campaign report shows message counts but not billed categories, it is showing you sends rather than cost. Ask for the second one.

The vendor's side, and how to compare it

Software pricing in this category takes a few shapes, and they are hard to compare because each one hides the cost somewhere different.

• Per seat. Simple to reason about, and it stops mattering once your team stops growing. Check whether a seat that only reads conversations is billed like one that answers them.
• Per monthly active contact. You pay for unique contacts you exchanged messages with in the period. The details vary enough to change the answer entirely: whether an inbound-only contact counts, whether the count resets, and what happens when you go over. Ask all three.
• Per message, on top of Meta. Sometimes described as a markup, sometimes as credits. The only way to read this is to establish Meta's own rate for your markets first, then subtract.
• Flat plan with limits. Fine until you hit the limit. Ask what happens on the day you do: a hard stop, an overage rate, or an upgrade conversation.

There is no single right model. There is a wrong way to compare them, which is to put the headline monthly figures side by side. Build one estimate of your own sending volume, by category and by country, and price it through each vendor's model. Two of the three will change places.

What actually moves your bill

After the model is settled, the total is driven by things you control.

How much of your volume is outbound. Answering people who wrote to you is close to free. Starting conversations is what costs money. A business whose messaging is mostly inbound will find WhatsApp cheap; a business that treats it as a broadcast channel will not.

How many of your templates are marketing. Some messages genuinely are marketing and should be sent as marketing. But teams routinely send as marketing what is really a utility message about an order the customer already placed, because the copy drifted into an offer. Splitting those into two templates lowers the rate on the one that goes to everyone.

Whether you are sending to people who want to hear from you. This looks like a compliance question and is also a cost question. Messages to an unengaged list are billed exactly the same as messages to an engaged one, and they damage the quality rating that decides how many conversations you can start at all.

Failed and re-sent messages. A template rejected at send time costs nothing, but the work around it does, and some failure classes are worth retrying while others are not. A per-user throttle is genuinely temporary and the message can go later. A recipient who opted out is terminal, and re-sending is both a waste and a complaint waiting to happen.

A short way to estimate your own cost

Before you talk to any vendor, write down four numbers.

1. How many conversations do customers start with you in a month? Those are close to free on Meta's side, and they are the volume that decides which software plan you need.
2. How many utility templates will you send, and what share of them land inside an open window? Order updates triggered by a customer's own question are frequently free.
3. How many marketing templates will you send, to how many people, in which countries? This is almost always the largest line.
4. How many people need to be in the inbox at once? This decides the software tier more often than message volume does.

With those four, every vendor quote becomes comparable, and most of them get noticeably less exciting.

What to ask before you commit

• Who owns the WhatsApp Business Account, and what happens to the number and the approved templates if we leave?
• Do we pay Meta directly, or do you resell messages to us? If you resell, what is the markup?
• Does your reporting show the billed category per message, taken from Meta's delivery receipt?
• What exactly counts as a billable contact under your plan, and does an inbound-only contact count?
• What happens on the day we exceed the plan?

None of these are awkward questions. A vendor who has thought about the model will answer all five in about two minutes, and one who has not will tell you what it costs per month.