Automated pre-check-in messages that help
The guest has a booking for tomorrow and writes to you in the evening: "What time can I arrive?" Then they ask about parking, access, documents or arrival conditions. The team replies, sometimes from three different inboxes, even though all this information could have been clear a day earlier. Automated pre-check-in messages solve this repetitive part of communication, without turning the relationship with the guest into an impersonal exchange.
For a service business, the message before arrival is not just a confirmation. It is an important operational moment. The guest needs instructions, the team needs accurate data, and any special requests must reach the right person before they become a problem at reception, on the phone or at the location.
What automated pre-check-in messages must accomplish
A good message does not try to say everything. It provides the information needed for the next step and opens a conversation when the guest has a particular situation. If the message is too long, it will be ignored. If it is too vague, it will generate exactly the questions you want to reduce.
In most cases, the guest must be able to confirm four things: the date and arrival window, the address or access method, what they need to prepare and how they can announce a change. For a hotel or resort, these can include the estimated arrival time, parking options and instructions for late check-in. For a clinic or a salon, they can mean appointment confirmation, required documents and the rescheduling policy.
The difference is simple: standard information is sent automatically, and exceptions reach the team quickly. The guest does not have to search through old emails or explain from the start what they need.
Timing matters more than frequency
There is no universal time for all businesses. The right moment depends on how early guests need to organize themselves and how much time the team needs to act after a reply.
For an arrival with many logistical details, a first message 48-72 hours in advance can be useful. The guest has time to read the instructions and announce a special request. A short message on the day of arrival can confirm the window, but it must not repeat the entire content.
On the other hand, if bookings are frequently made on the same day, the rule must be adapted. The message can be sent immediately after confirmation, then updated with relevant information before arrival. Good automation takes into account the time of booking, not just a fixed hour in the calendar.
Build the message around the guest's decision
An operational message has a simple structure. It starts with identifying the booking or appointment, continues with the practical information and ends with a clear action. The guest must know whether they need to reply or just keep the details.
For example:
"Hi, [first name]. We're expecting you on [date], starting at [time]. The address is [address]. If you estimate you'll arrive after [time], reply here with the approximate time and our team will prepare the next step."
This message works because it does not hide the action in a long paragraph. It does not promise things that cannot be offered and does not ask the guest to call for simple information. Above all, it allows a reply in the same conversation thread.
You can add a second sentence if there is a mandatory requirement: "Please have [document or information] with you, so that the handover goes faster." Avoid, however, turning the message into a complete set of rules. Detailed rules can be communicated separately, when needed.
Useful personalization does not mean just the first name
The first name is a start, but it is not the reason the guest feels the message is addressed to them. Real personalization uses data that changes the instruction: the arrival date, the booking number, the location, the selected window or the request the guest has already mentioned.
If they previously said they are arriving late, the message must include the relevant instruction, not the standard text for a midday arrival. If they asked about parking, the team should see this question in context when they take over the conversation. Repetition is one of the most visible signs of fragmented communication.
This is where continuity between channels matters. A guest may confirm on WhatsApp after receiving an email or may call for a clarification. If the history remains separate, the team wastes time reconstructing the situation. If the history is shared, the conversation becomes context. The context becomes the next step.
Choose the channel by urgency and the guest's habit
Email is suitable for more detailed instructions, especially when the guest needs to keep the information. SMS is effective for short and urgent alerts. WhatsApp can work well for confirmations and quick questions, if you have the necessary consent for communication on this channel.
There is no need to send the same message everywhere. Three identical notifications in one day can seem insistent, even if the information is useful. A practical rule is to choose a main channel for the complete message and a backup channel only for critical information or for the lack of a reply when a reply is needed.
Before any campaign or send to an audience, the team must be able to check the list, the message and the estimated cost. Pre-send control prevents inappropriate sends and makes communication easier to track afterwards.
Clearly define what is automated and what reaches people
Automation must not decide on its own in all situations. Its role is to deliver repeatable information, collect simple replies and flag exceptions. The team decides how to handle requests that involve a change, a dissatisfaction or a special need.
Set a few handover rules in advance. For example, a reply containing "arriving late", "I want to change", "I can't make it" or "I need help" can create a task for the responsible colleague. They receive the conversation, a summary and the proposed next step, not just a notification without context.
Runner can organize this continuity between WhatsApp, calls, SMS and email, so that an automated reply and a colleague's intervention are part of the same conversation. Automation prepares the case. The human keeps control over the decision and the final message.
Measure what happens after sending
Do not evaluate messages only by the number of sends. More relevant are the replies that change the team's activity: how many guests confirm, how many announce a delay, how many ask for clarifications and how much time passes until an exception is taken over.
Also track the repetitive questions that still appear. If many guests ask where they can park, the problem may be the wording, the timing of the send or the lack of a concrete detail. The message must not be defended just because it was configured. It must be adjusted based on real conversations.
A weekly check is usually enough to start with. Read a sample of conversations, see where the guest gets stuck and update the texts with information confirmed by operations. A good message becomes better through observation, not through assumptions.
Before the next wave of arrivals, ask yourself what the guest needs to know to arrive prepared and what the team needs to know to welcome them well. If every reply has an owner and a next step, the automated message is no longer just a notification. It becomes a useful part of your operation.