Communication Channels

The Mobile Campaign Manager contains a variety of communication tools that allow users to quickly and effectively interact with other users' within the platform.

The communication options include:

To learn more about any of these channels, select one of the links listed above.


Sending and receiving Short Message Service (SMS) is one of the most common tasks performed in the Mobile Campaign Manager.

The word SMS and the phrase text message are used interchangeably.

SMS is supported as both a main communication channel to reach a user or as a fallback to other Communication Channels. Throughout this platform documentation and in mobile marketing, the following terms are widely used:

  • Shortcode: shorter than full telephone numbers, they can be used to address SMS and MMS messages. They are typically 4 or 5 digits long and are designed to be easier to read and remember.

  • Longcode: a typical telephone number. Some times, shortcodes are not available, and long codes are configured to be used instead. The available reporting information for campaigns based on long codes is significantly more limited than when a shortcode is used. This limitation is based on communication protocols.

  • MO (Mobile Originated): an SMS message originated from a user’s mobile device and sent to the platform by addressing it to a preconfigured shortcode or long code.

  • MT (Mobile Terminated): an SMS originated from the platform and sent to a user’s mobile device. The message will be received from the configured shortcode or long code as the sender.

The available shortcodes and long codes are configured to the user's account and are listed at the top of the Main Menu (select the Main Menu button to open):


If more than one number is available, the selected number will be associated by default to all platform campaigns. It is always best practice to check the selected number upon logging into the campaign manager.

Data Coding

The Mobile Campaign Manager supports the four Data Codings as defined in section of the SMPP 3.4 standard:

  • SMSC default alphabet (7 or 8-bits)

  • LATIN 1 (8-bits)

  • US ASCII (7-bits)

  • UCS2 (16-bits)

It is possible to encode any language for SMS communications using the UCS2 Data Coding, however, SMS are limited to 70 characters max each (although concatenation can be used if the carrier supports it).


Multimedia Messaging Service (MMS) is supported by the platform to be used as any other communication channel.

The use of MMS may need some level of integration with the mobile operator's MMS Centre.

The platform leverages a third-party MMS Gateway (currently Mbuni: Open Source MMS Gateway) so that establishing connectivity, typically MM&, with any additional MMC Centre is very straightforward.

The campaign manager handles all the complexity of the assembly of the MMS message, commonly in the Synchronized Multimedia Integration Language (SMIL) format.

It simply requires text and images as input:



Email can be used as the main or an additional Communication Channel.

It leverages Amazon Simple Email Service as a robust, scalable, and reliable email service.

Originating email address(es) need to be pre-configured and validated similar to the case of shortcodes in SMS.


Check with your Administrator that all the email service validation has been done prior to its use.

Emails can be generic, where the same communication is sent to all users, or they can be configured to be personalized.

The Mobile Engagement Platform complies with all mobile marketing best practices, including providing a simple option for adding an opting-out mechanism to each email sent.

Push Notifications

The platform supports Push Notifications as the main or complementing Communication Channel.

This support is right out of the box with no special configuration necessary.

Both iOS and Android mobile devices are supported following the corresponding specifications of both services:

The use of Push Notifications from the campaign manager offers some significant advantages over the direct connection to the notification servers:

  • Consistency across all communication channels

  • Rich and interactive messages

  • Silent notifications: the mobile device application that receives the notification may decide to display it or not to the user

Was this article helpful?
0 out of 0 found this helpful



Article is closed for comments.