Set Up SMS Messaging
Goal
To set up the inbound mobile ID, outbound mobile ID, and reply handling settings for an SMS group, as part of the SMS messaging setup process.
Prerequisites
SMS messaging is an extra feature of Mapp Engage. Before you can send SMS messages, you must do the following.
- Work with your account manager to register the necessary codes and keywords for SMS messaging. For more information, see SMS Code Types.
- Create one or more dedicated groups for SMS sendout. For instructions, see Create a New Group.
Procedure
- In the main navigation, click Audience > Groups.
- In the Actions column next to the group that you want to configure, click the
symbol. - Open the Reply Handling tab and expand the SMS area.
- In the Inbound Mobile ID input field, enter the inbound mobile ID from your service provider. See below for details.
- In the Outbound Mobile ID input field, enter your outbound mobile ID. See below for details.
- From the Replies drop-down list, select how Mapp Engage handles SMS replies. See below for details.
- Click Save.
Define the Inbound Mobile ID
Contacts use the inbound mobile ID to reply to an SMS message or to contact the group. Mapp Engage uses the inbound mobile ID to route incoming SMS messages to the correct Mapp Engage group.
The inbound mobile ID is registered with SMS service providers. The inbound mobile ID is either a unique number or a keyword, depending on your SMS setup. For more information, see SMS Code Types.
You can use each inbound mobile ID for only one Mapp Engage group. You cannot re-use the inbound mobile ID in other Mapp Engage groups.
If a contact sends an SMS to a shared short code and the inbound SMS does not contain a recognized keyword, Mapp Engage does not know how to process the SMS. Mapp Engage ignores the SMS.
Shared Short Code Plus Keyword | Dedicated Short Code | Long Number | |
|---|---|---|---|
Inbound Mobile ID | Enter the keyword. Example: PIZZA | Enter the short code. Example: 88888 | Enter the long number. Example: 441234567890 |
Define the Outbound Mobile ID
The Outbound Mobile ID field stores the TPOA (Transmission Path Originating Address). The TPOA is a header field in an SMS message. On their mobile phones, your recipients see the TPOA displayed as the sender of the message.
This field contains the message sender's number or identity. This depends on the type of code you use for sendout.
Shared Short Code Plus Keyword | Dedicated Short Code | Long Number | |
|---|---|---|---|
Outbound Mobile ID | Enter the short code. Example: 12345 If you use a shared short code and multiple keywords in one Mapp Engage system, then you will use the shared short code as the outbound mobile ID in several groups. | Enter the short code. Example: 88888 You can use a dedicated code in multiple Mapp Engage groups. In that case, however, Mapp Engage will not know how to route inbound SMS messages from your contacts. | Enter the long number. Example: 441234567890 You can use a dedicated code in multiple Mapp Engage groups. In that case, however, Mapp Engage will not know how to route inbound SMS messages from your contacts. |
Alphanumeric Outbound Mobile ID
As an alternative to entering your mobile code in the Outbound Mobile ID, you can create a custom alphanumeric TPOA. For example, it is possible to use your company name as the TPOA.
The maximum length of the TPOA is:
16 characters for a number (for example, a phone number).
11 characters for an alphanumeric code (for example, a company name).
The TPOA cannot contain any underscores, empty spaces or special characters.
Advantages
On their mobile phones, your recipients see your company name displayed as the sender of the message.
Disadvantages
With this method, your recipients cannot reply directly to the SMS. This means that you must include a way to unsubscribe in the body of the SMS text. For example, the SMS can include the text "Text PIZZA CANCEL to 12345 to cancel your SMS subscription." This reduces the number of remaining characters in the SMS. Note that if you use a shared short code and keyword to send SMS messages, you must tell your contacts to include the keyword in the reply.
Some countries require you to register a custom TPOA. For France, SAP has implemented a mechanism that transforms any unregistered TPOA back into the original number. In other countries, SMS messages sent with an unregistered TPOA are not delivered.
Define How Mapp Engage Handles Incoming Messages
Mapp Engage enables two-way marketing with SMS. This means that your contacts can send SMS messages to your Mapp Engage group.
You must tell Mapp Engage how to handle incoming SMS messages. This is defined in the group settings.