> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://support.uplisting.io/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Automated Messages with Safeguest

# Automated Messages with Safeguest

To send your SafeGuest verification link automatically to guests, you can use Automated Messages together with SafeGuest custom tags and 'SafeGuest Status' filters.  This guide explains how to set this up.

When Safeguest is enabled, the Safeguest verification link is **not** sent automatically. To send the verification link to guests, you’ll need to include it in your preferred Uplisting automated messages.

To do this, add the following custom booking attribute tag to your automated message for the Safeguest enabled listing:

**`safeguest_verification_link`**

This tag can be found under *Custom booking attribute tags* on the Outbound page **[here](https://app.uplisting.io/outbound/messages)**. Once added to an automated message, the link will be sent to guests when that message is triggered.

![](https://files.readme.io/5ed1eec70cfa35330da5ff0406356aa9b14e9bf817295602e33956e28e8627d7-image.png)

You can include this in:

* New Booking messages
* Pre-arrival messages
* Reminder messages

This ensures guests automatically receive the SafeGuest verification link.

The \*\*`safeguest_verification_link` \*\*directs guests to the Safeguest verification page where they can complete their identity verification and deposit or waiver selection. ([**See the Guest Verification Flow guide**](https://uplisting.crisp.help/en/article/guest-verification-flow-1vtjfvk/))

> **📘**
> NOTE:
> This custom booking attribute tag cannot be edited

## 'Safeguest Status' Filter

Automated messages can also be triggered based on **`SafeGuest Status`** filter

![](https://files.readme.io/af7b7a0aa62e07bdc1f3f788f1cf848e9e9b6cf41479374892fc42b8f114b161-image.png)

Available filters:

* Low risk
* Medium risk
* High risk
* Pending

![](https://files.readme.io/6d452f6b330055a5f9ed4336580242672c39757a0236fc17158ccd5e3528aa4f-image.png)

Messages will **only** be sent when the configured conditions are met. If one of the conditions is **not** met, the message will not be sent

## **⚠️ Important: Updating Automated Message Filters When Using SafeGuest**

When using SafeGuest, guest verification and security deposit collection are handled entirely on the SafeGuest platform.

> **📘**
> Because of this:
> Uplisting's Guest Identity and Security Deposit features are disabled
> These features **cannot** run at the same time as SafeGuest

## What This Means

If you previously configured automated messages using the following Uplisting filters, they will no longer work *after enabling SafeGuest:*

#### **Guest Identity Filters**:

* Guest identity is verified
* Guest identity is not verified

#### **Security Deposit Filters**:

* Security deposit has been collected or is not required
* Security deposit needs payment information
* Security deposit payment method has been provided
* Security deposit collection attempt failed

These filters **only** work with Uplisting’s **native** Guest Identity and Security Deposit features, **not** SafeGuest.

## What You Should Use Instead

> **📘**
> When using SafeGuest, you may need to update your automated messages to use the '**SafeGuest Status**' filters
> These filters are designed ***specifically*** for SafeGuest verification and deposit workflows.
> **Example**:
> * SafeGuest Status = Low
> * SafeGuest Status = Medium
> * SafeGuest Status = High
> * SafeGuest Status = Pending

### For Existing Bookings (Pre-Safeguest)

**If you enabled SafeGuest after** bookings were already created, your existing automated messages that rely on Uplistings security deposit and guest identity features, may stop sending.

**This happens because:**

The automated messages rely on Uplisting's **native** Guest Identity or Security Deposit filters, but these native features are disabled when SafeGuest is active, as they **cannot** run simultaneously.

#### **How to Fix**

Update your automated messages:

* Remove **native** Guest Identity filters
* Remove **native** Security Deposit filters
* Add **SafeGuest Status** filter and select the appropriate risk scores (see the [Risk Scores guide](https://uplisting.crisp.help/en/article/risk-scores-971iav/) )
* Save your message

Once updated, messages will be sent correctly to **future** bookings.