WhatsApp Business API for hotels: setup, rules and real costs

The app is fine until these start happening to a hotel:

• OTA commissions eat 15-25% of every booking.
• Guests rebook through an OTA, not with you. The guest loved the stay. Next trip they book the same room through an OTA because you never gave them a direct way back.
• Return guests book via OTA again.

The app cannot send on a trigger, share one number across staff, or read your records. The API can. And customers keep asking the same things: guests ask about availability and rates for their dates, early check-in, airport transfers, directions, and what is included in the room.

• A verified Meta Business account in the hotel's legal name, backed by a registration, GST or utility document.
• A number not active on the WhatsApp app — your current one works once it is removed from the app.
• A display name matching the business, and a website or public page Meta can check.
• Opt-in from every customer you message first. Booking confirmation and check-in are the natural points; many guests prefer a WhatsApp thread to email for everything during the stay.

1. Connect the number through Meta's embedded signup inside Reputoo, and submit business verification — you can start sending within Meta's starting limit while it is reviewed.
2. Get your first templates approved for the few routine messages listed below; anything outside a customer's 24-hour reply window must be a template.
3. Wire the triggers to your records. What to connect: A property management system and a channel manager; the PMS reservation is what should trigger confirmations and pre-arrival messages.
4. Put staff on one shared inbox, with conversations assigned so two people never answer the same customer.

A 60-room hotel with 40 arrivals a day sending four utility messages per stay sends roughly 4,800 a month — about ₹552 in Meta fees on the July 1, 2026 India rate card, before GST. In-stay replies inside the 24-hour window are charged at the utility rate from 1 October 2026. Marketing messages cost ₹0.8631 each.

A day or two before arrival, one message does a lot of work: it confirms the dates, asks the expected arrival time, lists what ID to bring, gives directions and a map link, and offers an airport or station pickup. Guests who answer the arrival time let housekeeping prioritise rooms; guests who book the transfer are met at the airport instead of haggling with a taxi. Keep upsells like room upgrades for a separate message, so this one stays a utility message.

Meta charges per delivered template message, and the price depends on the category. For hotels, the day-to-day messages sort like this:

• Inquiry → direct booking offer (saves guest money) — service reply
• Pre-arrival personalisation on WhatsApp — marketing
• Post-checkout rebooking offer — marketing
• 6-month return offer for past guests — marketing

Timing matters as much as category. Pre-arrival messages a day or two before check-in, in-stay messages on request, and post-stay messages after checkout — not while the guest is travelling.

A service reply answers a customer who wrote first; from 1 October 2026 Meta charges those at the utility rate. Utility messages (confirmations, reminders, status updates) cost a fraction of marketing messages, so keep them strictly transactional — a discount line inside a reminder makes Meta classify the whole template as marketing.

Meta list rates, July 1, 2026. India in INR, plus 18% GST.

"Can I get extra towels?", "the AC isn't cooling", "two coffees to room 214" — guests prefer to message rather than call the front desk. On the API these arrive in a shared inbox, and each request can be routed: housekeeping gets towels and cleaning, maintenance gets the AC, room service gets orders. The guest gets an acknowledgement and a time. The front desk stops being a switchboard.

Every booking through an online travel agency costs the hotel commission. Guests who message the hotel directly — from Google, the website, a previous stay — can be quoted and booked in the chat with a payment link for the deposit. Answer fast: a guest comparing prices on an OTA will book there if the hotel takes an hour to reply. A clear direct-booking reason — the best available rate, free breakfast, flexible cancellation — gives them a reason to book with you.

Meta rates every number on how customers react. For hotels, the risk is usually messaging the whole contact list about something only some of them asked for. Send reminders only to people with a booking or order, promotions only to people who opted in to them, and never use a bulk-sender tool on the ordinary app — that is the route to a banned number. The full list of what Meta checks is in our WhatsApp Business API guide.

A bill sent to WhatsApp before checkout lets the guest check it in their room and pay by link, so the desk is not queued at 11 am. Business travellers need a proper invoice with company details for claims — ask for GST or company details at booking and send the invoice as a PDF after payment. Disputes about charges go to the front office manager, with the folio attached.

Group bookings and weddings involve room blocks, rooming lists, meal plans and deposits over weeks. A WhatsApp group run by the hotel's events team, or one thread with the organiser, keeps everything in writing: the contract summary, the deposit links, the rooming list deadline, the event timeline. The organiser forwards messages to guests; the hotel keeps the record.

Hotels receive messages at every hour from guests in other countries. An automatic reply outside desk hours — or better, a night manager on the shared inbox — must acknowledge every message and say when a full reply will come. Guests write in many languages; replies in the guest's language build confidence before arrival.

Hotel groups usually run one number per property, each with its own display name, under one business account. Central reservations can see every conversation and take group-wide enquiries. If one number serves several properties, the first question is always which property, and every confirmation names it clearly.

1. Week 1: move the number to the API; get confirmation, pre-arrival, check-in and checkout templates approved; set up routing to departments.
2. Week 2: every reservation, from any channel, gets confirmation and pre-arrival messages.
3. Week 3: in-stay requests routed to departments; bills and invoices by WhatsApp at checkout.
4. Week 4: direct-booking replies with deposit links, and the first seasonal message to past guests who opted in.

• The PMS reservation triggers the confirmation and pre-arrival messages.
• Department routing is set, and each department knows its response times.
• Night coverage of the inbox is assigned.
• Templates contain no offers; packages go in separate marketing templates.
• Invoices carry the guest's company details when requested.

Companies that send staff regularly want a single contact, negotiated rates, bookings made by their travel desk, and invoices in their name. A dedicated thread with each corporate travel desk — confirmations, changes, invoices, monthly statements — keeps everything in one place. Travellers still get their own pre-arrival and check-in messages, while billing goes to the company.

Hotels earn much of their revenue outside the room. Guests who can book a table, a massage or a sunset tour by message during their stay use them more. Send a short in-stay message on the first evening with what is available and how to book — a utility message if it is information about the stay, marketing if it carries an offer — and let requests flow to each outlet through the shared inbox.

Any guest message about a medical problem, fire, a security concern or a missing person must reach the duty manager at once, bypassing every queue. Write those words into the routing rules in each language you receive, and make sure the night manager's phone is alerted. It is the one kind of message where speed matters more than any process.

Many hotels run WhatsApp on a front-desk phone. It breaks when shifts change and the next person cannot see yesterday's promises, when three departments need the same message, and when a manager's personal number becomes the real reservations line. The API puts every conversation on the hotel's number, in a shared inbox, with routing, history and night coverage.

Keep hotel templates specific: guest name, dates, room type, the rate plan's cancellation terms, the property. Avoid offers in confirmations and pre-arrival messages, and avoid vague text that could mean anything. Separate templates per purpose — confirmation, pre-arrival, check-in, checkout — are approved faster and stay in the utility category.