Search Results

A2P Regulations & Conduct

About A2P Messaging

All traffic passing through Aerialink is categorized as application-to-person (A2P) traffic, i.e. business messaging, regardless of use case. Reference section 4 “CONSUMER / NON-CONSUMER TRAFFIC CLASSIFICATION” of CTIA Messaging Principles and Best Practices for details.

Registration is mandatory for traffic delivery towards carriers in the United States. Please note that registration does not “white-list” your traffic, as it will still be subject to carrier violation filtering. Unverified toll-free numbers and uncertified short codes are unable to send traffic. Unregistered 10DLC brands found to be sending traffic will be subject to heavy filtering, higher-rated carrier surcharge fees and potential additional fines until registered.

Some examples of A2P messaging include:

  • Customer Service - customer service agents answering questions, schedule appointments, provide service information or conduct a satisfaction survey
  • Reminders, Notifications, Alerts - delivery updates, appointment reminders, weather alerts
  • UCaaS (Unified Communications as a Service)
  • Marketing, Promotional
  • 2FA (Two-Factor Authentication)
  • Anonymized Numbers (Proxy Services) - car service communications between driver and passenger, customer-to-shopper grocery service chatting

For these messages to reach U.S. mobile subscibers they must be part of an approved campaign and are subject to ongoing compliance and monitoring obligations. Please read all articles on this page to familiarize yourself with the requirements expected of A2P traffic.

U.S. Compliance Overview

For customers who operate business messaging over Short Codes, Toll-Free Numbers (TFN), or 10 Digit Long Codes (10 DLC) in the US market, ensure your messaging operations follow the industry guidelines and carrier requirements. Failure to comply with these industry guidelines and carrier requirements could result in non-compliance penalty fees and/or suspension of services. To avoid potential consequences of non- compliance, we would like to highlight the following key points:

  1. Shared codes (Short Codes, Toll Free Numbers and 10DLC) are prohibited.*
  2. Content must always comply with what was originally approved in the Program Brief, Verification Form, or the campaign registry.
  3. For changes to content/programming on any code, submit an updated Program Brief, Verification Form, or 10 DLC Campaign.
  4. Maintain compliance with all rules described in the CTIA Monitoring Handbook and carrier codes of conduct.
  5. Understand content provider responsibilities.
  6. Maintain compliance with consent standards, including those related to deactivated numbers.
  7. Register Short Code, Toll Free, and 10DLC programs/campaigns as accurately as possible.
  8. Avoid prohibited content and prohibited behaviour, and watch out for red flags in your traffic.

Aerialink takes compliance matters seriously and encourages you to verify that all your programs follow the above-mentioned guidelines. In addition to potential non-compliance fees imposed by carriers, Aerialink and upstream providers reserve the right to suspend non-compliant campaigns/programs or campaigns/programs that appear to be fraudulently registered. Non-Compliance Fees are relevant across all number types and are not limited to only 10DLC traffic.

* “Shared code” refers to a single code of any type used by multiple content providers or brands.

Codes of Conduct

Aerialink is committed to creating a healthy messaging ecosystem that serves all participants and to keeping our customers informed about recent changes in the industry, including the CTIA Messaging Principles and Best Practices, available here.

All customers sending A2P traffic are subject to the FCC TCPA and any other applicable state or federal law, the guidelines for A2P traffic set by the CTIA and individual carrier codes of conduct to be executed and enforced at each carrier’s discretion. Failure to comply with carrier codes of conduct may result in damage to the carrier’s trust in the associated content provider or brand, traffic suspension or a permanent ban of traffic from the offender.

Carriers can and do include their own, additional rules and regulations beyond the FCC TCPA and the CTIA Best Practices Guidelines. We recommend that you read through these carrier codes of conduct for details of each carrier’s unique expectations for successful delivery of content on their network. Additionally, the regulations of the carriers and CTIA guidelines have been consolidated on this page for ease of reference. The information below may be updated or changed without notice as the telecommunications ecosystem continues to evolve, so please check this page regularly for updates.

While this page is intended to be a comprehensive representation of all CTIA and carrier expectations, carriers may make changes at any time and without notice. This is therefore not a replacement for reading the carrier documentation itself, nor is it a replacement for independent legal consultation for TCPA compliance.

