ATIPXpress TeleMessage Integration

  • Updated on Feb 18, 2026
  • Published on Jan 29, 2026
  • 2 minute(s) read
Prev Next

1 Introduction

1.1 About TeleMessage Integration

Users must configure their application settings prior to integrating ATIPXpress with

TeleMessage. This manual outlines the requirements and steps for configuring ATIPXpress for TeleMessage integration.  

1.2 TeleMessage Integration Prerequisites

Complete the following steps to ensure your ATIPXpress application is ready to be configured for TeleMessage integration:

  1. If you are not on ATIPXpress version 11.5.0 or higher, upgrade the application first.

    Follow the steps in the ATIPXpress Deployment Manual to upgrade your application.

  2. Upgrade the application license in the Administration settings.

Note: The TeleMessage feature is tied to your application license, and the feature is automatically enabled with the appropriate license. Please upgrade your license to include the TeleMessage integration.

  1. Ensure that the TeleMessage integration is enabled in the Application Features menu (Administration > Features and Licenses > Application Features). It should be enabled automatically after upgrading your license. If not enabled after upgrading your license, select the TeleMessage Integration checkbox and save the configuration:

 

  1. The TeleMessage Integration Configuration menu should be visible when accessing Administration > System Administration. If the menu is not visible, log out of the application and log back in.

 

Once these prerequisites have been met, you can set configurations within the application to enable the TeleMessage integration.

2 TeleMessage Integration Configuration

Follow the steps below to configure the TeleMessage integration:

  1. Navigate to the TeleMessage Integration Configuration menu (Administration > System Configuration > TeleMessage Integration Configuration):

 

  1. The TeleMessage Integration Configuration screen appears as shown below. Use these fields to configure the integration. They are described in the following table.

    Note: Please consult with Casepoint support to obtain the correct values for these fields, based on your specific environment and integration.

 

Field

Description

Client Id

The Client Id (or Application ID) represents the application's identity in the directory. When the application interacts with Azure services or APIs, it presents this ID as part of the authentication process to prove its identity.

Secret Key Value

A credential, often a string value, generated for an application to authenticate itself against Azure services. This key is paired with the Client ID to authenticate the application. It's like a password and is used as part of the authentication flow to ensure that only the application with the correct credentials can access protected resources.

Email

Represents a Microsoft Entra user account used for this integration.

Tenant Id

The identifier of the Azure AD tenant where the application and its related resources (like users, groups, and applications) are registered. Azure AD tenants are unique environments created by organizations to manage and secure access to their resources. The Tenant Id is used to specify which Azure AD tenant the application is associated with.

MailBox

The location where your emails, contacts, calendar events, tasks, and other personal information are stored.

  1. After configuring these fields, click Save to save the settings.

  2. Once your integration is configured, your users will be able to search the TeleMessage Mobile Message Archive using the Add Documents drop down and selecting Mobile Message Archive.

Related articles