WhatsApp Business for Hospitality

Takeaways

What is WhatsApp Business for hospitality?

WhatsApp Business for hospitality is the practice of hotels, resorts, vacation rentals, and travel operators using WhatsApp to communicate with guests before, during, and after their stay. A guest books a room and gets a confirmation in WhatsApp. The night before arrival, they get check-in instructions. During the stay, they message the front desk for towels or a dinner reservation. After checkout, they get a review request. Every touchpoint happens in one conversation thread on the WhatsApp Business Platform.

The model works because the guest never has to do anything new. There is no hotel app to install, no portal login, no hold music. They message the property the same way they message a friend.

WhatsApp Business App vs. WhatsApp Business Platform (API)

Any WhatsApp business for hospitality guide has to start with this distinction, because the two products solve different problems. The free WhatsApp Business App runs on a single phone. For a small guesthouse with one person answering messages, it works. The WhatsApp Business Platform is the API version. It connects to your property management system, supports multiple agents on the same number, and sends automated template messages at scale. Multi-property groups need the Platform, and it requires registering dedicated business phone numbers, which Telnyx provisions in 140+ countries with instant activation.

Benefits of WhatsApp over traditional guest communication channels

WhatsApp counts more than 2 billion monthly active users worldwide. In most of Europe, Latin America, the Middle East, India, and Southeast Asia, it is the default way people communicate. A hotel confirmation email lands in an inbox next to promotions and spam. A WhatsApp message lands in the same feed as messages from family, and guests typically read it within minutes. Phone calls interrupt guests and require staff time per call. WhatsApp conversations are asynchronous, so one agent can handle many guests at once.

Large hospitality groups have already made the shift. OYO uses WhatsApp for booking confirmations and stay communication across thousands of properties, and Accor brands use it for guest services in markets where WhatsApp dominates. The pattern is consistent. When hotels move guest messaging to WhatsApp, response rates rise and front-desk call volume drops.

How to manage message templates on the WhatsApp Business Platform

WhatsApp separates conversations into two types. When a guest messages you first, a 24-hour customer service window opens and you can reply with free-form text. When you message the guest first, outside that window, you must use a message template that Meta has reviewed and approved. This rule exists to prevent spam, and it shapes how every hotel messaging program is built.

How to create WhatsApp message templates in Meta Business Manager

Creating a template takes a few minutes in Meta Business Manager. The steps:

1. Open WhatsApp Manager inside Meta Business Manager and select Message templates, then Create template.
2. Choose a category. Utility covers transactional messages like confirmations. Marketing covers offers and upsells. Authentication covers one-time passcodes.
3. Name the template in lowercase with underscores, such as booking_confirmation_en.
4. Select a language and write the body. Use numbered variables like {{1}} and {{2}} for guest name, dates, and confirmation numbers.
5. Add an optional header, footer, or quick-reply buttons.
6. Submit for review. Meta typically returns a decision within 24 hours.

Template categories and approval best practices

Meta rejects templates that are vague, misleading, or miscategorized, so read the template guidelines before submitting. The most common rejection causes are marketing content submitted under the utility category, floating variables with no surrounding text, and grammar errors that make the message look like spam. Write templates the way a concierge would speak, state clearly what the message is about, and give the guest an obvious next step.

Categorization also affects cost. Utility conversations price lower than marketing conversations in most markets, so keep confirmations and stay logistics in utility templates and reserve marketing templates for genuine offers.

Hospitality template examples that convert

These four templates cover the core guest journey and pass Meta review when submitted in the right categories.

Hi {{1}}, your reservation at {{2}} is confirmed for {{3}} to {{4}}. Your confirmation number is {{5}}. Reply to this message with any questions before you arrive.

Hi {{1}}, we look forward to welcoming you tomorrow. Check-in opens at {{2}}. Reply here to arrange early check-in or airport pickup.

Hi {{1}}, enjoying your stay? Late checkout until 2 PM is available for {{2}}. Reply YES and we will add it to your room.

Thank you for staying with us, {{1}}. We would love your feedback. Leave a review here: {{2}}.

The real gain comes from sending these programmatically. When your booking engine or PMS fires a webhook, an API call sends the right template with the right variables, no staff involved. This pattern from the Telnyx order tracking notifications example adapts directly to booking confirmations and stay updates:

"""Proactive WhatsApp notifications, adaptable to booking confirmations and stay updates."""
import os, requests, telnyx
from dotenv import load_dotenv
from flask import Flask, request, jsonify

load_dotenv()
app = Flask(__name__)
client = telnyx.Telnyx(api_key=os.getenv("TELNYX_API_KEY"),
                       public_key=os.getenv("TELNYX_PUBLIC_KEY"))

WHATSAPP_NUMBER = os.getenv("WHATSAPP_NUMBER")
MESSAGING_PROFILE_ID = os.getenv("MESSAGING_PROFILE_ID")

bookings = {}  # booking_id -> {guest_phone, dates, status, updates[]}

