Send an email notification to User(s).

Add the message to a previously created Partner Level Queue.

Add the message to a previously created Client Level Queue.

Remove the message from a Partner Level Queue that was set up previously.

Remove the message from a Client Level Queue that was set up previously.

Assign the message to anyone of the Users or Users in the Group(s).

Assign the message based on user/group’s status i.e availability, the number of messages assigned to each assignee or other conditions such as the channel, account, etc.

Assign the message to a specific user.

Send email notifications to the Users selected based on the Volumetric Condition that must be first set up under the Basic Information of the Condition Section where you can choose the number of messages received in a specific duration to trigger an email notification.

Refers to the descriptive terms associated with the message that has been created within Custom Fields as message tags. (See 

Custom Fields

).

The tone of the message. The sentiment options are as follows: positive, negative, and neutral.

Refers to whether the message is spam or not.

Automatically tagging a message.

Refers to the notification sent on the Mobile App.

Descriptive terms associated with the message that have been created within Custom Fields as message tags. (See 

Custom Fields

).

Add the message sender to the Client level profile lists that have been set up.

Add the message sender to the Partner level profile lists that have been set up.

To copy the case related information such as the case number, case status or any case related custom field values.

To copy the custom field values associated with the outbound post. When you had published using Sprinklr then you must have associated a few custom field values with the post.

When you reply to an already grabbed message in the Engagement Dashboard that has a custom field associated with it and you want to copy that custom field.

Copies the custom field associated with any message, that means not only the messages that are grabbed in Engagement Dashboard but also considers the messages that are grabbed in Listening from various social media sources.

To copy the custom field information associated with the parent post. Here the parent post varies based on the comments and replies. If you are commenting on the post, then the post is considered as parent, and if you are replying to a comment, then the comment is considered as a parent post.

To copy the custom field information associated with any incoming messages that are grabbed in the Engagement Dashboard.

To copy the custom field information associated with the Message sender of the grabbed message. This is a profile level custom field. You can set the custom field in Message level or Case level.

To copy the custom field information associated with the brand account (The accounts that are added in the Sprinklr)

To copy the custom field information associated with the assigned user. When a message is assigned to any user via a rule, macro, or manually.

To copy the Profile level custom field information that is associated with a particular case. When a case is created with a profile. For example, you can create a profile level case which can contain messages that are sent from one profile.

To copy the custom field associated with the logged in user who had engaged with the messages.

Outbound post. When a message is published from within the Sprinklr platform.

The message that replies to already grabbed message in the Engagement Dashboard.

Parent post could be the first post or the comments based on the engagement type. If you are commenting on the post, then the post is considered as parent, and if you are replying to a comment, then the comment is considered as a parent post.

Any incoming messages that are grabbed into Sprinklr.

Message sender of the grabbed message. This is a profile level custom field.

The most recent fan message in the conversation thread.

A case associated with a profile.

A case can have multiple messages within a single case. 

A case can have multiple brand messages and does not include fan posts.