Buyer's guide
How to choose a hotel AI
A guide for any hotel comparing AI and automation vendors. Use it with every vendor, including us. Judge a system on how many enquiries become confirmed bookings, not on how many messages it answers.
The one idea: buy an enquiry to booking system
Do not buy a chatbot. A normal chatbot answers questions. A good digital front desk does much more, and the real measure is how many additional bookings it brings in, not how many messages it answers. It should:
- Respond instantly, around the clock
- Understand natural language, not just fixed buttons
- Explain room types, tariffs, facilities and policies
- Check availability and give an accurate quotation
- Collect the guest's details
- Turn an enquiry into a booking request
- Follow up with guests who have not confirmed
- Hand complicated enquiries to a receptionist
- Keep a record of every enquiry and its outcome
The golden rule. Do not purchase on the number of features. Purchase on the number of hotel enquiries successfully converted into confirmed bookings.
What to insist on before you sign
Judge a product on functionality, ownership, recurring cost and exit conditions. Ignore impressive feature presentations. These twelve areas are non negotiable.
| Area | Non negotiable requirement |
|---|---|
| The official Meta WhatsApp Business API | |
| AI | Genuine understanding, not just fixed buttons |
| Languages | The languages your guests actually write in, including mixed language |
| Room information | Accurate room types, tariffs, policies and facilities |
| Availability | Live PMS or booking engine integration |
| Booking | A booking link and real booking confirmation |
| Follow up | Automated, configurable follow ups |
| Human support | A receptionist can take over instantly |
| Dashboard | Enquiries, lost leads and confirmed bookings |
| Ownership | The hotel owns its WhatsApp number, its account and its guest data |
| Portability | You can move to another provider |
| Support | Defined response and resolution times |
Important. Live availability and booking integration are separate acceptance tests. A chatbot that merely collects dates is not a booking automation system.
What a digital front desk does
Insist on seeing all four of these jobs demonstrated, not described.
Enquiry handling
- A guest asks, "Do you have rooms tomorrow?"
- The AI understands check in, check out and number of guests
- It asks only for what is missing
- It replies in the guest's language
Rooms and tariffs
- Standard, Deluxe, Suite and Family rooms
- Single, double and extra person tariffs
- Breakfast inclusion, taxes and extra charges
- Cancellation and child policies
Real booking capability
- Checks live inventory
- Quotes the correct tariff
- Sends a booking or payment link
- Captures guest information, and confirms only after the required confirmation or payment
Human handover
- Transfers VIP, corporate and group enquiries
- Escalates complaints
- Lets staff take over the conversation
- Gives staff the full history
Five events, not one
Some systems collect a guest's dates and announce a confirmed booking without ever talking to the property system. “Booking confirmed” can mean five different things. Ask the vendor which of these steps its system really performs.
- Enquiry captured. The guest's details are noted.
- Availability checked. The system asked the live inventory.
- Booking request created. A request exists for the hotel to act on.
- Payment received. Money has actually arrived.
- Booking confirmed. The booking exists in your PMS or booking engine.
The twelve traps
Each row is something a vendor may say, and what you should demand instead.
| Trap | What the vendor may say | What you must demand |
|---|---|---|
| 1. Annual lock-in | Pay annually and save 20%. | A monthly pilot and the right to cancel. |
| 2. Unlimited messages | Unlimited WhatsApp. | Written usage limits, and who pays Meta's charges. |
| 3. Unlimited AI | Unlimited AI conversations. | The AI credit or token limits, and the overage rates, in writing. |
| 4. Feature overload | Thirty AI features included. | Pay only for the features you will actually use. |
| 5. Fake integration | Integrated with your booking system. | A live demonstration on your own booking system. |
| 6. Fake booking | Booking automation. | The booking must appear in your PMS or booking engine. |
| 7. Language claims | Supports your regional language. | Test real conversations, including mixed language and voice notes. |
| 8. Hidden charges | All inclusive pricing. | A complete written cost schedule. |
| 9. Data hostage | We manage everything for you. | Accounts and data owned by the hotel, with an export. |
| 10. Weak support | 24/7 support. | A defined response time and a named escalation contact. |
| 11. Customisation trap | We can customise anything. | Written scope, price and delivery dates. |
| 12. Vendor dependency | Our own proprietary AI platform. | Migration rights and documented integrations. |
Five loopholes in depth
1. The annual subscription trap
A vendor offers one price for the year instead of a monthly price. You pay upfront. Then the AI does not work properly, the integration is incomplete, or support is poor.
- Start with a paid pilot of about 30 days
- Move to a monthly subscription for the next 60 days
- Pay annually only after proven performance
- Put data export, cancellation and refund terms in the contract
2. Feature overload
A vendor demonstrates Instagram automation, Facebook automation, a website chatbot, voice AI, lead generation, broadcast campaigns, a CRM and AI analytics. It looks impressive, but the receptionist still checks room availability and sends quotations by hand.
Do not pay for twenty features when your hotel needs five working perfectly.
3. Fake booking automation
Some systems collect a guest's dates and say, "Your booking is confirmed." They may never communicate with your property management system. Enquiry captured, availability checked, booking request created, payment received and booking confirmed are five different events, and a vendor must show you which of them its system really performs.
4. Who owns the WhatsApp number
Ask who owns and controls the WhatsApp Business account and number. Then check that:
- The hotel keeps ownership of its number and its Meta business account
- The hotel can access its own WhatsApp Business Platform account
- The vendor cannot hold conversations and guest information hostage
- You can migrate to another provider
- You can export your conversation and enquiry history
- The implementation uses the official WhatsApp Business Platform API, not an unofficial WhatsApp Web connection
5. Hidden recurring charges
Ask for a complete cost breakdown. A headline subscription price on its own is misleading.
- Platform subscription
- AI usage or credit charges
- Meta WhatsApp charges
- Additional agent seats
- PMS integration
- Booking engine integration
- Initial setup and training
- Maintenance and customisation
- Support
WhatsApp charges: a hidden cost
Do not accept an old WhatsApp pricing quotation. India's WhatsApp Business Platform rates changed on 1 October 2026. These were the published rates, before applicable taxes and provider fees. Meta can change them again, so ask for the current rates in any quote.
| Message category | India rate |
|---|---|
| Marketing | ₹0.8631 |
| Utility | ₹0.115 |
| Authentication | ₹0.115 |
| Service replies | First 1,000 a month free per number, then ₹0.115 |
Ask every vendor
- Are Meta's charges passed through at actual cost?
- Is there an additional markup?
- Who pays the Meta bill?
- Can I see message level usage reports?
- What happens when the free service message allowance runs out?
Never accept an unexplained, bundled WhatsApp charge.
The contract to ask for
Do not pay a full year before the AI has proven it can handle your actual enquiries. This is the arrangement worth asking for.
| Stage | Arrangement |
|---|---|
| Initial setup | A one time, agreed fee |
| First 30 days | A paid pilot |
| The following 60 days | A monthly subscription |
| After 90 days | The option to move to annual |
| Cancellation | 30 days notice |
| Data export | Available without penalty |
| Price increase | Prior written notice |
| Integration failure | The right to terminate |
Test your language, do not ask about it
Do not ask a vendor whether a language is supported. Test it. The AI should understand conversational language, spelling variations and code switching between English and a regional language. Also test voice notes, because many guests prefer speaking to typing. Ask the same kinds of questions in your own guests' language, mixing two languages in one message and misspelling a word on purpose. For example, in English:
- “Do you have a room available tomorrow?”
- “Is breakfast included?”
- “We are driving in from Mysore. Is early check-in possible?”
Then repeat each one in the regional language your guests use.
The demo test
Do not accept a prepared presentation. Give every vendor these ten scenarios, run them live, and tick each one the vendor passes.
| Passed | Scenario | What you should expect |
|---|---|---|
| A guest asks for a room tomorrow | The AI asks for the missing dates and number of guests. | |
| A guest asks for a tariff in a regional language | A natural reply in that language. | |
| A guest asks for 3 rooms for 8 people | The right occupancy and room split. | |
| A guest asks for a corporate tariff | Correct escalation to your team. | |
| A guest asks for early check-in | A policy based answer, with no false promise. | |
| A guest asks for a discount | Escalation, or only the discounts you approved. | |
| A guest stops responding | A polite follow up. | |
| A guest sends a voice note | The enquiry is understood correctly. | |
| You change a room tariff | The AI uses the new tariff straight away. | |
| Your booking system shows no rooms | The AI must never invent availability. |
0 of 10 passed.
Scorecard
Score each vendor out of 100, using only what you saw in the live demo. The maximum for each area is its weight.
| Area | Your score | Maximum |
|---|---|---|
| 25 | ||
| 20 | ||
| 20 | ||
| 10 | ||
| 10 | ||
| 10 | ||
| 5 | ||
| Total | 0 | 100 |
A rule to keep. If the system cannot reliably check live availability and produce the correct quotation, do not call it a hotel digital front desk.
Seven questions to ask before purchasing
Copy these into an email to any vendor and wait for written answers.
- Is your solution built on the official Meta WhatsApp Business API?
- Does it check live room availability in our booking system, or only answer predefined questions?
- Can it give an accurate quotation from room type, guests, dates, taxes and meal plan?
- Can it complete the booking and update our booking system, or does it only create an enquiry?
- Are our regional languages supported for natural conversation and voice notes?
- Please give a complete cost breakdown: subscription, AI usage, WhatsApp charges, integrations, setup, extra users and maintenance.
- Will the hotel keep ownership of its WhatsApp number, Meta account, guest data and conversation history, and be able to move to another provider?
Add this: we would like a 30 day live pilot with real hotel enquiries before committing to an annual subscription, and we want to see the complete journey from the first message to a confirmed booking, not a feature presentation.
What matters most, in order
- Accuracy. Does it give correct answers?
- Conversion. Does it turn enquiries into bookings?
- Integration. Does it connect to your actual room inventory?
- Ownership. Can you leave without losing your number and data?
- Economics. Is the total cost predictable as enquiry volume grows?
Everything else is secondary. If a vendor cannot demonstrate the journey from the first WhatsApp message to a confirmed booking in your system, do not sign an annual contract.
