AI for Bed and Breakfasts: Inquiry Replies and Guest Memory

An AI agent can take over the repeated work of a bed and breakfast: answering booking inquiries about rooms, dates, rates posted on your own site, and house rules, and sending pre-arrival messages with directions, check-in times and parking details. The owner still decides which replies go out without review, which need approval, and which always reach a person. The agent's value depends less on how fluent its replies sound than on which guest details it may remember, how long it keeps them, and who can see them.

Key takeaways

• Start with booking inquiries and pre-arrival messages, because both follow repeatable rules and both come from a finite set of questions.
• Write approval boundaries before the agent sends its first message, including which topics always go to a person.
• Keep guest memory small and purposeful: store what the next stay needs, and delete what no one has a reason to keep.
• Measure success with a concrete criterion, such as the share of inquiries answered with correct facts that the owner later confirms, rather than a feeling that the replies sound good.
• Treat a more capable future agent as a reason to tighten memory and permissions now, not as a reason to loosen them.

What an agent can answer in a booking inquiry today

Most inquiries to a small guesthouse fall into a few families: is a room free on these dates, what does a room include, can we bring a child or a dog, is breakfast vegetarian or gluten free, how far is the station, and can we arrive late. Each of these has an answer that already exists somewhere in your records: the room list, the house rules, the breakfast menu, the travel directions and the availability calendar. An agent with access to those sources can compose a reply that is specific to the guest's dates and party size instead of pasting a generic paragraph.

The boundary matters more than the wording. A reply can state that a room is open for the requested nights only after the agent has checked the calendar at the moment of reply, not from a cached note. It can describe the breakfast menu as published. It should not promise a discount, confirm an exception to the cancellation policy, or say that a pet is welcome when that decision depends on the room and the season. Those answers belong to the owner or the person on the desk.

A good inquiry reply is short, answers the question first, and ends with one clear next step, such as a link to confirm the booking or a request for the guest's arrival time. If the inquiry contains two questions, the agent should answer both, and if one falls outside its boundary, it should say so plainly and route it to a person with a summary of the conversation.

Pre-arrival messages that reduce questions at the door

The second repeatable task is the message that arrives in the days before check-in. Its purpose is to remove the questions that otherwise arrive by phone at the moment the guest is lost in a parking lot. A well-designed pre-arrival sequence covers the arrival window, how to enter the building, where to park, how to reach the host if the arrival changes, the breakfast time, and any local item the guest must know, such as a street that is closed on a market day.

The agent can send these messages on a schedule and adjust them to the booking. A guest arriving after the evening hours receives the late-entry instructions. A guest who has booked two nights receives a reminder about the second day's breakfast schedule, not the first. The agent should also watch for replies. If a guest writes that the train was cancelled, the message is no longer routine and must move to a person quickly.

What the agent should never do is invent a detail to make the message complete. If the owner has not written down whether the gate code changes weekly, the agent must not guess. Missing facts are a signal to fix the knowledge base, not to fill the gap with plausible text.

Setting approval boundaries before the first message goes out

Before the agent speaks to a guest, the owner should write down three lists: what it may answer on its own, what it may draft for approval, and what it must never answer. This is a decision document, not a technical configuration, and it should be short enough that the front desk person can read it in five minutes. The NIST AI Risk Management Framework is a useful reference for thinking about these risks in a structured way, because it treats risk as something to map, measure and manage over the life of a system, not something to solve once.

A practical starting checklist:

• Name the agent's channels, such as the booking platform inbox, the website form and the business email address, and state which ones it may reply through.
• List the facts it may state directly, with the source for each one, such as the room list, the breakfast menu and the check-in procedure.
• List the topics that require approval before sending, including price adjustments, cancellations, refunds, special requests and any complaint.
• List the topics it must never answer, including medical or allergy advice beyond the published menu, legal questions and anything touching a guest's safety.
• Define the handoff: who receives the escalation, how quickly they must respond, and what summary the agent provides.
• Decide what the agent records after each conversation and who may read those records.

Owners often skip the last item. It is the one that becomes important later, because the conversation log is where guest personal data accumulates.

An illustrative scenario: a late arrival and a dietary note

The following scenario is illustrative and does not describe a real property. A guest writes to a six-room guesthouse asking whether a room is free for two nights in a month with a local festival, adding that she arrives after eleven at night and needs a gluten-free breakfast because of a medical condition. The agent checks the calendar at the moment of reply and confirms availability for the requested nights. It states the breakfast options from the published menu and says that the gluten-free items are listed there as prepared in a shared kitchen. It tells the guest that late arrival instructions will follow.

