Applying message conditions to automated messages

When setting up automated messages, you use two types of conditions: reservation conditions and message conditions.

  • Reservation conditions determine if the entire automation schedule applies to a reservation.
  • Message conditions apply to each individual message within that automation, determining if and when that specific message should be sent.

Read below to see the message conditions and how to combine them to define which event triggers a message in the automation.

How message conditions are applied

Guesty adds a message automation to a reservation at confirmation if the reservation meets the reservation conditions.

Once the automation is added, Guesty triggers each message independently based on its specific message conditions. If you set multiple conditions for a message, Guesty sends it at the scheduled time only if all conditions are met.

If the scheduled time arrives but the conditions aren't met, the message moves to a "waiting" status. It will send if the conditions are fulfilled later, or it will expire if they are never met.

For example:

You set up a message with the following conditions:

  • Scheduled to send 1 day after confirmation
  • Number of guests is more than 4
  • ETA is provided

How it works:

  • If the reservation has 5 guests and includes an ETA, the message sends 1 day after confirmation.
  • If the guest hasn't provided an ETA by the scheduled time, the message waits. 
    • If the guest provides an ETA later, the message will be sent immediatly.
    • If the guest never provides an ETA, the message expires and is never sent.

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

The status of automated messages based on their conditions is reflected in the automated messages widget.

When a condition is considered met

When you use message conditions, the condition status in the automated messages widget might display as pending, even after the guest completes the required action. For most conditions, Guesty evaluates the status only at the scheduled execution time, not when the action occurs.

For example:

A reservation is created on February 13, and the guest's check-in is on February 20. You set up an automated message with the "Guest App check-in form submitted" condition scheduled to send one day before check-in (February 19).

How it works:

  • The guest completes the Guest App on February 16. The Guest App status changes to met across all widgets.
  • However, the message condition status remains pending until the scheduled sending time on February 19. At that time, Guesty evaluates the condition, marks it as met, and sends the message.

Review the evaluation time for conditions below:

Condition type Evaluation timing
Custom fields At scheduled execution time
Check-in form completed At scheduled execution time (not before)
Agreement form completed At scheduled execution time (not before)
Guest review submitted At scheduled execution time
Available nights At scheduled execution time
Reservation was fully paid When reservation payment status changes

Expiration rules

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

Agreement completed

Toggle on to send messages only if the guest signed their rental agreement.

You can use this condition to ensure legal requirements are met before sending arrival details.

Authorization hold attempt

An authorization hold is a temporary amount you can charge guests to ensure they pay when payment is due. Send messages 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, its status may change over time.

AutoComply Guests submission status

Send messages based on the status of the guest's AutoComply submission.

Select from the following statuses:

  • "Pending"
  • "In progress"
  • "Completed"
Available nights before/after stay

Note:

This premium feature is available to all accounts.

Send messages to reservations based on whether there are available nights before or after the guest’s stay. This helps you maximize occupancy and increase potential revenue.

Use this condition to offer guests an extra night at a discount if the property is vacant before their arrival or after their departure.

Important:

The system ignores manual calendar blocks when checking for available nights. If you block a date manually, Guesty considers it available for this condition.

Customize this condition as follows:

  • Availability is before check-in, after check-out, or both.
  • Availability is on any day of the week, only weekdays, or only weekends.
  • The maximum length of the gap between reservations.

For example:

According to the condition below, the message sends only if:

  • The available nights are before check-in.
  • The gap nights overlap any day of the week.
  • The gap is two nights or less. If there is a gap of more than two nights, the message does not send.

Check-in form submitted

Toggle on to send messages only if the guest has completed their check-in form.

You can use this condition to release access information only after you receive the guest's details.

Note:

This condition supports the legacy Document mis sentanager. It also works for the Guest App if you only have one Guest App on your account. If you use multiple Guest Apps, use the "Guest App check-in form submitted" condition.

Guest App check-in form submitted

Add messages to reservations based on the Guest App associated with the reservation.

If you use multiple Guest Apps on your account, this ensures the automated message matches the specific Guest App.

Guest hometown

Send messages based on the guest's city of origin.

