9 Knowledge Base Entries Your STR AI Is Missing (And How to Add Them This Week)

Your AI Can Only Answer What You've Told It

If your AI guest messaging tool is still routing questions to you that feel like they should be automatic, the knowledge base is almost always where to look first. The AI isn't broken — it's doing exactly what it's supposed to do when it hits a gap: escalating rather than guessing.

That distinction matters. A well-configured AI that escalates an unanswered question is behaving correctly. The problem is that most of those escalations are questions with fixed, definite answers. They just haven't been written into the knowledge base yet.

One STR operator on r/ShortTermRentals described the pattern exactly: "The number one message I used to get after 9pm on check-in day was some version of 'where do I park?' or 'what's the WiFi password?' — stuff that was already in the listing, already in the message I sent earlier."

The gap isn't in the listing. It's in what the AI is reading from. Guests who message at 9pm aren't ignoring what you sent — they're tired, in transit, and reaching for the fastest channel. The question lands in your inbox instead of being resolved by the AI because the knowledge base doesn't have the entry for it.

Analysis of STR guest messaging patterns shows up to 37% of all messages are check-in day questions. Most of those have answers that don't change between guests. Every one of those messages is an AI resolution waiting for a KB entry.

What the Data Shows: 56 Escalations, 23 Properties, One Week

Guestar's weekly KB gap analysis reviews AI responses where confidence fell below threshold — messages the AI handled partially or escalated rather than resolving. In the week ending May 18, 2026, 23 active properties generated 56 low-confidence entries. The breakdown by category:

Gap Category	Asks This Week	Properties Affected	Priority
Early check-in / luggage storage	11	8	HIGH
Maintenance failures (WiFi, power, water, drainage)	9	5	HIGH
Door access code / lockbox entry	4	3	HIGH
Transportation / scooter rental	5	3	MEDIUM
Staff schedule / check-in handoff	3	2	MEDIUM
Breakfast / private catering	3	2	MEDIUM
Laundry / housekeeping schedule	3	1	MEDIUM
Security deposit policy	2	1	MEDIUM
Arrival directions / navigation	1	1	HIGH (critical)

None of these are ambiguous questions. Each has a specific, repeatable answer. They're escalating because the AI hasn't been told what that answer is — not because they're outside what AI can handle.

The concentration is notable: the top three gaps account for 43% of all low-confidence responses that week. Close those three and escalations drop significantly across the full portfolio. The remaining six are each quick fixes that pay dividends for every future guest who asks.

9 KB Entries to Add This Week

1. Early Check-In Policy — With Fee, Hours, and Luggage Drop-Off

11 asks in one week across 8 properties. This is the most common unanswered question in STR guest messaging — and the one with the most revenue upside if you handle it right.

A host on r/AirBnB who tracked the pattern found 75% of guests ask about early check-in at some point before their stay. Facebook community data puts it at 20–25% of bookings with an explicit pre-arrival request. Every one of those guests is waiting for an answer the AI can give in under two minutes — if the policy is in the knowledge base.

The reason this gap is so common: most operators have a mental policy but haven't written it in a form the AI can use. "Early check-in is $35 if available" exists as an informal rule — but the KB entry needs the full picture: what counts as early, how availability is determined, whether luggage can be dropped before the room is ready, and the payment instruction.

What to add to your KB:

• Standard check-in time and the earliest window you offer (e.g., "standard check-in is 3pm; early check-in from 11am if available")
• Early check-in fee and how it's confirmed (e.g., "$35 per 3-hour block; availability checked against the calendar before offering")
• Luggage drop-off procedure if the room isn't ready (e.g., "luggage can be stored from 9am in the storage room — code is [X]")
• What to offer when early check-in isn't available — a late checkout offer on departure day, or a specific time the room will be ready

With a Hostaway or Hostify integration, Guestar checks your live calendar before making any early check-in offer — confirming the prior guest has departed and cleaning is scheduled before triggering the upsell. It doesn't just answer the question; it verifies availability in real time. Early check-in and late checkout upsells average $157 per guest when offered proactively. For the full mechanics, see how to automate early check-in upsells in Hostaway.

2. Maintenance Emergency Contacts and Step-by-Step Triage

9 asks in one week. Maintenance questions are different from logistics questions: guests aren't looking for information, they need something actionable right now. WiFi drops. Hot water fails. Power cuts out. Drainage slows. These are urgent — and guests who don't get a useful immediate response post to the booking platform and the review clock starts.

Most KBs have a maintenance phone number. That's not enough. The AI needs enough context to give guests a first-step triage — both to reduce unnecessary call-outs and to show immediate responsiveness while the fix is arranged.

