[Index]
Tip
Use the Action search to navigate Automate
Important
The Webex Organization setting, Contact Center Customer, must be enabled in order to manage a Webex Contact Center in Automate.
If a Cisco Webex service is added to Automate from Webex Organization and the setting Contact Center Customer is enabled, Automate provides a range of features to manage a Webex Contact Center. In particular, this includes:
Automate also provides role-based access, menus, and dashboards to view and manage the Webex Contact Center
For continuity, the grouping of functionality on the menus and dashboards follows the format and naming as seen on the Webex Control Hub interface.
Related topics
Tip
Use the Action search to navigate Automate
Overview
This collection of features provides a single view of customer-specific functionality and reflects the layout in the Webex Control Hub.
Channels
Channels can be managed in Automate.
Queues
Queues can be managed in Automate.
A Queue Type (Inbound, Outbound) and Channel Type (Telephony, Email, Chat or Social Channel) is selected for a queue.
For outbound queue types, the channel types defaults to TELEPHONY and the Queue Routing Type is the agent who has been available for the longest time in all teams assigned to the queue.
Business Hours
Business hours can be managed in Automate and are used to define one or more shifts containing for example regular work hours, peak hours, off-peak hours and required for the operation of a specific contact center.
These are defined by working hours, a selected holiday list and overrides to working hours.
For the management of holidays and overrides, see: Webex Contact Center Advanced.
Audio prompts
Audio prompts can only be imported but not created or edited in Automate.
These are audio files containing for example predefined chat responses and music on hold.
Flows
Call flows can only be imported but not created or edited in Automate.
The flows are designed on the Webex Control Hub Flow Designer and allow for the routing of real-time calls through the system, how agents are assigned to calls and what occurs at each stage of the process. This is done by the configuration of activities and events.
| Title | Description | Details | |||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Flow Type | Type of the flow |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Organization ID | ID of the organization |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Name | Name of the flow |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Description | Description of the flow |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Assigned RS | List of assigned RS IDs |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Status | Status of the flow |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Version | Version number of the flow |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Tag Histories | History of tags associated with the flow |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Tags |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Flow Version Name | Name of the flow version |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Flow Version ID | ID of the flow version |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Fork From | ID of the flow version from which this version was forked |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Tags | List of tags associated with the flow |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Display Name | Display name of the tag |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Default | Indicates if the tag is the default tag |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Flow Version ID | ID of the flow version associated with the tag |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| ID | ID of the tag |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Version Number | Version number of the tag |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| ID | Unique identifier for the flow |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Created By | Email of the user who created the flow |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Last Modified By | Email of the user who last modified the flow |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Locked By | Email of the user who locked the flow |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Locked At | Date and time when the flow was locked |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Created Date | Date and time when the flow was created |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Last Modified Date | Date and time when the flow was last modified |
|
|||||||||||||||||||||||||||||||||||||||||||||||