Trigger Events are actions that act as a cue for the Workflow Automation to execute its action. All events need to be matched in order for the trigger to be activated. If multiple events were selected, all conditions should be met in order for the actions to be executed.
Disposition – Action will be trigger based on the status selected by the agent.
Redisposition – Action will be trigger based on the redisposition status selected by the agent.
Term Reason (Callee, Caller and System) – Trigger action will execute depending on who terminate the call.
Call Type (Manual and Outbound Auto Dial) – Trigger action will execute based on call type.
Lead Action (Create, Delete and Save) – Trigger will execute depending on the action made on the lead.(Note: Action will not get triggered in case of Lead Upload)
Call Count - Trigger action will execute based on the number of specified called count and the selected operator.
Field – Trigger action will execute based on the selected fields and operator.
Lead Status – Trigger action will execute based on the status of the lead. (Only available in Email and List relation)
Email Event (Open) – trigger action will execute once the email was opened by the recipient. (Only available in Email and List relation)
Submitted By - Action will be triggered based on the specific user/s who submitted the action.
Hopper Expired - This will remove the leads from the hopper once it expires from the time it was inserted.
Note: You can identify the Trigger Events and Actions if it's Active or Inactive by its text color. If it's Blue, it means it's Active and if it's Red, it's Inactive.
For the boxes of Action and Event with Field type, it will show the list of configured fields.
This will applicable to both Searchable and Non Searchable Fields.
This will applicable to both Searchable and Non Searchable Fields.
Example:
What the Event will look like after saving it.
================================================================
If the Admin creates a Workflow Automation that will create a loop, the system will automatically turn off the Workflow after creating 100 logs to prevent from keeping on processing the action.
Sample Workflow setup that will create a loop.
Event: Lead Save
Trigger: Field
Trigger: Field
(Logic: When the agent clicks on the Apply Changes button, the system will change the value on the field selected on Trigger Action. From the back end, the system also does "auto-save" this will then create a loop on the Workflow.)
After creating 100 workflow logs, the system will automatically turn off the Workflow and will show a notification message.