SMS Code Types

Description

A shared short code is a 3-6 digit number plus one or more unique keywords. You can request more than one keyword and use the keywords for different promotions or purposes. It is also possible for more than one company to share a short code and to use different keywords in each company.

Examples:

12345 FASHION
12345 INSIDERS

A dedicated short code is a 3-6 digit number that only your company can use. No keyword is required.

Example:

88888

A long number is a telephone number that is enabled for SMS.

A long number is internationally available. A long number is appropriate for companies who want to reach multiple markets with one number.

Example:

441234567890

Advantages

• Less expensive than a dedicated short code.

• Faster setup than a dedicated short code.

• Having multiple keywords allows you to run different SMS programs on the same mobile number.

• A dedicated short code clearly identifies the sender. In some countries, you can set up a "vanity code" that is easy to remember (for example, 88888).

• The contact does not need to know a special keyword to reply to a message.

• A long number is owned by your company (not leased from a mobile provider) and can be used for a long time.

• A long number can receive incoming SMS messages from other countries.

• A long number is often cheaper and faster to implement than a short code.

Limitations

• A contact who sends you an SMS must include the correct keyword in the SMS. Otherwise, the inbound SMS cannot be routed to your Mapp Engage system.

• A short code is limited to one country. You must set up a short code for every country to which you want to send SMS messages.

• A short code is leased, not owned.

• A dedicated code is more expensive than a shared code. In some countries, operator approval takes a long time.

• A dedicated code is limited to one country. You must set up a short code for every country to which you want to send SMS messages.

• A dedicated code is leased, not owned.

• Some countries (including the U.S.) do not allow SMS marketing with a long number.

• A long number is more difficult for contacts to remember.

• Long numbers are less well regulated than short codes.

Costs for End User

Usually, FTEU (free to the end-user).

Make sure to check local country regulations before you start to send, and inform your SMS subscribers accordingly.

Usually, FTEU (free to the end-user).

Make sure to check local country regulations before you start to send, and inform your SMS subscribers accordingly.

May incur normal SMS charges for the end-user in some countries. Make sure to inform your contacts that "Msg. & data rates may apply".

In other countries, all SMS messages are free for the recipient.

Mapp Engage Groups

Create one Mapp Engage group for every keyword you register. You can use each keyword (inbound mobile ID) in only one Mapp Engage group.

You can use the shared short code (outbound mobile ID) in multiple Mapp Engage groups.

Create one Mapp Engage group for every dedicated short code you register.

You cannot use the dedicated short code as the inbound mobile ID in multiple Mapp Engage groups.

Create one Mapp Engage group for every long number you register.

You cannot use the long number as the inbound mobile ID in multiple Mapp Engage groups.

Group Settings

(​Reply Handling​ tab)

• ​Inbound Mobile ID​: Enter the keyword.
  Example: PIZZA

• ​Outbound Mobile ID​: Enter the short code.
  Example: 12345

• ​Inbound Mobile ID​: Enter the short code.
  Example: 88888

• ​Outbound Mobile ID​: Enter the short code.
  Example: 88888

• ​Inbound Mobile ID​: Enter the long number. Example: 441234567890

• ​Outbound Mobile ID​: Enter the long number. Example: 441234567890

To Contact the Group

Contact sends an SMS to the short code. The SMS message must begin with the keyword. (This is the keyword registered with SAP and entered in the group settings in the ​Inbound Mobile ID​ input field.)

Example:

Contact sends a text to 12345. The first word in the inbound SMS is PIZZA.

If a contact sends an SMS to a shared short code and the inbound SMS does not contain a recognized keyword, SAP does not know how to process the SMS. In this case SAP cannot route the reply to your Mapp Engage system.

Contact sends an SMS to the short code. The SMS does not have to contain a keyword.

Example:

Contact sends an SMS with any body text to 88888.

Contact sends an SMS to the long number. The SMS does not have to contain a keyword.

Example:

Contact sends an SMS with any body text to 441234567890.

To Initiate an Automation

Words that should trigger an automation can appear anywhere in the body text - after the keyword!

Example:

Text PIZZA HELP to 12345 to get terms & conditions.

Words that should initiate an automation can appear anywhere in the body text.

Example:

Text HELP to 12345 to get terms & conditions.

Words that should initiate an automation can appear anywhere in the body text.

Example:

Text HELP to 12345 to get terms & conditions.