A2P SMS compliance requirements#

A2P SMS Compliance content requirements explain the message content, consent practices, and sending behavior required for A2P SMS using a Sender ID Verification.

This information helps users prepare compliant Sender ID Verification submissions and understand why a Sender ID Verification may be rejected, suspended, or returned for changes during verification.

Approval depends on the accuracy of the submitted business and messaging information, the Sender ID, the consent flow, the sample content, and the way messages are sent.

Messages must comply with applicable laws, regulations, and messaging industry requirements in the destination country.


Sender ID Verification requirements#

DIDWW Sender ID Verifications must clearly identify the sender, use accurate messaging information, and follow valid consent and opt-out practices.

The submitted description, sample messages, opt-in flow, and actual message traffic must describe the same use case.

Use a recognizable domain#

If an A2P message includes a link, the link should use a recognizable domain associated with the business or service identified in the verification.

Avoid generic, unrelated, suspicious, or frequently changing domains. A consistent business domain helps users recognize the sender and understand where the link will take them.

Use clear and natural language#

Messages should be written in clear, natural language.

Avoid unusual spellings, excessive symbols, misleading formatting, or wording that may make messages look like spam.

Messages should not use intentionally distorted words, random characters, or obfuscated text to bypass filtering or hide the real meaning of the message.

Set message frequency expectations#

Users should be informed about the expected message frequency before or during opt-in, especially for recurring campaigns.

Example:

You may receive up to 5 messages per month.

Identify the business#

Messages should clearly identify the business, brand, or service that is contacting the user.

Users should not have to guess who sent the message or why they received it.

Example:

Example Brand: Your appointment is confirmed for 10:00 AM. Reply STOP to unsubscribe. Reply HELP for further assistance.

Include STOP and HELP instructions#

A2P messages should include clear opt-out and help instructions where applicable.

For recurring messaging campaigns, opt-out instructions should be provided during opt-in and repeated regularly in messages.

Note

If an Alphanumeric Sender ID is used, recipients cannot reply directly to the message. In this case, the message should include an opt-out link or another clear opt-out method.

Examples:

Reply STOP to unsubscribe.

Reply HELP for help.

Keep verification information accurate#

Verification information must accurately reflect the live use case.

The messaging description, sample messages, Sender ID, opt-in method, links, and actual message content must remain consistent.

A Sender ID Verification may require changes or resubmission if the submitted information does not match the real message traffic. Associated traffic may also be restricted.

Note

DIDWW may request updates, clarification, or resubmission if the verification details do not match the actual message content or sending behavior.


Prohibited messaging practices#

The following sending practices are not allowed for A2P traffic registered through DIDWW Sender ID Verifications.

Grey routes#

A2P messages must not be sent through unauthorized or unsupported routes.

A grey route is a sending path, method, or setup that is not authorized for A2P or non-consumer messaging.

Snowshoe sending#

Snowshoe sending is not allowed.

Snowshoe sending means spreading similar or identical message traffic across multiple sender IDs, phone numbers, or routes to dilute reputation metrics, bypass filtering, or avoid spam controls.

Filter evasion#

Messaging campaigns must not use techniques designed to avoid spam controls, filtering systems, or compliance checks.

This includes automatically replacing blocked sender IDs, numbers, domains, or routes with new ones for the purpose of continuing the same non-compliant traffic.

Dynamic routing to avoid filtering#

Message routing must not be changed dynamically for the purpose of bypassing blocking, filtering, or other compliance controls.

Routing changes should not be used to hide the source, avoid detection, or continue traffic that has already been identified as suspicious or non-compliant.

Shared sender IDs or numbers#

Shared sender IDs or numbers must not be used in a way that allows multiple unrelated brands, services, or content providers to send different content from the same sender.

Each Sender ID Verification must clearly identify the business responsible for the messages.

URL cycling and public URL shorteners#

Messaging campaigns must not rotate multiple domains, shortened links, or URLs to evade filtering or dilute reputation tracking.

Public URL shorteners should not be used in A2P messages.

Where links are required, use a recognizable domain that belongs to or clearly represents the business or service identified in the verification.

URL redirects and forwarding#

Messages must not contain links that use multiple redirects or obscure the final destination.

Users should be able to understand where a link will take them.

Links that redirect through several domains or hide the final landing page may prevent approval, cause messages to be filtered, or result in messaging restrictions.

Number cycling#

Number cycling is not allowed.

Number cycling means replacing sender IDs or numbers after deliverability decreases, complaints increase, or filtering begins, while continuing the same or similar campaign traffic.

Number cycling suggests poor consent practices, unwanted messaging, or an attempt to avoid filtering.


Prohibited message content#

A2P messages must not contain unlawful, misleading, harmful, abusive, or inappropriate content.

The following content is not allowed:

  • Spam or unsolicited messages.

  • Fraudulent, deceptive, or misleading messages.

  • Phishing messages.

  • Scam messages.

  • Content that promotes, depicts, or endorses violence.

  • Inappropriate content.

  • Profanity, hate speech, harassment, abusive language, or discriminatory content.

  • Illegal drugs, illegal substances, or illegal prescriptions.

  • Any content that is illegal in the destination country or otherwise violates applicable laws, regulations, or messaging requirements.

