# WeCom & WeChat Compliance Archiving

Comma captures WeCom (WeChat Work) chats — 1:1, groups, attachments, and external WeChat — through Tencent's archive API into one exam-ready archive.

Source: https://commacompliance.com/channels/wechat-compliance
Last updated: 2026-07-23

---
Your recordkeeping obligations apply to the content of the business conversation, not the channel it traveled through. If your team is doing business on WeCom or WeChat, those messages are business records — and your firm is responsible for retaining and producing them on demand.

We all watched this play out in the 2021–2024 off-channel sweep. The activity was happening in WhatsApp, Signal, and iMessage, but the firms hadn't captured it, and the penalties followed. WeCom creates the same gap. The regulated firms that think they need WeChat capture almost always need WeCom.

Most archiving solutions either skip WeCom entirely or route capture through a third-party relay with per-user credential handshakes. Comma reads WeCom's server-side archive API directly — no relay, no device agent, no per-employee OAuth setup.

## What Comma captures from WeCom

Comma captures 1:1 and group enterprise chats, file and image attachments, reactions and edits where the WeCom API exposes them, external consumer-WeChat messages routed through WeCom's external contacts feature, and full metadata: sender, timestamps, and conversation context. All of it lands in the same tamper-protected archive as your other channels, with a single supervision queue.

## How the WeCom integration works

Comma pulls WeCom conversations straight from WeCom's server-side archive API. No third-party relay, no agent on anyone's device, no per-user OAuth handshake.