GuestsUpdated 11/15/2026

AI guest chat: one assistant across every site, guest portal, and domain

Every Haven site ships with a guest AI assistant. It is one assistant, everywhere you host — your property sites, your group site, every guest portal, and your custom domains — and it answers from the specific listing the guest is looking at, not from a blanket prompt you have to maintain.

Unlike fire-and-forget chatbots, Haven's assistant is a full-cycle tool: it grades its own replies, tells you where it fell short and why, and lets you fix a gap once for one site or all of them. That observability and self-healing loop is covered in Chat insights: observability & self-healing. This article covers what the assistant knows, how it keeps private information private, and how you teach it.

Where guests can chat

SurfaceWho can use itWhat it can answer
Property site (incl. custom domain)Anyone visiting your siteWhat the site itself shows: amenities, sleeping arrangements, house rules, cancellation policy, booking rules, location and local area, the reviews and FAQs the site displays, your public AI knowledge, and the site's pages. It checks dates, quotes the exact stay total, finds open dates, and shows a bookable card for the stay.
Group siteAnyone visiting your group siteEverything above across every home the site lists ("6 guests next weekend, which homes are open?"): it searches the dates across all homes, compares them, and shows a card for each open one, plus group-site-level knowledge.
Guest PortalGuests who pass the guest portal's access gateEverything above plus private stay details, exactly when the guest portal in front of the guest shows them: check-in and checkout specifics, door and lockbox codes, Wi‑Fi, emergency and maintenance contacts, during-stay notes, what the guest told you in guest forms, and private AI knowledge.
OTA booking threads (optional)Guests who booked on Airbnb, Vrbo or Booking.comThe same answers, written into the guest's booking thread through your PMS. Off until you turn it on, and arrival details follow the same reveal window. See AI replies to OTA guests.

The same assistant powers all of them; only the knowledge it is allowed to use changes.

Booking from the site chat

On your property site and group site, the assistant books like your own date search does. Ask it "is The Clementine free Dec 12–15 for 4?" or "what's open next weekend for 6 with a dog?" and it:

  1. Asks for the dates and the number of guests when the guest has not given them. It never assumes a party size.
  2. Checks availability with the same rules as your booking panel: minimum and maximum stay, booking window, check-in and check-out days, guest and pet limits.
  3. Shows a card for each open home with its photo, sleeps and bedrooms, and the price your booking panel would charge. The price is the stay total, or nights × the average rate when your site shows nightly prices, with "before taxes" or "50% due now" when those apply. A single-home quote expands to its line items.
  4. Offers close alternatives when the dates do not work: nearby open dates, or another home that fits.

Book these dates opens the home's page on the domain the guest is on, with the dates, guests and pets filled in and the booking panel open. View home opens the page without the panel. Every link the chat writes stays on your site: your custom domain when the guest is on it, and only pages the site actually shows.

When dates are not available, the guest hears only the public reason (not available, minimum stay, too many guests, no pets, outside the booking window). The chat never says whether the nights are taken by a booking, a hold or an owner block.

The cards a guest was shown appear in Messages under that reply, as an "Offered" line with each home and its total, so you can see what they were quoted.

Public vs. private — handled for you

Every piece of listing content Haven feeds the assistant is labelled public or booking-only:

  • Public — anything already on your listing page: description, amenities, rules, pricing, policies, location, area guide.
  • Booking-only — arrival and during-stay details: check-in/checkout instructions, access codes, Wi‑Fi, contacts, and reservation-specific answers from guest forms.

The site chat is public only, for everyone. On your property site and group site, the assistant knows only what a signed-out visitor can read on that site, plus the prices and availability your booking panel would show. That is the same for every visitor: signed in or not, booked or not, and when you test it yourself. Homes the site does not list (archived, draft, demo) are unknown to it, and it sees only the reviews and pages the site displays. A guest who asks for a door code, the Wi‑Fi or their own booking is pointed to their guest portal and Trips, where those details live. This is enforced by what the chat loads, not by instructions to the AI, so no prompt trick can draw out anything else.

The guest portal chat follows the guest portal. Booking-only content reaches the guest portal chat for exactly the stay the guest portal is showing, and exactly when the guest portal would show it (the arrival-details window, plus any agreement, ID check or blocking form you require). If the Wi‑Fi tile shows the password, the chat can give it; if the door-code tile shows a code and its window, the chat gives that code. When a tile is locked, the chat says when it unlocks and gives no value. You do not configure this per question — it follows your guest portal's rules automatically. See Guest Portal for the access options.

Your own AI knowledge entries carry the same distinction: mark an entry Public (used on every surface, including the site chats) or Private (guest portal only, under exactly the rules above; the assistant is also told to use it with discretion and never quote it). A Private entry never reaches the property site or group site chat, or a guest portal visitor whose arrival details are still locked. Saved replies you mark usable by the AI follow the Private rule: they reach the guest portal chat, never the site chats.

