Archiving WhatsApp, Teams and Email: A Rollout Playbook for Regulated Firms
Ten steps for capturing WhatsApp, Teams and email, from the channel inventory to e-discovery drills. Includes SEC/FINRA, FCA, MiFID II and MAS expectations side by side, indicative cost ranges and vendor red flags.
Examiners want proof that every business channel is either captured or blocked
Missing email is rarely the problem. The hard failures come from elsewhere: a relationship manager agrees a trade on WhatsApp, or a desk head confirms pricing in a Teams chat, and the firm can't produce either message. Financial communications archiving now comes down to one question. Can you show that every channel used for business is either captured or actually blocked, and that someone reviews what you capture?
US off-channel enforcement since 2021 has added up to well over a billion dollars in penalties. The FCA and European supervisors have said they expect the same discipline. The ten steps below cover inventory, device policy, capture, retention, supervision and e-discovery. As a rule of thumb, a mid-sized firm can reach a defensible baseline in about three to four months without buying more tooling than its risk profile needs.
How SEC/FINRA, FCA, MiFID II and MAS recordkeeping requirements compare
| Area | SEC / FINRA | FCA (UK) | MiFID II (EU) | MAS (Singapore) |
|---|---|---|---|---|
| Minimum retention | Broker-dealer communications: generally 3 years, the first 2 easily accessible (Rule 17a-4). Advisers: generally 5 years (Rule 204-2) | Generally 5 years, extendable to 7 at the regulator's request (SYSC 10A) | Generally 5 years, extendable to 7 at the competent authority's request (Art. 16(7) and the delegated regulation) | Generally at least 5 years for records of regulated activity |
| Scope | All business-related communications, on any channel | Communications relating to, or intended to lead to, transactions | Similar to the FCA, applied by national supervisors | Records supporting regulated activities and client dealings |
| Storage format | WORM or an audit-trail alternative for broker-dealers | Durable, retrievable and protected from alteration | Durable medium, protected from alteration | Retrievable. Technology-risk and outsourcing guidelines apply to cloud |
| Personal devices | Business use on any app must be captured | Firms must stop unrecorded communications on private devices | Firms must prohibit private devices they can't record | Firm-level controls expected. Confirm the detail locally |
| Supervision | Risk-based review (FINRA Rule 3110) | Individual accountability under SM&CR | Monitoring by the compliance function | Board and senior management oversight |
Treat this table as orientation, not a legal opinion. Hong Kong, the UAE financial free zones, India and Australia each have their own regimes. If you operate in several jurisdictions, build each record type to the strictest rule that applies to it. Have local counsel confirm the mapping before you lock in retention settings.
Steps 1 and 2: Inventory every channel, then tier it by risk
Step 1: inventory. An IT asset list won't find everything. Combine mobile device management data, staff surveys with named attestations, expense claims for personal phones and any client complaints that quote messages. Expect email, Teams chats and meetings, Zoom, Bloomberg chat, SMS, iMessage, WhatsApp, Signal and LinkedIn messaging, plus WeChat at many Asian desks.
Step 2: tiering. Put every channel in one of three tiers:
- Tier 1: client-facing or trade-related. Capture it and supervise it.
- Tier 2: internal business. Capture it and review it lightly.
- Tier 3: prohibited. Block it, train staff and collect attestations.
Tier against how your clients actually communicate. In much of Latin America, the Middle East, India and Africa, clients expect WhatsApp, and banning it there usually just moves the conversations somewhere you can't see them.
Steps 3 and 4: Set the device policy and decide how WhatsApp is permitted
Step 3: device model. Corporate-owned devices under MDM give you the cleanest control. BYOD with a managed work profile costs less, but it's harder to evidence. Whether you can capture SMS and voice at the carrier depends on the country and the carrier.
For WhatsApp you have three options: the official WhatsApp Business Platform through a capture provider, a managed archiving app on firm-controlled devices, or a ban. Where client-facing staff work in WhatsApp-heavy markets, choose the business-platform or managed-identity route. The firm owns the client relationship and keeps the number when an adviser leaves, which a ban can't give you.
Step 4: written policy. List the approved channels, name the prohibited ones and set out the disciplinary consequences. Require an attestation every year. Data-protection law covers the monitoring itself. Under GDPR, UK GDPR, India's DPDP Act, Singapore's PDPA and Brazil's LGPD, firms should generally expect to give employees notice, document an impact assessment and, in some cases, tell clients that conversations are recorded. Get privacy counsel to confirm what applies in each country where you have staff.
Steps 5 and 6: Choose the capture architecture and shortlist vendors
Step 5: architecture. Email is captured through journaling or an API. Teams can be retained natively in Microsoft Purview or pulled by a third party through Microsoft's export APIs. Those APIs may carry metered charges depending on your licensing, so check before you budget. Our view is that firms under about 200 users do better with a single platform running from capture through supervision, because every extra integration is one more place a gap can hide. Larger firms often pair specialist capture or compliance tools such as LeapXpert, Movius or Theta Lake with an archive from Smarsh, Global Relay or Proofpoint.
Step 6: vendor criteria. Only shortlist vendors that meet every one of these:
- Native capture of every Tier 1 channel
- Edits, deletions, reactions, attachments and threading kept in full context
- Documented support for SEC 17a-4 storage or your local equivalent
- Hosting regions that meet your residency needs, such as the EU, UK, Singapore, UAE or India
- Exports in standard formats, with a fixed or capped exit cost
| Component | Typical 2026 market range (USD) |
|---|---|
| Email archive | $4–12 per user/month |
| Teams, Zoom and chat capture | $8–25 per user/month |
| Mobile and WhatsApp capture | $10–35 per user/month |
| Supervision and surveillance | $10–40 per user/month |
| Implementation and migration | $15,000–150,000 one-time |
Hypothetical example: a 60-person wealth manager archives email and Teams for all 60 staff, and captures WhatsApp and runs supervision for 25 advisers. On the ranges above that works out to about $1,200–4,100 a month, or roughly $2,400 at the midpoints, plus perhaps $20,000–40,000 for setup. These are indicative ranges only. Pricing varies by contract, volume and region, so get quotes from each vendor.
Step 7: Configure retention, immutability and data residency
Set retention for each record type. One global number will either keep too much or too little: broker-dealer, adviser and MiFID records can have different periods even inside the same firm. Legal holds should override deletion automatically. When retention runs out, delete defensibly. Keeping everything forever causes storage-limitation problems under GDPR-style laws and gives litigants more to ask for.
Residency needs the same care. Transfers from the EU to third countries need a valid transfer mechanism. India's payment-data localization rules apply to payment system operators. Some Gulf and Asian regulators expect to be told before you outsource material functions to the cloud. Before go-live, test one specific case: a WhatsApp message that's edited and then deleted should show up in the archive as three events, namely the original, the edit and the deletion.
Step 8: Build electronic communications supervision reviewers can keep up with
Capturing messages nobody reviews won't satisfy an examiner. Supervision only works if alert volume stays at a level your team can actually get through. Start with risk-based sampling of Tier 1 users and a lexicon tuned to your products. Then add natural-language classifiers to cut false positives.
Put off-channel phrases in the lexicon: "text me on my personal", "call my other number", "let's take this offline". Track three numbers every month: alerts per reviewer, median review time and escalation rate. If a reviewer is closing several hundred alerts a day, treat that review as a rubber stamp until you've shown otherwise.
Steps 9 and 10: Run production drills, then evidence the program every quarter
Step 9: e-discovery drill. Choose a test client and a 30-day window. Produce every communication on every channel as threaded conversations with metadata, against an internal target such as 72 hours. Time the drill and write down what broke. Run it again in the formats your regulators actually ask for.
Step 10: ongoing evidence. Every quarter, reconcile capture volumes by user and channel. A trader with an active work phone and no captured WhatsApp messages needs an explanation. Keep a gap log with remediation dates, collect the annual attestations and report results to the senior manager or board committee accountable for recordkeeping.
Red flags that should end a vendor conversation
- Capture depends on users forwarding messages or taking screenshots.
- Edits and deletions aren't recorded as separate events.
- WhatsApp capture uses unofficial clients that may breach Meta's terms and get numbers banned.
- Exports are in proprietary formats or carry per-terabyte exit fees.
- The vendor can't name its hosting regions or subprocessors.
- Supervision is priced per alert, so you pay more when tuning is poor.
Next step: complete the Step 1 inventory this month. If it turns up Tier 1 business on a channel you can't capture within 90 days, prohibit that channel in writing now, and back the ban with attestations and monitoring until capture is live.
Frequently asked questions
Can we just ban WhatsApp instead of archiving it?
Yes, as long as you enforce the ban. That takes a written policy, training, attestations and monitoring for signs of off-channel use. Many US off-channel cases describe policies that existed on paper but weren't enforced. In markets where clients insist on WhatsApp, an approved capture route is usually easier to defend than a ban.
Is Microsoft Purview enough for Teams and email recordkeeping?
For many firms, Purview retention handles Microsoft channels well, and Microsoft has published independent assessments of how its preservation features map to storage requirements. It doesn't natively capture WhatsApp, SMS or Bloomberg chat, though, and its supervision tools are lighter than specialist products. Check it against your storage and supervision obligations with counsel before relying on it alone.
How long does a rollout typically take?
As a rough guide, a mid-sized firm with email, Teams and one mobile channel can reach a defensible baseline in about three to four months. Firms operating in several jurisdictions and migrating legacy archives often need six to twelve months. Tuning supervision and running the first production drill usually take longer than setting up capture, so start planning them early.
Written by the Adviser Hub Cloud editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.