What Changes for WhatsApp Service Messages on 1 October 2026?
From 1 October 2026, Meta charges on a per-message basis for service messages on the WhatsApp Business Platform. Service message rates are the same as utility and authentication rates for each market. Every business phone number gets one shared free tier of 1,000 delivered service messages per month, and Meta charges for service messages after that free tier is used.
A service message is a message you send inside an open 24-hour customer service window, which opens and resets each time a user messages you. Nothing about when you can send one has changed. What has changed is that it now costs money once you pass 1,000 deliveries in a calendar month on that phone number.
| What | Until 30 September 2026 | From 1 October 2026 |
|---|---|---|
| Service messages | Not charged | Charged per message at utility and authentication rates for the market, after a free tier |
| Free allowance | Not applicable | 1,000 delivered service messages per month, per business phone number |
| Utility templates replying to users | Not charged since 1 July 2025 | Charged when sent in an open 24-hour customer service window |
| Reaction messages | Not charged | Still not charged, and they do not consume the free tier |
| Non-template messages | Not charged since 1 November 2024 | No change stated for non-template messages |
Two changes land on the same date, and most coverage only mentions the first. Meta is charging for service messages, and separately it is charging for utility messages sent in response to users inside the customer service window, which had not been charged since 1 July 2025. If your support or post-purchase flows lean on utility templates inside an open window, that is a second new line on the same invoice.
How Does the 1,000 Free Service Message Tier Actually Work in 2026?
Each business phone number has one shared free tier of 1,000 delivered service messages per month. Both one-to-one and group service deliveries draw from that same pool. A one-to-one delivery consumes one unit, and a group send consumes one unit per delivered recipient. Unused allowance does not roll over, and the tier resets monthly for each business phone number.
Meta's own illustration is 1,000 for October with no roll-over, then 1,000 for November with no roll-over. The unit that matters is the business phone number, not the account or the portfolio, which is worth noting if you run several numbers for different brands or regions.
- Shared pool: one-to-one and group service deliveries both draw from the same 1,000.
- Group sends multiply: a group send consumes one unit per delivered recipient, so a single broadcast to 40 people in a group uses 40 units.
- No roll-over: unused units expire at the end of the month.
- Per phone number: five numbers means five separate 1,000-message tiers.
- Payment method required: if you have no payment method on the account, Meta will deliver service messages inside the free tier but will not deliver them after the tier is used.
Meta states that without a payment method on the WhatsApp Business account, service messages inside the free tier are delivered and service messages after the free tier are not. That is not a billing warning, it is a delivery outage on your support channel on the 1,001st message of the month. Check that a payment method is attached in Billing Hub, even if you expect to stay under the tier.
How Do You Tell From the Webhook Whether a Service Message Was Charged?
The pricing type in the pricing object of the status webhook changed on 1 October 2026 for messages whose pricing category is service or group_service. Inside the free tier the type stays as before and the message is not billable. After the free tier is used, the type becomes regular and the message is billable. That flip is how your own systems can count what the tier absorbed and what it did not.
| Which messages | Through 30 Sep 2026 | From 1 Oct 2026 | Charged from 1 Oct |
|---|---|---|---|
| 1:1 service messages inside the free tier | free_customer_service | free_customer_service | No |
| Group service messages inside the free tier | free_group_customer_service | free_group_customer_service | No |
| 1:1 service messages after the free tier | free_customer_service | regular | Yes |
| Group service messages after the free tier | free_group_customer_service | regular | Yes |
A one-to-one service message inside the tier arrives with "billable": false, "pricing_model": "PMP", "type": "free_customer_service" and "category": "service". The same message after the tier is used arrives with "billable": true and "type": "regular". If you log the pricing object today, you already have the instrumentation you need. If you do not, adding it before October is the cheapest possible preparation.
Who Still Gets Free Service Messages After 1 October 2026?
Starting 1 October 2026 and through 31 December 2027, service messages remain free beyond the monthly free tier only for eligible government and non-profit organisations. Meta lists the eligible cohorts as government departments and agencies, inter-governmental organisations, and community non-profit organisations. For organisations Meta has already identified as eligible, the policy applies as of 12am by WhatsApp Business account timezone on 1 October 2026.
Note the shape of that exemption. It is time-limited, it runs to the end of 2027, and it is granted by cohort rather than claimed by a business. Commercial brands are not in scope. Meta also states that service messages are charged differently for AI Providers, which is a separate category again.
The one carve-out that applies to everybody is narrow and specific: a reaction message is the only service message type that continues not to be charged for all businesses as of 1 October 2026, and reactions do not count toward the 1,000 free monthly service messages per business phone number.
What Else Changes on the Same Date in 2026?
1 October 2026 is a quarterly pricing date, so the service message change arrives bundled with rate card movements. Meta can update rates up to four times a year, on 1 January, 1 April, 1 July and 1 October, with a minimum of one month of notice for a rate card update.
| Change | Markets affected |
|---|---|
| Marketing rate increases | Kuwait, Mexico, Morocco, Saudi Arabia, UAE, Rest of Middle East, Rest of Asia Pacific |
| Utility and authentication increases | Kazakhstan, Kuwait, Morocco, Oman, Pakistan, Peru, South Africa, Ukraine |
| Utility and authentication decreases | Bangladesh, Iraq, Nepal, Sri Lanka |
| New authentication-international rates | Bangladesh, Iraq, Kazakhstan, Kuwait, Morocco, Nepal, Oman, Sri Lanka, Ukraine |
| Newly standalone on rate cards | Nine markets leave their "Rest Of" pricing region, taking that region's rate with them |
India is not on the list of markets with a marketing, utility or authentication rate change on 1 October 2026. Indian businesses are still affected, because service messages become chargeable everywhere and because service rates track the market's utility and authentication rates. The section on the calling rate cards covers the nine newly standalone markets in detail, including the fact that their per-minute rates do not change.
How Should You Estimate the Cost?
Count deliveries, not conversations. The billable unit is a delivered message inside the customer service window, so the number you need is how many service messages each phone number delivers in a typical month, and how that splits between one-to-one and group sends. Meta does not publish a universal per-message figure, because service rates match the utility and authentication rates for each market, so pull the rate card for your own currency and market.
The table below applies arithmetic to the free tier only. It shows how many deliveries fall outside the tier at different monthly volumes, which is the quantity you then multiply by your own market rate.
| Illustrative monthly service deliveries on one number | Covered by the free tier | Chargeable deliveries |
|---|---|---|
| 800 | 800 | 0 |
| 1,000 | 1,000 | 0 |
| 5,000 | 1,000 | 4,000 |
| 25,000 | 1,000 | 24,000 |
| 100,000 | 1,000 | 99,000 |
The volumes above are invented placeholders chosen to show the shape of the free tier, not observed traffic from any account. They are arithmetic against Meta's published 1,000-message tier and nothing else. To turn the right-hand column into money, multiply it by the utility and authentication rate for your market and currency from Meta's published rate cards, since service rates match those rates by market.
What Should You Check Now the Change Is Live?
Most of the work is measurement and hygiene rather than engineering, and all of it is quicker than the first invoice conversation.
- Attach a payment method in Billing Hub for every WhatsApp Business account, so service messages do not stop being delivered once the tier is used.
- Log the
pricingobject from status webhooks if you do not already, so you can separate free-tier deliveries fromregularones from day one. - Count service deliveries per phone number for a normal month, splitting one-to-one from group sends, since group sends consume one unit per recipient.
- Pull your own rate card for your currency and market, and use the utility and authentication rate as the service rate.
- Review utility templates used inside the customer service window, because those become chargeable on the same date.
- Check whether your organisation is in an eligible government or non-profit cohort, and if so, understand that the exemption runs only to 31 December 2027.
- Re-check template categories, because category decides the rate and an approved template can still be recategorised. See the section on automatic category updates.
How Should Marketing and Support Teams Respond in 2026?
Treat the 24-hour customer service window as a budget rather than a free channel. For most brands the practical consequence is not that WhatsApp support becomes expensive, it is that padding becomes expensive. Three separate acknowledgement messages where one would do used to cost nothing. From October each of them is a delivery against the tier.
- Consolidate acknowledgements: one clear reply beats a greeting, a holding message and a confirmation.
- Watch automated flows: bots and auto-replies inside the window are the most likely source of unplanned volume.
- Think carefully about group service sends: each delivered recipient consumes a unit.
- Keep reactions in mind: a reaction is free and does not touch the tier, which makes it a legitimate lightweight acknowledgement.
- Do not move support off WhatsApp reflexively: the free tier covers a genuine support load for a smaller brand, and the channel's response rates are why you are there.
Our WhatsApp commerce playbook for D2C in India covers the revenue side of the channel, and the WhatsApp Business API guide covers the mechanics of getting set up.
Can an Approved WhatsApp Template Still Be Recategorised?
Yes. On 15 September 2026 Meta clarified that a template whose category was confirmed by a review remains subject to automatic category updates. If the messages the template sends do not meet the template category guidelines, action can still be taken on the template. Approval is a starting point, not a guarantee that the category, and therefore the price, stays fixed.
This is the single most common billing surprise on the WhatsApp Business Platform. A team builds a flow around a template approved as utility, budgets it at the utility rate, and later finds it billed as marketing. Meta's pricing documentation is explicit about whose problem that is: businesses are responsible for reviewing the category assigned to their approved templates, and whenever a template is used, the business accepts the charges for the category applied to it at the time of use.
"Whenever a template is used, a business accepts the charges associated with the category applied to the template at time of use." The category that matters is the one in force when you send, not the one you were approved with. If it changed between the two, you pay the new rate.
Why Does a Category Change Matter So Much?
Because the category decides the rate. WhatsApp templates are categorised as marketing, utility or authentication, and each carries its own per-message price that varies by market. Marketing templates are always charged. Utility templates have different treatment depending on whether they are sent inside or outside the 24-hour customer service window. A move between categories can change both whether a message is charged and what it costs.
Meta's own worked example shows how the categories behave across a single customer journey. It is reproduced below as published, with one important caveat about the 1 October 2026 change that follows it.
| Hour | Action | Rate | Meta's reason |
|---|---|---|---|
| 0 | Marketing template promoting a new product | Marketing | All marketing template messages are charged |
| 2 | User messages the business, opening the 24-hour window | None | Messages from users are not charged |
| 3 | Text message with product details | None | Non-template message inside the open window |
| 4 | Utility template confirming the purchase order | None | Utility template inside the open window |
| 26 | Window closes after 24 hours with no new user message | None | No new message from the user |
| 30 | Utility template with an order status update | Utility | Utility template outside the open window |
From 1 October 2026 the hour-4 row changes. Meta begins charging for utility messages sent in response to users inside the 24-hour customer service window, which had not been charged since 1 July 2025. Service messages also become chargeable beyond a free tier on the same date. Our service message pricing guide covers both changes in full. The point here is simpler: from October, more of a template's life is billable, so its category matters on more of your sends.
How Does WhatsApp Tell You a Category Is Changing?
Through the template_category_update webhook. It fires in two situations: when a template's existing category is going to be changed by an automated process, and when a template's existing category has been changed, manually or by an automated process. The first is your warning. The second is your confirmation.
| Field | Impending notification | Completed notification |
|---|---|---|
message_template_id | Yes | Yes |
message_template_name | Yes | Yes |
message_template_language | Yes | Yes |
new_category | Yes: the template's current category | Yes: the category it now has |
correct_category | Yes: the category it will receive | No |
category_update_timestamp | Yes: when the change takes effect | No |
previous_category | No | Yes: the category it had before |
In the impending notification, new_category holds the template's current category and correct_category holds the one it is about to receive. Read the names at face value and you will log the change backwards. Map correct_category to "what it is becoming" and category_update_timestamp to "when", and treat new_category as "what it is now" until the completed notification arrives.
The impending notification is the useful one. Meta's reference describes roughly a day of notice before an automated recategorisation, with category_update_timestamp giving the exact moment the change takes effect. That window is your chance to pause a high-volume send, edit the template, or move the content to a correctly categorised template before the new rate applies.
Why Do Templates Get Recategorised After Approval?
Because review checks a template at one moment, and Meta's automated process keeps checking what the template actually sends. Meta's clarification ties action to whether the messages a template sends meet the category guidelines. A template approved as utility that, in practice, carries promotional content is the textbook case. The approval reflected what it looked like at review. The recategorisation reflects how it is being used.
- Promotion inside a transactional template: an order confirmation that also pushes a discount code is using a utility template for marketing.
- Variables that change the meaning: a template whose variable fields carry promotional content at send time can drift from its approved purpose.
- One template doing several jobs: a general-purpose template reused across campaigns is harder to keep inside one category's guidelines.
The practical rule follows directly. Keep each template to one job, and keep promotional content in marketing templates, so that what a template sends always matches what it was approved as.
How Should You Handle a Category Change When It Arrives?
Meta added template message routing guidance on 24 September 2026, covering how to maintain an up-to-date template-category mapping, how to select the correct send endpoint, and how to recover from category changes. The operational version is a short loop that should run automatically rather than in a spreadsheet.
- Subscribe to
template_category_updateand store every notification. - Keep your own template-to-category map and update it from the webhook, never from memory.
- Alert a human on every impending notification for any template with meaningful volume.
- Decide before
category_update_timestamp: accept the new rate, edit the template, or switch to a template already in the right category. - Re-cost affected flows at the new category's rate for each market you send to.
- Route sends using the current category, since Meta's routing guidance ties the send endpoint to the category.
- Confirm with the completed notification, using
previous_categoryandnew_category.
A note on moving content to a new template
Creating a fresh template is not free of cost either. Under the new business account model, templates migrated to a new Messaging account reset to baseline quality rating and messaging tier and need roughly two to four weeks to ramp up. A new template starts without history. If a high-volume utility flow is recategorised, the fastest fix is often to remove the promotional content from the existing template rather than to replace it.
How Should Marketing Teams Prevent Category Surprises?
Treat category as a budget input owned by marketing, not a technical detail owned by whoever submitted the template. The team writing the copy is the team most likely to push a utility template over the line.
| Practice | Why it works in 2026 |
|---|---|
| One template, one job | Keeps sent content aligned with the approved category. |
| No offers in order or delivery updates | The commonest route from utility to marketing. |
| Copy review against category before launch | Catches drift before Meta's automated process does. |
| Budget at the rate in force at send time | Matches how Meta actually charges. |
| Webhook alerts to the campaign owner | The person who can change the copy hears about it in time. |
| Quarterly category audit | Rates and rules change on Meta's quarterly pricing dates. |
If you are bidding on marketing messages, category also decides which pricing applies, which is covered in our guide to max price. For channel strategy more broadly, see our WhatsApp marketing agency guide.
What Are the Common Mistakes?
- Treating approval as permanent. Meta confirmed on 15 September 2026 that approved templates remain subject to automatic category updates.
- Budgeting at the approved category's rate. You are charged for the category in force at time of use.
- Reading
new_categoryas the incoming category. In the impending notification it is the current one;correct_categoryis the incoming one. - Ignoring the impending notification. It is the only window to act before the new rate applies.
- Adding offers to utility templates. The most common cause of recategorisation.
- Replacing a template reflexively. A new template starts without quality history.
- Forgetting the October change. Utility templates inside the customer service window become chargeable from 1 October 2026.
What Changes on WhatsApp Calling Rate Cards on 1 October 2026?
On 1 October 2026, nine markets move out of their respective "Rest of" pricing regions and become standalone on WhatsApp Business Calling API rate cards: Bangladesh, Iraq, Kazakhstan, Kuwait, Morocco, Nepal, Oman, Sri Lanka and Ukraine. Meta published the rate cards effective that date across 16 currencies on 11 September 2026.
The sentence most coverage leaves out is the important one. Calling rates do not change on 1 October 2026. Each of the nine markets keeps the rate of the region it is leaving, and Meta states that no market's per-minute rate or volume tier thresholds increase or decrease. This is a structural change to how the rate card is laid out, not a price rise.
| What | Until 30 September 2026 | From 1 October 2026 |
|---|---|---|
| Rate card listing | Inside a "Rest of" pricing region | Standalone market on the calling rate card |
| Per-minute rate | The "Rest of" region rate | Unchanged: the same rate as the region it is leaving |
| Volume tier thresholds | The region's thresholds | Unchanged: no increase or decrease |
| Currencies on the rate cards | Published across the current currency set | Rate cards effective 1 October 2026 across 16 currencies |
Which Nine Markets Become Standalone?
The nine markets that moved out of their "Rest of" regions on 1 October 2026 are listed below. Meta says the change aligns calling rate cards with the same nine markets becoming standalone for messaging, which it announced on 27 May 2026.
| Market | Calling rate on 1 October 2026 |
|---|---|
| Bangladesh | Keeps the rate of the region it is leaving |
| Iraq | Keeps the rate of the region it is leaving |
| Kazakhstan | Keeps the rate of the region it is leaving |
| Kuwait | Keeps the rate of the region it is leaving |
| Morocco | Keeps the rate of the region it is leaving |
| Nepal | Keeps the rate of the region it is leaving |
| Oman | Keeps the rate of the region it is leaving |
| Sri Lanka | Keeps the rate of the region it is leaving |
| Ukraine | Keeps the rate of the region it is leaving |
India is not on the list. Indian businesses calling Indian numbers see no change from this restructuring. Indian businesses that call customers in neighbouring markets, particularly Bangladesh, Nepal and Sri Lanka, should note that those markets become standalone, which matters for how future rate changes can be applied to them individually.
Why Does a Change That Does Not Change Prices Matter?
Because a standalone market can be repriced on its own. While a market sits inside a "Rest of" region, it moves only when the whole region moves. Once it is standalone, Meta can update that single market's rate at any of its regular pricing dates without touching the others. October 2026 changes nothing about today's bill and a great deal about how predictable the bill for those nine markets is from here on.
The messaging side of the same nine markets shows what that can look like. On the messaging rate cards for 1 October 2026, Meta lists utility and authentication rate increases for Kazakhstan, Kuwait, Morocco, Oman and Ukraine, decreases for Bangladesh, Iraq, Nepal and Sri Lanka, and new authentication-international rates in all nine. For calling, Meta has deliberately held the rates flat. For messaging, the same standalone status came with movement in both directions on day one.
If you call customers in any of these nine markets, stop budgeting them as part of a blended regional rate. Track them as individual lines from 1 October 2026, because the next time Meta updates calling rates it can move each of them independently.
How Is WhatsApp Calling Priced?
All user-initiated calls are free. Businesses are charged for the calls they place, and Meta prices those on three factors. A valid payment method is required to place calls at all.
- Duration, calculated in six-second pulses.
- The country code of the phone number being called.
- Volume tier, based on minutes called within the calendar month, using the same tiering accrual as messaging.
The six-second pulse rule
Meta counts fractional pulses as one full pulse. Its own example is a 56-second call, which is 9.33 pulses, billed as 10 pulses. Every call is therefore rounded up to the next six seconds.
| Illustrative call length | Exact pulses | Billed pulses | Billed duration |
|---|---|---|---|
| 6 seconds | 1.00 | 1 | 6 seconds |
| 7 seconds | 1.17 | 2 | 12 seconds |
| 56 seconds | 9.33 | 10 | 60 seconds |
| 2 minutes 1 second | 20.17 | 21 | 2 minutes 6 seconds |
Only the 56-second row is Meta's own example. The other rows apply the same published rule to invented call lengths to show how rounding works. Multiply billed duration by the per-minute rate for the destination market on your own currency's rate card to estimate cost.
Calls that cross a volume tier
Volume tiers reward monthly calling volume with lower rates. When a single call crosses from one pricing tier into the next, Meta prices the entire call at the lower rate, meaning the rate of the higher volume tier. A long call that tips you into a cheaper tier is therefore billed wholly at the cheaper rate, rather than split between the two.
What Does This Mean for Indian Businesses Using WhatsApp Calling?
For calls to Indian numbers, nothing changes on 1 October 2026. The practical work for an Indian team is not about this restructuring at all. It is about the pricing mechanics that apply every day, and about the accounts they sit on.
- User-initiated calls are free, which makes a call button on a WhatsApp message or profile a low-cost support channel.
- Business-initiated calls are rounded to six seconds, so short confirmation calls carry proportionally more rounding.
- Volume tiers accrue on calendar-month minutes, so concentrating calling on one account can lower the blended rate.
- A payment method is mandatory to place calls.
- Billing currency matters: eligible Indian customers must move all Messaging accounts to INR by 31 December 2026, as covered in our messaging_account_id and INR migration guide.
What Else Changed for WhatsApp Calling?
Alongside the rate card notice, Meta made several calling-related documentation changes in the same weeks. They are not pricing changes, but each affects how a calling integration should be built.
| Date | Change | Why it matters |
|---|---|---|
| 16 September 2026 | Calling integration patterns and the Calling FAQ recommend the new WhatsApp account model for messaging and calling on one phone number, replacing legacy multi-partner approaches. | Calling and messaging can share a number under the new model. |
| 22 September 2026 | SIP security guidance clarified: Meta supports mutual TLS when it acts as the TLS client, not when it acts as the TLS server. | Relevant to anyone integrating calling over SIP. |
| 31 August 2026 | Known issue noted: when a user changes networks during a call, the recording and transcript can be cut short. A fix is rolling out. | Do not treat a truncated transcript as a complete record. |
The account model recommendation connects to our guide to the new business account model. If calling and messaging are handled by different partners on one number, also read the partner assignment readiness checklist, since call routing and webhook delivery are separate from messaging thread ownership.
What Should You Do About the New Rate Cards?
- List the destination markets your business calls, and check whether any are among the nine.
- Download the 1 October 2026 rate card in your billing currency from Meta's calling pricing page.
- Confirm the rate is unchanged for any of the nine you call, as Meta states it should be.
- Re-budget those markets as individual lines rather than as part of a regional blend.
- Confirm a payment method is attached, since one is required to place calls.
- Check call-length patterns, since six-second rounding weighs most on very short calls.
- Review transcripts and recordings with the network-change known issue in mind.
What Are the Common Mistakes?
- Reporting this as a price rise. Meta states calling rates do not change on 1 October 2026.
- Assuming India is affected. India is not one of the nine markets.
- Budgeting the nine as a blended region. They are standalone from 1 October 2026 and can be repriced individually.
- Billing call length to the second. Calls are charged in six-second pulses, rounded up.
- Splitting a tier-crossing call between two rates. The entire call is priced at the higher volume tier's lower rate.
- Charging customers for calling you. All user-initiated calls are free.
- Treating every transcript as complete. A network change mid-call can cut recordings and transcripts short.
What Are the Common Mistakes in 2026?
- Assuming the free tier is per account. It is 1,000 delivered service messages per business phone number, per month.
- Forgetting that group sends multiply. One group send consumes one unit per delivered recipient.
- Expecting unused allowance to roll over. It does not.
- Running without a payment method. Service messages stop being delivered after the free tier if no payment method is attached.
- Missing the utility change. Utility messages sent in response to users inside the customer service window also become chargeable on 1 October 2026.
- Assuming a commercial brand can claim the exemption. It applies to eligible government and non-profit cohorts only, and runs to 31 December 2027.
- Reading
free_customer_serviceas proof nothing is billable. After the tier, the same traffic arrives asregular.
Key Takeaways for 2026
This is a dated cost change on a channel most Indian and global D2C brands now treat as core, and the preparation is measurement rather than engineering.
- From 1 October 2026 service messages are charged per message, at the same rates as utility and authentication for each market.
- Each business phone number gets 1,000 delivered service messages free per month, shared between one-to-one and group sends, with no roll-over.
- A group send consumes one unit per delivered recipient.
- Without a payment method, Meta delivers inside the free tier and does not deliver after it.
- Utility messages sent in response to users inside the customer service window also become chargeable on the same date.
- Reaction messages stay free for everyone and do not count against the tier.
- Eligible government and non-profit organisations keep free service messages beyond the tier from 1 October 2026 through 31 December 2027.
- The webhook
pricing.typeflips fromfree_customer_servicetoregularonce the tier is used, which is your own measurement hook.
Distk helps growth teams across India and internationally instrument WhatsApp spend per phone number, trim the padding out of service flows before it becomes billable, and keep template categories honest so the rate you planned for is the rate you pay. If the October changes land on a channel you depend on, that measurement is where we start.
Sources
- Pricing on the WhatsApp Business Platform, Meta for Developers, updated 28 September 2026.
- WhatsApp changelog, Meta for Developers, entries dated 29 September 2026 and earlier.
- template_category_update webhook reference, Meta for Developers.
- Calling API Pricing, Meta for Developers, updated 11 September 2026.
Every rate, date, field name and policy statement above is quoted or summarised from those two official Meta pages. Rates are market-specific and Meta can update them quarterly, so confirm your own market and currency on the published rate cards before budgeting.