Hotel Guest Messaging Glossary: The Terms Vendors Use and What They Mean

Guest messaging vendors use a vocabulary that sounds precise and is often not. These are the terms that come up in every evaluation, defined the way they are actually used in 2026 - including where a term hides a question you should ask.

Channels and WhatsApp

WhatsApp Business API / Cloud API. The official route for businesses to send and receive WhatsApp messages at scale, as opposed to the WhatsApp Business app on a single phone. Every serious hotel messaging product runs on it.

WABA (WhatsApp Business Account). The account, registered to a legal entity, that holds a business's phone number, verified name and approved templates. The question it hides: whose name is on yours. If the vendor's, the number is theirs when you leave.

Message template. A pre-approved message a business can send outside the 24-hour window. Every proactive message - pre-arrival, check-in link, reminder - is one. Templates are reviewed by Meta and can be rejected. The question: does the vendor have a library of approved patterns, or will you wait on approvals during onboarding.

24-hour window / customer service window. After a guest messages, the business may reply freely for 24 hours. After that, templates only. This is why the assistant answering instantly matters commercially: a reply inside the window is free-form; a reply the next day is a template.

Conversation (as a billing unit). Meta charges businesses per conversation, categorised by who started it and why. This is the main reason vendor pricing scales with volume.

Omnichannel / unified inbox. One view of guest messages from every channel - WhatsApp, Instagram, Messenger, Telegram, web chat. Its purpose is that a guest moving between channels does not have to repeat themselves, and staff do not have to check five apps.

The assistant

LLM (large language model). The technology behind the current generation of assistants. Understands meaning and intent rather than matching keywords; handles any phrasing, any language, typos included. The successor to the decision-tree chatbot.

Rules-based / scripted / decision-tree chatbot. The previous generation. Predefined buttons and paths. Predictable and cheap; fails the moment a guest phrases something unexpectedly. Still correct for deterministic flows, wrong as a conversation layer.

Grounding. Whether the assistant answers from the property's own knowledge base or from the model's general training. Grounded means it says what it was told and hands over the rest. Ungrounded means fluent, plausible, occasionally invented. The question: what is it grounded in, and what does it do when it does not know.

Hallucination. An ungrounded assistant producing a confident, wrong answer - a check-in time that sounds right and is not. The specific risk of language models, and the thing to test hardest.

Knowledge base. Everything the property has told the assistant - hours, policies, prices, tone, what to escalate. The largest part of a deployment's value, and the part that goes stale unless someone owns it.

Intent. What a guest actually wants from a message, as distinct from the words used. Can we get in at 8 is an early check-in intent. Language models detect intent; trees match words.

Escalation / handover. The assistant passing a conversation to a person. The most important behaviour in the product. The questions: where does it land, on what channel, and what happens if nobody responds.

Human-in-the-loop (HITL). The operating model where the assistant handles routine and a person handles exceptions, with the system flagging what needs a human. The alternative - full automation - is faster on the routine and worse on everything that matters.

Auto-resolution rate / resolution share. The share of guest conversations handled without a person. Across the vGuest portfolio it runs around 70%, with the best property at 98.7%. The headline metric for an operations deployment.

Integration

PMS (property management system). The system of record - reservations, guest profiles, room status, folios. Everything else in the stack is downstream of it.

Read-only vs two-way / write-back. Read-only: the assistant can see reservation details. Two-way: it can also record a late check-out, attach a signed form, update a preference. The question: which fields, specifically.

Booking engine. The system that takes reservations on the hotel's website. Pre-booking conversion assistants integrate here; operations assistants integrate with the PMS. Which one a vendor's deepest integration is tells you which category they are in.

Channel manager. Distributes rates and availability to OTAs. Rarely touched by messaging products directly, but the source of truth availability answers depend on.

Digital check-in. Guest completes registration, signs, and often pays before arrival, usually via a link sent on WhatsApp. Depends on PMS write-back to attach the signed document to the reservation.

Data

Data residency. Which jurisdiction guest data is stored in. Matters in Europe. The question: name the region. vGuest stores in the EU.

Retention. How long conversation data is kept. Ask, because the default is often indefinite.

Export. Getting your conversations, templates and knowledge base out. The question: in what format, and how long does it take. Ask before you need it.

Commercial

Pilot. A short run at real volume with real guests before a contract. The only evaluation that shows escalation, write-back and multilingual handling with your own data. A demo is not a pilot.

Per-property pricing. Standard for groups. Each site is a unit; discounts by volume.

Overage. What you pay above your tier's conversation cap. Read this line.

If a term you were quoted is not here, ask the vendor to define it in one sentence. The precise ones can.