WhatsApp Business Pricing in South Africa Now Depends on How Many Numbers You Run

Since 1 October 2026, Meta charges per message for WhatsApp Business Platform service messages, the replies a business sends after a customer writes first. Meta's updated WhatsApp Business Platform pricing rules also start charging for utility messages sent inside an open 24 hour customer service window. Most owners will look at the rate. I would look first at how many WhatsApp numbers the business runs, because that now changes what you pay.

Why the number of WhatsApp numbers now matters

Meta counts the free allowance per phone number, but it counts volume discounts across the whole business. Every business phone number gets 1,000 free service messages a month. Charging starts at the 1,001st, and free messages you do not use do not roll over to the next month. Volume tiers work at a different level: Meta calculates them across every messaging account in your business portfolio, not per number. Service messages get no volume tiers at all, and they are charged at the same rate as utility and authentication messages.

So the two rules do not cancel each other out. If you run WhatsApp Business on multiple numbers, each number brings its own 1,000 free replies, and you lose nothing on volume tiers because those are pooled at portfolio level anyway. That does not make more numbers automatically cheaper. Each number still has to be set up and answered. Service replies had been free since November 2024, so until now number count barely mattered for them.

Service messages are replies only, sent inside the open 24 hour window. Our earlier piece on how session windows drive WhatsApp costs covers that part.

Your software should not decide your number count for you

When we scoped a WhatsApp system for a South African property business working with multiple agents, the design ran every agent through one central number. The agent's identity travels in the message, not in the number. The link on each agent's own website opens WhatsApp with a prefilled message carrying a reference tag for the agent and the property. In that design, the system reads the tag, queries only that agent's properties, and for the rest of the conversation the bot serves only that agent's portfolio, so leads never leak across agents. For leads from third-party property portals, where we do not control the link, the system reads the listing page's title, price and suburb to match it against the listings. The agent still gets the feel of a private line, on shared infrastructure.

I am not saying one number is the right answer. The useful part is that the routing reads the tag in the message, not the number it arrived on. When routing is tied to the number, a pricing change like this one becomes a software change. That decision belongs in the scoping of any custom software development project, not on a monthly bill.

What to check this month

Count how many WhatsApp Business numbers your business actually runs, including any a branch manager set up once and nobody remembers. Then look at how many service replies each number sends in a month. A quiet number sits well inside its free tier. A busy support line may not, and you want to know that before the invoice does. Ask whoever built your WhatsApp setup whether routing depends on the number. That answer decides how much freedom you have.

Then check that a payment method is on file. Without one, Meta delivers service messages within the free tier and stops after it is used up. The 1,001st reply of the month simply does not arrive, and the customer sees silence. Conversations started from click to WhatsApp ads stay free inside their entry point window, so ordinary customer service takes the hit.

You can budget for a per message rate. A reply that never arrives is different, because you usually hear about it from an angry customer.