WhatsApp Replies Can Stop After 1,000 If Billing Hub Has No Payment Method

The rate change on 1 October 2026 is now a delivery problem, not only a finance problem. Meta bills service messages after the first 1,000 delivered per phone number each month. In the UAE that rate is USD 0.0157, about AED 0.0576 before 5% VAT. The operational clause is sharper: if the WhatsApp Business Account has no payment method in Meta Billing Hub, service messages beyond that free 1,000 are not delivered. The customer sees silence. Your team sees a sent tick that never becomes a delivery.

This is week one of the new card. Clinics, restaurants, and distributors that stayed inside the old free window are the ones hitting it first.

What to check before you blame the bot

1. Open Meta Billing Hub and confirm a valid payment method on the WhatsApp Business Account, not only on an ad account.
2. Count delivered service messages per number for October, not conversations. The free 1,000 is per number, per month, and it does not roll over. A second number has its own 1,000.
3. Ask the BSP for message-level failures after the 1,000th service send. A dashboard that still reports the old conversation metric will hide this.
4. Separate AI token cost from Meta's message cost. Meta's own Business Agent has been billed at USD 2 per million tokens since 1 August 2026. That bill does not replace the service-message fee, and a missing card still blocks delivery.

Who feels it this week in the UAE

A clinic that answers every "is the doctor in" with three short bubbles will cross 1,000 faster than a clinic that sends one booking reply. A restaurant bot that restates the menu as separate messages does the same. Incoming customer messages stay free. Your replies do not, once the allowance is gone.

Rates follow the customer's country. A Dubai number answering a UAE mobile pays the UAE service rate. The same thread to an India mobile pays India's rate. Marketing templates are a different, higher rate and were already billed. Do not mix a promo into the service thread to "use the window."

Fix the delivery, then cut the volume

Add the payment method first. A cheaper bot does not help if Meta will not deliver the reply. Then cut duplicates: one substantive answer, a menu or booking link once, no acknowledgement that adds no fact. The cost-control note for clinics and restaurants is the operating version. The rate card is in the October pricing guide.

Do not move the line back to the WhatsApp Business app to avoid the fee if more than one person must reply or you need a record. You will lose assignment, and you will still miss the lead once the customer messages the old API number.

If the inbox, the CRM, and the allowance need to sit on one number with a turn limit, that is a configuration on the Business API. Meta's card does not negotiate. We set the handoff so the first useful reply still goes out, and the third bubble does not.

Related reading:

• WhatsApp Business API pricing UAE
• Cutting service-message volume
• WhatsApp CRM