WhatsApp CRM for Hotels and Resorts in India: The Complete Playbook

The short answer: what a WhatsApp CRM does for a hotel

A WhatsApp CRM runs the entire guest journey, enquiry, quotation, confirmation, pre-arrival, in-stay service and win-back, on one business number with a shared inbox and approved templates. It pays for itself on commission: OTAs take 15 to 25 percent, so one direct repeat booking of Rs. 24,000 saves you about Rs. 4,300, which is more than four months of software at Rs. 999 per month.

That is the business case. Everything below is how to build it, workflow by workflow, with the template copy, the Meta rules you will hit, and an honest section on properties that should not buy this software.

Hotels fit WhatsApp well because the guest journey is long and full of scheduled moments, and every one of them is already a message somebody types by hand. A resort selling 750 room nights a month sends several thousand messages from a phone nobody can audit, back up or hand over at shift change.

OTA versus direct: the commission math that funds the whole project

OTAs are a distribution channel, not an enemy. They fill your low season and put you in front of travellers who have never heard of your property. What they are not is cheap. Indian hotels typically pay 15 to 25 percent depending on the platform and the contract, and once you add gateway charges and channel manager cost the effective take on a stay can cross 20 percent.

What 18 percent costs a 40-room resort

Take a 40-room resort at 62 percent occupancy and an ADR of Rs. 6,500: roughly 744 room nights a month and about Rs. 48 lakh in room revenue. If 55 percent of that arrives through OTAs at 18 percent commission, you hand over close to Rs. 4.8 lakh a month, about Rs. 57 lakh a year.

You will not move all of that to direct, and anyone promising it is selling you something. But shifting 10 percent of OTA revenue to direct repeat bookings puts about Rs. 48,000 a month back on your P and L. Repeat guests are the segment WhatsApp reaches best: you already have their number and they already know the place.

Be honest about the ceiling. WhatsApp will not win a first-time traveller comparing eight properties on a metasearch page. It reliably wins four buckets:

• The repeat guest who stayed last November and would come back if reminded in September.
• The direct enquiry from your Google Business Profile, a click-to-WhatsApp ad, or a QR code at the reception desk.
• The group, banquet, wedding and MICE lead, which almost never books through an OTA anyway.
• The guest already in-house, who can be sold a spa slot, a late checkout or one extra night.

Point the CRM at those four and ignore everything else in year one.

Workflow 1: enquiry to quotation for rooms

An enquiry arrives as "Rates for 2 adults 1 child, 14 to 16 Nov?" The moment it lands, a 24-hour customer service window opens. Inside it you can send free-form messages with no template and no per-message charge, so this is the cheapest part of the journey.

Your bot should collect four things before a human takes over: dates, adults and children, room preference, city of origin. Four questions, not twelve. The conversation then lands in a New Enquiry pipeline stage, assigned to the reservations agent on shift, with an SLA timer running.

The 90-second first reply

Speed beats price in reservations more often than owners believe. A guest who gets a rate in 90 seconds while still on your website converts far better than one who gets a perfect PDF four hours later, after booking elsewhere. Set the SLA at 5 minutes in office hours and use an honest auto-reply outside them.

An auto-reply that works, free-form inside the window: "Namaste, thank you for writing to Silver Oak Resort. Front desk replies between 8 AM and 10 PM. Share your dates and guest count and we will send rates with photos. For urgent bookings call 98XXXXXXXX."

Send the quotation as a short message plus one image, never a PDF. PDFs get downloaded and forgotten. Quote two options, not five: your recommended room and one cheaper alternative. Always end with a next step, for example "Shall I hold this for 24 hours?" Hold requests are the highest-converting sentence in a hotel WhatsApp inbox.

One rule catches people out: quoting after the window has closed needs an approved template, and because it is a rate offer to someone who has not booked, Meta will classify it as marketing, not utility. Plan for that cost.

Workflow 2: group, banquet, wedding and MICE enquiries

Group business is where a WhatsApp CRM earns its keep fastest: long sales cycle, manual follow-up, high-value leads. One wedding can be worth more than a fortnight of transient room revenue, and it never comes through an OTA.

Why a banquet quote takes five days, and how to cut it to two

A banquet quote is slow because it is a chain: date check against the banquet calendar, pax count, menu from the chef, decor and DJ estimate from a vendor, final rate approval from the owner. Each handoff happens on a different channel, so nothing is visible in one place.

