[Index]
:bdg:`Contact Center Management`
Tip
Use the Action search to navigate Automate
Overview
Webex Contact Center management is part of VOSS Contact Center Management, which is an add-on to VOSS UC Automation and requires the VOSS Core Platform. Contact center features follow the same platform principles used throughout VOSS:
This ensures a consistent operational experience when managing Webex Calling, Webex Contact Center, and other UC services from a single platform.
Webex Contact Center Management in VOSS focuses on agent administration and related configuration, providing centralized visibility, controlled access, and automation for day-to-day operational tasks.
Access to features and data is controlled using role-based access control (RBAC) and organizational segmentation, ensuring users see and manage only what is relevant to their role.
Webex Contact Center management becomes available in VOSS after the required platform and integration configuration has been completed, including enabling the Contact Center Customer setting for the connected Webex Organization.
Contact Center Management supports both enterprise and service-provider environments, including scenarios where multiple organizations or customers are managed from a single platform.
Once enabled, Automate provides tools to manage contact center agents and related configuration using the same operational model as other UC services, including hierarchy-based segmentation, role-based access control, automation, and audit tracking.
When Webex Contact Center is enabled, VOSS provides configuration and management capabilities for the following areas:
These features allow administrators to manage agent capacity, routing behavior, and agent experience from a single interface.
Related topics
For continuity and ease of use, the menu structure and terminology for Contact Center Management in VOSS closely follow the layout used in the Webex Control Hub. This allows administrators who are already familiar with Control Hub to navigate and manage contact center configuration with minimal retraining.
Administrators can view agent, license, and configuration data for Webex Contact Center alongside other UC services managed in VOSS, providing a centralized operational view across UC and contact center environments.
In addition to mirroring the Control Hub structure, VOSS introduces capabilities that support controlled administration at scale.
VOSS uses an internal business hierarchy to segment Webex Contact Center configuration data by region, site, or organizational unit. This makes it possible to:
All access and configuration changes are governed by RBAC policies and recorded in transaction logs, supporting centralized oversight, auditability, and consistent operational control.
This administration model is suited to environments with high agent churn, multiple operational teams, or shared service ownership.
Contact Center Management streamlines common agent lifecycle tasks, including:
Agent onboarding and changes can be performed individually, in bulk, or through automated workflows such as flow-through provisioning from identity sources or IT service management platforms. All configuration changes are logged, providing a complete transaction history for operational review.
Timely agent offboarding helps ensure unused contact center licenses are released and made available for reuse.
Webex Contact Center management in Automate supports:
Automation of repetitive administrative tasks, reducing manual effort and configuration errors Bulk operations for agent and configuration changes at scale Integration with external systems using APIs, including HR systems, ITSM platforms, and other business applications Dashboards and summaries that provide visibility into agent capacity, license usage, and configuration status, with access controlled by role
These capabilities help administrators respond more quickly to operational change while maintaining consistent governance.
Enabling Contact Center Management
Contact Center Management must be enabled on the VOSS Platform before use:
This relation implements the workflows to manage Webex Contact Center Channels.
| Title | Description | Details | |||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| End Point | Group Assigned by FDP |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Plan Name | Name of the plan |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Description | Description of the plan |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Entry Point Type * | Type of the entry point |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Channel Type * | The type of channel for the queue. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Asset ID | Unique identifier for the asset |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Outdial Transfer To Queue Enabled | Indicates if outdial transfer to queue is enabled |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Active Status | Indicates if the schema is active |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Created Time | Timestamp when the schema was created |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Last Updated Time | Timestamp when the schema was last updated |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| End Point Settings | Group Assigned by FDP |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Social Channel Type | Type of social channel. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Service Level Threshold | Service level threshold |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Maximum Active Contacts | Maximum number of active contacts |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Control Flow Script URL | URL for the control flow script |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Overflow Number | Overflow phone number |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Timezone | Timezone of the plan |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Subscription ID | Unique identifier for the subscription |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Route Point ID | Unique identifier for the route point |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Flow ID | ID of the flow |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Flow Tag ID | ID of the flow tag |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Music On Hold ID | Unique identifier for the music on hold |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Outdial Queue ID | Unique identifier for the outdial queue |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| System Default | Indicates if the plan is a system default |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| DN EP Mapping Count | Number of DN EP mappings |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Support Number | Group Assigned by FDP |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Dial Number |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Webex Calling location | Unique identifier for the location |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Support Number | Dialled phone number |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| PSTN Region | Unique identifier for the region |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Default ANI | Indicates if the default ANI is used |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Entry Point References | Group Assigned by FDP |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| References | references to Address Book entries |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Name | Name |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Reference Model Type | Type |
|
|||||||||||||||||||||||||||||||||||||||||||||||