{"id":3734,"date":"2026-10-11T09:00:00","date_gmt":"2026-10-11T03:30:00","guid":{"rendered":"https:\/\/chatmaxima.com\/blog\/?p=3734"},"modified":"2026-10-12T15:46:08","modified_gmt":"2026-10-12T10:16:08","slug":"whatsapp-business-updates","status":"publish","type":"post","link":"https:\/\/chatmaxima.com\/blog\/whatsapp-business-updates\/","title":{"rendered":"WhatsApp Business Updates: Every API and App Change in 2026 (Updated Monthly)"},"content":{"rendered":"

Last updated: October 12, 2026.<\/strong><\/p>\n

Meta changes WhatsApp for businesses almost every month, and the changes that cost you money are rarely the ones that make headlines. This page tracks every WhatsApp Business update<\/strong> that affects how businesses message, sell and get billed, newest first.<\/p>\n

Each entry answers five questions: what changed, when, who it affects, what it costs, and what you should do. Every entry names its source, and where Meta’s public documentation lags behind its announcements, we say so. The October 2026 service message billing change is checked against live WhatsApp billing data from numbers connected to ChatMaxima.<\/p>\n

Bookmark it. We update this page at the start of every month and whenever Meta ships a change that needs action.<\/p>\n

The WhatsApp Business updates that need action now<\/h2>\n
\n\n\n\n\n\n\n\n\n\n\n
Change<\/th>\nDate<\/th>\nWho it affects<\/th>\nAction<\/th>\n<\/tr>\n<\/thead>\n
Service and in-window utility messages are now billed<\/td>\nOct 1, 2026<\/td>\nAPI businesses that reply to customers<\/td>\nKeep a payment method on every WABA<\/td>\n<\/tr>\n
New rate card for 9 countries<\/td>\nOct 1, 2026<\/td>\nAPI senders in those markets<\/td>\nRe-check per-message costs<\/td>\n<\/tr>\n
INR billing migration<\/td>\nDec 31, 2026<\/td>\nNon-INR WABAs billed in India<\/td>\nMigrate before the deadline<\/td>\n<\/tr>\n
BSUID in webhooks<\/td>\nRolling out<\/td>\nEvery API integration<\/td>\nStore BSUID alongside phone numbers<\/td>\n<\/tr>\n
Max price required (eligible countries)<\/td>\nQ2 2027<\/td>\nMarketing Messages API senders<\/td>\nTest max price during the open beta<\/td>\n<\/tr>\n
BRL billing migration<\/td>\nJun 30, 2027<\/td>\nNon-BRL WABAs in Brazil<\/td>\nPlan the move to BRL<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\n

October 2026<\/h2>\n

Service messages are now charged per message<\/h3>\n

What changed:<\/strong> From October 1, 2026, Meta charges for service messages, the free-form replies a business sends inside the 24-hour customer service window. They are billed at the same per-message rate as utility and authentication templates in each market.<\/p>\n

The free tier:<\/strong> Meta gives each business phone number 1,000 free service messages per month<\/strong>. Group sends count once per delivered recipient. The allowance does not roll over.<\/p>\n

What we saw in live billing:<\/strong> Billing started at midnight in each WhatsApp Business account’s own time zone. Meta’s pricing analytics now report in-allowance messages as free customer service messages and everything above the allowance as regular service messages.<\/p>\n

Utility templates in the window are charged too:<\/strong> From the same date, utility templates sent in response to customers inside the customer service window are also billed per message. They had been free since July 1, 2025.<\/p>\n

Who it affects:<\/strong> Every WhatsApp Business Platform (API) user that replies to customers, including chatbots and AI agents. Inbound messages remain free, and so does the 72-hour free entry point window that opens from Click to WhatsApp ads and Facebook Page call-to-action buttons.<\/p>\n

The risk:<\/strong> A WhatsApp Business account (WABA) without a valid payment method<\/strong> gets service messages delivered only up to the free 1,000, then not at all. On a busy number, that means a bot that goes silent in the middle of the month.<\/p>\n

What to do:<\/strong> Confirm a payment method on every WABA in Meta Billing Hub (how to add a payment method<\/a>), cut multi-bubble replies into single messages, and watch per-number volume against the 1,000 allowance.<\/p>\n

Source:<\/strong> Meta: upcoming pricing updates for Meta Business Agent, service and utility messages<\/a>, confirmed in live billing data on October 1. Country rates: WhatsApp service message pricing by country<\/a>.<\/p>\n

New rate card for nine countries<\/h3>\n

What changed:<\/strong> On October 1, 2026, Bangladesh, Iraq, Nepal and Sri Lanka moved to lower utility and authentication rates, while Kazakhstan, Kuwait, Morocco, Oman and Ukraine moved to higher ones.<\/p>\n

Who it affects:<\/strong> API businesses sending templates to numbers in those countries.<\/p>\n

What to do:<\/strong> Re-run your cost estimates for those markets. Because service messages are priced at the utility rate, the change also moves your service message cost there.<\/p>\n

Source:<\/strong> Meta pricing documentation<\/a>.<\/p>\n

Max price for marketing messages enters open beta<\/h3>\n

What changed:<\/strong> On October 1, 2026, max price for marketing messages moved into open beta, so any partner can now enable it for all of its clients. With max price, you set the most you will pay per delivered marketing message on the Marketing Messages API, and Meta charges that amount or less.<\/p>\n

What is coming:<\/strong> At general availability in Q2 2027<\/strong>, Meta plans to make max price required in eligible countries. Fixed, published marketing rates will then apply only on the Cloud API.<\/p>\n

What to do:<\/strong> Run Meta’s recommended four-arm test (no max price, at the rate card, 1.5 times the rate card and 0.9 times the rate card) on one campaign during the beta.<\/p>\n

Source:<\/strong> Meta max price documentation<\/a>. Guide: WhatsApp max price for marketing messages<\/a>.<\/p>\n

September 2026<\/h2>\n

WhatsApp Business app terms updated<\/h3>\n

What changed:<\/strong> WhatsApp updated the Terms of Service for the WhatsApp Business app, effective September 23, 2026<\/strong>. Continuing to use the app after that date counts as accepting them.<\/p>\n

Who it affects:<\/strong> Businesses on the free WhatsApp Business app, including numbers running in coexistence mode with the API.<\/p>\n

What to do:<\/strong> Have someone responsible for compliance read the new terms, especially if you use the app for customer data or payments.<\/p>\n

Source:<\/strong> WhatsApp Help Center, “We’re updating the Terms of Service for the WhatsApp Business App, effective September 23, 2026.”<\/p>\n

Meta Muse brings a consumer AI agent into WhatsApp<\/h3>\n

What changed:<\/strong> Meta launched Muse, a consumer AI agent that acts on a user’s behalf, in the US on September 8, 2026. It can research, book and contact businesses for the user.<\/p>\n

Who it affects:<\/strong> Businesses with US customers. Meta has not said Muse will open chats with business accounts on WhatsApp, but agents that compare and contact businesses change how customers find you.<\/p>\n

What to do:<\/strong> Keep prices, hours and policies consistent across your website, catalog and chatbot, and make sure bookings and orders can be completed inside a chat.<\/p>\n

Source:<\/strong> TechCrunch and CNBC reporting, September 2026. Analysis: what Meta Muse changes for businesses<\/a>.<\/p>\n

Usernames reach more countries<\/h3>\n

What changed:<\/strong> After the first test waves in July, WhatsApp usernames continued rolling out to more countries from September. WhatsApp notifies people in the app when usernames reach their country.<\/p>\n

What to do:<\/strong> See the June entry below. If you have not reserved your business username, do it now.<\/p>\n

July 2026<\/h2>\n

WhatsApp Web gets calling<\/h3>\n

What changed:<\/strong> On July 28, 2026, WhatsApp added audio and video calling to WhatsApp Web, including call transfer between devices and a waiting room for call links.<\/p>\n

Who it affects:<\/strong> Teams using the WhatsApp Business app on a computer. This does not change the Business Platform Calling API, which stays billed separately.<\/p>\n

What to do:<\/strong> Move agents’ customer calls off personal phones and require approval to join call links.<\/p>\n

Source:<\/strong> WhatsApp blog<\/a>.<\/p>\n

Brazilian real billing and a quarterly rate update<\/h3>\n

What changed:<\/strong> From July 1, 2026, eligible businesses can create new WABAs billed in Brazilian reais (BRL). Existing non-BRL WABAs in Brazil must migrate by June 30, 2027<\/strong>. Rate cards also updated on July 1, as they can on the first day of any quarter.<\/p>\n

Who it affects:<\/strong> Businesses billed for WhatsApp in Brazil, and anyone budgeting per-message costs.<\/p>\n

Source:<\/strong> Meta pricing documentation<\/a>.<\/p>\n

Usernames go live in the first countries, and India pauses<\/h3>\n

What changed:<\/strong> Usernames went live in a first wave of countries on July 7 (Algeria, Azerbaijan, Ghana, Libya and Nepal), with a second wave from July 20. On July 1, India’s Ministry of Electronics and IT issued a notice asking Meta not to roll out usernames in India until consultations finish.<\/p>\n

Who it affects:<\/strong> Users and businesses in the rollout countries. The India pause covers the username feature only; the business-scoped user ID change for API integrations is global.<\/p>\n

Source:<\/strong> Rollout trackers and Indian press reports. Details: WhatsApp username feature halted in India<\/a>.<\/p>\n

June 2026<\/h2>\n

Username reservations open, and BSUIDs reach every API integration<\/h3>\n

What changed:<\/strong> On June 29, 2026, WhatsApp opened username reservations. Once a user turns on a username, a business they message for the first time does not see their phone number. There is no username directory, and users can add an optional username key that others must know before messaging them.<\/p>\n

To support this, Meta introduced the business-scoped user ID (BSUID)<\/strong>. It began appearing in April 2026 and is assigned to the user_id field in every messages webhook, whether or not the user has a username. A BSUID is tied to one business portfolio and one user, so it cannot be reused across portfolios.<\/p>\n

Who it affects:<\/strong> Every API integration, CRM sync and chatbot that uses the phone number as the customer’s unique key.<\/p>\n

What to do:<\/strong><\/p>\n