For an even more thorough, complete understanding of best-practices in the mobile ecosystem, we recommend reading through all Federal & Industry Regulations

Additional CTIA Requirements

The following additional terms apply to toll-free programs under the authority of the CTIA:

  • Only toll-free / long code numbers currently reserved or in working status for the benefit of a toll-free number voice subscriber should be enabled for texting. Businesses only interested in messaging campaigns are encouraged to enable voice recording on the number for a better consumer experience. The recorded message should include the business name and directions for the consumer to utilize the messaging experience.

Additional AT&T 10DLC Requirements

The following additional terms apply to 10DLC programs running on the AT&T network:

  • AT&T 10DLC programs are currently in a registration “grace period” during which all groups and organizations are encouraged to register their SMS campaigns. This grace period has been extended to address specific use cases and allow for additional campaign registration. AT&T will provide thirty days’ notice prior to ending the grace period.
  • Unregistered traffic is subject to P2P spam policies and traffic throughput restrictions. While unregistered senders do not pay fees to the Campaign Registry, they will pay the highest possible message termination fees for AT&T due to their unregistered status.
  • All A2P campaigns must be administered on a separate NNID (NetNumber ID) from P2P traffic.
  • While campaign-level filtering is currently in effect, additional throughput will be available to certain message classes effective September 1st, 2021.
  • Registered senders pay lower message termination fees and are less likely to be marked as spam.
  • Registration does not guarantee message delivery. Campaigns whose end-users file complaints with AT&T may be subject to remedial treatment, including suspension or blocking of unwanted, fraudulent or malicious messages.

Additional T-Mobile 10DLC Requirements

The following additional terms apply to 10DLC programs running on the T-Mobile network:

  • 10DLC does not support delivery receipts (DLR) for Free-to-End-User (FTEU) campaigns.
  • All customers should be prepared to prove ownership of the 10DLC number(s) they intend to use for any and all campaigns, and prove that the numbers in question are enabled for both SMS and voice services.
  • A Letter of Authorization (LOA) is required for those customers whose numbers are assigned to an NNID not under/different from that of Aerialink. The Aerialink team submits LOA and exception requests to T-Mobile on customers’ behalves.
  • There are two T-Mobile exception processes requiring additional application. If one or both special exceptions apply to applicant brands, please contact your Aerialink Account Director or reach out to us through our Help Desk Portal to complete the applicable forms and submit the exception request on your behalf.
  • T-Mobile has established daily messaging caps for brands. Please reference this chart for more information regarding message caps and their relation to vetting scores.

Additional Verizon 10DLC Requirements

The following additional terms apply to 10DLC programs running on the Verizon network:

  • Brands must conduct their own spam monitoring. Campaigns found to be fraudulent or otherwise sending spam traffic will be shut down immediately with zero tolerance.
  • Campaigns which have been shut down due to spam infractions must provide a full RCA (Root Cause Analysis) within forty-eight hours of the spam incident in order to be considered for reactivation. Reactivation is at Verizon’s discretion and is not guaranteed.
  • Long codes must be dedicated - one campaign per code. Exceptions for multiple codes per campaign are not permitted on the Verizon network at this time.

10DLC Registration Agreement

The following agreement, passed through from The Campaign Registry, is applicable to all Aerialink customers registering to run traffic on 10DLC:

Customer represents and warrants to Aerialink of Link Mobility that: (a) the person registering and operating the Customer’s account is over the age of eighteen (18) and has the power and authority to enter into and perform Customer’s obligations under this Agreement; (b) all information provided by Customer to Aerialink is truthful, accurate and complete; (c) if Customer provides a credit or charge card for payment of fees for the Service, Customer is the authorized signatory of the credit or charge card provided to Aerialink to pay the fees; (d) Customer shall comply with all terms and conditions of this Agreement, including, without limitation, the provisions set forth in this Section 4; (e) Customer has provided and will maintain accurate and complete registration information with Aerialink, including, without limitation, Customer’s legal name, address and telephone number; (f) Customer’s access to and/or use of the Campaign Registry does not and will not constitute a breach or violation of any other agreement, contract, terms of use, or similar policy or understanding to which Customer is or may be subject; (g) Customer shall comply with all laws attendant upon its performance of its obligations under this Agreement. (h) Customer and/or the Brand have obtained, and will maintain, all applicable consents, approvals, or permissions required by applicable law, including, without limitation, the Telephone Consumer Protection Act (“TCPA”), 27 U.S.C. § 27, as amended from time to time, to transmit or otherwise send messages to any End Customer; and (i) Customer and/or Brand is operating in accordance with rules, regulations, best practices and guidelines published by MNOs.

