Email

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

Generates a new email.

Dependencies

The maximum number of outbound emails that a specific business unit High-level organizational grouping used to manage technical support, billing, and global settings for your CXone environment can generate is 2000 per hour.
Attachments must be stored in your business unit directory or a sub folder.
Even though scripts can only handle one media type A medium, such as voice, email, and chat, through which a contact connects with an intended recipient. of contact, an email may be generated in any type of media script.


Generic	Email	Chat	Phone	Voicemail	Work Item	SMS	Digital

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.
Mail Server	This property defaults to a built-in mail server listed as Automatic.
Sender Name	The name of the sender.
Sender Address	The email address of the sender. The address is not required to be valid, but it must have @niceincontact.com as the domain. If this action does not have a sender address, the email will not be sent.
Recipient	The email address to receive the message.
CC Recipient	The email address(es) for the carbon copy recipient(s).
Subject	The subject of the email. If a subject is not entered, the email will not be sent.
Body	The content of the message to be sent to the recipient.
HTML	This property is optional. The HTML code of the body of the document. If the recipient's mail reader is not capable of showing HTML, they will see the plain Body text.
Attachments	Lists the file name and path for each attachment for the message. Separate multiple filenames with a semicolon. Attachment files must exist on the CXone file server. You can upload files on the Browse ACD Files page or using Desktop Studio.
Error Msg Var	The name of a variable to receive the mail server response text in case of an error.

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.
OnError	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.
OnInvalidFormatEmail	Path taken when the email content is in an invalid format.