Keep Your WhatsApp Bot Cheap: Count the 1,000 Free Messages and Merge Your Replies

Your WhatsApp bot can answer a customer late at night without waking you up. The cost question is whether that answer lands before or after the free allowance. From 1 October 2026, WhatsApp Business Platform customers pay for non-template replies sent while a customer's 24-hour service window is open once a business phone number has exhausted 1,000 delivered service messages in that calendar month. Keep the bill near zero by counting delivered service messages per business phone number per calendar month, merging multi-bubble replies, and adding a payment method before the allowance runs out.

Count the messages that actually cost you

Count only delivered service messages. Put the count next to the customer's phone number. Run multiple numbers? Keep separate counts. Switch numbers? Start a fresh count for the new number. A small dashboard line is enough: service messages delivered this month, reset on the first of the month.

The support bot may send a greeting, a status update, and a final answer. If each is delivered, each moves the count. Track the delivered service messages the business number has sent in the current calendar month, not customer volume, conversation count, or queued replies.

Template messages have their own rules. The previous exemption for utility templates delivered while a customer's 24-hour service window was open ended on 1 October 2026, so such templates are billed from the first delivered message rather than after a free allowance. Your bot may send utility templates inside that window; treat them as paid from the start.

Meta's service-message pricing has no volume tiers, so a business sending 100 service messages or 100,000 service messages pays the same flat per-message rate once the 1,000-message monthly allowance is exhausted. Growth does not automatically lower the per-message cost. Put the total next to the monthly allowance so you can see when the paid part starts. For a rough estimate, take the delivered service messages above 1,000 and multiply by the applicable per-message rate.

Merge replies before the paid part starts

A five-bubble answer sent after a business phone number has used its 1,000 monthly free service messages is billed as five separate delivered service messages, not as one conversation. Merge the status, the answer, and the next step into a single delivered service message. Done looks like one composed message with line breaks, not a cascade of short sends.

Before you publish a new reply, read it as the customer will see it. Keep line breaks inside the same message when the answer needs one. Wait for the customer's next message when the next step does not block the answer. When the customer has to wait for a link, a confirmation, or a support note, those separate sends can turn one question into several count hits. Do not assume every follow-up is free once the window closes.

Put a payment method in before the free month ends

Add a payment method to the business messaging account before the allowance runs out. You are done when the account can pay before the first paid reply. The live bot can hit a billing gap when the allowance is used, so you do not want the first paid reply to be the moment you discover the account has no way to pay.

Keep the billing email connected to a person who can act on a weekend, not a shared inbox that nobody checks. A bot used for customer support can miss an answer when a charge is missed.

Set a low monthly budget and an alert near the end of the month. The budget does not need to be large; it needs to be there. The side project can survive a small surprise charge, but it can also stop answering customers if billing is missing.

Review the country rates before you scale. Meta's India service-message rate is US$0.0014 per delivered message, and about 30 such service messages equal the cost of one Meta Business Agent reply. From 1 October, Meta's India utility-message charge is Rs 0.115 per delivered message before GST. For South African recipients, the utility and authentication list rate rose by 25%, from US$0.0076 to US$0.0095 per delivered message.

Check the dashboard after the monthly allowance resets, and again near the end of the month, when the allowance is close to running out. A rising count is a signal to tighten the reply template before the next customer message arrives.