SENDSESSIONTEXT

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

For digital Any channel, contact, or skill associated with Digital Experience. channels with ACD, this action can be used to include a message in an SMS interaction. You can configure who receives the message as well as who the message appears to be from. Messages sent with this action are included in SMS Messaging transcripts.

For example, you could use this action to provide an after-hours message for inbound SMS messages received when your contact center is closed.

Supported Script Types

SMS

Input Properties

These properties define data that the action uses when executing.

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.
Room ID	Associates the message with a specific interaction "room".
From ID	Associates the message with a specific sender.
Message	The text of the message you want to send. You can use a variablefor this field.
Chat Target	Allows you to specify the message sender and recipient as shown in the interaction itself. Choose one of the following from the drop-down: Caller from System: A system-generated message is sent to the SMS contact only. The contact sees that the system originated the message. This option would be appropriate for a message such as, "An agent will be with you shortly." Agent from System: A system-generated message is sent to the agent only. The agent sees that the system originated the message. Both from System: A system-generated message is sent to both the agent and the chat contact. Both parties see that the system originated the message. Caller from Agent: An agent-generated message is sent to the chat contact only. Both parties see that the system originated the message. Both from Agent: An agent-generated message is sent to both the agent and the chat contact. The contact sees that the agent originated the 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
Default	Path taken unless the script meets a condition that requires it to take one of the other branches. It is also taken if the action's other branches are not defined.
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.