Now that you saw the Workflow Automation (WFA) in action, let’s look into the respective filters and functionalities. We will set up some more example use cases in the next articles.
- Triggers
- Jobs
- Add a tag to a case
- Call an URL
- Change case custom field
- Change priority of the case
- Change case status
- Delete author’s name of a message
- Delete content of a message
- Delete end user’s name in all identities
- Inactivity Pop-up
- Mask credit card number in the message content
- Move the first case in the queue to another queue
- Reroute case to a different queue
- Reset routing
- Send message
- Send notification email
- Send satisfaction survey
Triggers
One of the most important parts of Workflow Automation is triggers. They define when the jobs will be executed once the conditions are met. In other words, the triggers are the fuel of the automation process.
The triggers are defined by means of the events, every event defines a specific action that will give way to the execution of the jobs.
First, go to the Triggers and click on ‘Add’ to create a new one.
Name the trigger and choose the desired event
Here are the event descriptions:
Case routing queue changed - this event will fire the trigger when the case has been changed from a queue to another.
The case created -this event will fire the trigger when a new case is created in Brand Embassy.
Case status changed - This event will fire the trigger when the status of the case has changed.
Before the case closed - This event will fire the trigger before the case will be closed.
Message created - This event will fire the trigger when a message is created.
Case Inbox Assignee changed – This event will fire the trigger whenever the inbox assignee of a case changes.
Triggered by API – This event is designed to be used whenever you are using WFA to create proactive popups that will appear within your live chat.
Pop-up clicked – The trigger is fired when the customer clicks on the popup to start the conversation (can be used to send a follow-up message).
Chat window opened – The trigger is fired when the customer clicks on chat the widget to open chat window and starts a conversation (can be used to relay information to the customer without creating a case).
Visitor page view - The trigger is fired when a web visitor arrives on a page.
Next, we can set up the delayed execution which determines the waiting time to validate and fire the trigger. This is a useful way to avoid neglected cases by the Chatbot. Imagine the Chatbot doesn’t reply for any reason so you want to re-route the case to the agents. With this setup, we say “check the case 30 seconds after it was created”. Then, in conditions and jobs, we set up the rest of the automation so a case without a reply gets to an agent queue.
Jobs
Jobs are the workers that run once they are fired by the triggers.
To create a job, go to jobs in the settings section and click on ‘Add’
Name the job and select the action, every action has parameters associated you need to set up. Let’s explore the actions you can choose as jobs.
Add a tag to a case
You are probably familiar with the auto-tagging feature, one of the first automated processes in Brand Embassy. Now, we are taking this feature to the next level with Workflow Automation. By selecting ‘add a tag to case’ you can add tags to cases based on the source, case status or queue. Awesome right? You only need to specify the tag you want to add to the case. This is especially useful if you want to review all the cases handled by the Chatbot for example.
Call an URL
With Call a URL you can execute an external URL to perform any action you want by using the post and case ID. It allows you to set up an external URL endpoint with this data to validate them when the job is triggered. As an example, let’s say you have a queue for high-priority cases, and you set up a trigger when a case is created in this queue and you want to receive an SMS on your phone every time this happened. As the action in your job, you can choose ‘Call an URL’ with the parameter ‘Post’, and the URL of the application will send the SMS with the endpoint Case ID.
Change case custom field
Change case custom field job allows you to change any specified custom field on certain cases to a value that suits your needs.
Change case priority in the queue
Changing the priority can help you to organize the cases in the agent queue so they work as efficiently as possible. To do so, you only need to define the new priority value.
Change case status
neglected cases are not a problem anymore! With this job, you can change your cases from pending back to new so the agents follow up on them.
Delete author’s name of a message
This job deletes the customer’s name. It can be used for GDPR, TTL, or other security reasons. When using this job, the customer’s name is permanently deleted from the platform.
Delete content of a message
This job deletes the whole content of the message. It can be used for GDPR, TTL, or other security reasons. When using this job, the content of the message is permanently deleted from the platform.
Delete end user’s name in all identities
This job deletes the customer’s name from everywhere, CRM and Conversations. It can be used for GDPR, Time to Live, or other security reasons. When using this job, the customer’s name is permanently deleted from the platform.
Inactivity Pop-ups
This job is created for the Live chat. After some time of inactivity, a pop up will show up. You may set the time interval you’d like the popups to show according to your needs.
Mask credit card number in the message content
This job recognizes the credit card numbers within the message and masks them.
Moves first case in a queue to another queue
Sometimes you do not want to re-route all cases but only the first case waiting in the queue. To set up this action you only need to specify the receiver queue or the new queue where the case will be re-routed.
Reroute case to a different queue
This action allows you to redirect cases to a different queue when the conditions are met. You simply choose the destination queue.
Reset routing
The queue routing works like a cascade where the cases go through each queue until they meet all the filters and are routed. This action allows you to reset the routing and make the cases go through the cascade again and try to match against the queues again. You can exclude either the current or the other queues.
Send message
Thanks to the send message job you can create automated notes to be sent to your customers as desired. For example, you can let your customers know the real status of their cases by sending a message when the case has been escalated, or that your support team is currently not working. You can also select the author of the message so everything is right in the reports.
Send notification email
This job lets you send automated notification emails based on your needs. You can use a variety of different placeholders in the subject and body of the notification email. For example, if you’d like to send the case number, you can use {{caseId}}, which will automatically send the case number to the customer.
Send Satisfaction Survey
The new Satisfaction Survey solution offers more possibilities for customization. If you would like to know more about please check our article here. Select the survey type between Standard BE survey, 3rd party provider URL or custom integration.
Assign Contact to Inbox
This Job lets you assign cases to a specific agent or chatbot.
Comments
0 comments
Please sign in to leave a comment.