Conversation OS
Start free
All posts

Hospitality

WhatsApp CRM for hotels

VartaDesk

WhatsApp CRM for hotels: stay and experience on the guest, booking confirm, pre-arrival and checkout thank-you on the same thread — not a booking-engine ticket.

A hotel pool at dusk — guest relations still talks to a person, not a booking-engine ticket.
A hotel pool at dusk — guest relations still talks to a person, not a booking-engine ticket.

A guest messages the number on the confirmation email: “Can we check in at 11? Also spa for two tomorrow.” The PMS has the stay. The spa book is a diary. The WhatsApp is a personal phone at reception. WhatsApp CRM for hotels means the stay and the experience sit on the same guest — confirm, pre-arrival, in-house request, checkout thank-you — without turning the inbox into a second property-management system.

This is as true for a 22-key boutique as for a small group. Growing hospitality still talks to a person, not a booking-engine ticket.

What a hotel inbox is not

It is not a PMS. Room inventory, folio, night audit, channel manager stay where they are. Do not ask a conversation OS to check a room in.

It is not a OTAs console. Booking.com and Expedia originate stays. The desk still owns the first human reply and the no-show.

It is where guest relations lives: arrival date, room type band, experience (spa, table, transfer), status (enquiry → staying → checked-out).

Lounge chairs by a pool at evening — pre-arrival is a CRM beat, not a mail-merge.
Lounge chairs by a pool at evening — pre-arrival is a CRM beat, not a mail-merge.

The objects that must exist

If your CRM only has “leads,” the night manager will invent a WhatsApp group called GUESTS_MAY.

  • Stay — dates, property, status (enquiry, confirmed, in-house, checked-out, no-show).
  • Experience — spa, table, transfer, tour — slot and outcome, linked to the guest.
  • Guest fields — stay purpose, party size band, loyalty note that is *not* a full card number.

VartaDesk’s hospitality pack installs stays and experiences on the conversation OS. Most properties should not fork “reservations WhatsApp” and “concierge WhatsApp” until assignment works.

Pre-arrival without spam

The expensive failure is not a missing greeting bot. It is a confirmed stay with no pre-arrival, or an in-house request that died in a personal chat.

A workable sequence:

  1. Booking confirm on the same thread (approved template).
  2. Pre-arrival (T-2 or T-1): timing, parking, spa hold. Email for the long PDF; WhatsApp for the question.
  3. In-house: a human owns the thread. Journeys pause on takeover — do not let a broadcast fire while the guest is at the desk.
  4. Checkout thank-you + one review ask. Then stop. Opt-out is a gate, not a suggestion.

India: SMS fallback for the guest who muted WhatsApp needs complete DLT. DLT guide.

A boutique facade over a pool — twenty-two keys still need one guest record.
A boutique facade over a pool — twenty-two keys still need one guest record.

OTAs, WhatsApp and the same person

The OTA ticket is not the guest. If the mobile on the booking and the WhatsApp number differ, identity has to resolve to one person or you will double-message them after checkout.

Comparing inboxes rather than PMS vendors: Wati vs VartaDesk. Phone in the manager’s pocket: WhatsApp Business App vs CRM.

First 10 days at the property

  • Connect the guest-relations WABA. Keep housekeeping groups off this number.
  • Install the hospitality pack. Import *upcoming* stays, not five years of folios.
  • Templates: confirm, pre-arrival, in-house request received, checkout thanks.
  • One journey: pre-arrival → no-show branch → assign duty manager.
  • Email for invoices and long menus. WhatsApp for the conversation.

Walk through the hospitality story or start free. The first win is the spa slot that still exists when the guest who asked at 11 pm comes down at 10.

Hospitality pack Start freeRSS