Jump to: navigation, search


An enterprise contains one top level account called the Enterprise Account. From within the Enterprise, there will be one or more individual accounts in which messaging campaigns are run.

The enterprise account is created automatically when the enterprise is created. It provides many of the same functions that are available to the individual accounts, but it also provides a way for you to perform some functions globally across all individual accounts at once.

Sign in to the Enterprise Manager

To sign in to the enterprise manager and select an account:

  1. Go to the enterprise sign in page at the URL supplied. (Individual account users sign in using a different URL.)
  2. Enter your User ID (which is the account email address) and your initial password provided to you when the enterprise was created. You will be asked to change your password upon login.

Refer to the Accounts page to learn how to find, create, and sign in to accounts within the enterprise.


The following rules apply to passwords:

  • Although passwords can be 8-10 characters long, password length is set by the enterprise administrator, so the minimum number of characters may be greater than 8.
  • Strong passwords contain a mix of letters, numbers and special characters. Passwords associated with secure enterprises must contain at least one of each.
  • Valid characters for passwords are A-Z, a-z, 0-9, the special characters $-_.+!*'(), and spaces.
  • Although other special characters can be used, they can create problems when entering passwords from a command line or in a web address, so they should be avoided.
  • Passwords cannot start or end with a space.
  • You cannot use an underscore (_) as the last character in a password.
  • A password is viable for a maximum of 90 days and then it must be changed. Users receive a warning message 13 days in advance that the password will expire. If you do not change your password in time, you receive a message to contact Customer Care to have the password reset.
  • You are restricted from using the last four most recently used passwords when changing your password.

Change a password

To change the password of your account:

  1. On any page, click the tools icon and click Change Password.
  2. Note that to sign in to the account over a telephone, the password must contain only digits. (0-9)
  3. Enter the current password.
  4. Enter the new password and confirm by entering again.
  5. Click Submit.

Reset a password

By default, the password reset feature is disabled for all clients but can be enabled on the settings page, by clicking Enable self-serve password reset.

The Forgot Password link appears on the login page but is only available if the feature is enabled for the enterprise.

Clicking the Forgot Password link will direct the user through the reset password scenario set up for the enterprise to the Create new password dialog. At a minimum, the user must supply the correct email address. The email address does not need to be the same as their User ID, but it should be a valid email address for that user. Password reset notifications will be sent to that email address. Users may also need to answer up to three security questions.

To set up password reset later, or change an email address or security questions, the user can:

  1. Go to the Edit Profile dialog via the menu in the upper-right corner
  2. Enter the email address. A verification email will be sent to that address with a link to verify that the email is valid.
  3. Answer the security questions, as described above.

Note that the Enterprise Manager has the option to see what state an individual login is in. From the Enterprise Settings page, click User - Edit Enterprise User to see their current status relative to the password reset feature. Whether or not a user can use the password reset feature, the Enterprise Manager can still reset their password via the Change password link on the Edit Enterprise User page.

Sensitive data

If you need to store or transmit sensitive data (such as credit card numbers or social security numbers), contact your account representative and request that the Secure the Enterprise option is enabled. You cannot enable or disable this option yourself.

When the Secure the Enterprise option is selected:

  • any data you store in the other1 or other2 fields of your contact lists will be stored in the system database in encrypted format. This data will be displayed in encrypted format in any detail reports that include the data. This data will also be displayed on-screen in encrypted format.
  • contact lists and suppression lists that are transmitted or imported into the messaging system will be encrypted during the data transfer. These files must be transmitted or imported in TXT or CSV format. ZIP and XLS formats are not supported for encrypted data. You must also use an input specification file when transmitting or uploading the data.
  • files handled via automation must be encrypted
  • while running a sub-campaign, secure data entered by your customers or clients using DTMF tones will be encrypted.
Changes to the Secure the Enterprise option do not take effect for up to 10 minutes. After the option is selected, wait at least 10 minutes before uploading any contact lists to ensure that the other1 and other2 fields are encrypted.

PGP encryption

PGP is asymmetric cryptography software, which means that sensitive data is encrypted with one key (known as a public key), and decrypted with another (known as a private key). If a user needs to receive data but wants to make sure that this data is protected (encrypted) during the transport, they could use PGP to protect the data.

To use PGP, the user generates both private and public keys and gives the public key to some other party. The other party uses the public key to encrypt the data and sends the encrypted data to the user. The user then decrypts the data with the private key.

PGP uses a public key system in which each user has a publicly known encryption key and a private key known only to that user. When a customer sends a file, it is encrypted with the receiving group's public key. When a client receives a file from the platform, it is decrypted using the client's private key. Both the platform administration and the client must exchange public keys before using this feature.

This page was last edited on July 14, 2017, at 14:06.
Comments or questions about this documentation? Contact us for support!