Fix it with pipeline stages, not a faster typist. Build a separate Banquet pipeline: Enquiry, Date Held, Menu Shared, Site Visit, Proposal Sent, Negotiation, Won, Lost. Make one field mandatory per stage, for example pax and event date at Enquiry. Add an ageing alert so a proposal sitting in Negotiation for four days pings the sales head.

The follow-up rhythm that works for weddings and offsites is T plus 2 days, T plus 7, T plus 21, then a seasonal touch. More aggressive and you get blocked. Less and you lose the file to the property that called twice.

For site visits, send a utility reminder the evening before: "Hi {{1}}, confirming your banquet site visit at Silver Oak on {{2}} at {{3}}. Ask for {{4}} at reception. Parking is at Gate 2. Reply here to reschedule." A reminder tied to a scheduled appointment sits comfortably in utility. One that leads with a discount does not.

Workflow 3: booking confirmation with a utility template

Once payment or a confirmed PMS status exists, the booking confirmation is a utility template, because it relates to a transaction the guest already agreed to. It is the highest-read message your property sends, so put real information in it.

Template copy that gets approved and actually helps:

"Namaste {{1}}, your booking at Silver Oak Resort is confirmed. Booking ID {{2}}. Check-in {{3}} from 2 PM, check-out {{4}} by 11 AM. {{5}} room, {{6}} guests, breakfast included. Total Rs. {{7}}, paid Rs. {{8}}, balance Rs. {{9}} payable at the property. Reply here for any change."

Add two buttons: a URL button with your Google Maps pin, and a quick reply labelled "Talk to front desk" that opens a fresh 24-hour service window when tapped. That second button is the quiet workhorse of the system: every tap gives you a free window in which to sell an airport pickup or early check-in.

Do not stuff a promotion into this template. A confirmation ending with "Book our spa at 20 percent off" gets recategorised as marketing, and you pay marketing rates on every confirmation for the rest of the year.

Workflow 4: pre-arrival messages that cut front-desk load

Pre-arrival is where the operational savings show up. Most front-desk calls at a leisure property are three questions: what time is check-in, how do I reach you, what ID do I need. Answer all three before the guest thinks to call.

The T-48 message: check-in time, directions and ID rules

"Hi {{1}}, we are getting your room ready at Silver Oak for {{2}}. Check-in opens at 2 PM. Please carry an original government photo ID for every adult; foreign national guests need passport and visa pages. Parking is free on site. Anything you would like arranged before you arrive?"

That last question is deliberate. A reply opens a 24-hour service window in which every follow-up is free and needs no template. Roughly a third of guests answer, and a good slice of those ask for something you can sell.

The morning-of message, and the upsell that pays for the software

"Good morning {{1}}. Your room is ready from 2 PM today. The last 4 km after {{2}} is a narrow ghat road, so please use the map pin below rather than the town name. Front desk {{3}}. Reply 1 for early check-in, 2 for an airport pickup quote, 3 for a candlelight dinner table."

Numbered replies beat open questions on a phone screen. Track attach rate on this one message: at most properties, airport pickups and early check-ins sold here cover the entire platform subscription in month one.

Workflow 5: in-stay service requests routed to housekeeping and F&B

Once the guest checks in, WhatsApp becomes your service channel and the economics turn in your favour: the guest is messaging you, so you are inside the 24-hour window and everything you send back is free-form and free.

The 24-hour service window, in plain English

Every guest message opens a 24-hour window. Inside it you can reply with anything: text, photos, a menu image, a bill. Outside it you must use a pre-approved template. Nothing else opens the window, and a guest simply being resident does not keep it open, which is why in-stay messaging should end with a prompt that earns another reply.

Route by intent, not keyword guessing. A simple in-stay menu works: "How can we help? 1 Housekeeping, 2 Room service, 3 Spa and activities, 4 Front desk." Each option assigns the chat to a team queue with its own SLA, say 10 minutes for housekeeping and 5 for room service. It stays on the guest thread, so the evening shift sees that the guest already asked for towels at 11 AM.

Two things most properties skip. First, an escalation rule: any in-stay chat unanswered for 15 minutes pings the duty manager, because an in-house guest waiting on WhatsApp is a one-star review forming in real time. Second, a complaint tag: tag the thread, close it before checkout, and never send that guest a review request while it is open.

Workflow 6: checkout, feedback and winning the guest back next season

Checkout is a sales moment disguised as an administrative one, and the post-stay window is where commission-free future revenue is created.

The checkout hour is your best upsell window

Send a utility message at 9 AM on departure day: "Good morning {{1}}, checkout is at 11 AM today. Reply LATE for a 2 PM checkout at Rs. {{2}}, or BILL to see your folio now." Late checkout is near pure margin on a day the room is not resold, and more guests take it on the phone than at a counter.