@app.route("/booking/created", methods=["POST"])
def booking_created():
    data = request.get_json()
    bookings[data["booking_id"]] = data
    return jsonify({"status": "confirmation sent"})

How to enhance guest engagement, streamline bookings, and boost customer satisfaction

The way to get results from WhatsApp is to map it to the guest journey stage by stage. Each business-initiated message is a template. Each guest reply opens a two-way service window. Each step needs a fallback path for guests who are not reachable on WhatsApp.

Automate booking confirmations and pre-arrival messaging

To streamline bookings, connect your booking engine to the messaging flow. A new reservation fires a webhook, your integration sends the booking confirmation template within seconds, and the guest has proof of purchase in the app they check most. Twenty-four hours before arrival, a scheduled job sends the pre-arrival template with check-in times and an invitation to reply. Guests who reply asking for early check-in or an airport transfer open the service window, and your team converts a logistics message into a service conversation before the guest sets foot on the property.

Deliver in-stay concierge service and upsells

In-stay messaging is where WhatsApp drives revenue directly. A guest who can text for a dinner reservation, spa slot, or late checkout will do it more often than one who has to call the front desk. Quick-reply buttons on upsell templates make accepting an offer a single tap.

Scale is where informal WhatsApp operations break. A shared phone at the front desk gives you one agent per number, no audit trail, and no response-time metrics. Once a property passes a few dozen conversations a day, you need software-based routing that assigns conversations to available agents, escalates unanswered messages, and reports median response time per property. Those numbers are the difference between a channel that delights guests and one that quietly drops requests.

Collect feedback and drive repeat bookings

To boost customer satisfaction after checkout, send the review request template within a few hours of departure, while the stay is fresh. Guests who reply with a complaint get a recovery conversation instead of leaving a public one-star review. Guests who reply positively get a direct-booking offer for their next stay, which keeps the repeat booking off commission-charging OTA channels. The same WhatsApp thread that confirmed the first booking becomes the channel for the second.

Add SMS fallback so no guest message is missed

Not every guest is reachable on WhatsApp in every market. US travelers in particular often default to SMS. Before routing a message, run a number lookup to check the destination number, attempt WhatsApp delivery first, and fall back to SMS when the guest is unreachable. The Telnyx SMS API delivers the fallback leg on the same platform, with smart routing and delivery optimization, so hotels run both channels through one integration and one bill instead of stitching a chatbot vendor to a separate SMS provider.

The WhatsApp-SMS bridge example shows the pattern:

"""WhatsApp-SMS Bridge - bidirectional bridge between two messaging channels."""
import os, requests, telnyx
from dotenv import load_dotenv
from flask import Flask, request, jsonify

load_dotenv()
app = Flask(__name__)
client = telnyx.Telnyx(api_key=os.getenv("TELNYX_API_KEY"),
                       public_key=os.getenv("TELNYX_PUBLIC_KEY"))

TELNYX_API_KEY = os.getenv("TELNYX_API_KEY")
SMS_NUMBER = os.getenv("SMS_NUMBER")
WHATSAPP_NUMBER = os.getenv("WHATSAPP_NUMBER")
MESSAGING_PROFILE_ID = os.getenv("MESSAGING_PROFILE_ID", "")

def send_sms(to, text):
    resp = requests.post(
        "https://api.telnyx.com/v2/messages",
        headers={"Authorization": f"Bearer {TELNYX_API_KEY}",
                 "Content-Type": "application/json"},
        json={"from": SMS_NUMBER, "to": to, "text": text,
              "messaging_profile_id": MESSAGING_PROFILE_ID},
        timeout=10)
    return resp.ok

Delivery speed and reliability define the guest experience once volume grows. A confirmation that arrives an hour late, or not at all, generates a phone call and an anxious guest.

Run guest communications on the Telnyx platform

The playbook is short. Map your guest journey, build approved templates for each business-initiated step, wire triggers from your PMS or booking engine, and measure response times per property. What matters underneath is the infrastructure. Telnyx runs WhatsApp, SMS, and voice on one owned, carrier-grade network, with messaging APIs, phone numbers in 140+ countries, and verification in a single platform. Hospitality teams skip stitching together a chatbot vendor, an SMS provider, and a number supplier.

For secure booking modifications, the Verify API sends one-time passcodes over WhatsApp, so a guest changing dates or payment details proves ownership of the booking first. The same API delivers those passcodes over SMS, voice, or flash call to users in 190+ country codes, so a guest who never opened WhatsApp still gets verified. The WhatsApp Verify OTP example shows the flow:

"""Send and verify one-time passwords via WhatsApp using the Telnyx Verify API."""
import os, requests
from dotenv import load_dotenv
from flask import Flask, request, jsonify

load_dotenv()
app = Flask(__name__)

TELNYX_API_KEY = os.getenv("TELNYX_API_KEY")
VERIFY_PROFILE_ID = os.getenv("VERIFY_PROFILE_ID")
API_BASE = "https://api.telnyx.com/v2"

FAQ