Every channel your team uses. One archive.

Your business conversations happen over WhatsApp whether or not your policy says they should. Comma captures business threads and attachments into exam-ready storage, so you save what matters and leave your employees’ personal chats out of the record.

Your deals aren’t happening in Outlook anymore: they’re over iMessage. Capture client chats, media attachments, and timestamps right from Comma’s managed solution. Employees keep using iMessage. The capture is on Comma’s side.

Securely archive Signal 1:1 and group messages, on mobile and desktop, without altering the user experience or storing local data. Messages, metadata, and attachments are encrypted in transit and stored in immutable, audit-grade archives. End-to-end encryption.

Early access. Compliance archiving for self-hosted Matrix / Element homeservers, built for the sovereign deployments EU governments and enterprises are standing up. Capture runs inside the customer's own infrastructure as a trusted, cross-signed participant device, so encrypted rooms are archived the technically credible way. WORM retention, legal hold, supervision, and search over Matrix. Request access to join the design-partner program.

Rich Communication Services is the SMS successor on Android. Comma captures RCS 1:1 and group messages, edits, reactions, and rich attachments through a managed Android device, archiving the full thread context with full WORM retention.

Archive SMS, MMS, text messages, attachments, photos, and voice notes in native format, captured from a company-owned, fully managed Android device.

Telegram is increasingly being used for client communication and group coordination at financial firms, making those messages subject to SEC and FINRA retention requirements. Comma captures 1:1 messages, group chats, and file attachments, preserving sender details, timestamps, and edit history, and stores everything in a tamper-evident, WORM-compliant archive.

Capture iMessage business communications in real time, without impacting devices, user privacy, or relying on iCloud. Messages, media, and metadata are archived in full conversational context for audit trails and secure compliance.

Preserve all conversations across Slack. Slack Connect, direct messages, private groups, and public channels, along with edits, deletions, and file shares. Works on Team plan and Enterprise Grid. Everything is stored in context-rich threads, so you never lose important details and can produce records on examiner request without a support ticket.

Instant Bloomberg (Bloomberg Chat) is your second CRM, so treat it that way. We archive every trader ping, analyst insight, and file share in its original format, giving you a full audit trail without forcing you to change how you work.

Your business conversations are happening on WeChat, whether they’re labeled "off-channel" or not. Comma captures WeCom (WeChat Work) enterprise chats directly through Tencent’s server-side archive API — 1:1 and group chats, attachments, and external consumer-WeChat messages — with consumer WeChat covered via BYOD device archival.

Arc is our platform for capturing, governing, and archiving AI and agent activity alongside the human channels we already cover.

Archive AI agent tool-calls, prompts, responses, and chain-of-custody evidence in the same exam-ready record as your human channels. Arc Relay forwards from Anthropic, OpenAI, and other AI providers into Comma via authenticated handoff with per-tenant key rotation.

Capture ChatGPT Enterprise activity through OpenAI's official Compliance Platform: conversations, uploaded files, workspace GPT configuration and metadata, memories, and the user directory, delivered as immutable compliance logs. Routed into the same exam-ready archive as your other channels to support SEC Rule 17a-4, FINRA 4511, and other recordkeeping requirements.

Archive accessible files from connected users' Drives and Shared Drives, with metadata and deletion markers. Each sync captures the visible file version; pre-connection revision history, intermediate edits between syncs, comments and a complete user-activity log are outside this scope. Google-native documents use supported export formats.

Configure Gmail, Chat, Drive and available Meet artifacts for your connected workspace. Each surface has its own permissions and coverage status. Drive captures current versions, with supported exports for Google-native files. Calendar authorization is separate from archival ingestion, which is not included in this capture scope.

Retrieve available Meet recordings and transcripts for eligible connected Workspace users. Your Google edition, delegation and recording settings govern capture. Fathom and Fireflies use separate connections.

Store every inbound and outbound Gmail conversation, as well as CCs, BCCs, attachments, and full threads. Messages are preserved in their original format with timestamped details and legal-hold controls — records are immediately searchable and exportable in examiner-ready format.

Retain all Microsoft 365 business content: email including CC, BCC, attachments and full threads, Teams chats, files, calendar events, in native format with full metadata, attachments, and message direction. Direct-source ingestion ensures encrypted, searchable, and immutable archiving designed against SEC and FINRA recordkeeping requirements.

Outlook is Microsoft’s email client across desktop, web, and mobile, and it sits on top of Exchange. Comma captures every Outlook email (inbound, outbound, CC, BCC, and attachments) at the moment of delivery. Native format preserved, full metadata retained, immutable WORM storage. Works alongside Microsoft 365 and Exchange capture.

Exchange is the server underpinning every Microsoft 365 mailbox. Comma captures at the tenant level via Microsoft Graph API — every message (sent, received, CC, BCC, attachments, conversation threads) regardless of which email client your employees use. Direct-source ingestion, no forwarding rules, no client-side dependencies. On-premises Exchange and private data center deployments available on enterprise.

Complete capture of all Microsoft OneDrive activity. Retain folder structure and native file formats (Office docs, PDFs, images, videos, etc.), version history, sharing links and permission changes, comments, and collaborative edits. Archive file operations (create, modify, move, delete), external shares, and access logs, enriched with user, device, and location metadata.