Four hours after checkout, send a feedback template. Keep it purely about the stay: "Thank you for staying with us, {{1}}. How was your stay at Silver Oak? Reply 1 to 5, where 5 is excellent. We read every reply." A feedback request tied to a completed transaction sits in utility. Here is the move most properties miss: do not put the Google review link in the template. Wait for the reply, which opens a free 24-hour window, then send the link only to guests who rated 4 or 5. Anyone rating 1 to 3 gets a call from the manager instead. Same cost, better review profile, no reclassification risk.

Seasonal broadcasts, opt-in and the DPDP Act

Win-back is a marketing template and it goes only to guests who opted in. Opt-in is a Meta policy requirement, and under India's DPDP Act consent must be free, specific, informed and easy to withdraw. Capture it where the guest is happiest, on the registration card and in the checkout message, stating what you will send and how often. Our guides on building a compliant opt-in list and on DPDP Act compliance for WhatsApp marketing cover the wording and record-keeping.

Then segment by what the guest actually booked. A family that took a two-bedroom villa at Diwali should not get the same broadcast as a midweek couple in a standard room. A win-back template that works, sent 8 to 10 weeks before their season:

"Hi {{1}}, the valley is green again and our monsoon package opens on {{2}}. You stayed with us in {{3}}, so your returning guest rate is Rs. {{4}} per night with breakfast, below our online rate. Reply BOOK and we will hold a room for 24 hours."

Include a "Stop promotions" button, honour it instantly, and cap marketing at about one send per guest per month. Discipline protects your quality rating, and a poor rating quietly reduces how many messages Meta lets you send.

The message templates you will actually use

Ten templates cover a full-service hotel. Build these, get them approved, and resist creating thirty more. Approval usually takes minutes and rarely more than a day, and the most common rejection reason is a promotional line inside a utility template.

What it costs: template categories, Meta billing and your software bill

Two separate bills. Meta charges per template message delivered and the rate depends on category. Marketing is the expensive one, utility and authentication are cheap, and free-form service replies inside an open 24-hour window are free, as are utility templates sent while that window is open. Another reason to design every message to earn a reply. Indian rates at the time of writing run about Rs. 0.78 for marketing and Rs. 0.12 for utility, detailed in our WhatsApp Business API pricing guide.

The second bill is the platform. ZupiChat Starter is Rs. 999 a month for one number and 3 agents, enough for a boutique property with a single reservations desk. Growth is Rs. 2,499 a month for 10 agents and full API access, which you want once housekeeping, F&B and banquet sales each need a queue. Details on the pricing page.

The comparison that matters to an owner, on a three-night stay at Rs. 6,500 per night:

Rs. 3,118 on one stay. Twenty such bookings a month and the platform cost stops being worth discussing. One clarification owners always ask about: the green tick is a separate Meta verification badge, it is not required to use the API and it will not win you bookings by itself. Our green tick guide explains when to chase it.

When a WhatsApp CRM is NOT the right tool for you

Plenty of properties should not be on the API, and any consultant who tells you otherwise has a quota to hit.

If you run a homestay or small villa with under about eight rooms, one person answering, and fewer than 50 conversations a day, use the free WhatsApp Business app. Labels for booking stages, quick replies for rates and directions, a greeting and away message, and the catalogue for room photos cover your entire operation. No template costs, no approval queue, no opt-in mechanics, no monthly fee. The API adds friction you have nothing to spend it on.

You are also not ready if bookings are almost entirely OTA-sourced and you have no direct funnel. Fix the front of the funnel first: a Google Business Profile with a WhatsApp link, a click-to-WhatsApp button on the website, a lobby QR code. Software cannot create demand nobody is generating. And if nobody can answer within 10 minutes in business hours, a shared inbox only makes slow replies more visible.

The moment to switch is specific: two people need the same number at once, you cannot tell who replied to which guest, bookings are copied into a register by hand, you want scheduled pre-arrival messages, or you need to broadcast to more than 256 contacts. That is the day the app stops being enough.

Then measure five things in month one and nothing else: median first response time, enquiry to booking conversion, direct share of room revenue, opt-in list growth, and template quality rating. If response time falls and direct share rises, it is working. If quality rating drops, you are broadcasting too hard, so cut frequency before Meta cuts it for you.

Also read: our guide to WhatsApp broadcast best practices for 2026, the step-by-step WhatsApp Business API setup walkthrough, and the full ZupiChat pricing breakdown.