How to Build a Vacation Rental Knowledge Base That Handles 80% of Guest Questions (2026)

Why Most Vacation Rental Knowledge Bases Don't Work

Most STR operators have some version of a knowledge base. It's usually a PDF house manual, a Notion doc, or a collection of saved canned responses in their inbox. When a guest asks a question, someone finds the right reply, copies it, pastes it, and sends it. That's not a knowledge base — that's a filing cabinet.

The problem isn't effort. It's structure. A KB that a human uses to find-and-paste is completely different from a KB that AI uses to generate accurate, contextual responses. The difference comes down to three things:

• Specificity: "The WiFi password is in the welcome book" doesn't help. "WiFi network: Beachhouse5G, password: Sunset2026!" helps immediately.
• Completeness: Most house manuals cover check-in and WiFi. They miss parking edge cases, early check-in policies, appliance instructions, pet rules, and the 12 other things guests ask every week.
• Structure: A PDF is designed for sequential reading. AI needs discrete, searchable entries — one question, one answer, no ambiguity.

Fix those three things and your KB goes from a document guests ignore to a system that handles 80% of your incoming messages without you.

The 20 Questions That Cover 80% of What Guests Ask

Across thousands of STR guest conversations, the same questions appear again and again. If your KB answers these 20, you'll have covered the vast majority of what lands in your inbox:

1. What is the WiFi network name and password?
2. What time is check-in? Can I check in early?
3. What time is checkout? Can I check out late?
4. How do I get in? (door code, lockbox, key location)
5. Where do I park?
6. Is the property pet-friendly?
7. How do I use the TV / streaming services?
8. How do I use the washing machine / dryer?
9. Is there a coffee machine? How does it work?
10. What should I do with rubbish / recycling?
11. Are there extra towels / bedding?
12. Can I have visitors / guests who aren't staying?
13. Is there air conditioning / heating? How do I adjust it?
14. What's the nearest supermarket?
15. Is there a BBQ / outdoor area? How does it work?
16. What do I do if I lose the key or get locked out?
17. What happens if something breaks or stops working?
18. Is smoking allowed?
19. Are there noise restrictions / quiet hours?
20. What do I do at checkout? Do I need to strip the beds?

Notice that most of these are logistics and access questions — not questions about your area, your story, or your philosophy. Guests want to know how to get in, how to use the property, and how to leave. That's where your KB should start.

How to Write a KB Entry That AI Can Actually Use

Most house manual entries are written for human readers who will skim and infer. AI needs entries that are unambiguous and self-contained. Here's the difference in practice:

WiFi — The Wrong Way

"WiFi details are on the card on the kitchen counter. The network is the same one as last time if you've been before."

This is useless to an AI. There's no network name, no password, no fallback if the card isn't visible. A guest asking for WiFi details at 11pm gets nothing useful.

WiFi — The Right Way

"WiFi network: SeashoreHouse_5G. Password: Sandcastle2026. If you can't connect, try the 2.4GHz network: SeashoreHouse_2.4, same password. The router is in the hallway cupboard and can be rebooted by unplugging and re-plugging the power cable."

That entry answers the question, handles the most common failure mode, and tells the guest exactly what to do without involving you.

The structure that works

Each entry should follow this pattern:

• The answer first — specific, concrete, no hedging
• The most common follow-up — anticipate the next question ("what if it doesn't work?")
• A contact escalation — for anything the KB can't resolve

Entries should be under 150 words. If an entry needs more than 150 words, it's probably two entries.

Building Your KB in Hostaway

Hostaway gives you two native tools for building a knowledge base: the House Manual and Canned Responses. Each serves a different purpose.

The House Manual

Hostaway's house manual is the foundation. It's sent to guests before arrival and covers the information they need before they arrive or as they settle in. Build it around the 20-question list above. Use clear section headers (Access, WiFi, Appliances, Parking, Rules) so guests — and AI tools — can navigate it quickly.

The house manual is a broadcast document: it goes out once and isn't personalised to the conversation. It's the starting point, not the complete system.

Canned Responses

Hostaway's canned responses let you save templated replies for common questions. They're more granular than the house manual and can be pulled up in the unified inbox when a guest asks something specific. Build canned responses for the questions that come up most — early check-in, late checkout, parking, pet policies — and make them your human team's starting point when they do touch the inbox.

Where Hostaway's built-in tools stop

Hostaway's house manual and canned responses are excellent for planned communication. They don't answer live guest questions automatically. If a guest messages at 2am asking for the door code because they've lost the welcome email, Hostaway's automation won't respond — you will, or someone on your team will, or the guest waits until morning.

That's the gap AI guest messaging fills: real-time responses to live guest questions, drawn from a KB that knows your specific property.

