Updated via BpDeleteTranslateTags script |
Wyler.metge (talk | contribs) Updated via BpClonePage extension. Source page: draft:Contact-center-administrator-guide/WorkflowEntries |
||
| Line 1: | Line 1: | ||
= Workflows= | = Workflows = | ||
After | After interactions are completed, dispositions and other such actions can start scenarios that automate what happens next. For example, setting a particular disposition for an interaction could trigger the following series of events to happen: | ||
* Send a survey to the customer | * Send a survey to the customer | ||
* Wait a specified amount of time (e.g., 30 minutes, 1 day, 1 week, etc.) | * Wait a specified amount of time (e.g., 30 minutes, 1 day, 1 week, etc.) | ||
* Send a follow-up email to the customer. | * Send a follow-up email to the customer. | ||
This series of events is called a ''workflow'' | |||
This series of events is called a ''workflow''; workflows are [[#Triggers|triggered]] by agents selecting dispositions for interactions. In order for a workflow to be invoked, a [[#Workflow_Entries_Screen_Properties|Workflow Entry]] must be configured. | |||
Workflows are created in the Contact Center Administrator application and are edited in the Workflow Builder application. Workflows will handle any necessary follow-ups, depending on the interaction’s disposition type. Such follow-up actions include setting context variables, sending an email, sending a text message, scheduling an event, clearing a scheduled event, and making an external request (or internal API call). Workflows reduce the workload of agents while following up with customers and gathering data in a consistent way. | Workflows are created in the Contact Center Administrator application and are edited in the Workflow Builder application. Workflows will handle any necessary follow-ups, depending on the interaction’s disposition type. Such follow-up actions include setting context variables, sending an email, sending a text message, scheduling an event, clearing a scheduled event, and making an external request (or internal API call). Workflows reduce the workload of agents while following up with customers and gathering data in a consistent way. | ||
For more information, see the [[Workflow-builder-reference-guide/Purpose|''Workflow Builder Reference Guide'']]. Note that variables may be used when configuring both scenarios and workflows. For more information, see the | For more information, see the [[Workflow-builder-reference-guide/Purpose|''Workflow Builder Reference Guide'']]. Note that variables may be used when configuring both scenarios and workflows. For more information about variables, see the list of [[Workflow-builder-reference-guide/Variables|Workflow Variables]]. | ||
| Line 15: | Line 17: | ||
== Workflow Entries Screen Properties == | == Workflow Entries Screen Properties == | ||
Workflows are added to services as workflow entries. To add a workflow, navigate to ''Configuration > Workflows'' and select the '''+''' button. | Workflows are added to services as workflow entries. To add a workflow, navigate to ''Configuration > Workflows'' and select the '''+''' button. | ||
=== Name === | === Name === | ||
Every workflow entry needs a ''name''. This field is mandatory. | Every workflow entry needs a ''name''. This field is mandatory. | ||
=== Type === | === Type === | ||
Type of workflow. Currently only post-processing workflows are supported. The email pre-processing workflow type is reserved for future use. | Type of workflow. Currently only post-processing workflows are supported. The email pre-processing workflow type is reserved for future use. | ||
<!--''Type'' lets you define when a workflow is executed; the options are ''post-processing'' and ''pre-processing''. Note that the ''Type'' property is available in contact centers where workflows are allowed on inbound emails. For more information, contact your service provider. | |||
==== Post-processing ==== | |||
The ''Post-processing'' option allows workflows to be excuted after interactions are completed and triggered by dispositions; this option is available for all interaction types (i.e., chat, email, voice). | |||
==== Pre-processing (email only) ==== | |||
The ''Pre-processing (email only)'' option allows workflows to be executed before email interactions begin; this option has one trigger: [[#New_email_arrives|New email arrives]].--> | |||
=== Service === | === Service === | ||
''Service'' is the name of the service with which the workflow entry should be associated. | ''Service'' is the name of the service with which the workflow entry should be associated. | ||
=== Triggers === | === Triggers === | ||
''Triggers'' are the events that cause a configured workflow to be launched. To add triggers, click '''add''', select the available triggers and their properties, and select the green check mark to apply your changes. | ''Triggers'' are the events that cause a configured workflow to be launched. To add triggers, click '''add''', select the available triggers and their properties, and select the green check mark to apply your changes. | ||
| Line 35: | Line 44: | ||
* Average sentiment | * Average sentiment | ||
==== Interaction ends with disposition ==== | ==== Interaction ends with disposition ==== | ||
If this trigger is selected, you must select a specific disposition from the drop-down list. | If this trigger is selected, you must select a specific disposition from the drop-down list. | ||
| Line 42: | Line 51: | ||
==== Non-final case disposition ==== | ==== Non-final case disposition ==== | ||
If this trigger is selected, you must select a specific non-final case disposition from the drop-down list. | If this trigger is selected, you must select a specific non-final case disposition from the drop-down list. | ||
| Line 49: | Line 58: | ||
==== Average sentiment ==== | ==== Average sentiment ==== | ||
If this trigger is selected, you must show the percentage of the average sentiment. This is done by selecting '''<''' or '''>''' and moving the percentage slider to the complete the following type of example statement: ''A workflow is triggered if the average sentiment is greater than 0.51.'' | If this trigger is selected, you must show the percentage of the average sentiment. This is done by selecting '''<''' or '''>''' and moving the percentage slider to the complete the following type of example statement: ''A workflow is triggered if the average sentiment is greater than 0.51.'' | ||
[[File:Workflow-Average-Sentiment-50.png|450px|thumbnail|center|Average sentiment]] | [[File:Workflow-Average-Sentiment-50.png|450px|thumbnail|center|Average sentiment]] | ||
<!-- ==== New email arrives ==== | |||
The ''New email arrives'' trigger is the only option available for [[#Pre-processing_(email_only)|email pre-processing]]. This trigger allows all actions dictated in the configured workflow to be executed when a new email arrives in the selected ''Email account''. | |||
[[File:Workflow-Entry-Pre-Processing-54.PNG|450px|thumb|center|New email arrives trigger]] | |||
--> | |||
Revision as of 11:09, 1 July 2025
Workflows
After interactions are completed, dispositions and other such actions can start scenarios that automate what happens next. For example, setting a particular disposition for an interaction could trigger the following series of events to happen:
- Send a survey to the customer
- Wait a specified amount of time (e.g., 30 minutes, 1 day, 1 week, etc.)
- Send a follow-up email to the customer.
This series of events is called a workflow; workflows are triggered by agents selecting dispositions for interactions. In order for a workflow to be invoked, a Workflow Entry must be configured.
Workflows are created in the Contact Center Administrator application and are edited in the Workflow Builder application. Workflows will handle any necessary follow-ups, depending on the interaction’s disposition type. Such follow-up actions include setting context variables, sending an email, sending a text message, scheduling an event, clearing a scheduled event, and making an external request (or internal API call). Workflows reduce the workload of agents while following up with customers and gathering data in a consistent way.
For more information, see the Workflow Builder Reference Guide. Note that variables may be used when configuring both scenarios and workflows. For more information about variables, see the list of Workflow Variables.
Workflow Entries Screen Properties
Workflows are added to services as workflow entries. To add a workflow, navigate to Configuration > Workflows and select the + button.
Name
Every workflow entry needs a name. This field is mandatory.
Type
Type of workflow. Currently only post-processing workflows are supported. The email pre-processing workflow type is reserved for future use.
Service
Service is the name of the service with which the workflow entry should be associated.
Triggers
Triggers are the events that cause a configured workflow to be launched. To add triggers, click add, select the available triggers and their properties, and select the green check mark to apply your changes.
Trigger types include the following:
- Interaction ends with disposition
- Non-final case disposition
- Average sentiment
Interaction ends with disposition
If this trigger is selected, you must select a specific disposition from the drop-down list.
Non-final case disposition
If this trigger is selected, you must select a specific non-final case disposition from the drop-down list.
Average sentiment
If this trigger is selected, you must show the percentage of the average sentiment. This is done by selecting < or > and moving the percentage slider to the complete the following type of example statement: A workflow is triggered if the average sentiment is greater than 0.51.
