Hotel pre-arrival questions at a small guesthouse or holiday apartment repeat almost word for word: is there parking, when is check-in, can I bring my dog, how do I find you after dark. They arrive through three channels at once, usually while the owner is cleaning a room or spending time with family. One answer retyped twenty times a week is an hour nobody counts.
This guide sorts questions by the stage of the guest's trip and gives each one a home: a help article, a template or a conversation with a person. It does not cover booking systems or travel portals, only the messages guests send to your website and social profiles.
A three-stage map of guest questions
Go through the messages from your last two seasons and assign each to a stage: before booking, after booking or arrival day. The same topic can be a different matter at each stage. A question about a dog before booking decides whether the guest picks you at all; after booking it is about details such as a water bowl or a cleaning fee. The map below is a starting point, so add your own questions and drop the ones you never get.
Scroll the table sideways to see all columns.
| Stage | Typical questions | First place to answer |
|---|---|---|
| Before booking | Is there parking and is it free; are pets allowed; is breakfast included; a cot for a child; step-free access; distance to the trail or beach | Help article on the website and in the widget |
| After booking | Check-in and check-out times; early arrival; luggage storage; towels and bedding; nearby shop and restaurant; EV charging | Template with property details |
| Arrival day | Finding you after dark; where to park; arriving after check-in hours; key collection; Wi-Fi; emergency contact | Template sent by a person who knows the booking |
Count how much of your inbox the eighteen questions in the table actually cover, using your own messages rather than a hunch. When one question comes back every week, fix the information at the source first: the room description, the website footer or your profile bio.
The Holidu magazine suggests sending key handover, parking and directions a few days before arrival and warns against too many messages from the host. It is industry advice without effectiveness data, not a study of guest behaviour. Holidu.
Help article, template or a person
Every question on the map goes into one of three drawers. The test is simple: is the answer the same for every guest, and could a mistake cost someone money or a night's stay?
- Help articleThe answer is identical for everyone and stable for the season: parking, pets, breakfast, check-in hours, directions. Guests find it themselves before they write.
- TemplateFixed content sent within a conversation with a small addition: name, arrival date, room number. A person sends it after reading the question.
- Always a personPrices, availability, discounts, special requests, complaints, changing or cancelling a stay. Every answer here is a commitment and needs checking.
Keep help articles short, one answer per question, titled in the guest's words: "Can I bring my dog?" rather than "Pet policy". Where to find topics and how to check whether an article reduced questions is covered in the guide to a website knowledge base and FAQ. For templates with placeholders, read our article on customer service reply templates.
Reply samples you can copy
Here are two samples from a fictional guesthouse called The Larch House. Replace the bracketed details with your own and save them as team macros, so everyone who replies uses the same version.
Hello [name]. Check-in runs from [3 pm] to [8 pm], check-out is by [10 am]. Parking is free behind the building; the entrance is from [street name]. If you arrive later, message us here with a rough time and we will arrange the key handover.
Dogs are welcome in rooms [numbers]. The fee is [amount] per stay, and a blanket and bowl will be waiting in the room. Please do not leave your dog alone in the room. Shall I add this to your booking?
The second sample ends with a question because adding a pet to a stay needs a person. A template saves typing, but it does not replace checking whether that room is free on those dates.
Website, Messenger and Instagram in one inbox
The same guest may ask about parking in your website chat and then message you on Instagram the next day about arriving late. When every channel lives in its own app, the second person in your family or team has no idea what has already been promised. Meta platform limits, including the reply window, are covered in a separate guide to customer service on Facebook and Instagram.
- Connect channels to one website.Connect website chat, your Facebook Page and your Instagram professional account to the same website, so messages land in one list.
- Decide who replies.Assign the conversation to a person before they start typing. That way a guest never gets two different answers to the same question.
- Tag the stage.Tags such as "before booking", "after booking" and "arrival" show after a month which stage creates the most work.
- Reply from your phone.The team mobile app sends notifications for new messages from the widget, Messenger and Instagram, so you do not have to sit at a computer.
This is how Meetlead customer support works: one inbox for three channels, searchable Help Center articles in the widget, and macros with categories and variables. Meetlead does not connect to travel portals or property management systems, so you check booking status wherever you manage it.
When a guest writes in German or Polish
At properties near a border or in popular mountain areas, some questions arrive in a second language. Help articles and widget texts can be prepared in Polish, English and German, and search shows the guest the version in their language when one exists. Translate the articles with the most questions in the first table before anything else, and keep templates in separate macros for each language.
Meetlead does not translate messages automatically, so a person writes the reply in the guest's language or uses a ready macro. When to switch on language detection, and how to avoid promising faster service than your team can deliver, is explained in the guide to multilingual customer service.
A realistic reply time and a rule on payments
A guest who does not know when to expect an answer writes on another channel or calls. Set an availability schedule and state in the offline texts the reply time you actually keep, not the one that looks good. Outside your hours, guests leave a message through the offline form and know when you will be back. Our article on first-response time in chat explains how to measure that time honestly.
We reply every day between [8 am] and [9 pm], usually within [two] hours. Leave your question and email address. Answers about parking, pets and check-in are available right away in the help tab.
The second rule concerns money: in chat and direct messages you never ask for a card number, security code or online banking login. If a guest sends them anyway, do not copy them anywhere, and point them to the safe payment method you already use. Put this rule in a help article, so guests know that a request for card details in chat does not come from you.
According to the PCI SSC FAQ, PCI DSS Requirement 4.2.2 prohibits sending unprotected card numbers by email, instant messaging, SMS or chat. The source describes a card security standard, not legislation or the rules of a specific bank. PCI Security Standards Council.
Questions about guest questions
Can an AI assistant send these answers? In website chat, some of them; on Messenger and Instagram a person replies. The condition is that the assistant works from approved house rules and never confirms availability or prices. The scope and limits of such an assistant are covered in the guide to an AI assistant for a guesthouse. Build the map from this article first, because without it the assistant has nothing clear to stick to.
Where do I start if I only have one evening? List the five questions you received most often last month and write a help article for each. Then save the check-in and parking sample as a macro. After four weeks, review your tags and add the questions that still keep coming back.