The agent does not say whether the kitchen can guarantee a safe meal for a medical need, because that is a decision for the owner. It flags the message for approval on that specific point, with a short summary: the dates, the late arrival, and the dietary question. The owner replies within the morning with a precise answer, and the agent then sends the confirmed statement and the late-entry instructions. The owner also adds a note to the guest's profile so that the next stay starts with the dietary detail already on record, marked with its date and the source, which is the owner's own reply.

The scenario shows the pattern. The agent handles the routine facts, routes the consequential question, and keeps the record tied to a source a person can verify.

Guest memory: what to store and what to forget

Repeat guests make a bed and breakfast feel personal, and an agent can help by recalling preferences: a room with a view, a late breakfast on weekends, a guest who always travels with a dog. That recall is useful only if the memory is deliberate. Store the preference, the date it was given, and where it came from. Do not store the reason behind a preference unless the guest offered it and the owner needs it to serve them, and do not store sensitive health details in a general notes field where any staff member or any tool can read them.

The discipline matters for two reasons. First, a memory that is wrong or out of date causes a worse experience than no memory at all, for example when an agent offers a room type that was renovated away. Second, a larger memory is a larger target. Prompt injection, where text in an inbound message attempts to override the agent's instructions, is a documented risk, and the OWASP prompt injection guidance describes why untrusted input should never be treated as instructions. An agent that can read and write guest history should treat every incoming message as data, not as orders.

A memory rule that works for small teams: keep a short profile per guest with three kinds of entries, stated preferences, confirmed facts, and open requests. Give each entry a date and a source. Set a retention period for conversation logs that matches your data protection obligations in the countries where your guests live, and review it at a fixed time each quarter. Anthropic's guidance on context engineering for agents makes the same point from the engineering side: an agent performs better when its context is curated and relevant rather than filled with everything that has ever been said.

How Be Human's managed approach handles this

Be Human designs the agent around this boundary before anything reaches a guest. The first engagement defines the role, here inquiry replies and pre-arrival messages, the facts and memory it needs, the channels it may use, the approval rules and a success criterion the owner can observe, such as the rate at which inquiries get a correct first reply without a correction. Access is limited to the calendar, the published room and menu information and the channels named in the plan, and permissions are reviewed on a schedule. Managed operations then cover monitoring of conversations, recurring evaluations of reply accuracy, maintenance of the calendar and messaging integrations, and a defined response when something goes wrong, such as a booking mismatch or a guest complaint that needs immediate handling by a person.

The approach is deliberately modest. The agent does not become the owner's voice on every matter. It handles the repetitive layer and makes the rest easier to reach.

Where to start and what to decide first

Choose one inquiry type and one pre-arrival sequence, write the three approval lists, and run the agent in draft mode for a few weeks so that the owner can compare its replies with what the desk would have sent. Only then decide which replies may go out without review. Keep the memory small until the first repeat guests show what is worth remembering. The question is not whether an agent can write a good reply, but which replies your business can stand behind when no one is watching. Take the free Be Human AI diagnostic to find the first task worth handing to an agent.

Frequently asked questions

Can an AI agent answer booking inquiries for a bed and breakfast without the owner reviewing each reply? It can for routine questions whose answers already exist in your records, such as room features, breakfast times and house rules, as long as the availability check happens at the moment of reply. Anything involving price changes, exceptions, refunds, medical or dietary safety, or complaints should still go to a person. Most owners begin with draft mode and move a topic to unreviewed replies only after several weeks of accurate results.

What should a pre-arrival message include so that guests stop calling the house? It should cover the arrival window, the entry procedure, parking, the breakfast schedule, how to reach the host if plans change, and any local detail that is easy to miss, such as a road closure. The message should be sent on a schedule that fits the booking length and arrival time. If a guest replies with a problem, the agent should hand the conversation to a person rather than improvising.

What guest information is safe for an agent to remember? Preferences and confirmed facts are the most useful and the least risky, such as a preferred room or a late breakfast request, provided each entry has a date and a source. Sensitive health details should be recorded only where the owner has a clear need and access is restricted. Conversation logs should have a retention period that matches your legal obligations, and you should review it on a fixed schedule.

Why should a small guesthouse prepare its guest memory now if more capable agents are still developing? Because the discipline is the same whatever the agent's capability: a clear record of what is known, where it came from, and who may see it. A more capable agent would be able to use a messy memory more widely and more quickly, which makes errors more costly, not less. Tightening permissions and memory rules now means the business is ready to extend the agent's role later without rebuilding its records.

Be Human editorial guidance. Examples are illustrative unless explicitly attributed. Sources provide background; implementation choices depend on your workflow.