After using the Intelligent Contact Center (ICC) APIs for call tasks, you can configure the Message Service (MNS) consumption mode or the HTTP batch push mode to receive receipt messages.
The system may push duplicate receipt messages due to network exceptions or response timeouts.
The response timeout for the HTTP batch push mode is 700 ms.
To pull messages from Message Service (MNS) using an SDK, see Message Receipt API Demo.
Receipt message modes
You can receive receipt messages in two modes: Message Service (MNS) consumption mode or HTTP batch push mode.
Message Service (MNS) consumption mode
The Message Service (MNS) consumption mode lets you receive receipt messages through the MNS queue model. All business messages from Alibaba Cloud Communications support delivery through MNS. In the Intelligent Contact Center (ICC) console, on the General Settings page, go to the Subscribe to Receipts tab. When you enable MNS subscription for a specific message type, the system automatically creates a dedicated message queue and provides a queue name (QueueName) for that type. You can use this queue name, message type, and a temporary token obtained using your Alibaba Cloud AccessKey to retrieve message details from the queue.
HTTP batch push mode
The HTTP batch push mode pushes messages to a specified web URL using HTTP POST requests. After you set an HTTP callback URL (callback_url) in the Intelligent Contact Center (ICC) console, the system pushes business messages to this URL as they are generated.
Receipt message types
Intelligent Contact Center (ICC) supports the following receipt message types (MessageType).
Feature | Parameter | Description | MNS consumption | HTTP push |
Communication Intelligence Engine | LlmSmartCall (Communication Intelligence Engine call record message) | Provides call record details after a call ends, such as answer time, end time, and duration. | ||
LlmSmartCall (Communication Intelligence Engine call recording message) | Provides the call recording after a call ends. | |||
Communication Agent | AlicomAgentCallReport (Communication Agent call record message) | After a call ends, this message provides call record information, including the hang-up party, end time, call duration, and more. | ||
AlicomAgentCallRecord (Communication Agent call recording message) | After a call ends, this message provides the call recording. | |||
AlicomAgentCallNote (Communication Agent note message) | After a call ends, this message provides the configured output tag records. | |||
Intelligent Communication Bot | VoiceReportAiccs (Call record message) | After a call ends, this message provides call record information, including the call type, start and end times, duration, hang-up reason, and more. | ||
VoiceCallReportAiccs (Intermediate call status message) | Provides call status events during a call, such as call start, ringing, answered, and hang-up, with their timestamps. | |||
VoiceRecordReportAiccs (Call recording message) | After a call ends, this message provides the call recording. | |||
RobotCallReportAiccs (Bot call record message) | After a call ends, this message provides call record information, including the callee number, start and end times, duration, and more. | |||
Configure receipt message modes
To receive receipt messages, you must first enable a receiving mode in the Intelligent Contact Center (ICC) console.
MNS consumption
Enable the MNS consumption mode for Communication Intelligence Engine
In the and turn on the toggle switch for a queue under Message Service (MNS) Consumption Mode. The Communication Intelligence Engine provides a general queue and application-specific queues.
General queue: If enabled, you can retrieve message receipts from the default queue.
Application-specific queue: You can configure separate message queues for specific applications. After configuration, receipt messages for an application are sent only to its dedicated queue, not the general queue. To create a queue, select an application, and the system automatically generates it.
Enable the MNS consumption mode for Communication Agent
In the and turn on the toggle switch for a queue under Message Service (MNS) Consumption Mode. Communication Agent provides a general queue and application-specific queues.
General queue: If enabled, you can retrieve message receipts from the default queue.
Application-specific queue: You can configure separate message queues for specific applications. After configuration, receipt messages for an application are sent only to its dedicated queue, not the general queue. To create a queue, select an application, and the system automatically generates it.
Enable the MNS consumption mode for Intelligent Communication Bot
In the and turn on the toggle switch for Message Service (MNS) Consumption Mode.
HTTP push
Enable the HTTP batch push mode for Communication Intelligence Engine
In the and turn on the toggle switch for an address under HTTP Batch Push Mode. The Communication Intelligence Engine provides a general message receiving address and application-specific addresses.
Message receiving address: If enabled, the system pushes message receipts to the configured receiving address.
Application-specific address: Select an application and configure a unique receiving address for it.
Enable the HTTP batch push mode for Communication Agent
In the and turn on the toggle switch for an address under HTTP Batch Push Mode. The Communication Agent provides a general message receiving address and application-specific addresses.
Message receiving address: If enabled, the system pushes message receipts to the configured receiving address.
Application-specific address: Select an application and configure a unique receiving address for it.
Enable the HTTP batch push mode for Intelligent Communication Bot
On the page, enable the switch to the left of HTTP batch push mode.
Turn on the toggle switch for HTTP Batch Push Mode.
Enter the receiving address and click Save.
To save the address, your server must return a response in the specified JSON format, for example:
{"code": 0, "msg": "Success"}. You can click Test to verify the address's connectivity.