Content Provider Responsibilities

All Aerialink customers are responsible for following the guidelines listed below to maintain A2P messaging compliance in addition to adhering to our Acceptable Use Policy.

All Aerialink customers using A2P messaging routes are responsible for:

  1. Obtaining express consent prior to sending messages to any recipients. See Consent Per Content Type below for the required level and type of consent applicable to your messaging content.
  2. Providing an opt-out method, permitting end-users to decline to receive any further messages.
  3. Supplying useful customer care information in response to the “HELP” keyword on any 10DLC long code.
  4. Ensuring messages do not violate CTIA or carrier rules or regulations for acceptable A2P messaging.*
  5. Understanding carriers’ right to re-evaluate messaging use-cases at any time and shut down existing messaging programs at their discretion.
  6. Maintaining of compliant rules and regulations equal to or greater than those imposed by the CTIA, carriers and Aerialink for their own traffic or any A2P traffic resold to customers.
  7. Obtaining use-case information for their own messaging programs or any/all client programs, and maintaining the right and ability to audit said programs upon request by Aerialink.
  8. Avoiding the inclusion of any Protected Health Information content within any part of any messages, including MMS content.
  9. Providing appropriate security and privacy controls to protect subscribers and maintain opt-in and opt-out integrity and full confidentiality of end-user information.
  10. Providing terms of service and privacy policy accessible at point of opt in and on any/all associated landing websites.
  11. Completing 10DLC registration before attempting to send A2P traffic on long codes.
  12. Ensuring all websites whose URL is accessed through message content unambiguously identify the website owner and include a postal mailing address and other contact information.
  13. Complying with all anti-spam filtering and regulation without attempt to avoid detection.

* Note that these rules and regulations are subject to change. Those changes will be reflected in the Aerialink Acceptable Use Policy.

Compliant Best-Practices

The following recommendations, while not explicitly mandated, help to ensure compliance with CTIA and carrier guidelines, as well as maintain best deliverability with lowest risk of incurring carrier blocks.

  1. Use as few numbers for your campaign as possible. While there are some use-cases which require the use of multiple numbers (e.g. your company has different departments and you want a different TFN for each), limit the use of one number per clear use-case (e.g. one number per department rather than two). This helps to allay carrier concerns of snowshoeing.
  2. Keep branding, URL domains and messaging consistent. Multiple names, differing or changing URLs and mis-matched content cause confusion and concern.
  3. Keep phrasing conversational. Messages that sound like the transcribed words of a carnival barker will always appear spammy, even if they are legitimate.
  4. Obtain consent directly. Consent should be obtained directly from the end-user to receive the text messages you intend to send.
  5. Maintain expected frequency. If your advertising told end-users they would receive messages once a month, hold to that. If your advertising doesn’t indicate frequency at all, it might be time to add it.
  6. Keep messages short - messages exceeding the supported character length will be sent in multiple installments and may cause the end-user to feel like they’re being spammed.
  7. Offer STOP/HELP instructions in-message.
  8. In the event you change your sender number for a recurring message program, message subscribed end-users from the old number informing them of the number they can expect to see in the future, then send no further messages from the old number.
  9. Ensure all published campaign details are kept accurate and up-to-date.

Canadian A2P Responsibilities

In order to be permitted to send A2P messaging in Canada, content providers must ensure their messaging programs:

  • maintain an opt-out rate below 1%
  • include “STOP” language in the first message and in every fifth message or one message monthly. Including “STOP” language in every message is recommended.
  • use secured URLs only. Full URL domains recommended.
  • do not jump from number to number upon being blocked
  • identify their brand in every message
  • send no more than ten (10) messages per month
  • make clear the number of messages a subscriber may receive at point of opt-in
  • support INFO, HELP and STOP as well as all French translations with a response in the keyword’s corresponding language
  • include “data rates may apply” or “std msg & data rates may apply” verbiage in messages containing links to mobile-accessible websites.

