Development Map
Layer |
Open Characteristics |
Implementation Method |
Supported Scenario |
---|---|---|---|
Business implementation |
Self-service |
Online page configuration |
An enterprise can customize the IVR flows of a call center on the online flow orchestration page of the CEC. The IVR flows can be used to implement functions such as voice/video playing during ringing, voice/video digit collection, call transfer, interface invoking, and value assignment judgment. For details, see Self-Service (IVR) Integration Solution.
NOTE:
|
Agent |
|
On the agent workbench, the button area for customer service personnel to answer and process inbound calls is called a connection bar or connection block. The connection bar or block can connect, hold, transfer, or hang up an agent's phone (OpenEye softphone provided by the CEC). The CEC provides the following agent-related open capabilities. For details, see Voice and Video Agent Integration Solution.
|
|
Intelligence |
|
If an enterprise needs to use the voice self-service or text chatbot, the enterprise can use the intelligent IVR page provided by the CEC to complete related configurations. In addition, to provide guidance on agent scripts and check whether the agent scripts contain sensitive words, you can configure the intelligent IVR and enable the intelligent assistant feature. For enterprises that do not use the agent workbench provided by the CEC, the RESTful interfaces of the OIAP can be used to query the existing chatbot configuration and bind dialog IDs. In addition, the intelligent subscription RESTful interfaces of the CC-Gateway can be used to display the quasi-real-time ASR result on the self-developed workbench, and complete the identification of the natural language. For details, see Intelligence Solution. |
|
Mobile agent |
|
By using the CC-Gateway interfaces and mobile agent interfaces provided by the CEC, enterprises can develop their own H5 apps to enable agents to answer and make calls (VoIP) using mobile phones. |
|
Outbound call management |
RESTful |
By invoking the RESTful interfaces of the CC-iSales, enterprises can write the information such as outbound call task data, outbound call sample data, and user blocklist in the outbound call management system developed by the enterprise to the AICC. |
|
Media routing |
- |
- |
The CEC routes voice, video, and multimedia requests in a unified manner. |
Media adaptation |
Multimedia adaptation service |
RESTful |
Currently, the CEC supports access through voice and video (VoLTE/VoIP), web client, WeChat, Facebook, Twitter, and 5G message. Except the web client, other channels can be enabled by page configuration. For details, see Multimedia Channel Access Solution. |
Channel access |
User App Integration (Android SDK) |
RESTful Android SDK invoking |
If an enterprise requires that users can initiate voice and video calls through the Internet, the enterprise can use the Android SDK to integrate self-developed applications. During the development, the enterprise can use related interfaces provided by the CEC to query information. For details, see Multimedia Channel Access Solution. |
Text chat access |
|
Enterprises provide the following methods to integrate the text chat access capability on the user side. For details, see Multimedia Channel Access Solution.
|
|
Operations support |
Agent monitoring |
RESTful |
If enterprises need to query, display, and collect statistics on real-time operations data (such as monitoring data of call center objects including skill queues, agents, teams, and IVRs) of a call center, the enterprises can use RESTful interfaces to obtain related data. |
Offline CDR |
RESTful |
Enterprises provide an offline CDR download interface for obtaining CDR files and recording files in batches. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot