The difference between a voice agent that earns money and one that merely answers the phone comes down to one thing: whether it can write to your PMS or only read from it. Everything else — the voice, the languages, the script — is secondary to that.
Reading is not writing
This is the distinction that decides the project's return, and the one most blurred in sales presentations.
An agent that reads can check availability and tell the guest rooms are left. An agent that writes closes the booking in the system, with its rate, its board and its confirmation, without anyone keying it in afterwards.
If it only reads, you have automated the informational half and left the administrative half untouched: somebody at the front desk still enters bookings by hand at the end of the shift, with the duplication and overbooking risk that carries.
The four capabilities to demand
1. Live availability
Not a copy synced every fifteen minutes. In a hotel running high occupancy, fifteen minutes is enough to sell the same room twice.
The concrete question: does it query the PMS at the moment of the call, or query a cache?
2. Booking creation
The booking should land in the PMS like any other, with the guest's details, the right rate and the same confirmation flow.
The warning sign is any variant of "it raises a task for reception to enter it". That is not integration, it's a voice-operated form.
3. Respecting rates and restrictions
Minimum stays, stop-sells, channel rates, supplements. If the agent doesn't read those rules, it will sell things it shouldn't at prices that don't apply.
This is where most projects stall, because it requires the rules to be loaded correctly in the PMS in the first place.
4. Changes and cancellations
A good share of a hotel's phone volume isn't new bookings: it's changes. An agent that can only create solves half the problem and leaves the other half at the front desk.
How the connection actually works
There are three routes, and it pays to know which one you're being offered.
Against the PMS API. The clean route: the agent talks directly to your management system. It requires the PMS to expose a booking API and your contract to include it, which is not always the case.
Against the channel manager. Useful when the PMS has no open API but the channel manager does. It works well for availability and rates, less well for guest-profile detail.
Through a middle layer. The vendor maintains its own connector. This is the norm with the larger systems, and the question to ask here is who maintains that connector when the PMS ships a new version.
Bookline's AI agent connects natively to the main systems on the market — Mews, Opera, Cloudbeds, SiteMinder, Beds24 and others; the current list is on integrations.
What changes depending on your system
The PMS name matters less than its specific configuration at your hotel, and this surprises a lot of people.
Two hotels on the same Opera can have different access levels, different modules contracted and rate structures that aren't comparable. That is why no serious vendor can promise you a timeline without having looked at your installation.
What does depend on the system is how access is requested: in some cases you enable it from your own panel, in others a request goes to the manufacturer and you wait. That paperwork, not the technical work, is usually what sets the start date.
What happens when the PMS doesn't respond
It's the question almost nobody asks and the one you notice at 8 p.m. on a Tuesday in August.
A well-built agent degrades gracefully: if the PMS doesn't answer, it keeps handling the call, says what it knows, takes the guest's details and flags the front desk to close it once the system is back. What it must not do is hang up, or promise a booking it couldn't create.
Ask vendors to walk you through that specific scenario. The answer says a lot about product maturity.
Seven questions for your PMS vendor
Before you talk to anyone else, these are the ones to settle with whoever supplies your PMS:
1. Do you expose a booking API, and is it included in my contract or billed separately?
2. Does it allow create, change and cancel, or only read?
3. Does it return live availability?
4. Does it expose sales restrictions and channel rates?
5. Is there a rate limit per minute or per day?
6. What is the process to authorise a third party, and how long does it take?
7. How do you notify breaking changes to the integration?
With those seven answers in writing, every later conversation with a voice vendor takes half as long.
Frequently asked questions
What if my PMS has no API?
Then the agent can take calls, inform and collect details, but not close bookings on its own. It still has value — it handles the repetitive questions and stops losing calls — but go in knowing half the return is missing.
How long does an integration take?
The connection work is usually short when the connector already exists. What stretches timelines is authorisation from the PMS manufacturer and cleaning up rates and rules in your installation.
Can it coexist with my booking engine?
Yes, and that's the norm: the engine covers the web channel and the agent the phone. Both write to the same PMS, which is what prevents mismatches. If the direct channel is your priority, why direct bookings get lost is worth reading.
The next step
Get those seven answers from your PMS vendor before comparing agents. It changes the conversation entirely: you stop listening to promises and start checking capabilities.
If you want to see what an agent does once connected, that's on voice agent, and the wider picture in AI voice agents for hotels.