Remember that all programs are subject to audits by Aerialink and/or by carrier hubs and wireless providers. Failure to comply with a requested consent audit may result in suspension or cancellation of a messaging program.

Prohibited Provider Behavior

The following traits are considered by the carriers to be suspicious and indicative of spam or fraudulent traffic. As such, campaigns found to be doing the following are not complying with best practices guidelines:

  1. Snowshoeing - utilizing a large block of numbers to spread high-velocity traffic among them to avoid carrier spam filters.
  2. Ignoring or Avoiding Opt-Outs - any attempts to make it difficult for an end-user to opt out run the risk of noncompliance with the FCC TCPA, as are instances of ignoring opt-out attempts made in a reasonable manner.
  3. URL Cycling, Redirects and Forwarding - campaigns utilizing strange or misleading URL behavior to manipulate end-user consent, attention or capture information.
  4. Unpublished Contact Numbers - unless the owner of the number is unambiguously identified in the text message.
  5. Number Cycling - dropping blocks of numbers which have been burned by the carriers and replacing with fresh numbers to simply repeat the process.
  6. Running or Enabling Prohibited Use Cases - resellers are responsible for vetting and preventing prohibited use cases on their account.
  7. Sharing, Selling or Renting Consent or any other collected information to or with third parties.
  8. Grey Routes for A2P - “Grey Routes” not authorized to send non-consumer (business, A2P) messages cannot be used for those purposes.
  9. Intentional Filter Evasion - providing mechanisms intended to assist messages in evading anti-SPAM controls regardless of use-case is not permitted.
  10. Dynamic Routing - sender codes and numbers should have a single route by which they deliver messages to destination end-users. These routes should not change dynamically to avoid SPAM controls.
  11. Shared Codes - a code of any type should be dedicated to one content provider only.
  12. Cannabis/CBD Content - any messages promoting cannabis or CBD are prohibited in the United States. This includes messages relating to the marketing or sale of cannabis or CBD products, regardless of whether those messages explicitly contain cannabis terminology, images or links to cannabis-related websites. Sending content of this nature is prohibited by the carriers and violates our AUP.

Per the FCC TCPA, express consent must be obtained prior to sending messages. The form which that consent must take varies depending on the nature of the campaign and its content. Reference the table below for a better understanding of consent needed to meet carrier expectations.

The following information references the CTIA Messaging Principles and Best Practices.

Defined AsBack-and-forth conversation via text.Ongoing informative business messages requested by consumer.Sales or marketing promotional messages, including promotional materials (e.g. coupon codes) included within otherwise informational texts.
ExampleA consumer initiates a text to a business and the business returns a direct response and no further prompting - e.g., a text requesting a business’s hours of operation.Appointment reminders, customer welcome texts, alerts. The first text sent by the business fulfills the consumer’s request.Any number of use-cases recommending and/or incentivizing end-user recipients to patronize or otherwise give attention to products, businesses, organizations, services.
First MessageSent by consumer.Sent by consumer or business.Sent by business.
CorrespondenceTwo-way conversationOne-way alert or two-way conversationOne-way message
Consent Required


No verbal or written permission required.


Prior to messaging, consumer consent required via text; verbally; or clear and conspicuous form, website or written documentation


Prior to messaging, consumer consent required via form or website including explicit checkbox explaining they will receive promotional text messages. Consent must never be a condition of service or purchase.

* IMPLIED CONSENT occurs when a consumer initiates an inquiry to a business via text chat and the business replies to the consumer’s inquiry with only information that is relevant to that initial inquiry. Exchanges of this nature constitute “implied consent” and do not require verbal or written permission. Please note that the implied consent applies only for that relevant exchange - any additional messaging would require express or express written consent.
** EXPRESS WRITTEN CONSENT standards can be met by literal handwritten documentation or by electronic or digital forms of signature from a website, inbound text message, or email.

Remember - consent must not only be obtained, but must be informed when obtained, in order for it to be considered “express” consent. That means that the end-user is aware, at the time they opt in, that they are agreeing to receive text messages. Some examples of reasonable consent mechanisms, when accompanied by appropriate consumer disclosures, include the following:

  • Entering a telephone number through a website (which discloses they will receive texts by providing their number)
  • Clicking a button on a mobile webpage (which discloses they will receive texts by clicking the button)
  • Sending a consumer-initiated text message containing a keyword (after being instructed to do so by a clear and conspicuous CTA)
  • Signing up at a point-of-sale or other message sender on-site location (wherein the end-user is informed directly they will receive texts upon sign-up)
  • Opting in over the phone using IVR (which discloses that by opting in, they are agreeing to receive texts)

