How Hotels Automate WhatsApp Bookings, Step by Step

Hotels automate WhatsApp bookings by connecting the WhatsApp Business Platform to an agent that reads live availability and rates from the PMS or booking engine. The agent answers the guest, creates the booking and sends a payment link in the same chat. Approved templates handle follow-ups once the 24-hour reply window closes, and a person takes over when the agent can't help.

The same agent can also answer guests in your website chat and inside your web app or booking portal, where Osvi's Chat SDK runs it as a launcher widget, an inline panel or a headless client you build your own UI on, and can sign in guests who are already logged in.

The steps below suit independent hotels, hostel chains and small groups. Our worked example is Zostel, which runs a WhatsApp booking agent we built.

Step 1: Choose the WhatsApp Business App or the Platform

Meta offers two products, and you can automate only one of them.

The WhatsApp Business App is a phone app "built with the small business owner in mind." It gives you a business profile, a catalog, and greeting and away messages. Your front desk still types every reply.

The WhatsApp Business Platform is the API. You can connect to Meta's Cloud API yourself, or go through a Business Solution Provider (BSP) such as Gupshup, which handles onboarding and billing for you. Any agent that checks your inventory and creates bookings needs the Platform.

If one person can answer every enquiry within a few minutes, at every hour guests write, the App is enough. Once you run more than one property, or guests message you at night, move to the Platform.

You can keep the number guests already have. Meta lets a business connect its existing App number to the Cloud API and keep using the App for one-to-one chats. Messages mirror between the two, and the last six months of chat history can sync. The link has costs: Meta disconnects linked companion devices, turns off broadcast lists and caps the number at 20 messages per second.

Verify your business early. New business portfolios can message only 250 unique people per rolling 24 hours outside an open conversation, and business verification is one way to raise that limit. If you plan to send payment reminders to guests who went quiet, a busy weekend can use up that cap.

Step 2: Connect live availability and rates

A guest who asks "two dorm beds for Friday and Saturday?" needs an answer from tonight's inventory. Last month's rate sheet won't do.

Your data probably lives in one of three places:

• PMS. Rooms, reservations and guest records. If you run Cloudbeds or apaleo, both have APIs an agent can call.
• Booking engine. The checkout on your website, often with its own rate plans and promo codes.
• Channel manager. Pushes inventory to the OTAs and pulls their bookings back.

Connect the agent to whichever system holds the true count of sellable rooms, and have it read availability and rates through an API call on every quote.

Don't paste rates into the prompt or into a document the bot searches. We learned this building support agents for Zostel. Document search works on paragraphs, and a hotel's data is rows: rooms, dates and prices. Availability read from an API stays correct. A rate copied into a doc goes stale the next time your revenue team changes it.

Then decide how much the agent can write. Some hotels start read-only, where the agent quotes and then sends a booking engine link with the dates filled in. Others let the agent create the reservation and attach a payment link. Both work. Write access saves the guest a step, but start with whichever your PMS supports without workarounds.

Step 3: Put booking rules in code

Your front desk applies dozens of rules from memory. Write them down first, and decide where each one lives.

Only the last row belongs in the prompt. The model is good at conversation and bad at arithmetic a guest can talk it out of. If a guest says "so that's $300 total, right?" and the real figure is $354, the agent should read the number your code returned and hold to it.

Groups need their own path. A group booking can run for days while one guest checks dates with the rest, so the agent has to remember where the conversation stopped and follow up. See how we handle group bookings for hostels and hotels.

Step 4: Take payment with a payment link

Most hotels take payment on WhatsApp with a link. Your payment gateway or booking engine creates a link tied to the reservation, the agent sends it, and a webhook marks the booking paid. Links work for guests in any country and with any card.

In India you have a second option. Meta's Payments API lets a business send an order message inside the chat, which the guest can pay from any UPI app on their phone. Cards, net banking and wallets also work if your gateway has Meta's deeper integration, which the docs list for Razorpay, PayU, Billdesk and Zaakpay. Your BSP has to support these APIs, so ask before you plan around it.

