The busiest period for front desk messaging is not during a guest's stay. It is the 48 hours before they arrive. This is when guests finalize their transport plans, confirm their meal preferences, ask about access and parking, and flag any special requests that did not make it into the booking form. If those questions pile up unanswered until check-in day, the front desk starts each arrival wave already behind.
For properties with a high proportion of foreign guests, the pre-arrival window is where the language barrier creates the most concentrated pressure. A guest in Seoul sending a question about the private bath schedule at midnight Japan time does not expect an immediate answer. But they do expect an answer before they board their flight the next morning. If the question sits in an inbox until 9am and the flight is at 8:30, it goes unanswered and the guest arrives uncertain.
This article covers how to build a pre-arrival messaging approach that handles the predictable questions automatically, in the guest's language, and leaves the front desk free to prepare the property and manage in-person arrivals rather than working through a message queue during the busiest hours of the day.
Mapping the pre-arrival question window
When we worked with properties in our pilot network to build their FAQ libraries, one of the most useful exercises was mapping when questions arrived relative to check-in time. The pattern was consistent across property types and locations. Questions about meal preferences and dietary requirements typically arrive 5 to 7 days before check-in. Questions about transport and access cluster in the 48-hour window. Questions about check-in time, luggage storage, and early arrival peak in the final 24 hours.
Understanding this timing matters because it tells you where to front-load your FAQ library. A property that has excellent answers for transport and access questions in multiple languages will absorb the largest pre-arrival message cluster automatically. The meal preference questions, which arrive earlier when staff typically have more bandwidth, are a better candidate for manual handling if needed.
The three message types that drive most pre-arrival volume
Based on the patterns we observed across our early-access pilot network, the pre-arrival message volume at inbound-focused properties in Japan is driven primarily by three types: access and transport questions, check-in timing questions, and meal and dietary requests.
Access questions are the highest volume. "How do I get to your property from Shinkansen station X?" is asked by the majority of first-time guests who are navigating an unfamiliar transport system in a language they do not read. The answer to this question is the same every time, for every guest. It can be written once, translated into the top 5 or 6 languages your guests use, and delivered automatically with no staff involvement.
Check-in timing questions are the second cluster. "Is early check-in possible?" "What time does check-in open?" "We have a late flight and will arrive after midnight, is that acceptable?" Each of these has a defined answer based on your property's policy. A property that can respond to these questions in Korean or Thai within minutes of receiving them, at 11pm on a weekday, is doing something that has historically required either a bilingual night-shift staff member or a backlog of unanswered messages.
Meal and dietary requests are the third cluster and require more care. Questions about vegetarian options, halal requirements, or severe food allergies are situations where the answer matters for the guest's wellbeing. These are good candidates for automatic first responses that acknowledge the request and provide the standard options, while flagging for human review when the situation is complex.
Building the pre-arrival messaging sequence
A pre-arrival messaging sequence is not a single template. It is a series of touchpoints calibrated to the distance from check-in. The structure that works well for small properties with high foreign guest proportions typically has three stages.
The first stage is a booking confirmation message that arrives immediately when a direct booking is confirmed. For OTA bookings, this is the confirmation message you can configure in the OTA platform. This message should include your WhatsApp or LINE contact number or handle prominently, along with a clear statement that guests can message you in their language and will receive a response. This single step increases the proportion of pre-arrival questions that come through a channel you can manage, rather than scattered across OTA inboxes and email.
The second stage is a pre-arrival reminder sent 48 to 72 hours before check-in. This message includes the core information that pre-empts the highest-volume questions: access instructions, check-in time, a request for meal preferences if applicable, and a reminder of your messaging contact. Done well, this message answers the majority of questions before the guest thinks to ask them, which is its purpose.
The third stage is the check-in day message. This arrives the morning of arrival day and is brief: a confirmation of check-in time, any relevant practical detail (luggage storage if arriving early, gate access code if checking in independently), and a direct line for any last-minute questions. Its function is to confirm that everything is in order and that the guest does not need to wonder whether the property knows they are coming.
What a structured pre-arrival approach does not replace
A well-structured pre-arrival messaging sequence handles the predictable questions efficiently. It does not replace human judgment for the questions that fall outside your FAQ, and it should not try to. A guest who has a complex special request, a medical need, or a situation that your templates do not cover needs a human to read and respond thoughtfully.
The goal is not to automate everything. It is to automate the questions that have known answers, in the languages your guests actually use, at the hours when your staff cannot reasonably respond. What remains after that is a smaller, more meaningful set of conversations that genuinely require someone's attention.
One thing I noticed consistently across the properties in our pilot network is that when the pre-arrival message volume dropped (because the routine questions were being handled automatically), the quality of human communication with guests improved. Staff had more time to read the messages that needed reading, and more capacity to respond thoughtfully rather than just working through a queue. That is not a technology outcome, it is an operations outcome that the technology enables.
Getting the language coverage right
Pre-arrival messaging only works if the response is in the guest's language. A beautifully structured sequence delivered in Japanese to a guest who does not read Japanese is not useful. The minimum viable language coverage for most inbound-focused properties in Japan is English, Simplified Chinese, Traditional Chinese, and Korean. Those four languages cover the largest share of foreign guest message volume at most Japanese properties in the main tourist regions.
Beyond those four, the priority depends on your specific booking mix. Properties with significant Thai, French, or German guest proportions should add those languages to their pre-arrival templates. The effort to translate a 200-word pre-arrival message sequence into one additional language is small compared to the improvement in guest experience for every guest from that market.