How AI Uses Your Knowledge Base to Answer Guest Questions

When a guest sends a message, an AI like Guestar doesn't search the internet or make up an answer. It searches your KB. This approach — called retrieval-augmented generation, or RAG — means every response is grounded in what you've told the AI about your property. It won't hallucinate a door code, invent a parking space, or offer an early check-in you can't provide.

Teachable KB: the AI gets smarter the more you tell it

Guestar's KB works as a set of discrete entries — each one covering a specific question, policy, or piece of property information. You build it once and maintain it over time. The AI draws from those entries when it constructs a response, combining the relevant information into a natural, on-brand message that matches your property's tone.

If a guest asks something your KB doesn't cover, Guestar flags it as a low-confidence event and escalates to you. That escalation is also a signal: a question that comes up twice or three times is a KB gap worth filling.

Calendar-aware responses

One of the most common early check-in KB problems: the KB says "early check-in is available for $30" but the AI doesn't know whether the previous booking has checked out yet. Without calendar awareness, the AI either refuses all early check-in requests to avoid overpromising or agrees to requests it shouldn't.

Guestar connects directly to your Hostaway calendar. When a guest asks about early check-in, the AI checks real-time availability before responding — so it only offers early check-in when it's genuinely possible, and declines accurately when there's a back-to-back booking. The KB sets the policy; the calendar sets the availability.

Keeping Your Knowledge Base Current

A KB built once and never updated becomes stale within months. Door codes change. Appliances get replaced. Parking rules change with new neighbours. Prices get updated. If your KB says the gate code is 1234 and you changed it to 5678 in March, the AI will confidently give guests the wrong code.

Build a simple update habit:

• After any property change — update the affected entry the same day. This takes 5 minutes and prevents weeks of incorrect responses.
• Weekly review of escalations — every question your AI escalated is either a KB gap or a KB inaccuracy. Review them once a week and update accordingly.
• Seasonal review — once per quarter, go through your full KB and check that the information is still accurate. Pool rules change in winter. Heating instructions matter in autumn. Local recommendations go stale.

With Guestar, low-confidence events are surfaced automatically — so you don't have to guess where the gaps are. Every question the AI wasn't confident answering is a data point about what to add next.

How Many KB Entries Do You Need?

For a single property, 30–50 well-written entries covers the overwhelming majority of guest questions. For a portfolio, you'll have a mix: a shared KB with entries that apply across all properties (house rules, noise policy, pet policy) and property-specific entries for access codes, appliance instructions, parking, and local information.

Don't try to build the complete KB on day one. Start with the 20 core questions above and add new entries as questions come in. After 30 days of live operation, most operators find they've covered 85–90% of their actual message volume with fewer than 40 entries.

The goal isn't comprehensiveness for its own sake — it's hitting the point where your AI handles the bulk of incoming messages without escalation, and you're only touching the edge cases that genuinely need a human.

FAQ

What should I include in a vacation rental knowledge base?

Start with the 20 questions guests ask most: WiFi credentials, check-in/checkout times, door access instructions, parking, appliance instructions (TV, washing machine, coffee machine), house rules (pets, smoking, noise, visitors), what to do at checkout, and emergency contacts. Once you have those, add property-specific details — appliance models, bin collection days, nearby supermarkets, local recommendations. A KB of 30–50 entries covers 80% of what guests ask.

How is a vacation rental KB different from a house manual?

A house manual is a document designed for human readers — guests read it once before arrival. A knowledge base is a structured set of discrete entries designed for systems (AI, canned response tools) to query against live questions. The content overlaps significantly, but the KB needs to be more granular, more specific, and structured so each entry can stand alone as a self-contained answer.

Can Hostaway's canned responses replace a proper KB?

Canned responses are a good start for your human team. They don't respond automatically to live guest questions — someone still has to be there to select and send them. For automated, real-time responses to guest messages across all channels, 24/7, you need a tool like Guestar that draws from your KB and responds without manual involvement.

What happens when a guest asks something not in the KB?

With Guestar, any question the AI can't answer with high confidence triggers an escalation — you get notified and can respond directly. The escalation is also logged as a potential KB gap. Over time, those escalations are your clearest signal about what to add to the KB next. A well-maintained KB reduces escalations progressively — most operators see them drop by 60–70% in the first 60 days.

How long does it take to build a vacation rental knowledge base?

For a single property, a first-draft KB covering the 20 core questions takes 2–3 hours. Most of that time is thinking through the answers and making them specific enough to be useful — not the writing itself. Portfolio operators building a shared KB across multiple properties typically spend a morning on it, then add property-specific entries for each unit. After that, maintenance is ongoing but light: 10–15 minutes per week reviewing escalations and updating any entries that have changed.