Either way, set a hold time, tell the guest what it is, and release the room when it expires. An unpaid booking that sits for three days blocks inventory you could have sold.

Step 5: Follow up with approved templates

WhatsApp gives you a reply window. A guest's message opens a 24-hour customer service window, and each new message from the guest resets it. Inside the window you can send any normal message. Once it closes, you can send only pre-approved templates.

Many guests ask for a quote and go quiet until the next day, so your payment reminder will often need to be a template.

Meta sorts templates into three categories: marketing, utility and authentication. A utility template has to follow from something the guest did and must have no promotional intent. A template that mixes an update with a promotion counts as marketing. In practice:

• "Your room for 14 to 16 November is held until 6pm. Pay here to confirm." This is a utility message.
• "Still thinking it over? Book today and get 10% off." This is marketing.

Category affects price. Meta has charged per delivered message since July 1, 2025, with rates that vary by country and category. On October 1, 2026, Meta started charging for utility messages sent inside an open window, which had been free. Meta now charges for service messages, the normal replies you send inside the window, after the first 1,000 per business phone number each month. If you priced your WhatsApp budget before October, check it again.

Keep follow-ups few. One reminder before the hold expires is usually enough, and if the guest says no, stop.

Step 6: Hand off to a person with context

Some requests belong with a person: refunds, complaints, no hot water at 11pm, a guest who asks for a manager. Decide those cases up front.

A handoff works when the staff member can act without scrolling. Send them the guest's number, the booking and a one-line summary of the issue. Tell the guest what happens next and roughly when. Plan for the hour when nobody picks up, so the guest doesn't wait in silence.

At Zostel, escalations reach the property team as a ticket with the guest's number, booking and issue attached.

Phone calls feed the same flow. If nobody answers a guest's call at night, a missed-call follow-up on WhatsApp brings them into that flow and they can still book.

Step 7: Measure it

Track these from the first week:

• First reply time. How long a guest waits for the first answer, broken out by hour of day.
• Resolution rate. The share of chats the agent closes without staff.
• Booking link rate. The share of chats where the agent sent a booking or payment link.
• Link-to-payment rate. The share of sent links that turn into paid bookings.
• Bookings and revenue. Paid bookings through the channel each month.

Every booking that closes on WhatsApp is a direct booking with no OTA commission attached. If that's your main reason to do this, read our guide on how to cut OTA commissions too.

Review conversations weekly, and test every change before it ships. A fix for one flow can break another.

Results at Zostel

Zostel is India's largest backpacker hostel brand, with 111+ properties across 70+ destinations in India and Southeast Asia. Its WhatsApp agent, Zobu, handles guest enquiries. A separate group booking agent works across chat and voice, and a voice agent answers property phone lines.

Zobu checks live availability, applies property policy and any coupon, and creates the booking inside the conversation. Guests get a first reply in about 5 seconds and a booking link in about 3 minutes, at any hour. More than a quarter of guest messages arrive before 9am or after 9pm.

The numbers so far:

• The agent fully resolves 69% of Zobu chats.
• Zobu sends a booking link in 35% of conversations.
• Agents fully resolve 77% of group chats.
• Guests completed 81% of payments through agent-generated booking links.
• Monthly bookings through the agents grew 50% from June to August 2026.
• Guest chats grew more than fourfold since July 2026.

The hallucination rate is under 1%. Each change has to pass a test suite of more than 250 scenarios before it ships.

Mistakes to avoid

• Putting rates in the prompt. They go stale and the model will quote them anyway.
• Sending promotions as utility templates. Mixed content counts as marketing, so write promotions as marketing templates from the start.
• Holding rooms with no expiry. Set a hold time and release unpaid inventory.
• Hiding the person. Make the handoff easy to find and pass the context along.
• Shipping changes without tests. Replay saved conversations before each update.

If you want to see a booking agent working on your own inventory, look at our WhatsApp booking agent for hotels or talk to us.