What to add per property:

• Emergency maintenance contact: name, number, and when they're reachable
• WiFi reset: router location, restart steps, alternate password if the primary fails
• Hot water: boiler or water heater location, reset switch, typical recovery time
• Power outage: breaker box location, which breakers cover which areas
• Drainage: which drains are most likely to need the strainer cleared, who to call if it doesn't resolve
• Pool or outdoor equipment: who manages it, normal maintenance schedule, what's expected vs. urgent

Each entry is one to two sentences per issue type. The AI gives the guest something concrete to try while escalating to maintenance — better guest experience and fewer unnecessary call-outs in the same response.

3. Door Access Code and Lockbox Backup Procedure

4 asks, 3 properties. Access code questions cluster on check-in day, which is exactly when the host is hardest to reach. A guest standing outside at 6pm unsure which code works for which door is a 1-star review developing in real time.

The fix is straightforward: the code goes in the KB, resent 24 hours before arrival via automated pre-arrival message, and the AI confirms it on demand. What most operators miss is the backup: what happens when the lockbox fails or the code doesn't work. That second layer is what turns a potential emergency into a handled situation.

What to add:

• Primary entry code
• Codes for secondary areas: pool gate, storage room, parking, elevator if applicable
• Lockbox physical location — be specific: "the grey lockbox mounted on the left post of the front gate, not the main door"
• Backup contact for lockbox failures — ideally someone local who can respond within 20 minutes
• Lockbox operation steps if the model is unfamiliar to guests (some electronic lockboxes have non-obvious reset sequences)

4. Transportation: Scooter Rental, Taxi Apps, and Pickup Coordination

5 asks, 3 properties. This gap is most acute in markets where public transport is limited and guests depend on local recommendations. Scooter rental, airport transfers, and ride apps are high-frequency questions with fixed, per-market answers.

What to add:

• Preferred scooter or car rental vendor with a booking link or contact and a price range
• Best local taxi or ride app, including any search tip for finding the property (e.g., "Grab works well here; search for [Landmark Name] rather than the street address")
• Airport transfer contact if you have a preferred provider
• Any specific pickup coordination: "message the driver 15 minutes before arrival; gate code is the same as the property"

5. Staff Schedule and Check-In Handoff Window

3 asks, 2 properties. Guests arriving without knowing whether anyone will be on site is an anxiety source that generates messages. Even if check-in is fully self-service, the question "is someone there?" is a trust question as much as a logistical one — and the AI can answer it definitively if the KB has the information.

What to add:

• Whether staff is on-site during check-in or if it's self-service
• If staff is present: hours and contact method for the day
• If self-service: reassurance language and what the guest should do if something is wrong at arrival
• The villa manager or property contact name for the stay

6. Breakfast, Private Chef, and In-Property Catering

3 asks, 2 properties. For staffed properties or markets where private catering is common, guests ask about breakfast and cooking options before arrival. "Not available" is a perfectly valid KB entry — the AI just needs to know it so it can answer confidently rather than escalating.

What to add:

• Whether breakfast is offered and if so, the format (e.g., "continental breakfast available 8–10am at $12/person — message us to arrange")
• Private chef or cook availability, pricing, and how to book
• Nearest grocery store or market for self-catering guests
• If nothing is available: "No in-property catering — the nearest restaurant is [Name] at [X] minutes walking"

7. Laundry, Housekeeping Schedule, and Mid-Stay Cleaning

3 asks, 1 property — but relevant for any stay over five nights. Guests on longer bookings need to know how laundry works and whether mid-stay cleaning is included. Without KB entries, these questions reach you every time instead of being handled once in the setup.

What to add:

• In-unit laundry: machine location, instructions — especially for non-standard settings or non-English labelling
• Laundry service: pricing per bag or kg, collection process and turnaround
• Mid-stay cleaning: included or optional, how to request, cost if applicable
• Towel and linen change schedule if different from on-demand

8. Security Deposit: Amount, Payment Method, and Refund Timeline

2 asks from a single property, but security deposit questions generate disproportionate anxiety when unanswered. Guests with unresolved deposit concerns message with urgency — and the overlap with the review period makes timing critical.

What to add:

• Deposit amount
• Payment method: card pre-auth, bank transfer, cash — whichever applies
• When the deposit is collected and when it's returned
• Refund timeline: "returned within 5 business days of checkout, subject to property inspection"
• What circumstances could affect the return amount

9. Arrival Directions: Landmark-Based, App-Friendly, With a Backup

