What is Symphony Messaging capture?
Symphony Messaging (sometimes referred to as Symphony Chat) capture brings supported Symphony communications into MCO eComms so they can be retained, monitored, and reviewed according to your organization’s electronic communications policy.
Overview
Symphony is a messaging and collaboration platform used by financial services organizations for business communications. Symphony Messaging communications can include business records that compliance teams need to preserve and supervise.
MCO eComms can process Symphony Messaging exports provided in the supported export format. Symphony creates encrypted ZIP files through recurring or ad hoc content exports. These files should be provided to MCO eComms unchanged so they can be processed for archiving and review.
Your organization configures Symphony content export in the Symphony Admin Portal. After export is configured, MCO eComms can receive and process the exported chat data according to your implementation setup.
Supported export format
MCO eComms requires Symphony Messaging content to be exported in Symphony XML format.
WARNING! Do not unzip, rename, or change the exported Symphony ZIP files before providing them to MCO eComms. File changes can delay or prevent processing.
Export types
Export type | Description |
Recurring export | Symphony generates scheduled export files. The default recurring export interval is 24 hours and starts at 23:59:59 UTC. |
Ad hoc export | Symphony generates an export for a selected date range. The export includes data from 00:00:00 to 23:59:59 GMT for the selected dates. |
NOTE: An ad hoc export should not run at the same time as a recurring export.
How it works
Step | Description |
Confirm Admin Portal access | Your organization confirms the user configuring the export has Symphony Admin Portal access. |
Open content export settings | An administrator opens Company Settings > Export Content in the Symphony Admin Portal. |
Choose the export type | Your organization configures either a recurring export or an ad hoc export. |
Select the export format | The export format is set to Symphony XML. |
Generate export files | Symphony creates encrypted ZIP files for the configured export. |
Provide files to MCO eComms | Your organization sends the exported ZIP files to MCO eComms unchanged. |
Import communications | MCO eComms processes the Symphony XML files for archival and review. |
Apply policies | Once communications are imported and mapped, configured retention and detection policies apply based on your organization’s setup and license limitations. |
Review communications | Compliance users can search, monitor, and review captured Symphony Chat communications in MCO eComms. |
File naming
Symphony uses different file naming patterns for recurring and ad hoc content exports.
Export type | File naming pattern |
Recurring content export | <export_format><company-name>_SD-<ContentStartDateHourUTC>_ED-<ContentEndDateHourUTC>_GD-<GenDateUTC><GenTimestampInMillisecond>.zip |
Ad hoc content export | <export_format><company-name>_CD-<ContentDateUTC>_GD-<GenDateUTC><GenTimestampInMillisecond>.zip |
Message availability
Symphony Messaging communications may not appear in the archive immediately after files are provided to MCO eComms. Availability depends on the export schedule, file delivery timing, source configuration, and processing schedule.
After communications are imported and mapped, they can be retained and reviewed in MCO eComms according to the policies assigned to the user.