Message Templates
Create reusable message templates with languages, images, and dynamic variables.
Create reusable message templates with languages, images, and dynamic variables.
βοΈ Message Templates
Message templates are the building blocks of automatic communication in OkupAI.
A template defines what is sent to a guest β when and to whom is defined later using Message Rules.
π§ What is a message template?
A message template is a reusable message that can:
be written in multiple languages
include dynamic variables (guest, booking, property data)
include images per language
be reused across many properties and events
A template does nothing by itself until it is linked to a rule.
π‘ Example
Welcome message "Hi {{guest_name}}, thanks for booking {{unit_name}}. We're looking forward to hosting you!"
β Adding a new template
Go to Messaging β Automation
Click Add new template (top right)
The template is created and opens automatically
You are now on the Template Details page.
π Template languages
Each template can contain multiple languages.
Click Add Language
Choose the language
Write the message text for that language
π How language selection works
The booking platform sends the guest language to OkupAI
OkupAI automatically selects the matching template language
If no exact match exists, your default language is used
πΌ Images
You can add images per language:
Drag & drop files into the upload area, or click to browse
Reorder images by dragging β the order badge shows the sending order
Each language can have different images
This is especially useful when your images contain text, or when you want to localize instructions or visuals.
π Variables (dynamic content)
Variables adapt your message automatically to the guest, the booking, and the property.
β¨οΈ How to insert a variable
Type
{{anywhere in the textA searchable list of available variables appears
Select the variable you want
The value is filled automatically when the message is sent.
π Booking variables
booking_id
Unique booking identifier
booking_date
Date when the booking was made
checkin_date / checkout_date
Stay dates
nights_price
Total price for the nights
cleaning_price
Cleaning fee amount
platform_city_tax
City tax amount
currency
Booking currency
payment_method
Payment method used
platform_name
Booking platform name
π€ Guest variables
guest_name
Primary guest name
guest_email
Guest email (online check-in first, platform as fallback)
platform_guest_phone
Guest phone from the platform
platform_guest_origin
Guest origin reported by the platform
n_adults / n_children / total_guests
Guest counts
ai_guest_country
Guest country (AI detected)
πͺͺ Online Check-In variables
Filled from your guests' Online Check-In submissions:
oci_guest_name
Guest name(s) from check-in
oci_birthdate / oci_nationality
Guest identity data
oci_address / oci_country
Guest address data
oci_guest_phone
Phone number(s) from check-in
oci_id_type_uploaded
Uploaded ID document type(s)
oci_arrival_time / oci_departure_time
Expected arrival / departure
oci_bed_wishes
Bed preferences
oci_invoice_address
Invoice address from check-in
oci_submission_date
When check-in was submitted
has_completed_checkin
Whether check-in was submitted
π Property variables
unit_name
Friendly name of the unit
unit_floor / unit_door_number
Location inside the building
object_address / object_city / object_country
Property address
object_max_guests_capacity
Maximum guest capacity
checkin_time / checkout_time
Standard times for the unit
wifi_login / wifi_password
Wi-Fi credentials
taxi_number
Local taxi phone number
π Access code variables
building_code
Building entrance code
unit_door_code
Unit door code
garage_door_code / basement_code
Additional access codes
custom_code
Custom property access code
ttlock_passcode
Booking-specific smart lock passcode, generated automatically by the lock integration
π Templates vs Rules (important)
Define what is sent
Define when & to whom
Can be reused
Trigger messages
No timing
Time-based or event-based
A template is not associated with any event or unit until you create a rule.
π± WhatsApp Template Approval
When using WhatsApp templates, they must be approved by Meta before they can be sent. If a template is not yet approved, you will see a message indicating that it was skipped due to pending approval.
π Deleting a template
Open the template, click Remove, and confirm the warning.
β Next step: Message Rules
Once your template is ready:
β‘οΈ Go to Automatic Message Rules
There, you will:
choose when the message is sent
select which properties and channels it applies to
define conditions and timing
Last updated