Hotel WhatsApp Costs Change on October 1, 2026: A Budget and Setup Checklist
What will it cost your hotel to message guests on WhatsApp after 1 October 2026-and how should you design guest communication so unnecessary messages do not increase the bill? The direct answer is that Meta will charge per delivered service message on the WhatsApp Business Platform from 1 October 2026. Each business phone number will [ ]
By Gaurav Sharma · · hotels
What will it cost your hotel to message guests on WhatsApp after 1 October 2026-and how should you design guest communication so unnecessary messages do not increase the bill?
The direct answer is that Meta will charge per delivered service message on the WhatsApp Business Platform from 1 October 2026. Each business phone number will have a shared monthly free tier of 1,000 delivered service messages. After that tier is used, service messages become billable according to the applicable market rate card. Your budget will therefore depend on delivered message volume and category, not simply on whether a guest replied within the 24-hour window. Meta’s pricing documentation is the source to use for current market rates.
What actually changes on 1 October 2026
The important distinction is between a service message, a utility template, and a marketing template. They may all be sent through WhatsApp, but they are not treated the same way.
| Message type | Through 30 September 2026 | From 1 October 2026 | What it means for a hotel |
|---|---|---|---|
| Service message: non-template reply inside the 24-hour window | Not charged | Charged per delivered message after the free tier | Count guest-support replies, not only outbound campaigns |
| Utility template in response to a user inside the window | Not charged | Charged per delivered message | A booking or service update can still be billable inside the window |
| Utility template sent outside the window | Charged by the utility rate card | Charged by the utility rate card | Budget for messages that must use templates after the window closes |
| Marketing template | Charged by the marketing rate card | Charged by the marketing rate card | Keep promotions separate from genuine service communication |
Meta’s published October update says service rates will match utility and authentication rates by market. It also introduces the 1,000-message service free tier and makes utility messages sent in response to users inside an open 24-hour customer service window chargeable. These changes are effective 1 October 2026, not before. Read the full Meta pricing update.
The free tier, read carefully
The free tier is not 1,000 messages for your entire hotel group or business portfolio. It is:
- 1,000 delivered service messages
- Per business phone number
- Per month
- Shared across one-to-one and group service deliveries
- No rollover of unused messages
- Reset monthly for each business phone number
A one-to-one service delivery consumes one unit. A group service delivery consumes one unit for each delivered recipient. This means your hotel must count delivered recipients, not simply the number of send actions initiated by a staff member or system.
The free tier also does not apply to every WhatsApp message. It concerns service messages. Marketing and utility templates continue to follow their respective category rules and rate cards.
There is also an operational risk if the account has no payment method. Meta says it will deliver service messages within the free tier but will not deliver them after the free tier has been used if no payment method is available. Finance or the account owner should therefore confirm billing readiness before October.
Why category, not channel, now drives the bill
A hotel may think, “We use WhatsApp for guest service, so our WhatsApp cost is one line item.” That is too broad.
The practical question is: What is each message trying to do?
- Service: Respond to a guest who has initiated a conversation, such as asking about early check-in or requesting an in-stay service.
- Utility: Communicate a functional update, such as a booking or service-related notification.
- Marketing: Promote an offer, package, upgrade, or other commercial message.
From 1 October, a guest-initiated service conversation is no longer automatically free simply because the 24-hour customer service window is open. The hotel must decide which messages are necessary, which can be combined, and which should not be sent.
This is not an instruction to avoid replying to guests. It is an instruction to remove low-value repetition. One clear response may be more useful than several partial messages. A message that a guest would reasonably read as promotional should not be presented as ordinary service communication simply because the conversation is already open.
Hotels planning multiple guest journeys can use a structured trigger, audience, timing, action, exception, and outcome model. The automated guest communication campaign framework is a useful reference for reviewing those journeys.
The two deadlines an India-first hotel should not miss
1. Migrate eligible accounts to INR by 31 December 2026
Billing localisation for eligible India customers launched on 1 January 2026. Eligible customers must migrate all WhatsApp Business Accounts in their portfolio to INR by 31 December 2026.
From 1 January 2027, Meta says it will no longer deliver messages from non-INR WhatsApp Business Accounts belonging to eligible customers. This is an account and billing-readiness issue, not merely an accounting preference.
The finance owner or business administrator should confirm:
- Whether the hotel is an eligible India customer
- Which WhatsApp Business Accounts are in the portfolio
- Which accounts are already billed in INR
- Whether any account still requires migration
2. Review the rate card every quarter
Meta’s pricing calendar allows pricing updates on the first day of a quarter: 1 January, 1 April, 1 July, and 1 October.
The minimum notice depends on the type of change:
- One month for a rate-card update
- Three months for a pricing-model add-on
- Six months for a pricing-model change
Revenue, finance, or ownership should therefore review WhatsApp assumptions at least once every quarter rather than setting an annual budget and leaving it untouched.
Check your messaging limit before you scale
Billing and messaging capacity are different questions.
Messaging limits are the maximum number of unique WhatsApp user phone numbers a business can deliver messages to outside a customer service window during a moving 24-hour period. The limit is set at the business portfolio level and shared by every business phone number in that portfolio.
A newly created business portfolio starts at a limit of 250. The limit can rise to 2,000 through a scaling path, including business verification, partner-led verification, or delivering 2,000 messages to unique users within a moving 30-day period using high-quality templates. It can then scale automatically to 10,000, 100,000, and unlimited when Meta’s criteria are met.
Automatic scaling depends on maintaining high-quality messages across the portfolio and using at least half of the current limit during the previous seven days.
One number can consume the portfolio’s available messaging capability. A reservations number, events number, and front-desk number should therefore not be treated as independent capacity pools merely because they are separate phone numbers. Check the current limit in WhatsApp Manager before scaling an outbound campaign.
A six-step setup and budget checklist
1. Count delivered messages by category
Owner: Revenue or reservations manager
Prerequisites: WhatsApp delivery records, campaign logs, conversation exports, and the number of business phone numbers
Count a normal month of delivered service, utility, and marketing messages separately. Include staff replies, automated replies, group deliveries, and messages sent by connected systems where they are part of the same account.
2. Review category fit
Owner: Front office manager with reservations and marketing
Prerequisites: Template list, message copy, campaign purpose, and guest journey map
Classify each message by its actual purpose. Review anything that a guest would read as promotional and keep it out of a service workflow. Also identify repeated replies that could be consolidated without removing information the guest needs.
The hotel campaign guide for WhatsApp and voice can help teams examine common booking, pre-arrival, in-stay, and win-back journeys.
3. Confirm payment method and messaging limit
Owner: Finance or business administrator
Prerequisites: Meta Business Suite access, Billing Hub access, and portfolio ownership details
Confirm that a valid payment method is attached. Check the portfolio-level messaging limit and document which phone numbers share it.
4. Confirm billing currency
Owner: Finance or owner
Prerequisites: Portfolio list, WABA billing details, eligibility status, and migration access
For India-based eligible customers, confirm that every WhatsApp Business Account is migrated to INR before the 31 December 2026 deadline.
5. Reduce unnecessary touchpoints
Owner: Front office manager; GM approves removals that affect guest service
Prerequisites: Message-level volume data, guest complaint history, and operational journey owners
Combine messages where the guest can understand the same information in one delivery. Remove reminders that do not change a guest decision or help staff complete an operational task. Do not remove a message simply to reduce volume if it protects arrival coordination, payment clarity, or service recovery.
6. Review cost and outcome together
Owner: GM with finance, revenue, and operations
Prerequisites: Meta delivery and billing data, booking data, ancillary revenue data, and service metrics
Review delivered message volume, category mix, billable messages, bookings assisted, enquiries converted, service requests completed, and unresolved handoffs. Keep message cost separate from the value of a booking or ancillary service it may protect.
A useful review asks both: “How many messages did we send?” and “What operational or commercial outcome did those messages support?”
Worked example: illustrative assumptions
Consider this illustrative example, not measured hotel data:
- Hotel size: 120 rooms
- Assumed monthly stays: 900
- Assumed guest messaging touchpoints per stay: 6 delivered messages
- Assumed monthly delivered messages: 900 × 6 = 5,400
- Assumed setup: one business phone number
- Free service tier: 1,000 delivered service messages
- Messages outside that free tier: 4,400, if all 5,400 messages were service messages delivered through the same number
The hotel should replace every assumption with its own data. The example does not establish a price. Finance should apply the relevant Meta rate card, then compare the resulting cost per delivered interaction with the value of the booking, stay, or ancillary service the interaction supports.
Also remember that not all 5,400 messages would necessarily be service messages. Some may be utility or marketing messages and would follow different category rules.
The main exception and the handoff
Complaints, refunds, billing disputes, vulnerable guests, accessibility concerns, serious service failures, and requests requiring judgement should stay with a person.
A queued template is not a resolved guest issue. A delivered message is not the same as accepted ownership, a recorded decision, guest notification, or completed action.
For every exception, the hotel should record:
- What the guest requested
- Which person accepted ownership
- What decision was recorded
- Whether the guest was notified
- Whether the matter is complete or still pending
The hotel review-triage workflow uses the same ownership principle: automation can organise and route work, but a responsible person must handle issues that require context, discretion, or recovery authority.
The operating decision
Before 1 October 2026, audit your WhatsApp activity by delivered message, category, business phone number, and guest journey.
Then remove low-value repetition, confirm payment and billing currency, check the shared portfolio messaging limit, and set a quarterly review process. Your hotel does not need to stop using WhatsApp. It needs to know which messages are necessary, which category they belong to, and who owns the exception when a template is not enough.
Use this checklist with your reservations, front office, revenue, finance, and operations teams. If you want to discuss how this scenario fits your hotel’s communication workflow, bring it to Voxido.