ICE Chat is a messaging platform used by financial market participants to communicate with counterparties and colleagues. MCO eComms can capture ICE Chat messages so they can be retained, monitored, and reviewed according to your organization’s electronic communications policy.
Overview
ICE Chat communications can include business messages that are subject to supervision, retention, and review requirements. To bring these messages into MCO eComms, your organization must first configure message export with ICE, then provide the Secure File Transfer Protocol (SFTP) connection details to MCO.
MCO eComms receives ICE Chat messages through a daily feed from ICE. After the feed is configured, messages can be added to the archive and made available for monitoring and review.
User mapping is required so MCO eComms can associate ICE Chat messages with the correct user profiles. When messages are mapped to users, the appropriate retention and detection policies apply to those communications.
How it works
Step | Description |
Confirm ICE services | Your organization must have the appropriate ICE Chat compliance contract in place before ICE can provision message export services. |
Set up the ICE export | ICE creates an SFTP feed that exports ICE Chat message logs for the selected users or registered domains. |
Provide credentials to MCO | Your organization sends the ICE SFTP credentials to MCO through a support ticket or implementation contact. |
Configure the source | MCO configures the daily download process for the ICE Chat source. |
Map users | Admin users map ICE Chat usernames or Instant Messaging IDs (IMIDs) to MCO eComms user profiles. |
Archive messages | Newly received ICE Chat messages are added to the archive and associated with mapped users. |
User scope
ICE can export messages for specified users or for all users in a registered domain.
If your organization provides ICE with a user file, ICE exports messages for the users in that file. If your organization does not provide a user file, ICE can include all users from the registered domain.
NOTE: If your organization exports only individually listed ICE Chat users, you must maintain that user list with ICE when covered employees join or leave. MCO cannot independently identify those onboarding or offboarding events.
Exporting all users from the registered domain can reduce ongoing administration because new and removed users are covered by the domain-based export scope.
User mapping
ICE Chat users are mapped in MCO eComms by ICE Chat username or ICE Chat Instant Messaging ID (IMID). These identifiers can be mapped to the primary email address on the user profile or added as additional source mappings.
After a mapping is saved, newly arriving ICE Chat messages that match the mapped identifier are associated with that user. Once the messages are mapped, the user’s retention and detection policies apply to future ICE Chat communications.
Message availability
Messages may not appear in the archive immediately after setup is complete. ICE Chat messages can take a few days to begin appearing in MCO eComms.
If user mapping is incomplete, messages may initially appear as unmapped. Complete ICE Chat source mappings so MCO eComms can apply the correct user policies.
Sample Email Template (Client → ICE Chat)
Subject: Request to Establish ICE Chat SFTP Feed for Data Delivery
To: [ICE Chat Sales Contact]
Body:
Hello [ICE Chat Team],
On behalf of [Client Company Name], we would like to proceed with setting up an SFTP feed for ICE Chat data delivery to meet our compliance and archiving requirements.
We have obtained the latest version of the ICE Data ServICEs Agreement from your site and are prepared to execute it as part of this process. Could you please provide guidance on the next steps for:
SFTP Feed Configuration
– Establishing the SFTP endpoint where ICE Chat can deliver our chat data on a regular basis.
– We will provide the necessary encryption keys (PGP/SSH) and network details required for setup.Credentials and Connectivity
– Once the feed is provisioned, we will need the connection details (hostname/IP, port, and any required firm code, username, and password).
Please also let us know if there are any additional requirements, timelines, or fees we should be aware of.
Thank you for your assistance in enabling this connection. We look forward to your guidance and to completing this setup.
Best regards,
[Client Contact Name]
[Title]
[Client Company]
[Contact Information]