Only 1 ask this week, but flagged as critical — because an address-only entry fails in markets where street addressing is inconsistent or doesn't match GPS databases. One guest arriving at the wrong location is a bad check-in experience and a 1-star review potential at the worst possible moment. This entry is short to write and high-stakes to have.

What to add:

• Google Maps pin URL — share the exact pinned location, not just the street address
• Landmark-based directions: "turn left at [visible landmark], look for the green gate"
• Ride app search tip if address lookup is unreliable: "Tell the driver to head for [Nearest Known Landmark] and ask for the property with the [identifying feature]"
• On-arrival instructions: ring bell, call the manager, enter via the side gate — whatever applies

What Changes When You Close These Gaps

For each gap closed, that question category shifts from near-zero AI resolution to 90%+. The AI can't infer an access code. It won't fabricate a maintenance procedure. But once that information exists in the knowledge base, the same question — asked by any guest at any hour — gets resolved without routing to you.

The compounding math: if the 9 gaps above generated 56 escalations in one week, closing them reduces that to roughly 8–12 — the genuinely ambiguous situations that require human judgement. That's 44–48 fewer messages per week across the portfolio. At 5 minutes per manually handled message, that's 3–4 hours recovered per week, permanently, with no recurring effort.

The early check-in entry is different in character from the rest. Closing it doesn't just eliminate an escalation — it creates a revenue opportunity. A guest who asks about early check-in and receives an instant, availability-verified response with a payment link converts at a far higher rate than one waiting for a manual reply. Early check-in upsells run $30–$50 per stay in most markets; late checkout adds another $30–$50. One upsell per property per month covers Guestar's cost entirely. For operators managing 10+ properties, this becomes a revenue line that didn't exist before. See the full STR upsell revenue playbook for the broader picture.

The Guestar knowledge base accepts free-form text, PDFs, and URLs. Each of the 9 entries above takes 3–10 minutes to write per property. For a five-property portfolio, the full update is a 45-minute one-time task. The AI reads from the updated KB on the next incoming message — no retraining, no delay. If you're setting up a KB for the first time rather than filling gaps, see how to build a vacation rental knowledge base from scratch. For a complete picture of what your AI is already handling well, see the 15 questions Hostaway guests ask most.

Frequently Asked Questions

Why is my vacation rental AI still escalating messages even after setup?

Almost always, it's a knowledge base gap. AI guest messaging tools escalate when they can't answer from available information — not because the question is complex. The most common causes are missing early check-in policy, no maintenance triage steps, access codes absent from the KB, and local logistics (transport, catering, directions) that vary by property. These gaps don't fix themselves as the AI learns — they require a deliberate KB update. Identifying which questions keep reaching you manually and adding those entries first is the highest-ROI optimization available.

What should I include in my vacation rental AI knowledge base?

Start with the highest-frequency questions: check-in procedure and timing, access codes and lockbox location, WiFi credentials, early check-in policy with fee and availability logic, emergency maintenance contacts with triage steps, late checkout availability, parking and transport options, and house rules. Once those are solid, layer in property-specific detail: appliance instructions, pool or hot tub operation, laundry, recommended restaurants and services. The goal is to answer everything a well-briefed on-site manager would know on their first day — without requiring that person to be available at 2am.

How does AI handle early check-in requests automatically?

The AI needs three things in the KB: your standard check-in time, your early check-in policy including fee and earliest availability window, and what to offer when early check-in isn't possible. With a live Hostaway or Hostify integration, Guestar checks your real calendar before making any offer — confirming the prior guest has departed and cleaning is scheduled — so early check-in is only offered when it's actually available. This turns the most common STR guest question into an automated, revenue-generating conversation rather than a manual interruption.

How often should I update my vacation rental knowledge base?

A few times a year for stable properties — or immediately when a recurring guest question reveals a gap. The practical trigger: if you've answered the same question from two different guests in the past month, it belongs in the KB. Seasonal updates matter too: pool heating availability, transport options, and early check-in pricing often shift with season or occupancy levels. Tools like Guestar surface these gaps automatically each week ranked by frequency, so you're not hunting for them manually after the fact.

What's the difference between a vacation rental knowledge base and a house manual?

A house manual is written for guests to read — typically a PDF or printed document covering house rules, appliance instructions, and checkout procedures. A knowledge base is the source the AI reads from to answer questions in real time. They overlap in content, but the KB needs to be structured for retrieval — individual entries per topic, not a single long document. Most operators start by converting their house manual into KB entries, then add the dynamic pieces (early check-in policy, staff availability, local pricing) that wouldn't belong in a printed binder. The entries don't need to be long — a two-sentence lockbox procedure is better than no entry.