For compliance administrators and mobile program administrators.
Before you begin
Confirm your organization meets the O2 requirements for SMS archiving before you request onboarding.
Your organization has purchased O2 Capture (MVR) directly from O2.
Your organization has a corporate or enterprise account with O2.
An O2 representative has assisted with enabling O2 Capture.
Your organization has an administrator account and user licenses from MCO.
Your organization has O2 account and billing contact details available for onboarding.
Employees use corporate-owned and corporate-liable mobile devices on the O2 network.
Employees have been informed that the service is used for mobile compliance and governance and that their SMS communications will be archived.
Enhanced messaging services, such as iMessage on iOS devices and RCS on Android devices, are disabled.
SMS restrictions are removed from the O2 numbers that need to be archived.
NOTE: MCO coordinates setup with TeleMessage and the carrier.
WARNING: O2 Capture is available only for corporate-owned and corporate-liable mobile devices on the O2 network. It is not available for employee-owned devices.
O2 SMS capture overview
O2 SMS capture allows supported SMS communications from corporate-owned and corporate-liable O2 mobile numbers to be archived for compliance review.
This article covers SMS capture only. Voice call capture is not included in this onboarding workflow.
To start setup, your organization provides the required O2 account, user, and mobile number details to MCO. MCO uses that information to coordinate provisioning with TeleMessage and the carrier.
O2 and TeleMessage also complete an SFTP setup that allows O2 data to be delivered for capture processing. The O2 public key for SFTP is generated by TeleMessage and must be deployed by O2.
Capture limitations
Communication type | Capture support |
SMS | Supported when the O2 number is provisioned for archiving and SMS restrictions are removed. |
Voice calls | Not included in this onboarding article. |
iMessage | Not captured through O2 SMS archiving. |
RCS | Not captured through O2 SMS archiving. |
Confirm the O2 account setup
Before submitting users for capture, confirm the O2 account is ready for onboarding.
Requirement | Description |
O2 Capture purchase | Your organization must purchase O2 Capture (MVR) directly from O2. |
Corporate or enterprise account | Your organization must have a corporate or enterprise account with O2. |
O2 enablement | An O2 representative must assist with enabling the feature. |
Capture Mobile access | Your organization must have an administrator account and user licenses from Capture Mobile. |
Billing details | Your organization must have the billing contact details required for onboarding forms. |
Archive destination | Your organization must confirm the desired destination for archived data. |
Employee notification | Employees must be informed that SMS communications will be archived for mobile compliance and governance. |
Confirm the mobile number setup
Each O2 mobile number that requires capture must be ready for SMS archiving.
Requirement | Description |
Corporate-owned device | The device must be owned by the organization. |
Corporate-liable number | The mobile number must be corporate-liable. |
O2 network | The number must be on the O2 network. |
SMS enabled | SMS must be enabled for the number. |
SMS restrictions removed | SMS restrictions must be removed before archiving can begin. |
Enhanced messaging disabled | iMessage and RCS must be disabled to support SMS archiving. |
O2 archiving enabled | O2 must set up the number for archiving. |
Provide O2 setup details to MCO
Provide the required O2 setup details to your MCO implementation representative or MCO Support.
Include the following information:
Field | Description |
Company name | Name of the organization requesting O2 SMS capture. |
O2 account details | O2 corporate or enterprise account information required for onboarding. |
Billing contact details | O2 billing contact information required for onboarding forms. |
Capture scope | Confirm that the request is for SMS capture only. |
Archive destination | Destination for archived data, such as Microsoft 365 or SMTP. |
SMTP details | Email address or destination details if SMTP is selected. |
Covered users | List of employees who require O2 SMS capture. |
Mobile numbers | O2 mobile numbers that should be provisioned for SMS archiving. |
Provide O2 user details to MCO
Provide the required user and mobile number details for each employee who requires O2 SMS capture.
Field | Description |
First name | First name of the employee. |
Last name | Last name of the employee. |
Email address | Employee email address used for identification and message metadata. |
Mobile number | O2 mobile number in international format. |
Device ownership | Confirmation that the device is corporate-owned. |
Number liability | Confirmation that the number is corporate-liable. |
SMS status | Confirmation that SMS is enabled and SMS restrictions are removed. |
SFTP setup
O2 SMS capture requires SFTP setup between O2 and TeleMessage.
TeleMessage generates the private and public keys for SFTP setup. The public key must be deployed by O2. After O2 completes the SFTP setup, O2 provides SFTP credentials that are used by TeleMessage to complete the setup.
Customers should provide required O2 and SFTP setup details to MCO. MCO coordinates directly with TeleMessage.
NOTE: Do not send private keys through unsecured channels. MCO will advise how required setup details should be shared during implementation.
Submit setup details to MCO
Confirm your organization has purchased O2 Capture (MVR) directly from O2.
Confirm the request is for SMS capture only.
Confirm employees use corporate-owned and corporate-liable mobile devices on the O2 network.
Confirm enhanced messaging services, such as iMessage and RCS, are disabled.
Confirm SMS restrictions are removed from all O2 numbers that require archiving.
Provide the required account, billing, archive destination, user, and mobile number details to your MCO implementation representative or MCO Support.
MCO reviews the details and coordinates with TeleMessage to complete O2 SMS capture provisioning.
MCO coordinates the required setup activities, including SFTP setup and user registration.
User registration
Users can be registered for O2 SMS capture through the method required for your implementation.
Registration method | Description |
Excel sheet | Employee details are provided in an Excel sheet for enrollment. |
Map users in MCO eComms
After provisioning is complete, users must be mapped in MCO eComms so captured O2 SMS communications can be associated with the correct user profiles.
SMS users are typically mapped by mobile number.
Sign in to MCO eComms as an administrator.
Go to Settings > Users.
Locate the user you need to map.
Click Edit.
Locate the Sources section.
Click Edit in the Sources section.
Click Add Source.
In Source name, select the SMS source used for O2 SMS capture.
In Unique Identifier, enter the user’s mobile number.
Click the check icon.
Click Save.
Message availability
Employees are registered and activated for archiving to MCO. This process may take up to five business days.
Archiving begins after registration is complete, provided that O2 has set up the numbers for archiving and there are no SMS restrictions on those numbers.
TeleMessage may retrieve historical data for up to 30 days, depending on the source setup and availability.
Result
After O2 SMS capture is provisioned and users are mapped in MCO eComms, captured SMS communications can be associated with the correct user profiles and reviewed according to your organization’s configured policies and license limitations.