Note that the disclosures must not only be present, but must be clear and conspicuous, and should contain the following:

  1. Program/Product Description
  2. Identity of organization/individual being represented
  3. The scope of opt-in and opt-out mechanisms and any applicable privacy policy

Informational & Promotional CTA & Opt-In

The CTA is the point at which the consumer is made aware of the campaign and provided a method or directions for how to opt in or otherwise consent to receive messages. CTAs must always be clear and conspicuous and never misleading so that customers fully understand what they are consenting to when they opt in. In some cases, the CTA and the point of opt-in or consent may be one in the same, such as a description beside a checkbox explaining that checking the box will opt the consumer into receiving text messages. In order to ensure your CTA and opt-in are clear and conspicuous, not misleading and are adhering to legal and industry requirements of proper consent, we recommend following these guidelines:

  1. Always the purpose of the text messages the end-user will receive and the nature of the content they can expect.
  2. Provide the source number (long code, toll-free number, short code) from which the end-user can expect to receive messages.
  3. Ensure the organization or individual behind the messages is clear in the CTA, opt-in and initial message.
  4. Explain any and all associated fees and charges explicitly (“message and data rates may apply”)
  5. Provide access to opt-out instructions, company or mobile terms & conditions and company privacy policy.
  6. Keep the CTA and opt-in separate from the Terms & Conditions.
  7. If you are unsure whether your use-case is Informational or Promotional, follow guidelines for Promotional messages.
  8. Perform a double opt-in in cases where consent was initially collected outside of SMS channels.
  9. Update opt-in instructions in any/all CTAs whenever necessary to ensure they always work correctly.

Opt-Out Requirements

It is required for all text messaging programs to provide a way for consumers to revoke their consent to receive messages, or “opt out” of messaging programs. To ensure this is observed, all messaging programs must:

  • Clearly and conspicuously display opt-out instructions at point of opt-in as well as in the CTA or Terms and Conditions and regular intervals of content service messages (min. once monthly) for recurring message programs.
  • Provide an SMS-based opt-out method. It is recommended to offer other methods as well, including phone or email in addition to text.
  • Ensure any/all published opt-out instructions are kept up-to-date and work as-described.
  • Recognize universal keywords STOP, END, QUIT, CANCEL, UNSUBSCRIBE as valid method of opt-out in addition to any/all otherwise published/displayed opt-out methods. Customer use of these keywords or other displayed opt-out methods must trigger an opt-out event.
  • Respond to an opt-out event with a confirmation that an end-user has opted out, regardless whether they were subscribed at the time they sent the message.
  • Recognize the aforementioned universal keywords regardless of any other accompanying combination or permutation of text content, punctuation, capitalization without inference and trigger the opt-out event for that end-user.
  • Remove end-users from any subscriber lists to prevent the end-user receiving any additional messages after opt-out except for the opt-out confirmation message triggered by the opt-out event.
  • Allow end-users to opt out at any time without penalty beyond the loss of benefit provided by the canceled subscription itself.
  • Understand that carriers, hubs and Aerialink reserve the right to impose opt-outs at a network level for any reason. (Note that this exists already on the carrier-level for toll-free numbers.)
  • Monitor and process published carrier deactivation/deactivated number lists daily.

Network-Side Toll-Free Keywords

For toll-free numbers, end-users who send “STOP” will be opted out on the carrier side. This means that they will receive a carrier response to “STOP.” Additionally, they have the option of opting back in using one of two carrier keywords - “UNSTOP” or “START” - both of which lift the carrier-side block the “STOP” had placed.

Prohibited Use Cases

Within the mobile messaging space, some marketing campaigns or segments are considered problematic by the carriers due to a high volume of subscriber complaints and propensity to be associated with deceptive practices - in other words, “high risk” and therefore prohibited use cases.