Note

Sender ID Verifications may be returned for changes or closed if their traffic includes or promotes prohibited content. Associated traffic may also be blocked.

DIDWW may also restrict new verification submissions, request corrective action, or limit provisioning if prohibited content is detected.

Important

A2P message content must be appropriate for the intended audience and must comply with applicable laws and messaging requirements in the destination country.


Disallowed messaging categories#

The following A2P messaging categories are not supported:

Category

Disallowed content

High-risk financial services

Payday loans, non-direct lending, and debt collection.

Debt forgiveness

Debt consolidation, debt reduction, and credit repair programs.

Illegal substances

Cannabis, illegal prescriptions, and other illegal substances.

Work and investment opportunities

Work-from-home programs, job alerts from third-party recruiting firms, and high-risk investment opportunities.

Gambling

Gambling-related campaigns, betting-related campaigns, or other gambling content.

Lead generation

Campaigns where collected user information is shared, sold, rented, or transferred to third parties.

Other illegal or non-compliant content

Any campaign type that is prohibited by applicable law, regulation, or messaging industry requirements.

Note

Verifications for these categories may not be approved even if similar content was previously approved or accepted by another provider.


Phishing#

Phishing is not allowed.

Phishing means sending messages that appear to come from a reputable company, service, or organization in order to trick users into revealing personal information.

Examples of sensitive information include:

  • Passwords.

  • Account credentials.

  • Payment card details.

  • Banking information.

  • Verification codes.

  • Personal identification details.

A2P messages must not impersonate another company, service, government body, or individual.


Fraud or scam#

Fraudulent or scam messages are not allowed.

This includes messages that use wrongful or criminal deception to obtain financial or personal gain.

Such messages often involve money, payments, account access, prizes, investments, or business transactions.

Examples of prohibited fraud or scam content include:

  • Fake payment requests.

  • Fake account alerts.

  • Fake prize or reward claims.

  • Messages requesting payment under false pretenses.

  • Messages designed to trick users into sharing personal or financial information.


Deceptive marketing#

Marketing messages must be truthful, clear, and not misleading.

A2P messages must not use false claims, deceptive wording, hidden conditions, or misleading calls-to-action.

If a campaign includes promotional content, the user must have provided the required level of consent before receiving those messages.

The following practices are not allowed:

  • Using false or misleading claims in promotional messages.

  • Hiding important terms, fees, conditions, or opt-in details.

  • Using deceptive language in calls-to-action, forms, landing pages, or message content.

  • Promoting products or services with claims that cannot be verified or substantiated.

  • Using a misleading or unclear Sender ID.

  • Making the message purpose unclear.


Compliance audits and notices#

Sender ID Verifications and their associated traffic may be reviewed for compliance with applicable messaging requirements.

Traffic that creates consumer harm, generates complaints, or appears to violate messaging requirements may be restricted, blocked, or require corrective action.

A verification may require review or corrective action if:

  • The traffic appears to be unwanted or harmful.

  • The campaign receives excessive complaints.

  • The message content does not match the registered campaign use case.

  • The campaign uses prohibited sending practices.

  • The campaign falls under a prohibited or disallowed content category.

  • The sender cannot provide valid consent records when required.

  • The campaign continues sending messages to users who opted out.

Depending on the severity of the issue, corrective actions may include traffic blocking, verification closure, a request for root cause analysis, verification updates, or resubmission.

Repeated violations or severe compliance issues may result in long-term or indefinite traffic restrictions or closure of the verification.


Age gating#

Messaging that includes age-restricted content must comply with applicable laws and must use a valid age verification process.

Age-restricted content may include, but is not limited to:

  • Sexually explicit or adult content.

  • Alcohol-related content.

  • Firearms-related content.

  • Tobacco-related content.

  • Other content restricted by age under applicable laws or regulations.

A simple Yes or No confirmation is not considered a sufficient age gate.

Where age verification is required, the opt-in process should include date of birth verification or another appropriate age verification mechanism.

Important

DIDWW may reject, close, or request changes to a Sender ID Verification, or restrict its traffic, if the submitted use case, message content, consent flow, or sending behavior does not meet applicable messaging requirements.


Reasons a verification may require changes#

A Sender ID Verification may require changes or may not be approved if:

  • The campaign content falls under a prohibited or disallowed category.

  • The campaign description does not match the submitted sample messages.

  • The Sender ID is unclear or inconsistent.

  • The opt-in process is missing, unclear, or not specific to the campaign.

  • The opt-out message is missing or incomplete.

  • The campaign uses public URL shorteners, suspicious domains, or redirect chains.

  • The campaign appears to use third-party lead lists or shared consent.

  • The message samples contain misleading, deceptive, or non-compliant content.

  • The campaign information is incomplete, inaccurate, or inconsistent with the intended use case.

  • The campaign uses prohibited sending practices, such as snowshoe sending, number cycling, grey routes, or filter evasion.