Preserve Teams chat and channel messages. 1:1 chats, group chats, and channel messages, with edits, deletes, reactions, attachments, and timestamps retained in full conversational context. Recordings and transcripts of meetings a monitored user organized are stored in source format.

Archive Confluence knowledge assets such as wiki pages, blog posts, comments with complete version history, and file attachments. Securely store all content in a WORM-compliant database with customizable retention periods.

Capture Jira Cloud data: project descriptions, comments, attachments, and full issue details. Securely store all content in a WORM-compliant archive.

Outbound sync: deliver business conversation summaries to matched HubSpot contacts. Supported last-touch fields and delivery settings are configured for your organization. This connection does not archive native HubSpot records.

Outbound sync: deliver conversation summaries to matched Zoho CRM contacts, with provider-specific field settings and regional connection routing. Native CRM-record archival is a separate requirement.

Outbound sync: add conversation summaries to matched Wealthbox contacts. Confirm destination visibility and connection settings during rollout. This connection does not archive records created inside Wealthbox.

Outbound sync: deliver conversation summaries as household notes associated with matched Slant clients. Book selection and household visibility govern the destination. A separate last-touch field is not included.

Outbound sync: deliver conversation summaries to the lead associated with a matched Close contact. Optional last-touch fields and destination checks are configured separately. Native CRM-record archival is outside this connection's scope.

Outbound sync: deliver conversation summaries to matched Pipedrive people, with optional last-touch field updates. Contact Comma to confirm the authorization path and enablement for your organization.

Not on Microsoft or Google? Comma connects to any IMAP-compatible mailbox (FastMail, Zoho, ProtonMail Bridge, on-prem Exchange) using AES-256 encrypted credentials and captures every inbound and outbound message, attachment, and folder into the same archive, designed against SEC 17a-4.

LinkedIn 1:1 messages, InMail, connection activity, and business-page interactions. Connect via OAuth from your team’s Integrations page and Comma archives the full thread context with timestamps, edits, and read receipts.

Complete recording of all Facebook activity: preserving links, media, questions/polls, Events (and RSVPs), editable Docs/Notes, Timeline posts & threaded comments (personal & business Pages), 1:1 Messenger chats & private Group Messages, Business Page inbox interactions, Marketplace listings & buyer-seller chats, plus Live videos & Stories. Every item (including link-rich posts, Event pages, Docs and Questions) is stored with full metadata (timestamps, author/edit history, device info, location tags) in immutable storage.

Early access. Collect YouTube channel activity, including video uploads, associated metadata (thumbnail, title, description, link), comments, replies, and user interactions, in structured format.

Archive accessible Fathom transcripts and meeting details, with optional AI summaries, action items and recordings. One API-key connection per Comma team. Source sharing permissions govern access; request team enablement to get started.

Archive accessible Fireflies transcripts, with optional AI summaries, action items, audio and video. Connect an API key and configure delivery in Fireflies. Source plan and permissions govern access; request team enablement to get started.

Available on request. Requires Otter Enterprise on the Otter side for API access. Contact Comma to arrange setup and confirm the transcripts, summaries, action items or recordings you need.

Archive available Zoom cloud meeting recordings and transcripts through the enabled meeting capture surface. Permissions, licensing and source download windows govern coverage; local recordings are outside this capture path. Review capture status and known gaps in Comma.

Archive available Zoom Phone call records, recordings, voicemails and SMS/MMS on enabled surfaces. Transcripts are captured where Zoom provides them. Licensing, permissions and source retention determine what is available to retrieve.

Comma captures RingCentral calls, call recordings, voicemail, and fax into a single tamper-protected archive. Organization-level connection, no per-user setup, and all four surfaces land alongside your other 40+ channels for one unified supervision workflow.

Archive Quo Calling business calls with full recordings, automatic transcripts, and WORM-sealed storage. Captured at the moment each call completes and searchable alongside your other channels.

Discuss Webex meeting archival requirements with Comma. Confirm the connection path and demonstrated coverage for recordings, transcripts and participant context before including Webex in your deployment scope.

Collect conversations, including text exchanges (direct & channel), files, GIFS, and whiteboards. Additionally, store all metadata and context, including channel and topic context, edits, and deletes, as well as reactions and read receipts, to ensure regulatory compliance and secure audit trails.

Securely archive all Twilio cloud communications, including phone calls, text messages, and SMS. Whether you’re using Twilio directly or any tool built on top of it, Comma captures what’s underneath.

Archive inbound and outbound voice calls of business contacts: PSTN, VoIP, and soft-phone sessions. Caller ID, timestamps, and duration for secure, chain-of-custody compliance.

Comma stores your Substack posts, emails, comments, and formatting in native HTML/Markdown, encrypted at rest with AES-256 and locked down with WORM retention on AWS/Azure. As more teams adopt Substack for marketing and newsletter outreach, that activity becomes part of your recordkeeping obligations.

Push messages into Comma from any system. Per-tenant HTTPS endpoints with bearer-token or HMAC authentication, IP allowlists, idempotency keys, and on-demand secret rotation. Use it to wire up internal tools, custom apps, or any platform not yet on our self-serve list.