Meet Indian guests on WhatsApp with the same confirm-gated action model as web Concierge: grounded answers, proposed stay actions, staff takeover, and audit—not a shadow CRM in a personal phone.
01
Integrations
Section 01
What is the integration trying to accomplish?
Section 02
Which surfaces are designed for WhatsApp?
When enabled with a compliant WhatsApp Business setup (typically via an approved BSP and Meta processes), intended surfaces include:
- Guest-initiated service conversations tied to reservation context when identifiable
- Template-based business-initiated updates (pre-arrival, delay, payment nudges) where policy allows
- Confirm cards for stay-altering actions before HMS writes
- Staff takeover / release with thread continuity
Section 03
What must be true before you call it “live”?
You need WhatsApp Business account readiness, template approvals where required, BSP connectivity, property knowledge content, and NISKA entitlements for Concierge messaging. Until those are configured, treat WhatsApp as planned—not production.
Section 04
How do templates fit?
Business-initiated outreach generally requires approved templates. Use operationally clear language and keep promotional content in policy-compliant campaigns. The free WhatsApp template pack on NISKA tools is a content starter, not a substitute for Meta approval.
Section 05
Where should you read next?
Start with Concierge for the guest-agent model, Concierge integrations for stack touchpoints, and the India WhatsApp concierge article for operating habits.