Privacy: what the chat sees and keeps

Haven saves every guest chat so you can read it later. Here is what that record holds, and what it leaves out.

What each chat keeps

  • Your account, and the property, multi-unit site or guidebook the chat happened on
  • A random id from the guest's browser cookie
  • The guest's Haven account, if they were signed in
  • The name and email the guest typed, if they gave them
  • The stay, when the chat happened in a guidebook
  • The messages themselves, both sides

What the assistant never sees. The assistant never sees a guest's IP address, device or location. None of them is sent to the AI, and the chat record has no field for them. When the assistant looks up local places, it searches around your property, not the guest. The site keeps only a scrambled form of an IP address to stop one sender flooding the chat; the address itself is never stored. The browser id also links a chat to the visit in Site analytics, which records device type and rough location; the chat record does not.

The one exception: a reply to an attack. When a message tries to read files or secrets, pull out the assistant's instructions or run a command, Haven answers it in code before the AI sees it. That reply shows the sender their own IP address, rough location, device, account (if signed in) and a reference number. It stays in the chat history like any other reply, and Haven's team is emailed about it. The assistant reads the recent conversation on each turn, so if that sender keeps chatting, the reply and the details in it are part of what the AI reads from then on.

Who reads chats. You do, in Communication → Chatbot messages and Analytics → Chats. Haven's team can read them too, in its admin tools and in an email copy of each assistant reply that includes the guest's name and email when they gave them.

How long chats are kept. Chats stay so you can go back to them; there is no automatic deletion.

Teaching the assistant: AI knowledge

The assistant already knows each listing from its content. On top of that, Messages → AI knowledge lets you add anything a guest might ask that is not on the listing page — parking quirks, EV charging, early bag-drop, "which unit for a family of six", neighbourhood tips.

Sites view — knowledge scoped where it belongs