As stated by the CTIA, “Message Senders should use reasonable efforts to prevent and combat unwanted or unlawful messaging traffic, including spam and unlawful spoofing. Specifically, Message Senders should take affirmative steps and employ tools that can monitor and prevent Unwanted Messages and content, including for example content that: (1) is unlawful, harmful, abusive, malicious, misleading, harassing, excessively violent, obscene/illicit, or defamatory; (2) deceives or intends to deceive (e.g., phishing messages intended to access private or confidential information); (3) invades privacy; (4) causes safety concerns; (5) incites harm, discrimination, or violence; (6) is intended to intimidate; (7) includes malware; (8) threatens Consumers; or (9) does not meet age-gating requirements. Message Senders should take steps to ensure that marketing content is not misleading and complies with the Federal Trade Commission’s (FTC) Truth-In-Advertising rules.”

The landscape of SPAM has changed and carriers are taking a zero-tolerance approach to traffic that exposes subscribers to shady companies who use texts to tempt end-users into taking certain opt-ins. From “wipe out debt” to job scams asking consumers to share personal information or hand over money, many of these SPAM texts are sent by fee-charging businesses that make unrealistic promises to help with consumers’ money worries and prey on people in debt.

The following use-cases have been deemed high-risk and will be blocked by carriers even when the program claims to support opt-in and opt-out mechanisms. That’s right - even if there is an opt-in and an opt-out, the use-case could still be problematic. In the case of affiliate marketing, for instance, the consumer can text “STOP,” but what exactly are they stopping? More often than not, they are opting out of a single number, but their own number has been shared to the subscriber lists of hundreds or thousands of numbers across multiple content providers. This is the primary reason why affiliate marketing is high-risk and blocked by carriers.

Ultimately, carriers reserve the right to reject programs at their discretion on all messaging routes including short codes, toll-free numbers and standard (local) numbers. Please note that as new SPAM campaigns are identified every day, the below list may change or evolve at any time.

  • Lead/Commission Generation, Affiliate Marketing
  • Marketing of Third-Party Loan Forgiveness, Loan Matching, Loan/Debt Consolidation, Debt/Student Debt Relief
  • High-Risk Financial Services*
  • Finance/Investment Opportunities
  • Tax Relief
  • Credit Report Scoring, Credit Repair/Related Content
  • Work From Home, “Get Rich Quick,” Third-Party Job Recruitment, “Secret Shopper”
  • Phishing, Fraudulent/Deceptive/Misdirecting Links
  • CBD/Marijuana Dispensary Promotions, Tobacco, Vape, Federally Illegal Drugs
  • Promotions of Any Illegal Substances or Prescriptions
  • Gambling
  • Sweepstakes**
  • Any content containing malware or non-secure app downloads
  • Any content in violation of CTIA policies or guidelines such as SHAFT.***

* Some examples of these problematic “High-Risk Financial Services” campaigns include but are not limited to payday loans, short-term loans, auto loans, mortgage loans, student loans, stock alerts, cryptocurrency.
** Prohibited on toll-free. Sweepstakes may be acceptable on 10DLC long code routes dependent on carrier codes of conduct.
*** Note that while SHAFT is technically a policy which applies to short codes, any content on any sender ID type found to be in violation of SHAFT may be subject to blocking by the carrier or by Aerialink.

Cannabis or CBD Message Content

Although the sale of cannabis has been legalized in some states, it is illegal on the federal level. Because of this, SMS and MMS messages related in any way to promoting the sale or use of cannabis or CBD products are not allowed in the United States. Aerialink’s Acceptable Use Policy is reflective of U.S. carrier rules in this area.

This includes any cannabis-related message that relates to the marketing or sale of a cannabis or CBD product regardless of whether those messages explicitly contain cannabis terms, images or links to cannabis websites.

Political Messaging

Political campaigns are supported but must adhere to all applicable CTIA guidelines, including the Messaging Principles and Best Practices and Political Campaign Messaging Document as well as all carrier codes of conduct and the Aerialink Acceptable Use Policy. All prohibited behavior outlined in these articles must be avoided and compliance responsibilities must be obeyed. Importantly, the scope of the anti-spam protections in the Messaging Principles – and the expectations placed on message senders – are separate from and broader than message senders’ minimum legal obligations. Regardless of whether the TCPA and associated FCC consent requirements apply, message senders must obtain a consumer’s consent to receive messages.

