REPLY

This help page is for Studio. This information is also available for Desktop Studio.

Automatically sends a reply message to the email sender. Automatically sends a reply message to the email sender. The recipient address is taken directly from the original message header.

Dependencies

Use caution when using the Reply action with CXone Mpower emails that have a point of contact email address as the From address. Doing this will cause a repetitive loop.
Reply is a terminal event (meaning it ends that contact).

Supported Script Types

Properties

Property	Description
Add Caption	Enter a short phrase that uniquely identifies this action in the script. The caption appears on the script canvas under the action icon.
Message	The text of the message you want to send. You can use a variable for this field.
Include Original Msg	Determines whether the original message will be appended to the reply text. If enabled, the original message is appended with the standard style that includes the original message header. If disabled, the original message is not included. In Value Mode: Click to On to enable. Leave set to Off to not include the original message. In Expression Mode: Enter true to enable. Leave set to false to not include the original message.

Property

Description

Add Caption

Enter a short phrase that uniquely identifies this action in the script. The caption appears on the script canvas under the action icon.

Message

The text of the message you want to send. You can use a variable for this field.

Include Original Msg

Determines whether the original message will be appended to the reply text. If enabled, the original message is appended with the standard style that includes the original message header. If disabled, the original message is not included.

In Value Mode: Click to On to enable. Leave set to Off to not include the original message.

In Expression Mode: Enter true to enable. Leave set to false to not include the original message.

Result Branch Conditions

Result branch conditions allow you to create branches in your script to handle different outcomes when an action executes.

Condition	Description
Error	Path taken when the action fails to execute properly. For example, when there is an unexpected problem such as poor connectivity, syntax errors, and so on. The _ERR variable, with a single underscore character, should be populated with a condensed explanation of the problem.