KNOWLEDGE CENTER

Campaign registration recommendations

A2P 10DLC Campaign registration recommendations

March 13, 20253 min read

Campaign registration recommendations

Campaign registrations should meet each of the following descriptions for each field.

Campaign Type

Please choose the use case that best represents your campaign. For more information, please refer to the details provided here.

Custom HTML/CSS/JAVASCRIPT

Campaign Description

The description should be thorough and explain the campaign’s objective or purpose. Provided description needs to answer who the sender is, who the recipient is, and why messages are being sent to the intended recipient.

Custom HTML/CSS/JAVASCRIPT


How do end-users consent to receive messages?

The answer should contain the following information:

  1. The program or product description

  2. Telephone number(s) from which messaging will originate

  3. Identify of the organization or individual being represented in the initial message

  4. Clear and conspicuous language about opt-in and any associated fees or charges

  5. Compliant Privacy Policy

  6. Other applicable terms and conditions (e.g., how to opt-out, customer care contact information)

Opt-in needs to apply per campaign, should be not transferable or assignable and can not be obscured in terms and conditions (especially terms related to other services). If multiple opt-in methods can be used for the same campaign, please list them all.


A compliant Privacy Policy must state that no mobile information will be shared with third parties/affiliates for marketing/promotional purposes. Information sharing to subcontractors in support services, such as customer service is permitted. All other use case categories exclude text messaging originator opt-in data and consent; this information will not be shared with any third parties.


Campaign reviewers need to be able to verify details provided in this field. Provide evidence such as a hosted link to screenshot or document for opt-in that occurs behind a gated login or on a paper form.

Custom HTML/CSS/JAVASCRIPT

Sample message
Sample messages should reflect actual messages to be sent under the campaign and indicate templated fields with brackets. Ensure consistency with use case and campaign description.

Sample messages should identify who is sending the message (brand name). Ensure that at least one sample message includes your business name.

Include opt-out language to at least 1 sample message.

Custom HTML/CSS/JAVASCRIPT

Opt-in Keywords

Please provide all keywords that allow users to opt-in to receive campaign messages.

Custom HTML/CSS/JAVASCRIPT

Opt-in Confirmation Message

Campaign must provide customers with an opt-in confirmation message. This is required for all recurring campaigns, regardless of opt-in method,   CTIA Messaging Principles and Best Practices.


It should not exceed 160 characters. Must have the following:

  1. Program (brand) name or product description

  2. Customer care contact details: Reply HELP for help

  3. Opt-out instructions: Reply STOP to opt-out.

  4. Disclosure: that the messages are recurring and the frequency of the messaging

  5. Message frequency (must align with the frequency on the CTA and SMS Terms)

  6. A “Message and data rates may apply” disclosure

Custom HTML/CSS/JAVASCRIPT

Opt-out Keywords

Please provide all keywords that allow end users to stop receiving messaging from this campaign.

Custom HTML/CSS/JAVASCRIPT

Opt-out Confirmation Message

When end users send opt-out keywords, the response messages need to include acknowledgement of opt-out request, brand name, and confirmation that no further messages will be sent.

Custom HTML/CSS/JAVASCRIPT

Help Keywords

Please provide all keywords that allow end users to receive more information about this campaign.

Custom HTML/CSS/JAVASCRIPT

Help Message

When end users send help, the response message needs to include brand name, phone number, or email address.

Custom HTML/CSS/JAVASCRIPT

 

A2P 10DLC Campaign registration recommendationsPHONE
Back to Blog
Campaign registration recommendations

A2P 10DLC Campaign registration recommendations

March 13, 20253 min read

Campaign registration recommendations

Campaign registrations should meet each of the following descriptions for each field.

Campaign Type

Please choose the use case that best represents your campaign. For more information, please refer to the details provided here.

Custom HTML/CSS/JAVASCRIPT

Campaign Description

The description should be thorough and explain the campaign’s objective or purpose. Provided description needs to answer who the sender is, who the recipient is, and why messages are being sent to the intended recipient.

Custom HTML/CSS/JAVASCRIPT


How do end-users consent to receive messages?

The answer should contain the following information:

  1. The program or product description

  2. Telephone number(s) from which messaging will originate

  3. Identify of the organization or individual being represented in the initial message

  4. Clear and conspicuous language about opt-in and any associated fees or charges

  5. Compliant Privacy Policy

  6. Other applicable terms and conditions (e.g., how to opt-out, customer care contact information)

Opt-in needs to apply per campaign, should be not transferable or assignable and can not be obscured in terms and conditions (especially terms related to other services). If multiple opt-in methods can be used for the same campaign, please list them all.


A compliant Privacy Policy must state that no mobile information will be shared with third parties/affiliates for marketing/promotional purposes. Information sharing to subcontractors in support services, such as customer service is permitted. All other use case categories exclude text messaging originator opt-in data and consent; this information will not be shared with any third parties.


Campaign reviewers need to be able to verify details provided in this field. Provide evidence such as a hosted link to screenshot or document for opt-in that occurs behind a gated login or on a paper form.

Custom HTML/CSS/JAVASCRIPT

Sample message
Sample messages should reflect actual messages to be sent under the campaign and indicate templated fields with brackets. Ensure consistency with use case and campaign description.

Sample messages should identify who is sending the message (brand name). Ensure that at least one sample message includes your business name.

Include opt-out language to at least 1 sample message.

Custom HTML/CSS/JAVASCRIPT

Opt-in Keywords

Please provide all keywords that allow users to opt-in to receive campaign messages.

Custom HTML/CSS/JAVASCRIPT

Opt-in Confirmation Message

Campaign must provide customers with an opt-in confirmation message. This is required for all recurring campaigns, regardless of opt-in method,   CTIA Messaging Principles and Best Practices.


It should not exceed 160 characters. Must have the following:

  1. Program (brand) name or product description

  2. Customer care contact details: Reply HELP for help

  3. Opt-out instructions: Reply STOP to opt-out.

  4. Disclosure: that the messages are recurring and the frequency of the messaging

  5. Message frequency (must align with the frequency on the CTA and SMS Terms)

  6. A “Message and data rates may apply” disclosure

Custom HTML/CSS/JAVASCRIPT

Opt-out Keywords

Please provide all keywords that allow end users to stop receiving messaging from this campaign.

Custom HTML/CSS/JAVASCRIPT

Opt-out Confirmation Message

When end users send opt-out keywords, the response messages need to include acknowledgement of opt-out request, brand name, and confirmation that no further messages will be sent.

Custom HTML/CSS/JAVASCRIPT

Help Keywords

Please provide all keywords that allow end users to receive more information about this campaign.

Custom HTML/CSS/JAVASCRIPT

Help Message

When end users send help, the response message needs to include brand name, phone number, or email address.

Custom HTML/CSS/JAVASCRIPT

 

A2P 10DLC Campaign registration recommendationsPHONE
Back to Blog