Pick a scope for each entry:

  • All chats (global) — applies to every site and guest portal you run.
  • A property — applies to that property's site and guest portal.
  • A group site — applies to the group site and flows down to every unit in it (a group note like "the lot behind building B is for guests" reaches each unit's chat). Turn the flow-down switch off on a group site if you want its knowledge to stay on the group site only.

Each entry has a title, the context itself, and a visibility: Public or Private.

Library view — reusable knowledge sets

Build a knowledge set once (a titled group of entries), then attach it to any number of properties or group sites — or flag it Applies to all sites. Sets are additive: a property can inherit several sets plus its own entries. Editing a set updates every site it is attached to immediately.

Learned view — answers from your own replies

Haven reads the replies you and your team write to guests (your Haven inbox, email, text, WhatsApp and the booking threads your PMS shares) and saves the answers you give as entries marked Learned. They reach the chat like any other entry. The Learned tab lists each one with the replies it came from. There you keep, edit or remove it, OK answers that state a price, and choose which answer stands when your replies disagree with an entry you wrote. Learn from my replies at the top switches it off. See Haven learns from your replies.

What else feeds the assistant automatically

  • FAQs — every FAQ a site shows (or inherits from your FAQ library) is answered verbatim by the assistant. A site whose FAQ section is hidden does not feed its FAQs to the site chat.
  • Reviews — the site chat uses the reviews your site displays, with the same reviewer names. Reviews you hid, or all reviews when the section is hidden, stay out.
  • Guest form answers — what a guest told you (dietary needs, arrival time) is available privately in that guest's own guest portal chat.
  • Local guide — your curated recommendations back the "things to do / where to eat" answers. On the site chats they count only when the guest portal is open to anyone; a guest portal that requires sign-in keeps them in the guest portal chat.

Changes are live for the next chat. There is nothing to redeploy or re-train.

Its tone: your voice

AI knowledge is what the assistant knows. How it sounds comes from Settings → Account & Profile → AI assistant → Your voice (the Guest messages side), the same voice your AI replies to OTA guests use. On your site and guest portal the chat takes your tone but still speaks as your assistant, never as you, so a sign-off note is left out there. A greeting note shapes only the chat's first reply. The site chats use your voice summary and notes only, never the example messages you pasted, since those were written to real guests. See Teach Haven your voice.

Train it by talking to it

You do not need a sandbox to test the assistant — you use the same environments your guests do:

  1. Open any of your surfaces as a guest would: your property site, your group site, or a guest portal (open it through the guest portal link so you see the private, post-booking behaviour).
  2. Ask the questions a guest would ask — "is there parking?", "can I check in early?", "what's the Wi‑Fi?".
  3. Watch how it answers. The chat is listed under Communication → Chatbot messages, and the same reply is graded in Analytics → Chats (Answered / Low confidence / Couldn't answer), with a reason when it struggled.
  4. If an answer is thin or wrong, feed it the right context right there — open the transcript and click Add context, or go to Messages → AI knowledge. Choose the scope (this property, this group site, or all sites) and the visibility (public or private).
  5. Ask again. The new context is live immediately.

Do this on each surface you care about — public site, group site, guest portal — because each one has a different knowledge boundary. It is the fastest way to see exactly what a guest sees. On the site chats, Test your assistant answers exactly as it would for an anonymous visitor; to see booked-guest answers, test in a guest portal.

While you are signed in to your Haven account, the assistant on your own property or group site knows it is you. Guest questions still get the answer a guest would get. Questions about the page itself ("why is this section blank?", "can I change this photo?") get where to fix it in your editor (Layout → Home → Sections on a listing site, Layout → Home → Page Content on a group site), and it never offers to pass your message to the host, since that would be you.

Where to read a chat

Communication → Chatbot messages lists every chat a guest had with the chatbot on a property site, a group site, or a guest portal. Open a row to read the transcript. A chat the chatbot struggled with is marked, and the Chatbot messages pill shows how many of those are waiting. Add context on a weak reply teaches it for the next chat.

Analytics → Chats is a different view of those same replies: each one graded, with the gaps grouped. Communication → Inbox is where you write to a guest. A reply the assistant sent inside an Airbnb, Vrbo, or Booking.com thread stays on that stay’s thread in Inbox, not in Chatbot messages.

When the assistant can't answer

The assistant is grounded: it does not invent property-specific details. If it does not know something it says so, and offers to pass the question to you. If the guest agrees, the full conversation lands on your Communication → Inbox thread and you are emailed — see Guest communication. It sends straight away, without asking first, when the guest asks for you or the owner, cannot get in (a door or gate code, key or lock that does not work), or is unsafe. In that reply it tells the guest where the code is used, as your check-in details describe it, and gives them the phone number from your guest portal's contact details so they can call you. If people are in danger, it tells them to call emergency services first. Guests can also open Message host at any time. A reply they have not seen yet opens the guest portal chat on Message host and puts an unread count on that tab; a reply that arrives while they are already on Ask AI badges Message host and leaves them where they are.

One exception to the two tabs: when AI replies to OTA guests answers a stay's message thread automatically, the guest portal shows a single Message host chat instead of the pair — on that stay, messaging the host already is the assistant, with you reading everything.

Every unanswered reply is also graded and surfaced in Chat insights so you can add the missing context and stop the same question from failing twice.

Frequently asked questions

Do I have to write one big prompt for all my properties? No. Each surface is grounded in its own listing automatically. Use AI knowledge to add per-property, per-group-site, or global entries and reusable knowledge sets — you never maintain a monolithic prompt.

Will the public site chat leak my door code? No. The property site and group site chats never load access codes, Wi‑Fi, contacts or anyone's reservation, even for a guest who has booked; they point that guest to their guest portal. The guest portal chat gives those details only when the guest portal itself shows them. Mark your own sensitive entries Private to keep them to the guest portal too.

Can guests book from the chat? They get a card with the exact price for their dates. Book these dates opens the home's page with the dates and party filled in and the booking panel open, and the guest checks out there as usual.

Does it work on my custom domain? Yes — the assistant runs wherever your Haven site runs, including custom domains and group sites, and its links and booking cards stay on the domain the guest is on.

Can I see what guests are asking? Yes. Analytics → Chats lists every conversation with search, signals, topic insights, and a plain-English "ask your chats" bar. See Chat insights.

Does this replace my PMS auto-messages? No — it complements them. PMS templates fire on a schedule; the Haven assistant answers what a guest actually asks, on your own branded surfaces, and reports back on what it could not answer.

Why does my chat history show a cheeky reply with an IP address in it? Someone tried to break the assistant, not book a stay: they asked it to read files or secrets, give up its instructions, or run a command. Haven answers those messages itself, before the AI sees them, with a short cheeky refusal that shows the sender their own IP address, rough location, device, account (if they are signed in) and a reference number, and Haven's team is emailed about it. Nothing on your site was read or changed. See Privacy: what the chat sees and keeps.

Can I delete or redact a reply in a chat? No. You cannot delete, edit, or hide a reply or the transcript. Add context on a weak reply teaches the assistant for the next chat. A reply to someone trying to break the assistant was written by Haven, not the AI, and nothing was revealed.

What happens when someone pitches me SEO through the chat? Vendors offering SEO, backlinks, traffic or "first page of Google" are not passed to you. Haven answers them with a cheeky reply (emojis included) pointing to the free SEO scanner Haven built, so they can check their own site first and run yours through it too. The obvious pitches never reach the AI at all, and you still see them in your chat history.

Can it answer my Airbnb and Vrbo guests too? Yes, when you turn it on. It replies in the guest's booking thread through your PMS, either drafting for your approval or sending on its own. See AI replies to OTA guests.

New to Haven?

Everything in this guide, done for you

Haven is the direct booking platform these guides are written for — a branded site, secure payments, and guest relationships you own. Build yours free.

See how Haven works

Free to build · No credit card · Private until you publish