Applying message conditions to automated messages

While reservation conditions apply to an entire message automation, message conditions are rules that apply to a specific message within a message automation. Message conditions specify if the message is sent based on the defined criteria—for example if the guest submitted a check-in form, or if the number of guests exceeds 4—they do not determine or affect the time the message is sent.

How message conditions are applied

A message automation is added at reservation confirmation when the reservation meets the defined reservation conditions. Each automated message is triggered independently based on its specific message conditions. If multiple conditions are set, the message is sent at the scheduled time once all are met. If the scheduled time passes and conditions are still not met, the message moves to a waiting status until the conditions are fulfilled or the message expires.

For example:

You set up a message with the message conditions:

  • Scheduled to send 1 day after confirmation
  • Only if the number of guests is more than 4
  • ETA is provided
How it works:
  • If the reservation has 4 or more guests and includes an ETA, the message is sent 1 day after confirmation.
  • If the conditions are not met at that time, the message enters a waiting status and will be sent if the conditions are later fulfilled.
  • If the conditions remain unmet until expiration, the message will not be sent

If the scheduled time of the message has already passed when the reservation is confirmed, the message will be sent immediately at confirmation.

For example, if a message is scheduled to be sent 1 day before check-in, but the reservation is confirmed after the scheduled time 8 hours before check-in, the message will be sent immediately at confirmation.

The status of automated messages based on their conditions will reflect in the automated messages widget. Messages expire under the following conditions:

  • Messages related to check-out expire 7 days after their scheduled time
  • Messages unrelated to check-out expire at check-out

Types of message conditions

There are two types of message conditions: default message conditions and custom message conditions.

Default message conditions

Number of guests

Add messages to reservations based on the number of guests.

Example 1:
Let's say that your condition is relevant to 4 guests.

Is The message will be sent when the total number of guests confirmed in the reservation is equal to 4 guests.
Is not The message will be sent when the number of guests confirmed is either more than or less than 4 guests.
Is more than The message will be sent when the total number of guests confirmed is higher than 4 guests—meaning 5 guests or more.
Is less than The message will be sent when the total number of guests confirmed is lower than 4 guests—meaning 3 guests or less.
Reservation was fully paid

Add messages to reservations based on whether or not the guest paid for the reservation: Toggle on or off.

You can use this condition to make sure the check-in instructions are only sent to guests that have paid for their reservation, giving only them access to the property.

Important:

Do not use this condition when sending check-in instructions for Airbnb reservations since they are only marked as fully paid 24 hours after check-in. You can use the "Channels" reservation condition to exclude Airbnb in this case.

Check-in form submitted

Add messages to reservations based on whether or not the guest has completed their check-in form: Toggle on or off.

You can use this condition to make sure the check-in instructions are only sent to guests that have completed their check-in form, giving only them access to the property.

This condition can also be applied when using the Guest app.

Agreement completed

Add messages to reservations based on whether or not the guest signed their rental agreement: Toggle on or off.

You can use this condition to make sure the check-in instructions are only sent to guests that have signed their rental agreement, giving only them access to the property.

Planned arrival

Add messages to reservations based on the guest's planned arrival. If the reservation does not have an estimated time of arrival (ETA), the condition will be checked against the reservation's default check-in time instead.

You can use this condition to send a message to guests that are arriving before the designated check-in time to charge them for early check-in. Similarly, if needed, you can use this condition to send specific check-in instructions to guests that are arriving late at night.

Guest provided an ETA

Add messages to reservations based on whether or not the guest has given an estimated time of arrival (ETA): Toggle on or off.

You can use this condition to remind guests to provide an ETA.

Planned departure

Add messages to reservations based on the guest's planned departure. If the reservation does not have an estimated time of departure (ETD), the condition will be checked against the reservation's default check-out time instead.

You can use this condition to send a message to guests that are checking out after the designated check-out time to charge them for late check-out. Similarly, if needed, you can use this condition to send specific check-out instructions to guests that are leaving late at night.

Guest provided an ETD

Add messages to reservations based on whether or not the guest has given an estimated time of departure (ETD): Toggle on or off.

You can use this condition to remind guests to provide an ETD.

Guest preferred language

Add messages to reservations based on the guest's preferred language. For example, if the guest’s preferred language is Spanish, you can create a message template in Spanish and add the condition “Preferred language is Spanish” so the message will only be sent to guests with Spanish preferred language.

Important:

The guest preferred language field is not populated automatically, it must be filled out under Guest Details.

Guest hometown

Add messages to reservations based on the city the guest is originally from. You can use this condition to selectively target guests that book a reservation in the city they live in, particularly a short stay, to emphasize their understanding of your house rules, party restrictions, etc.

Note:

This condition is only supported when the hometown is provided by the booking channel or added manually in Guesty.

Is a returning guest

Add messages to reservations based on whether or not a guest has stayed at this property before: Toggle on or off.

You can use this condition to adapt your messages to the experience of returning guests that have already received the basic messages in the past.

Host total payout

Add messages to reservations based on how much the guest paid for the reservation: equals/does not equal/is more than/is less than/is between X listing currency.

You can use this condition to create unique messages for guests that pay more for their reservation to offer additional services free of charge, for example, or a VIP experience to make sure they feel their money was well spent and encourage them to return.

Should review

Note:

This message condition applies only to Airbnb reservations.

Add messages to reservations based on whether the guest should be auto-reviewed. Use the toggle to enable or disable the auto review feature for a guest on the reservation page.

Guest submitted a review

Note:

This message condition applies only to Airbnb reservations.

Add messages to reservations based on whether the guest has already submitted a review of their stay and your property: Toggle on or off. You can use this condition to remind guests to leave a review only if they have not left one yet.

Security deposit attempt

A security deposit is a payment youprotects you in case of damages or other costs during a stay. A reservation can have multiple deposits and the status of a security deposit can change.

You can trigger a message at a supported scheduled event only if the charge failed or succeeded.

Authorization hold attempt (Pilot users only)

An authorization hold is a temporary amount you can charge your guests to ensure they pay when payment is due. You can trigger a message at the scheduled event based on whether the charge failed or succeeded.

  • An authorization hold fails if the reservation has at least one failed authorization hold attempt and no successful ones.
  • An authorization hold succeeds if the reservation has at least one successful authorization hold attempt.

You can set up different messages for successful and failed authorization hold attempts to notify guests accordingly. Since a reservation can have multiple authorization holds, their status may change over time.

Security deposit attempt (Pilot users only)

A security deposit is a temporary amount you can charge your guests to protect you against damages during a stay. You can trigger a message at the scheduled event based on whether the charge failed or succeeded.

  • A security deposit fails if the reservation has at least one failed security deposit attempt and no successful ones.
  • A security deposit succeeds if the reservation has at least one successful security deposit attempt.

You can set up different messages for successful and failed security deposit attempts to notify guests accordingly. Since a reservation can have multiple security deposits, their status may change over time.

Custom message conditions

You can use reservation custom fields that have a yes/no field type to create message conditions for specific cases.

Create the custom field, add it as a message condition and activate it before the scheduled sending time for the relevant reservation to make sure the message is added to it. Learn more about using custom fields for reservations as conditions in messages.

Was this article helpful?
0 out of 1 found this helpful