Data & benchmarks

Meta Made Your Buyer's Reply Free. Some Messaging APIs Still Charge You For It.

A kraft paper parcel tied with string, a small ceramic dish and a spool of orange thread on a linen surface.

A repeat buyer messages back inside the free reply window WhatsApp itself created, already knowing the product, the size and the delivery city. Somewhere behind that reply sits a messaging API charging a fee for it anyway.

What metered messaging APIs are built for

Developer messaging APIs exist to let a technical team route WhatsApp traffic at scale, often across many products, brands or campaigns at once. Pricing by message volume makes sense when a platform is serving thousands of businesses through one pipe. For that kind of infrastructure, a per-message rate is a fair way to bill. A solo seller closing one order at a time is not running infrastructure. You are running a shop.

Why a per-message fee loses what a conversation keeps

What happens when a buyer replies inside the window Meta made free in November 2024? Under a metered API, that reply can still carry a fee, because the platform bills by message rather than by conversation. It adds up quietly, one reply at a time, on exactly the messages that should cost nothing. A metered line counts messages. Your checkout counts sales.

The per-message rate looks fair

A blended per-message rate looks fair. One number covers everything. No seat fees, no hidden tiers. Surely a flat rate per message means the cost stays predictable?

Never.

Predictable is not the same as free. A buyer who replies five times to confirm size, payment and delivery costs five times over, even though the conversation itself never changed. That is one remembered checkout, not five billed messages.

Where a sales assistant fits

This is where a WhatsApp sales assistant supports a solo seller closing orders on their own number. It keeps product, size, stock, price, payment preference and delivery city inside the same WhatsApp thread the buyer already started, with no per-message meter deciding whether a reply is worth answering. The order closes without asking the buyer to repeat anything they already told you.

Why this wins for a growing shop

Metered messaging APIs are strong infrastructure for platforms routing traffic across many brands at once. That is not a criticism. It is what they are built for. A solo seller needs something different, one remembered checkout that never resets, on your own WhatsApp number, with no per-message fee deciding how a buyer gets answered. See pricing when you are ready to set it up.

Close every order in one thread

Frequently asked questions

What are developer messaging APIs built for?
They let a technical team route WhatsApp traffic at scale, often for a large platform serving many businesses through one connection. Billing by message volume makes sense at that scale.
Did WhatsApp really make some replies free?
Meta opened a free service window for replies inside an existing conversation in November 2024, covering many routine follow-up messages between a business and a customer.
So why would a seller still pay for those replies?
Some platforms bill by message rather than by conversation, so a fee can still apply on top of the underlying WhatsApp cost, even on a reply that falls inside a free window.
Is a per-message API a poor choice for every seller?
No. For a platform managing many brands or a high volume of automated sends, per-message pricing keeps billing simple. It is built for a different job than one seller closing individual orders.
Does a remembered checkout change how a buyer pays?
No. Payment still happens however the seller normally arranges it. The thread only keeps the product, size, stock and delivery detail together so nothing needs repeating.