The messages along the stay
Guests don’t want more messages; they want the right information at the right time.The booking confirmation is the most important message you send. It goes out immediately, contains dates, room, price, cancellation policy and your contact details, and it looks like your hotel. This is where it is decided whether the guest feels in good hands or picks up the phone just to be sure.
The pre-arrival message, usually three to seven days before, is the most useful. It answers arrival time, parking, directions and check-in times before the guest asks, and invites them to check in online. Many properties also offer extras here, such as breakfast, late check-out or a table in the restaurant. On the day of arrival itself, a short message with the essentials is enough, especially for late arrivals or self check-in.
During the stay, the rule is: as little as possible, as much as necessary. For longer stays, a short message after the first night asking whether everything is fine can make sense. After departure come thanks and the invoice and, one to three days later, a request for a review. If you only ask after two weeks, you get far fewer responses because the stay has already faded.
| Timing | Message | Content | Automate? |
|---|---|---|---|
| Right after booking | Booking confirmation | Dates, price, cancellation policy, payment, contact | Yes, always |
| 3 to 7 days before arrival | Pre-arrival message | Arrival, parking, check-in times, online check-in, extras | Yes |
| Day of arrival | Quick info | Arrival time, self check-in, emergency phone number | Yes, especially for late arrivals |
| During the stay | Check-in for longer stays | Is everything OK? Any requests? | Optional, with conditions |
| After departure | Thanks and invoice | Invoice, thanks, a note on booking direct next time | Yes |
| 1 to 3 days after departure | Review request | Short request with a direct link to the review | Yes |
Templates, personalisation and multiple languages
Good templates don’t sound like templates. They address the guest by name, mention their dates and room, and are written in your property’s tone of voice. A family hotel in the mountains writes differently from a business hotel by the station. Write your templates carefully once, have someone who doesn’t know your property proofread them, and use placeholders for everything that changes: name, arrival, departure, room type, price, payment status.
In Austria and Germany, multiple languages are not a luxury. In many regions a large share of guests come from abroad, and a confirmation in their own language builds trust. You don’t have to maintain every message in ten languages. Start with German and English, add the languages of your two or three biggest source markets and assign templates by the guest’s origin or language.
OTA messages belong in the same inbox. If questions from Booking.com guests end up in the extranet, emails from direct bookers in the hotel inbox and callbacks on scraps of paper, the front desk loses track. The goal is one conversation per booking, whatever channel the guest writes through.
Checklist for good templates
- Personal greeting with the guest’s name, no “Dear Sir or Madam”
- All booking-related data via placeholders, never typed by hand
- A subject line that names the content, e.g. “Your arrival on Friday: everything you need to know”
- One clear action per message, e.g. “Check in online now”
- A way to get in touch with questions and an emergency phone number
- At least German and English, plus the languages of your most important source markets
- No promotional content in service messages without appropriate consent
What runs automatically and what stays personal
The line is simpler than it seems. Automate what is the same for every guest and tied to a fixed point in time: confirmation, pre-arrival information, thanks, review request, payment reminder. Everything that needs empathy or a decision stays personal: complaints, booking changes, special requests, group enquiries and anything involving money.
Automation is what makes personal communication possible in the first place. If the front desk doesn’t answer the parking question twenty times a week, it has time for the guest arriving for their wedding anniversary. What matters is that automations know conditions: no review request after a complaint, no upgrade email to guests already staying in the suite, no pre-arrival message for a booking for tomorrow that only came in today.
Consent, AI and transparency
Distinguish between service messages and marketing. Confirmation, arrival information and invoice belong to the booking and may be sent. Newsletters, offers for next season or discount campaigns are marketing. For these, in Germany and Austria you generally need the guest’s express consent; a narrowly defined exception for existing customers requires, among other things, a clear opt-out notice. Have these rules checked for your property by your legal advisor, and don’t mix marketing into service messages.
AI can recognise guest enquiries, sort them by topic and write draft replies from your hotel knowledge: check-in times, parking, pets, breakfast. That saves time, as long as a person checks the replies. A good way to start: AI writes the draft, the front desk reads it, adjusts it and sends it. Only once you trust the replies to certain standard questions do you let those be answered automatically.
Guests should know when they are writing to an AI. Article 50 of the EU AI Act sets transparency obligations for AI systems that interact with people; according to its timetable, they apply from August 2026. In practice: don’t give an automatic assistant a made-up human name with a photo, and label automatically sent AI replies clearly, for example with a short note at the end of the message. Drafts that your team reviews and sends itself are a reply from your property.
Introducing AI step by step
- 01Maintain your hotel knowledge
Store check-in times, parking, pets, breakfast, directions and cancellation policies once, cleanly. The AI is only as good as this foundation.
- 02Drafts only
For a few weeks, the AI writes drafts and the team checks every reply, seeing where it is good and where it isn’t.
- 03Release standard questions
Release only simple, low-risk questions such as check-in time or parking for automatic replies.
- 04Label
Label automatic replies so the guest can recognise them as AI replies, and offer a way to reach a person.
- 05Review continuously
Read samples regularly and be able to switch the automation off immediately if something is wrong.
How STRYK handles it
In STRYK, every message is tied to a booking. You write directly from the guest or the booking, and the channel follows from the booking: you reach direct bookers by email, and guests from Booking.com and other connected OTAs through the OTA’s messaging. You send emails from your own mailbox or from a STRYK sender address for your hotel, and guests’ replies land back in the same conversation. STRYK does not offer SMS or WhatsApp.
You maintain templates with placeholders centrally. Automations trigger messages, internal alerts, tasks, notes or tags at fixed points: on booking, confirmation, modification or cancellation, before arrival, at check-in and check-out, after online check-in is completed, when a payment is received or due, after departure and as a review request. Conditions limit who receives a message, for example by booking source, room type, length of stay, returning guest or country of origin, so you can send German- and English-speaking guests the right template each. Before switching an automation on, you test it on a real booking.
STRYK Guest AI is an add-on module. It matches incoming guest emails to the right stay, writes draft replies from your approved hotel knowledge in the language of the enquiry and prepares booking, modification and cancellation requests for review; changes to bookings are always confirmed by a person. Only standard questions you have explicitly released are answered automatically, and the automation can be switched off at any time. Guest AI is free for one month and then costs €4 per room per month excl. VAT, billed annually, only if you activate the module.
| Area | How STRYK works |
|---|---|
| Channels | Email from your own mailbox or a STRYK sender address, OTA messages; no SMS, no WhatsApp |
| Conversation | One conversation per guest and booking, outgoing and incoming |
| Templates | Maintained centrally, with placeholders for guest and booking data |
| Automations | Triggers along the stay, conditions, test run before switching on |
| Guest AI (add-on) | Drafts with approval, auto-reply only for released standard questions, free for 1 month, then €4 per room per month |