Our guest-message inbox taught us something we didn’t expect. Most of the questions were not hard. Guests asked the same things over and over: how to get in, how to get from the station, where to leave a suitcase, which bin a plastic bottle goes in. The answers were simple. The problem was that most of them were only in my head, in old message threads, or in a house manual nobody opens.

This week’s spotlight is our AI concierge. I want to start one step earlier, though, with the work that decides whether any chatbot helps your guests: getting your property’s answers written down.

TL;DR

  • At our guesthouse, guests repeatedly asked about check-in, directions, luggage, house rules and equipment.
  • An AI concierge grounded in a property’s own information works best when that information is clear and up to date.
  • Building the source material means pulling real past questions, writing one clear answer for each, and marking which questions should always go to a human.
  • With BenStay AI concierge, booking changes go through the booking page or staff, and staff handle refunds.
  • BenStay AI concierge uses your property information to answer routine guest questions 24/7 in multiple languages. Questions that need judgment go to staff. Each property gets its own concierge page.

Why Do Guests Keep Asking Questions Your Listing Already Answers?

Guests ask because they can’t find the answer when they need it, not because the answer doesn’t exist. A guest standing outside the station at 11pm with a phone at 8% battery won’t scroll back through a booking confirmation. They’ll send a message and wait.

At our guesthouse in Kyoto, guests repeatedly asked about check-in, directions, luggage, house rules and equipment (we described those recurring guest questions in our Kyoto operations account). The questions before and during a stay kept landing in the same few buckets:

  • Getting in: the check-in procedure, door codes, arriving before check-in time
  • Transit: directions from the nearest station or the airport
  • Luggage: storing bags before check-in or after check-out
  • House rules: trash separation, quiet hours, shoes
  • Facility how-tos: wifi, laundry, air-conditioning

Each answer is specific to the property, but it rarely changes. That combination is what makes these questions worth automating, and it’s also why the groundwork matters so much.

Where Does a Guesthouse’s Know-How Actually Live?

Operators can check four places where this know-how tends to sit: the owner’s memory, past message threads, a house manual, and the cleaning team’s habits. Each can be incomplete in its own way.

The house manual may cover the wifi password and not the fact that the nearest station has two exits and only one of them makes sense with luggage. Message threads can have great answers buried under dozens of “thank you!” replies. Memory is accurate but asleep at 3am.

No tool fixes this by itself. A chatbot grounded in your property’s information repeats that information faster and in more languages. If the information has gaps, the chatbot has the same gaps.

How Do You Turn That Into Answers a Guest (or a Bot) Can Use?

Start from the questions guests actually asked, not the ones you think they’ll ask. This is the process I’d suggest to any operator, whatever tool they end up using:

  1. Pull your last few months of guest messages. Copy each question into one list, omitting names, booking references and entry codes. For “Is my code 1234?”, record “Where can I find my entry code?” Don’t edit beyond that yet.
  2. Group them. You’ll probably find the five categories above, plus a few that belong to your building alone (a shared entrance, a tricky elevator, a nearby konbini that closes early).
  3. Write one canonical answer for each. Keep it short, concrete and sequential: “Take the East Exit, turn left at the bakery, the building is the third on the right.” Mention landmarks guests can see, not ones only locals know.
  4. Decide what not to put in a shared document. Some things, such as per-booking entry details, may be better sent only to a confirmed guest at the right time. Decide that deliberately.
  5. Mark the questions that must go to a human. In our experience these are mainly reservation changes and refunds: anything that involves money, exceptions or judgement.
  6. Give the document an owner and a review rhythm. When the laundry machine changes or the trash schedule shifts, the answer has to change the same day.

Even without a chatbot, your co-host and cleaning staff can use the same instructions when a guest asks for help.

What Did We Build, and How Does It Work?

BenStay AI concierge is an AI concierge for hospitality. The concierge uses your property information to answer routine questions around the clock, in multiple languages. Questions that need judgment go to staff. Each property gets its own concierge page. You can see it at ai.benstay.jp.

In plain terms:

  • Grounded in your property. It answers routine questions from the information you provide about your place, not from general guesses about Japan, and questions that need judgment go to staff. That’s why the groundwork above matters: it’s the material the concierge works from.
  • 24/7. The 11pm-at-the-station guest asking how to get in gets an answer at 11pm, not the next morning. If a question needs staff judgment, it goes to staff instead.
  • Multilingual. Guests can ask in Japanese, English, Chinese or Korean, among other supported languages.
  • A page for each property. Each property gets its own concierge page.

We built it because we needed it ourselves. Our questions were repetitive and stable, and we were losing time to them. That pattern shows up in our own operations data, and it’s what the product is designed around.

Where Does It Fit, and Where Doesn’t It?

It fits best where questions are frequent, predictable and property-specific. At our guesthouse, that described the questions guests asked again and again.

Where it doesn’t fit, honestly:

  • If your property information isn’t written down yet, start with the process above. A concierge can’t answer from information that doesn’t exist.
  • Reservation changes and refunds are still for a person. Booking changes go through the booking page or staff, and staff handle refunds. They involve money and judgement, and I wouldn’t want a chatbot improvising on either.
  • It doesn’t replace hospitality. A warm welcome, a local recommendation from someone who actually lives there, and handling a guest who is upset all stay human. The point is to free up time for those things, not to remove them.
  • Information goes stale. If you change a rule and don’t update the source, the concierge gives the old answer. Someone still has to own the content.

If most of your inbox is “how do I get in” and “where’s the trash,” a grounded concierge can take that load off. If your inbox is mostly negotiation and special requests, you’ll get less out of it.

FAQ

Q: What information does a property-grounded AI concierge need?

It needs clear, written answers to the questions guests actually ask: check-in steps, directions from the nearest station or airport, luggage options, house rules and how to use the facilities. The more concrete and up to date that information is, the better the answers.

Q: Can the BenStay concierge change my booking or issue a refund?

For a booking change, use the booking page or contact staff. Staff handle refunds. The concierge is meant for routine, property-specific questions.

Q: Do I need a chatbot to benefit from writing down my property’s answers?

No. A single document of canonical answers helps co-hosts, cleaning staff and anyone covering for you, whether or not you ever add a chatbot.

Sources