Doesn't my PMS already do this?

If "this" means sending the check-in email and the checkout reminder, yes — your PMS already does it, and does it well. If "this" means answering the guest who writes back, no. A property management system automates the messages you wrote in advance and send on a schedule. It does not answer questions, and questions are most of what lands in your inbox. A New Orleans host told us this week: "I use a PMS for all of my hosting needs." That is a reasonable thing to believe, and worth taking apart, because the gap it hides is where a host's evenings go.

What a PMS actually automates

The PMS is the system of record, and a good one earns its fee. It syncs calendars across Airbnb, Vrbo, and Booking.com so you never get a double booking. It moves money: payouts, cleaning fees, taxes, owner statements. And it sends triggered messages — booking confirmed, check-in instructions three days out, door code the morning of, checkout reminder, review ask. Those are messages you composed once, fired by dates. Nothing in this post argues against any of it. Keep your PMS.

The messages a PMS cannot send

Templates fire on your schedule. Guests write on theirs. "Where does the second car go?" "The wifi password isn't working." "Can we check in at noon?" "Is the pool heated in March?" "The door code says invalid." No trigger predicts these, so the PMS does the only thing it can: it delivers them to your phone. The automation ends exactly where the conversation starts. That is not a flaw in the PMS — answering was never its job. Its messaging module is a mail merge, not a co-host.

There is a simple test. Open your guest thread from the last stay and sort the messages into two piles: sent by an automation, and typed by you (or answered with your thumbs at some inconvenient hour). The first pile is the PMS doing its job. The second pile is the job it left you — and the second pile is the one that arrives at 11pm, mid-dinner, or while your other listing is also mid-check-in.

Different layer, not a rival

StayPilot sits on top of the PMS, not in place of it. The PMS keeps doing bookings, calendars, and money. StayPilot reads each property's actual details — wifi, parking, house rules, the quirk with the side gate — and answers the unscripted pile in under a minute, day or night. Hostaway connects directly today, picking up guest messages from Airbnb, Vrbo, and Booking.com through it; hosts on Guesty, OwnerRez, and others run StayPilot alongside while direct connections are in progress. The works-with page keeps the current list.

The same boundary holds for judgment. Refunds, complaints, and anything touching safety always go to you — the AI answers routine questions and flags the sensitive ones, with every message logged. And the operational follow-through a template can't do — issuing a fresh door code when one fails, scheduling the cleaner and lining up a backup when they cancel, booking a plumber under your spending limit — is handled as an action, not a reply.

"All of my hosting needs" is two jobs

The confusion is baked into the category name: a property management system does not manage guests, it manages properties — inventory, dates, money. Guests are managed in conversation, and conversation is the one thing that never fit in a template. That is why running both layers is becoming the normal stack, the same way a PMS plus a pricing tool already is: one system books the stay, another prices it, and a co-host — human or AI — talks to the person actually staying. If your listings are quiet and questions are rare, your PMS plus your phone genuinely may be all you need. The hosts who feel the gap are the ones whose second pile is growing.

The honest way to check whether the second layer is worth it is to watch it answer for your listing, not take our word. Paste your listing into the demo and ask it the questions your PMS forwards to your phone — the parking one, the early check-in one, the wifi one. If the answers sound like you on a good day, that is the pile handled. Your PMS never has to know.