Depending on the carrier, political campaigns may be required to register and undergo vetting for authenticity. Please see carrier code of conduct documents for explicit instructions for carrier vetting.

Additionally, keep in mind that political campaigns must always:

  • obtain express consent prior to sending a message. Opt-in lists are not permitted to be shared, bought or sold for any message types. Political use cases are not excepted.
  • inform recipients at opt-in who will be messaging them, the purpose for the messages and the expected frequency and quantity of the messages under clear and conspicuous terms.
  • store all consent records in case of audit or inquiry
  • honor all opt-out requests

Please review the following additional articles as they are applicable to all political messaging:

Other Use Case Guidelines

Adult Content Use Cases

Adult content is highly regulated and may likely be subject to additional reviews or audits in excess of other use cases.
All adult content programs must include as part of any and all opt-in methods a substantial, robust age gate effective in verifying the age of a subscriber at point of opt-in and preventing minors from subscribing. Additionally, the following content remains prohibited for adult content messaging:

  • illegal sexual themes of any kind, simulated or real, including the exchange of illegal sexual imagery
  • prostitution/exchange of intimate acts for money
  • misrepresentation of adult content as family-friendly
  • adult substances, actual or implied, targeting minors

Shopping Cart Reminder Notifications

Cart Reminders are sent as strategic marketing follow-ups to users who have added items to online shopping carts but did not complete their transaction. This is high-risk traffic because end-users often do not directly opt in to receive text messages and these messages carry high potential for negative interaction with recipients.

Simply put - you must establish clear consent from recipients at the time information is collected. Consumers must consent to the type of message and from whom they are receiving it. Carriers field a lot of subscriber complaints from marketing messages because e-comm businesses fail to get explicit consent from consumers. The Call-to-Action for opt-in should describe the types of messages recipients can expect to receive and should include clear opt-out instructions.

Cart Reminders must comply with guidelines from the CTIA and T-Mobile regarding this use case:

  1. The CTA opt-in verbiage must explicitly state that the message program includes cart reminders.
  2. Double opt-in via text is required, and must explicitly state that the program includes cart reminders.
  3. Certification submissions must be filed as an “Account Information” campaign with a description explicitly stating that the program includes cart reminders.
  4. The Privacy Policy must explicitly state how information is captured by the e-commerce site to determine when a cart has been abandoned (e.g. cookies, plugins, etc.)
  5. Terms & Conditions must link to the privacy policy.
  6. Cart reminders must be sent within forty-eight (48) hours and limited to one alert per unique abandoned cart.
  7. Cart reminders must not result in the e-commerce site completing the transaction on behalf of the customer.
  8. Cart reminders must not collect payment information or accept approval for purchase via keyword confirmation.
  9. Consumers must complete the transaction by processing payment themselves via a direct URL link to the e-commerce website.

Charitable Donation Use Cases

Programs facilitating end-users’ donations to charitable causes and organizations are supported on some carrier networks. Mechanisms for supporting this may vary by carrier. Consult individual carrier codes of conduct for details about how donations are supported and requirements for donation campaigns.

Direct Lender Use Cases

Marketing of loan use cases is strictly prohibited. However, customer support, status, acct notifications are permitted.

Emergency Notifications Use Cases

While emergency notifications are supported on all number types, it is recommended that the campaign undergo certification as-applicable per number type.

High-Risk Use Cases

High-risk use cases (typically marketing) may not be outright prohibited, but run a high chance of getting blocked or resulting in carrier complaint. It is critical to set expectations that the following use cases are unlikely to run smoothly on carrier networks.

  • Mailbox Rental
  • Cart Reminders (read more above)
  • Weight Loss

Higher Education & K-12 Use Cases

These messages are intended for teacher-parent-student communications and may not be used for marketing.

Machine to Machine Use Cases

IoT/M2M messages are not expected to engage in direct customer interaction and use cases intending to incorporate both direct consumer communication and IoT/M2M messages must utilize separate dedicated codes for each.

Sweepstakes & Contest Use Cases

Programs which offer a chance to receive a prize must adhere to all applicable laws and should consult legal counsel prior to submitting sweepstakes or contest campaigns for 10DLC, Verified Sender or short code certification.

Red Flags

