A guest asks something ordinary, such as the parking rule or whether early check-in works, and the Hostaway AI draft gets it wrong or says it does not have the information. Your team ends up rewriting the replies you switched the feature on to avoid.
The question is usually not "is the AI bad". It is "what does it actually read, and what did I leave out". This guide answers that from Hostaway's own documentation, then covers what no reply setting can fix: facts that live in your team's routine, not in the booking. (Scheduled messages such as check-in instructions are a separate topic, covered in Hostaway automated messages.)
What Hostaway AI reads
Per Hostaway's help center, when a guest messages you the AI looks at four things: your rules, facts in the Knowledge Base, details about the reservation, and information about the listing.
The Context article is more specific. Reservation details include guest name, door code, check-in and check-out times, guest and pet counts, reservation status and payment status. Listing details include house rules, amenities, Wi-Fi credentials, key pickup instructions and cleaning status. Calendar availability and the full conversation are included too. You can see this yourself under Inbox > AI Replies > Context.
So a reply that "answers from the reservation" is something Hostaway supports. When a reply is wrong or incomplete, start with the checks below.
Six checks for wrong or incomplete replies
1. Read the Context panel first. If a field you assumed was there is empty (a door code, a pet policy), no rule will compensate. Fix the source field in Hostaway.
2. Put missing facts in the Knowledge Base. Hostaway says the AI tells you which data is missing when it cannot draft a reply, and that you can add it as a fact. Facts can also come from uploaded PDFs and from messages you send, per the Knowledge Base article. Sort the listings table by Last updated, then open a listing to review the facts the AI added.
3. Write one rule per topic. The best-practices article is blunt about this: one rule, one scenario. Split "if available, say X, otherwise say Y" into two rules. Keep tone, language and sign-off in the General tab, not in rules, because tone rules match nearly every message and interfere with the Draft and Auto-Reply logic.
4. Test before you automate. The Test AI panel lets you pick a listing and a specific reservation and send questions as a guest, such as "Can we check in early?" (Test Replies and Set Delays). Check accuracy, policy and escalation, not only tone. Hostaway's suggested test questions are a good starting set: check-in time, early check-in, parking, Wi-Fi, late checkout and pets. Run each against a real upcoming reservation, not only a listing, so the reply uses live reservation context. One more behavior to know before you judge the results: Hostaway does not generate replies to messages received before you enabled the feature, or when the latest message is not from the guest. An existing conversation can still get an AI reply when a new guest message arrives.
5. Choose the delivery mode per topic. Hostaway recommends Draft mode for complex or sensitive questions and Auto-Reply for predictable ones like check-in instructions, Wi-Fi and parking. Delay settings let your team answer first, with the AI stepping in after hours.
6. Set escalation rules. Hostaway can flag negative sentiment and lets you define your own escalation triggers (no hot water is one of its examples), with a notification per rule (Escalations).
Where the context stops
Hostaway documents two limits that matter to a growing operation.
First, the AI's context is limited to one reservation and its listing. Questions that depend on another unit or another booking are out of reach.
Second, rules are reactive. Per the same article, they answer guest messages; scheduled or proactive messages belong to Automations. And per the Common Questions article, AI responses are only created for new incoming messages where the last message is from the guest.
Neither is a flaw in Hostaway. A PMS is built around the reservation. The harder questions at 10 or 30 units are about what happens after the booking.
An illustrative example
This scenario is illustrative, not a customer story. A guest writes at 9 a.m. on arrival day: "Is the cabin ready for an early check-in?"
The booking says check-in is at 4 p.m. Whether the cabin can be ready by noon depends on whether the cleaner has started, whether a late checkout is next door, and whether a maintenance item is open. Check whether the relevant status is available and current in Hostaway's Context panel, which lists cleaning status among the listing details. If the facts needed to approve an early arrival are missing or stale, have the team confirm readiness before promising a time, and hand the decision to a person when the situation is unusual.
Where InnSync fits
InnSync is the operations layer around your PMS. Carmen, InnSync's AI agent, answers from the booking, the unit and your house rules, and brings in your team when a conversation needs a person. InnSync also supports cleaning, check-in and exception routines around each reservation. You decide, per channel, whether she replies on her own or drafts for review.
If your Hostaway replies are mostly right and your gaps are in the work around the stay, that is the layer to add. If they are wrong on basic facts, work through the six checks above first.
If you use Hostaway
Keep Hostaway. InnSync runs the operation around it — the connection is set up with you during onboarding.
See InnSync for Hostaway.