Every channel your team uses. A working archive.

An archive you can work from

An archive should help you answer a question: what was discussed, which records relate to it and who needs to review them? Comma brings captured business communications into an archive, with search, source browsing and connections to policy review and cases.

Start with your organization’s email and collaboration tools, mobile messaging, calls, available meeting recordings and business files. Connector coverage determines the sources, content types and events available for your deployment.

Capture before messages disappear

Most mobile messaging platforms weren’t designed for compliance. Messages can be edited, deleted, or live only on a device. Connect business communications to the archive before a review depends on finding them. Capture methods and edit or deletion coverage vary by connector; a connection cannot recover content it never received.

Find the context behind the conversation

Files belong in the archive conversation too

Shared files can provide context that a message alone cannot. Comma’s file archive lets reviewers browse source locations and inspect the available file history alongside related information.

Different records need different capture paths

See meeting recording archiving and CRM records and sync for those separate workflows. Capture methods and edit, deletion or historical coverage vary by connector. Agree on the coverage your organization needs rather than assuming every source behaves the same way.

Configure the archive for your organization

Your team chooses its retention configuration and the business communications in scope. There is no single retention period that establishes suitability for every record or organization. Review the selected framework and operating policy with your legal and compliance team.

The Configuration Center brings team settings, channels, classification and retention into the administration workflow. For enabled teams, the jurisdiction workspace also records legal baselines and counsel positions. It distinguishes recorded intent from active enforcement.

Comma is designed against SEC 17a-4, FINRA 4511, CFTC 1.31 and MiFID II electronic-recordkeeping requirements. That is a design statement, not regulatory approval or a determination that your obligations are satisfied.

Get records to the people who need them

Use case reports for an investigation’s working record. Discuss source-record collections and recipient-specific requirements when planning an evidence handoff. E-discovery and investigations explains the available workflow and its enablement boundaries.

For an additional copy in your own cloud tenancy, Comma supports delivery to a customer-owned Amazon S3 bucket or Azure Blob container after activation. This adds a copy alongside the Comma archive. It starts from activation and does not backfill earlier content. You control the delivered copy’s storage and immutability configuration. The customer bucket delivery guide explains setup and activation.

Data location requires its own review. A copy in your bucket does not relocate Comma’s operating environment. Data residency and enterprise deployment planning cover that discussion.