Microsoft Teams + Mobile · Call recording compliance
Teams compliance recording is great. It doesn't cover mobile.
For regulated firms running Microsoft Teams with a compliance recording integration (Smarsh, Theta Lake, Verint, ASC, NICE), the desk-call side is solved. The gap that gets flagged in FCA supervisory reviews and audit findings is what happens when staff pick up the mobile, the call doesn't go through Teams, so the Teams recording integration never sees it.
ONSIM closes that gap at the mobile network layer. Issue regulated staff an ONSIM SIM/eSIM alongside their Teams identity, and every mobile-network call is captured automatically, regardless of whether they remember to dial through Teams.
The Teams compliance gap on mobile
Teams compliance recording integrations capture calls made on Teams. A staff member taking a regulated call on their personal or work mobile, without going via Teams, produces a call that the compliance archive never sees.
The FCA's enforcement actions in 2022-2024 around off-channel communications make the same point in a different form: policy alone ("staff must use Teams") doesn't deliver compliance, because users predictably do whatever is most convenient. The firm-level answer is to make the convenient channel itself recorded.
How Teams + ONSIM fit together
| Scenario | Teams compliance recording | ONSIM Mobile Compliance Recording |
|---|---|---|
| Desk call via Teams | Recorded | N/A |
| Mobile call via Teams app (PSTN out) | Recorded | N/A |
| Mobile call NOT via Teams (native mobile dialler) | NOT recorded ❌ | Recorded ✅ |
| Inbound call to mobile number | NOT recorded ❌ | Recorded ✅ |
| SMS on mobile | NOT recorded ❌ | Recorded ✅ |
| Calls when Teams app is closed / phone restarted | NOT recorded ❌ | Recorded ✅ |
One archive, two recording streams
ONSIM exports recordings to the same compliance archive vendor your Teams recordings already use, Smarsh, Theta Lake, Verint, ASC, NICE, Global Relay and others. Your compliance team gets a consolidated archive view; the only difference in operational terms is that the firm has eliminated the mobile-channel gap.
Close the mobile gap in your Teams compliance setup
Tell us which staff group needs mobile coverage, your existing Teams compliance recording vendor, and your retention requirements. We'll quote a tailored deployment that integrates with your existing archive.
Frequently Asked Questions
What regulated firms running Teams most often ask.
What is Teams call recording compliance?
Microsoft Teams offers compliance recording via integrations (Verint, Theta Lake, ASC, NICE, Smarsh, etc.). These capture calls made on Teams. The gap they don't cover is anything that happens off Teams, typically: a staff member taking a regulated call on their mobile, or making an outbound mobile call to a client. For FCA and MiFID II firms that's a recording obligation gap.
How does ONSIM complement a Teams compliance setup?
ONSIM records calls made on the mobile network, i.e. calls that don't go through Teams. By assigning regulated staff an ONSIM SIM/eSIM (alongside their Teams identity), every mobile-network call is captured at the network level, regardless of whether the user remembers to dial through Teams or pick up via the mobile.
Can't we just stop staff using mobile for regulated calls?
In theory. In practice, the FCA's 2022-2024 enforcement actions on off-channel communications (WhatsApp, personal mobile, signal) show that policy-only controls don't work. Staff use mobile because it's convenient. The compliance answer is to make the mobile channel itself recorded, not to fight the user behaviour.
Does ONSIM integrate with our existing Teams compliance archive?
Yes, ONSIM recordings can be pushed to the same archive vendor your Teams recordings already use (Smarsh, Theta Lake, Verint, ASC, NICE etc.) via API or SFTP. Your compliance team gets one consolidated archive view. Specific integrations are scoped during sales.
Does this replace Teams call recording?
No. Teams compliance recording covers calls made via Teams. ONSIM covers calls made on the mobile network outside Teams. Most regulated firms run both, Teams for desk-based and structured comms, ONSIM for any time the user picks up the mobile. Together they close the recording gap.
Which Teams compliance recording vendors does ONSIM work alongside?
ONSIM is vendor-agnostic, it sits at the mobile network layer, not on the device. Recordings can be exported to any major compliance archive (Smarsh, Theta Lake, Verint, ASC, NICE, Global Relay) via standard formats. If you're using a vendor not listed, talk to sales, most integration patterns are similar.
What about Microsoft Teams Phone Mobile (the operator-connect mobile product)?
Microsoft Teams Phone Mobile lets users present their Teams number on mobile calls via select operator partnerships (Vodafone, Verizon, etc.). It records those calls into the Teams stack. ONSIM is a different model: independent UK SIM with network-level recording, not tied to your Teams licensing. Some firms use both; ONSIM is typically deployed for staff who need a UK landline-presence mobile (which Teams Phone Mobile doesn't deliver) or where the Teams operator-connect option isn't commercially viable.
How do we deploy this alongside an existing Teams setup?
Identify the staff group who need mobile recording (typically: anyone with FCA-regulated activity, or anyone who handles client-facing communications on mobile). Issue them an ONSIM SIM/eSIM. They keep their Teams identity for desk calls and their ONSIM number for mobile. The two streams are recorded independently but archive together. Request a quote at quote.onsim.uk for a scoped deployment.
We're not a regulated firm, do we still need this?
Probably not. If you're not subject to a recording obligation, the Teams compliance recording you already have is likely sufficient for general business call recording. ONSIM's value here is specifically about closing the mobile-channel gap for firms that have a regulatory recording duty.