You can use this condition to remind locals of strict party policies or house rules.

Note:

This condition only applies when the booking channel provides the hometown or if you add it manually in Guesty.

Guest preferred language

Send messages based on the guest's preferred language.

You can use this condition to create language-specific templates (for example: a Spanish template with the condition "Preferred language is Spanish").

Important:

  • Airbnb, Booking.com, and Vrbo: The guest’s preferred language imports and saves in Guesty, automatically populating the preferred language field.
  • All other channels: The guest's preferred language field does not populate automatically. Complete it under guest details.

Learn more about setting a default preferred language for guests.

Guest provided an ETA

Toggle on to send messages based on whether an ETA exists on the reservation.

You can use this condition to remind guests to provide their arrival time if they haven't done so yet.

Guest provided an ETD

Toggle on to send a message based on whether an ETD exists.

You can use this condition to remind guests to provide their departure time if they haven't done so yet.

Guest submitted a review

Note:

This message condition applies only to Airbnb, Booking.com, and Vrbo reservations.

Toggle on to send messages based on whether the guest reviewed you. Set a specific rating for the condition.

You can use this condition to remind guests to leave a review if they haven't yet, or thank guests who left a 5-star review.

GuestVerify screening status

Send messages based on the outcome of a GuestVerify screening.

Use this condition to prevent unverified or high-risk guests from receiving check-in details and to automate follow-up communication.

Select from the following statuses:

  • "Passed": Sends check-in instructions and key codes.
  • "Pending": Reminds the guest to complete verification.
  • "Failed" or "Partly failed": Notifies the guest or alerts your team.
Host total payout

Send messages based on the total amount the guest paid (in listing currency).

You can use this condition to offer VIP services or a special thank you to guests who pay more for their reservation to make sure they feel their money was well spent and encourage them to return.

Is a returning guest

Toggle on to send messages if the guest stayed at this property before.

You can use this condition to send a "welcome back" note or skip the basic instructions they already know.

Number of guests

Send messages based on the confirmed number of guests.

For example:
Your condition applies to four guests.
Is The message sends when the total number of guests is exactly four guests.
Is not The message sends when the number of confirmed guests is any number except the specified one.
Is more than The message sends when the total number of guests is higher than four guests (five guests or more).
Is less than The message sends when the total number of guests is lower than four guests (three guests or fewer).
Planned arrival

Send messages based on the guest's estimated time of arrival (ETA). If no ETA exists, Guesty uses the default check-in time.

You can use this condition to offer early check-in services to guests arriving early or send late-night access instructions to guests arriving after hours.

Planned departure

Send messages based on the guest's estimated time of departure (ETD). If no ETD exists, Guesty uses the default check-out time.

You can use this condition to offer late check-out for a fee, or send specific instructions for early morning departures.

Reservation payment

Send automated messages based on the success or failure of general reservation-related payments. This condition covers common payment scenarios beyond authorization holds and security deposits, allowing you to automatically notify guests about their payment status.

This condition applies to all payments processed through any payment processor. You can choose from three status options:

  • Not successful (failed): The reservation has at least one failed general payment and no successful payments or payments awaiting authentication.
  • Successful: The reservation has at least one successful general payment.
  • Awaiting authentication: The reservation has at least one payment awaiting authentication.

You can set up different messages for each payment status to notify guests accordingly.

Reservation was fully paid

Toggle on to send messages to guests who paid in full.

You can use this condition to send check-in instructions or door codes after payment confirmation.

Important:

Don't use this condition when sending check-in instructions for Airbnb reservations because they are marked as fully paid 24 hours after check-in. Use the "Channels and sources" reservation condition to exclude Airbnb.

Security deposit attempt

A security deposit is a temporary amount you can charge guests to protect you against damages during their stay. Send 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, its status may change over time.

Should review

Note:

This message condition applies only to Airbnb and Vrbo reservations.

Toggle on to send messages based on whether the auto review feature is active for this guest.

Custom message conditions

For specific scenarios not covered by default conditions, use reservation custom fields.

Create a custom field with a yes/no field type, add it as a message condition, and activate it before the scheduled sending time for the relevant reservation to ensure 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