Some of the characteristics listed below may be innocuous when viewed as isolated incidents, and could occur regardless whether a campaign is absolutely compliant. However, if a messaging program is exhibiting certain characteristics consistently and/or repeatedly, this may indicate noncompliance and is effectively a red flag to the carriers. Aerialink customers should look out for these red flags as well to proactively monitor customer traffic and use-cases in advance of carrier complaint.

  • Upset inbound consumer messages such as expletives, legal threats, confusion about message source or content.
  • Opt-out requests of unusual volume, submitted correctly or incorrectly, such as colloquial inbound requests (e.g. “leave me alone,” “I told you not to contact me,”)
  • Complaints of message blocking. Good traffic absolutely gets blocked incorrectly, but customers whose traffic constantly gets blocked may not be exercising full compliance.
  • Consistent use of high-risk marketing rather than other campaign types may indicate the provider caters to spammers.
  • Regular requests to turn over number inventory due to numbers being “burnt” by carrier blocks.

Deactivated Numbers Compliance

These guidelines are relevant for SMS and MMS compliance in the United States of America.

Deactivated numbers have been removed from service by mobile operators on the end-users’ behalf, typically because the end-user has switched operator or otherwise closed their account. Deactivated numbers are eventually recycled and activated for new subscribers. Because of this, it is easy to mistakenly send an unwanted text message to a previously deactivated number which has been reassigned to an end user who has not opted in to receive the text. Such unwanted texts are considered spam by the FCC and may incur fines of up to $1,500 per outbound message per end user, and could leave the message sender subject to class action litigation.

Note that mobile operators do not keep numbers inactive for a standardized period of time - some may reassign a deactivated number in as little as two days, while others may wait fifty (50) days before reassigning a number. To assist senders in maintaining subscriber lists which are aligned with industry best practices, carrier rules and legal requirements, some U.S. mobile operators provide deactivation files to Aerialink, which are accessible to Aerialink customers to cross-check and clean up subscriber records.

Retrieve Deactivation Files

Aerialink customers can access number deactivation files programmatically through an Aerialink endpoint. Request access to the files through a support request to the Aerialink Help Desk, and please refer our Number Deactivations API Documentation.

About Deactivation Files

Retrieving and processing the deactivation files as daily is important. The files are updated daily and the content of each file is incremental, containing only phone numbers for which the deactivation status has changed from the previous report. Because mobile operators can reassign inactive phone numbers in as little as two days’ time, it is crucial to process the deactivation files every day, and ensure that no further messages are sent to deactivated numbers until such a time as the number’s new subscriber chooses to opt in (at a date later than the date of deactivation). NOTE: use the preceding date value to retrieve the most recent file as the files are always one day behind of the current date.

We recommend that message senders contact the previous owner of a deactivated number to request their opt-in with their new number if possible.

File Property Details

Scope1 file daily from participating carriers*
Contentdeactivated numbers, changed numbers, suspended numbers (temporary state), reactivated number (un-suspended)
File Namemcdn_deact_{YYYYMMDD}.csv (e.g. mcdn_deact_20230610.csv)

* Participating carriers include Verizon Wireless, US Cellular Corp, T-Mobile and AT&T (displayed as “Cingular”).

File Content Details

MDNThe unique Mobile Directory Number for which action is being taken, in E.164 format (i.e. “12223334444”).
REASON_CODEDEACTIVATE - a disconnect event, or indication that the subscriber has elected not to receive messages
SUSPEND (Verizon) - outbound messages to this MDN should be halted until reactivation.
REACTIVATE (Verizon) - halted messages to a previously suspended MDN may resume.
CHANGE_MDN - an old, deactivated MDN has been replaced with a new MDN.
MODIFICATION_DATEA timestamp for the action in ISO 8601 format (the time zone will be zeroed out) (i.e. 2023-06-10T00:00Z).
NEW_MDNA subscriber’s new MDN in E.164 format (i.e. 12223334444). This field will have a value of “1” if the REASON_CODE is not “CHANGE_MDN.”
CARRIER_NAMEThe carrier who initiated the action.


Aerialink Compliance articles are for informational use only. They do not constitute, and should not be taken as or in place of, legal advice. Aerialink customers are responsible for meeting all legal requirements applicable to their programs and are strongly encouraged to consult formal legal counsel.