Templates fill in name, dates and amount, your team just gives them a quick check.

For recurring guest emails and booking channels where content, tone and property data must reliably match.

Email and the OTA or booking channel derived from the reservation. The team does not arbitrarily bypass the booking channel.

Yes. Email templates can be maintained as plain text or HTML and reviewed before sending.

So messages respect the rules and display limits of the relevant booking channel; HTML is deliberately not allowed there.

Guest name, stay, room, property contact, prices, payment state, extras, key links and date values, among others.

A guest email offers relevant guest, stay, property and payment details. An invoice or booking page offers only the information genuinely needed there.

Directly from the selected guest, the specific booking and maintained property details. An arrival template therefore uses the exact date, room and balance for that stay.

Yes. Preview assembles the subject and message with the selected guest and booking. Missing details are shown before the message is sent.

STRYK marks the missing detail in preview. The team completes the property details or corrects the template before the guest receives the message.

Yes. Email templates keep subject and body separate; channel messages focus on the permitted plain text.

Yes. Only approved templates appear in daily hotel work. Drafts and outdated versions remain paused until they are reviewed or replaced.

Yes. Name, channel, format, subject, body and active state are stored for the property.

Yes, with the appropriate permissions. In operations, pause first, test the replacement and then remove obsolete duplicates.

STRYK shows the team current approved templates with clear field names. Outdated versions can be paused and removed after a replacement has been reviewed.

Only where the message context explicitly permits it. Internal data does not belong unchecked in public documents or booking pages.

Yes. The copy stays the same while specific values resolve anew for every booking. Each send must therefore still be reviewed in its stay context.

No. They secure recurring facts. Welcome, special request and sensitive situations still need an attentive human review.

Yes. Automated guest messages use the same approved copy and booking details. Before launch, the property reviews recipient, timing and the finished message on a test booking.

Booking engine confirmation and cancellation copy is maintained per event and active guest language and follows the same controlled placeholder principle.

With a dedicated test booking: verify language and channel, resolve every value, open links, read on mobile and activate only afterwards.

One clearly responsible person per property. This keeps check-in time, payment path, contact details and tone consistent while the team safely uses approved copy.

Creation, editing and deletion follow the roles of the relevant business area. Daily sending is additionally tied to guest and booking context.

No. Templates, placeholders, preview and automation context are part of the single STRYK offer-with no setup fee and no hidden module price. External delivery partners may charge their own fees.