For compliance administrators and mobile program administrators.
Before you begin
Confirm your organization meets the Bell requirements for message archiving before you request onboarding.
Your organization has an administrator account and user licenses from MCO.
Your organization has a Bell corporate or enterprise account.
Your organization has the billing contact details needed to complete the onboarding forms.
Employees use corporate-owned and corporate-liable mobile phones on Bell.
Employees have been informed that the service is used for mobile compliance and governance and that their communications will be archived.
SMS and MMS are enabled for each Bell number that requires capture.
Enhanced messaging services, such as iMessage on iPhone devices and RCS on Android devices, are disabled.
SMS and MMS restrictions are removed from the Bell numbers that need to be archived.
NOTE: MCO coordinates all setup with TeleMessage and the carrier.
WARNING: Bell Capture is available only for corporate-owned and corporate-liable mobile phones on Bell. It is not available for employee-owned devices or consumer accounts.
Bell capture overview
Bell Capture allows supported SMS and MMS communications from corporate-owned and corporate-liable Bell mobile numbers to be archived for compliance review.
To start setup, your organization provides the required Bell account, billing, user, and mobile number details to MCO. MCO uses that information to coordinate provisioning with TeleMessage and the carrier.
Bell numbers must be provisioned for archiving before they can register and activate employees. Archiving begins after registration is complete, provided that Bell has set up the numbers for archiving and there are no SMS or MMS restrictions on those numbers.
Capture limitations
Communication type | Capture support |
SMS | Supported when the Bell number is provisioned for archiving and SMS is enabled. |
MMS | Supported when the Bell number is provisioned for archiving and MMS is enabled. |
iMessage | Not captured through Bell Capture. |
RCS | Not captured through Bell Capture. |
Confirm the Bell account setup
Before submitting users for capture, confirm the Bell account is ready for onboarding.
Requirement | Description |
Bell account type | Your organization must have a Bell corporate or enterprise account. Consumer accounts are not supported. |
Account verification | Contact Bell if you need to verify whether your account type is supported. |
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 where archived data will be accessed, such as Microsoft 365 or SMTP. |
SMTP details | If SMTP is selected as the archive destination, provide the email address where archived data will be viewed. |
Employee notification | Employees must be informed that SMS and MMS communications will be archived for mobile compliance and governance. |
Confirm the mobile number setup
Each Bell mobile number that requires capture must be ready for message archiving.
Requirement | Description |
Corporate-owned phone | The phone must be owned by the organization. |
Corporate-liable number | The mobile number must be corporate-liable. |
Bell network | The number must be on Bell. |
SMS enabled | SMS must be enabled for the number. |
MMS enabled | MMS must be enabled for the number. |
SMS and MMS restrictions removed | SMS and MMS restrictions must be removed before archiving can begin. |
Enhanced messaging disabled | iMessage and RCS must be disabled to support message archiving. |
Bell archiving enabled | Bell must set up the number for archiving. |
Provide Bell setup details to MCO
Provide the required Bell setup details to your MCO implementation representative or MCO Support.
Include the following information:
Field | Description |
Company name | Name of the organization requesting Bell Capture. |
Bell account details | Bell corporate or enterprise account information required for onboarding. |
Billing contact details | Bell billing contact information required for onboarding forms. |
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 Bell Capture. |
Mobile numbers | Bell mobile numbers that should be provisioned for archiving. |
Billing Account Number | Billing Account Number, or BAN, associated with the Bell mobile numbers. |
Provide Bell user details to MCO
Provide the required user and mobile number details for each employee who requires Bell 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 | Bell mobile number in international format. |
Billing Account Number | BAN associated with the user’s Bell mobile number. |
Device ownership | Confirmation that the phone is corporate-owned. |
Number liability | Confirmation that the number is corporate-liable. |
SMS and MMS status | Confirmation that SMS and MMS are enabled and restrictions are removed. |
Provision Bell numbers
Bell numbers must be provisioned before the capture service can register and activate users for archiving.
Provisioning may be completed by either:
Provisioning method | Description |
Bell provisioning | Your organization contacts Bell directly and provisions employees for Bell Capture. |
MCO-assisted provisioning | Your organization provides required information, such as mobile number and BAN, to MCO. MCO coordinates the request with TeleMessage and the carrier. |
Submit setup details to MCO
Confirm your organization has a Bell corporate or enterprise account.
Confirm employees use corporate-owned and corporate-liable mobile phones on Bell.
Confirm SMS and MMS are enabled for each Bell number that requires capture.
Confirm enhanced messaging services, such as iMessage and RCS, are disabled.
Confirm SMS and MMS restrictions are removed from all Bell numbers that require archiving.
Provide the required account, billing, archive destination, user, mobile number, and BAN details to your MCO implementation representative or MCO Support.
MCO reviews the details and coordinates to complete Bell Capture provisioning.
Capture Mobile registers and activates employees for archiving to the specified destination.
User enrollment
Users are enrolled or activated for Bell Capture after the required provisioning details are provided and the Bell numbers are ready for archiving.
Capture Mobile registers and activates employees for the specified archive destination. This process may take up to five business days.
Your customer administrator receives a welcome letter from Capture Mobile. The welcome letter includes setup information and archiving instructions.
Map users in MCO eComms
After provisioning is complete, users must be mapped in MCO eComms so captured Bell SMS and MMS 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 Bell Capture.
In Unique Identifier, enter the user’s mobile number.
Click the check icon.
Click Save.
Message availability
Registration and activation of employees for archiving to MCO may take up to five business days.
Archiving begins after registration is complete, provided that Bell has set up the numbers for archiving and there are no SMS or MMS restrictions on those numbers.
Captured communications may not appear in MCO eComms immediately. Availability depends on Bell provisioning, capture activation, transfer timing, user mapping, and MCO eComms processing.
Result
After Bell Capture is provisioned and users are mapped in MCO eComms, captured SMS and MMS communications can be associated with the correct user profiles and reviewed according to your organization’s configured policies and license limitations.