The PMS Questions to Ask Before Any AI Purchase

Most hotel AI deployments that fail do not fail in the AI. They fail at the property management system - the assistant cannot see the reservation, cannot record what it did, or works at one property and not the next. These are the questions that find that out before the contract rather than after.

Why the PMS decides everything

The PMS is the system of record. Reservations, guest profiles, room status, folios - everything the assistant needs to know about a guest, and everything it might need to change.

An assistant that cannot read from the PMS answers from a copy of the information, and copies go stale. One that cannot write to it does work that nobody at the desk can see. The quality of the language model matters far less than the quality of this connection.

The questions

1. Which PMS platforms do you have live in production today? Not integrated. Not supported. Live, at a named property, handling real guests. A vendor should answer with a list. vGuest's, for the record: Optima, EzGo and MiniHotel in production, with two-way sync for Mews, Cloudbeds, Guesty and SimpleBooking. If your PMS is not on a vendor's production list, you are the pilot, and the pricing should reflect it.

2. Read-only or two-way? Read-only: the assistant sees reservation details and answers questions about them. Two-way: it also records the late check-out, updates the room preference, attaches the signed check-in form to the reservation. The first answers questions; the second does the front desk's work. Ask which, and do not accept full integration as an answer.

3. Which fields, specifically? Two-way with which fields. Can it write a note to the reservation? Update a guest profile field? Attach a document? Change a check-in status? The answer is a list, and the list is what you are buying.

4. What happens per property? Most PMS platforms are configured per property, not per installation. Storage paths, permissions, document directories are set up individually. An integration that works at one property may hit a missing directory or a different permission set at the next. Ask how the vendor handles per-property setup, and how long it took at the last property they onboarded on your PMS.

5. Who charges for the API connection? Some PMS vendors charge for API access, some per connected partner, some nothing. Some chatbot vendors bundle it, some pass it through. Ask both sides who invoices what. This is the most common surprise on the second month's bill.

6. What is the latency? When a guest asks whether their room is ready, how long between the question and an answer that reflects the PMS right now? Seconds is right. Minutes means a cache, and a cache means the answer can be wrong.

7. What does the assistant do when the PMS is down? It happens. The right answer is: it says so, honestly, and escalates. The wrong answer is: it answers from the last thing it saw.

8. Can we see it working on our PMS before signing? A pilot against your actual PMS instance with real reservations. A demo on the vendor's sandbox proves nothing about your configuration.

The per-property trap, in detail

Question four deserves its own paragraph, because it is the one that takes go-live dates.

The vendor's code is identical at every property. The PMS environment underneath is not. At one property the document directory exists; at the next, the same API call fails because a folder was never created on the PMS host. Same integration, different result, and it looks like a software bug to everyone watching.

The defence is to exercise every integration point against the new property with real data before the launch date. Particularly anything that writes a file - attachments, signed forms, uploaded IDs - because those depend on server-side setup nobody has looked at.

What a good answer sounds like

We run on your PMS at four properties today. Two-way: we write notes and check-in status to the reservation and attach documents to the guest card; we do not write to folios. Per-property setup takes about a week, mostly waiting on the PMS vendor to configure the connection, and they charge a one-off fee we will confirm in writing. If the PMS is unreachable the assistant tells the guest a person will confirm and escalates. Yes, we will run a pilot on your instance.

That is eight questions, one paragraph. A vendor who can say it has done this before. One who cannot is about to learn on your property.