Pre-Arrival Messages and Guest Guidebook Templates

Five adaptable guest messages from enquiry to departure, plus a guidebook structure and a checklist for accurate, consistent guest communication.

Published 25 October 2026

Editorial illustration: Pre-Arrival Messages and Guest Guidebook Templates
AI-generated editorial illustration

The key point

A useful message tells guests what to do at that stage and whom to contact for help. Adapt each template to the booking and actual terms, while keeping reusable property information in one maintained guidebook.

Source and scope of this guide

1. Match each message to the guest’s stage

Use these guest communication templates as a starting point for Airbnb or other booking channels, then adapt them to the booking, actual terms and the channel’s communication process. The aim is to make the next action clear without rewriting essential property information each time.

These messages are examples to adapt, not a claim that every package uses them. Replace each [field] with verified information before sending. Never place real guest information, passwords or entry codes in a public template.

2. Before booking: answer the actual enquiry

Use this when a guest asks about rates, availability or facilities. Check the information first, especially guest numbers and conditions affecting room choice. Do not promise an arrangement the team has not confirmed.

Hello, and thank you for considering [property]. For [arrival–departure dates] and [guest count], we currently have [verified room type]. The confirmed rate and inclusions are [details]. The key booking and cancellation terms are [applicable terms]. If you need [additional requirement], please let us know so we can check it before you confirm.

If availability or a request is still unconfirmed, state what is being checked and when the team can realistically respond instead of guessing.

3. After confirmation: align the essential details

Thank you for booking [property]. Your stay details are [arrival date] to [departure date] / [room type] / [guest count]. Check-in is [actual time or window] and check-out is [time]. Payment details and applicable terms are recorded in [confirmation source]. If anything is incorrect, please contact us through [channel]. We will send directions and arrival instructions through [agreed channel].

This gives guests a chance to spot errors, but it does not replace checking payment status. Describe any pending item accurately and follow the team’s process. Sending a confirmation message does not itself prove payment.

4. Before arrival: provide actionable directions

Your stay at [property] is approaching. Address and checked map pin: [link]. Entrance and landmark: [details]. Check-in is available [actual time]. Key collection or entry instructions: [booking-appropriate steps]. Parking: [confirmed information]. Guest guide: [current link]. If you expect to arrive outside the stated hours or have trouble on the way, contact [team/channel/actual coverage hours]. Please share your expected arrival time so the team can prepare.

Check directions to the entrance guests will use, not just the building location. If entry codes are used, follow the team’s process for sharing them with the intended recipient. Do not put live codes in this article or a publicly accessible guide. Do not say a room is ready before the team has released it.

For the separate physical check, see the room readiness checklist. A welcome message does not replace on-site inspection.

5. During the stay: make help easy to request

We hope you have settled in comfortably. If you cannot find something or an item is not working, contact [channel] and tell us where the issue is. The team is available [actual hours]; for urgent assistance, use [confirmed contact process]. Equipment instructions and house information are in [guide].

After a request arrives, record who received it, who is taking over and when the guest will receive a realistic update. Do not promise a repair deadline before the team has assessed the issue. An automated acknowledgement should not be the final action on a problem requiring a person.

6. Departure and follow-up: close the information loop

Thank you for staying at [property]. Check-out is by [time]. Please return your key or leave the property using [actual steps]. For forgotten belongings or anything else to report, contact [channel]. After your stay, we welcome feedback about your actual experience through [review or feedback channel] so we can improve.

Send the departure instructions before check-out and the feedback request after the stay where appropriate; they do not need to be one message. Ask neutrally rather than requiring a positive review, and continue following up on unresolved complaints or forgotten belongings.

7. What belongs in the guest guidebook

Keep reusable information in one maintained guide and link to that version from relevant messages. Assign an owner and a last-checked date so chats and the guide do not give different times or entry instructions.

  • Arrival and departure: address, correct entrance, parking, confirmed times and access steps.
  • Using the room: internet, air conditioning, television and equipment instructions matching the actual items. Share guest-only access details separately through the agreed process.
  • House rules: quiet hours, smoking, guest count, pets and the property’s actual disclosed conditions.
  • Getting help: responsible contact, coverage hours and checked urgent-assistance process.
  • The neighbourhood: checked transport and nearby services. Do not promise opening hours that have not been verified.

Everything need not fit on one page. Use clear mobile-friendly sections, and ask someone unfamiliar with the property to follow the guide from the entrance to the room.

8. Checklist before sending or automating

  • All placeholders are replaced with booking-specific information.
  • Dates, rooms, guest count and payment status match source records.
  • Service hours and contacts reflect actual coverage.
  • The map, guide link and arrival steps work.
  • No live access codes or personal details appear in the public master.
  • Thai and English versions communicate the same conditions.
  • A person can take over guest replies and problems.
  • Templates are updated when terms or on-site arrangements change.

If the owner still handles every message, distinguish repeatable responses from decisions requiring judgment. Read self-management versus hiring support and contact Kines with common guest questions and the coverage you need to discuss an appropriate scope.

Practical questions

Should every detail be sent to guests at once?

Separate messages into enquiry, confirmation, pre-arrival, in-stay and departure stages so guests receive useful information at the right time.

What should I prepare before contacting Kines?

Prepare the property type, location, room count, current team and the specific problem you want help with. Avoid sending passwords or guest personal data.

About this guide

Prepared by Kines as practical editorial guidance for property owners.

About Kines

Sources and scope

The downloadable checklist is adapted from this guide. Named editorial materials: Hotelpreneur 101 framework; Property business preparation checklist

Related Kines guides · Kines Academy catalog (Thai)

Company editorial sources; original working documents are not published here.

PACH Group

PACH Hospitality Group Co., Ltd.

Operator of Kines Hospitality and Kines Academy

Company registration number 0105564067192

Head office: 50 Sukhumvit 65, Phra Khanong Nuea, Watthana, Bangkok 10110

Telephone 063-694-5555 · Email hello@kines.co.th