Help with registration rejections in AWS End User Messaging SMS - AWS End User Messaging SMS

Help with registration rejections in AWS End User Messaging SMS

If your registration was rejected, use the following table to determine why it was rejected and what you can do to fix your registration. After you determine why the registration was rejected, you can modify the existing registration to address that issue and resubmit. For more information, see Edit a registration in AWS End User Messaging SMS.

If your brand registration was rejected, use the following table to determine why it was rejected and what you can do to fix it. You can modify the existing registration to address the issue and resubmit. For more information on editing a registration, see Edit a registration.

Brand rejection reasons
AWS End User Messaging SMS rejection short description AWS End User Messaging SMS rejection long description
Brand physical address is missing or invalid. The brand's physical address can't be verified. Check the physical address is correct and resubmit the form.
Brand support email address is missing or invalid. The brand's email address is missing or invalid. Update the email address and resubmit the form.
Brand support email is a public email domain. The brand's email domain is from a public email provider, like Gmail. The email domain must be associated with the brand's business.
Repeated use of same Employer Identification Number (EIN) for multiple different brands. Same EIN is used for multiple brands. Only register minimum number of brands per EIN and do not resubmit until brand registration is updated
Brand associated with or website references lead generation or affiliate marketing which is prohibited by mobile operators. Brand associated with or website indicates that message content contains the following which is considered restricted or disallowed by mobile operators: Lead generation or affiliate marketing.
Brand associated with or website references gambling which is prohibited by mobile operators. Brand associated with or website indicates that message content contains the following which is considered restricted or disallowed by mobile operators: Gambling.
Brand associated with or website references high risk financial services which are prohibited by mobile operators. Brand associated with or website indicates that message content contains the following which is considered restricted or disallowed by mobile operators: High risk financial services.
Brand associated with or website references illegal substances which is prohibited by mobile operators. Brand associated with or website indicates that message content contains the following which is considered restricted or disallowed by mobile operators: Illegal substances.
Brand associated with or website references third party job boards which is prohibited by mobile operators. Brand associated with or website indicates that message content contains the following which is considered restricted or disallowed by mobile operators: Third party job boards.
Brand associated with or website references SHAFT content which is prohibited by mobile operators. Brand associated with or website indicates that message content contains the following which is considered restricted or disallowed by mobile operators: SHAFT (sex, hate, alcohol, firearms, tobacco/vape).
Brand associated with or website references SHAFT content which is prohibited by mobile operators. Brand associated with or website indicates that message content contains the following which is considered restricted or disallowed by mobile operators: SHAFT (sex, hate, alcohol, firearms, tobacco/vape).
Brand associated with or website references sweepstakes which is prohibited by mobile operators. Brand associated with or website indicates that message content contains the following which is considered restricted or disallowed by mobile operators: Sweepstakes.
Brand support phone number is missing or invalid. The brand's support phone number is missing or invalid. Update the phone number and resubmit the form.

If your campaign or use case was rejected, use the following table to determine why it was rejected and what you can do to fix it. You can modify the existing registration to address the issue and resubmit. For more information on editing a registration, see Edit a registration.

Campaign rejection reasons
AWS End User Messaging SMS rejection short description AWS End User Messaging SMS rejection long description
Campaign appears to be associated with a known Spam or Phishing brand and is not allowed. The provided phone number, business, traffic, or marketing for the campaign has been flagged as Spam or Phishing; or the Privacy policy or Terms associated with the campaign may indicate that SMS opt-in consent or phone numbers are being shared with third parties or affiliates.
Brand website is missing, inaccessible, or online presence could not be validated. The provided URL is incorrect. If the website is not live yet then indicate that in the campaign description. Check the URL is correct and resubmit.
Brand references charity content that does not match the campaign use case. Brand associated with or website references content that is not indicated in the registered use case of the campaign. Mismatched use case: Charity.
Brand references political content that does not match the campaign use case. Brand associated with or website references content that is not indicated in the registered use case of the campaign. Mismatched use case: Political.
Vetted brand does not meet minimum vetting score requirements. The brand's vetting score may be a value that it insufficient for campaign approval.
Campaign description does not match sample messages or use case. The campaign description doesn't match the messaging use case, message samples, or both. Update the campaign description, messaging use case, and message samples to match, then resubmit.
Campaign description does not match sample messages, or use case: Charity. The use case described in the campaign description indicates that the brand is soliciting charitable donations, but the use case is not set to "Charity" or the sample message content doesn't match the use case. Update the campaign description, use case, and message samples to match, then resubmit. "
Campaign description does not match sample messages or use case: Political. "The use case described in the campaign description indicates that the brand is soliciting donations, but the use case is not set to "Political" or the sample message content doesn't match the use case. Update the campaign description, use case, and message samples to match, then resubmit."
Same or similar use case repeated across multiple campaigns. The campaign appears to have content that has been duplicated and indicates the disallowed practice of snowshoeing. Make sure that only one campaign is registered for your use case.
Use case is considered restricted or disallowed by mobile operators: Affiliate marketing. Campaign use case indicates that message content contains one or more of the following which is considered restricted or disallowed by mobile operators: Lead generation or affiliate marketing.
Use case is considered restricted or disallowed by mobile operators: Gambling. Campaign use case indicates that message content contains one or more of the following which is considered restricted or disallowed by mobile operators: Gambling
Use case is considered restricted or disallowed by mobile operators: High-risk financial services. Campaign use case indicates that message content contains one or more of the following which is considered restricted or disallowed by mobile operators: High risk financial services such as short-term loans or cryptocurrency.
Use case is considered restricted or disallowed by mobile operators: Illegal substances. Campaign use case indicates that message content contains one or more of the following which is considered restricted or disallowed by mobile operators: Federally illegal substances, such as cannabis.
Use case is considered restricted or disallowed by mobile operators: Third party job boards. Campaign use case indicates that message content contains one or more of the following which is considered restricted or disallowed by mobile operators: Third party job boards.
Use case or message samples appear to be for testing or non-subscriber facing. 10DLC is only allowed for production use cases. Campaign use case description indicates that Machine-to-Machine content is being shared, which is restricted to non-subscriber facing message programs. Register the campaign again with the correct use case and resubmit.
Use case is considered restricted or disallowed by mobile operators; prohibited content: SHAFT. Campaign use case indicates that message content contains one or more of the following which is considered restricted or disallowed by mobile operators: SHAFT (sex, hate, alcohol, firearms, tobacco/vape).
Use case is considered restricted or disallowed by mobile operators; prohibited content: SHAFT without an age gate. Campaign use case indicates that message content contains one or more of the following which is considered restricted or disallowed by mobile operators without an age gate mechanism: SHAFT (sex, hate, alcohol, firearms, tobacco/vape).
Use case is considered restricted or disallowed by mobile operators: Sweepstakes. Campaign use case indicates that message content contains one or more of the following which is considered restricted or disallowed by mobile operators: Sweepstakes or sweepstakes related messaging.
Brand referenced in campaign description does not match registered brand name or Doing Business As (DBA) name. The company name in the campaign description should match or be close to the registered brand name or DBA name to be clear who the sender is. Update the campaign description and resubmit.
Campaign description does not sufficiently describe the service the message program is providing to the end user. It must be clear from your campaign description what the purpose of your message program is. Add more details to the description and resubmit.
Campaign appears to be Direct Lending Arrangement but appropriate Content Attribute was not selected. From the campaign description it appears that the purpose of your campaign is direct lending but Direct lending or loan arrangement has not been selected. Either update your campaign description or choose Direct lending or loan arrangement and resubmit.

If your HELP message was rejected, use the following table to determine why it was rejected and what you can do to fix it. You can modify the existing registration to address the issue and resubmit. For more information on editing a registration, see Edit a registration.

Help message rejection reasons
AWS End User Messaging SMS rejection short description AWS End User Messaging SMS rejection long description
HELP message or support contact email address provided in HELP message does not contain or match registered or DBA brand name. The company name and email domain in the HELP message samples must match or be close to the registered brand name or DBA name, to be clear who the sender is. Update the company name and support email domain in the HELP message samples and resubmit.
HELP message does not contain support contact of email, phone number, or support website The HELP message must include customer contact care info to inform the end user how they can receive further support including: email address, phone number, link to a support website. Update the HELP messages to include these and resubmit.

If your opt-in message was rejected, use the following table to determine why it was rejected and what you can do to fix it. For overall guidance on how to create a compliant opt-in, see How to Build a Compliant SMS Opt-In Process. You can modify the existing registration to address the issue and resubmit. For more information on editing a registration, see Edit a registration.

Opt-in message rejection reasons
AWS End User Messaging SMS rejection short description AWS End User Messaging SMS rejection long description
Opt-in message does not contain registered brand name or Doing Business As (DBA) name The company name in the opt-in message samples must match or be close to the registered brand name or DBA name, to be clear who the sender is. Update the company name in the Opt-in message samples and resubmit.
Opt-in message not provided Recurring message programs must send the end user an opt-in message with HELP and STOP instructions, message frequency, and "Message and data rates may apply" disclosure. Update the opt-in message and resubmit.
Opt-in message does not include one or more of the following: Message frequency disclosure for recurring message program or "message and data rates may apply" disclosure. Opt-in message must include the frequency of messages such as the number of messages a month, message frequency varies, if the message are reoccurring and the "Message and data rate disclosure". Update the opt-in message and resubmit.
Opt-in message does not contain HELP or STOP instructions. Opt-in message must include instructions on how opt-out of the message program, for example "Reply STOP to cancel". Update the opt-in message and resubmit.

If your opt-in workflow was rejected, use the following table to determine why it was rejected and what you can do to fix it. For overall guidance on how to create a compliant opt-in, see How to Build a Compliant SMS Opt-In Process. You can modify the existing registration to address the issue and resubmit. For more information on editing a registration, see Edit a registration.

Opt-in workflow rejection reasons
AWS End User Messaging SMS rejection short description AWS End User Messaging SMS rejection long description
Opt-in workflow does not obtain sufficient consent Opt-in message must show that the appropriate type of consent is gained for the message program. The call-to-action must show that express written consent was obtained from the end user before sending promotional message content. For more information, see Obtain permission. Update your opt-in workflow and resubmit.
Opt-in workflow does not match the registered brand name or Doing Business As (DBA) name. The company name in the Opt-in message samples must contain the registered brand name or DBA name. Add the company name in the Opt-in message samples and resubmit.
Opt-in workflow URL or image is missing or inaccessible and could not be verified. No opt-in workflow URL or image was provided in the opt-in workflow or campaign description, or the URL provided is inaccessible. Provide a compliant opt-in process through either a live opt-in URL, or a URL to a hosted opt-in image (screen shot or mock-up) and all possible methods end-users consent to messaging then resubmit.
Opt-in workflow indicates that use case is considered restricted or disallowed by mobile operators: Gambling. Opt-in workflow indicates that message content is related to gambling, which is not permitted by mobile operators.
Opt-in workflow indicates that use case is considered restricted or disallowed by mobile operators: High risk financial services. Opt-in workflow indicates that message content is related to high risk financial services such as short-term loans or cryptocurrency, which is not permitted by mobile operators.
Opt-in workflow indicates that use case is considered restricted or disallowed by mobile operators: Illegal substances. Opt-in workflow indicates that message content is related to federally illegal substances, such as cannabis, which is not permitted mobile operators.
Opt-in workflow indicates that use case is considered restricted or disallowed by mobile operators: SHAFT (sex, hate, alcohol, firearms, tobacco/vape). Opt-in workflow indicates that message content contains sexual explicit or hateful content which is considered restricted or disallowed by mobile operators: SHAFT (sex, hate, alcohol, firearms, tobacco/vape).
Opt-in workflow not compliant or is missing the required "message and data rates may apply" disclosure. Opt-in workflow is not compliant or opt-in does not include the following: "Message and data rates may apply" disclosure. The opt-in workflow must inform the end user of the message and data rate disclosure, as mandated by U.S. carriers.
Opt-in workflow does not contain HELP or STOP instructions. Opt-in workflow must include instructions on how the end user can receive further support from the brand regarding the message program such as "Reply HELP for help", "Reply STOP to cancel", or HELP instructions in Terms & Conditions.
Opt-in workflow not compliant or is missing required message frequency disclosure. Opt-in workflow is not compliant or does not include the following: Message frequency disclosure. The opt-in workflow must indicate the frequency at which messages will be sent to end users for recurring message program.
Opt-in workflow not compliant or is missing statement that data will not be shared with third parties or link to privacy policy disclosure. Opt-in workflow is not compliant or opt-in does not include the following: link to privacy policy or statement that mobile opt-in data will not be shared with third parties. The opt-in workflow must include a link to the message program privacy policy, or language that indicates mobile opt-in data will not be shared. Update the opt-in workflow and resubmit.
Opt-in workflow not compliant or is missing required terms and conditions language. Opt-in workflow is not compliant and does not include the following: Complete message program terms and conditions language or a link to the complete terms and conditions.

If your opt-out message was rejected, use the following table to determine why it was rejected and what you can do to fix it. For overall guidance on how to create a compliant opt-in, see How to Build a Compliant SMS Opt-In Process. You can modify the existing registration to address the issue and resubmit. For more information on editing a registration, see Edit a registration.

Opt-out message rejection reasons
AWS End User Messaging SMS rejection short description AWS End User Messaging SMS rejection long description
Opt-out message does not contain registered brand name or Doing Business As (DBA) name. The company name in opt-out message should match or be close to the registered brand name or DBA name to be clear who the sender is. Update the opt-out message and resubmit.
Opt-out message does not indicate that no further messages will be sent. The opt-out message must state that no further messages will be sent. Update the opt-out message and resubmit.

If your privacy policy was rejected, use the following table to determine why it was rejected and what you can do to fix it. For overall guidance on how to create a compliant opt-in, see How to Build a Compliant SMS Opt-In Process. You can modify the existing registration to address the issue and resubmit. For more information on editing a registration, see Edit a registration.

Privacy policy rejection reasons
AWS End User Messaging SMS rejection short description AWS End User Messaging SMS rejection long description
Privacy policy link is missing or inaccessible. The privacy policy URL is unavailable to review or the provided URL is inaccessible. Update the URL and resubmit.
Privacy policy references mobile opt-in data sharing with third parties or does not state that no mobile opt-in data will be shared with third parties or affiliate. The privacy policy must indicate that mobile opt-in data will not be shared with third parties. Update the privacy policy and resubmit.
Privacy policy references mobile opt-in data sharing with third parties or does not state that no mobile opt-in data will be shared with third parties or affiliate. The privacy policy must indicate that mobile opt-in data will not be shared with third parties. Update the privacy policy and resubmit.

If your samples messages were rejected, use the following table to determine why it was rejected and what you can do to fix it. For overall guidance on how to create a compliant opt-in, see How to Build a Compliant SMS Opt-In Process. You can modify the existing registration to address the issue and resubmit. For more information on editing a registration, see Edit a registration.

Sample message rejection reasons
AWS End User Messaging SMS rejection short description AWS End User Messaging SMS rejection long description
Sample message(s) do not contain registered brand name or Doing Business As (DBA) name. The company name in the sample messages should match or be close to the registered brand name or DBA name to be clear who the sender is. Update the sample messages and resubmit.
Sample message(s) indicates that message content is related to gambling and is not permitted by US carriers. Sample message(s) indicates that message content is related to gambling and is not permitted by US carriers.
Sample message(s) indicates that message content is related to high risk financial services such as loans or cryptocurrency, and is not permitted by US carriers. Sample message(s) indicates that message content is related to high risk financial services such as loans or cryptocurrency, and is not permitted by US carriers.
Sample message(s) indicates that message content is related to federally illegal substances, such as cannabis, and is not permitted by US carriers. Sample message(s) indicates that message content is related to federally illegal substances, such as cannabis, and is not permitted by US carriers.
Sample message(s) indicates that message content is related to third party job boards and is not permitted by US carriers. Sample message(s) indicates that message content is related to third party job boards and is not permitted by US carriers.
Sample message(s) indicates that message content is related to SHAFT (sex, hate, alcohol, firearms, tobacco/vape) and is not permitted by US carriers. Sample message(s) indicates that message content is related to SHAFT (sex, hate, alcohol, firearms, tobacco/vape) and is not permitted by US carriers.
Sample message(s) indicates that message content is related to sweepstakes and is not permitted by US carriers. Sample message(s) indicates that message content is related to sweepstakes and is not permitted by US carriers.
Use of embedded phone number is selected but not present in message samples. Use of embedded phone number is selected but not present in message samples. Add the embedded phone number to the message samples or unselect embedded phone number then resubmit.
Sample message(s) include restricted content such as generic shortened URLs. Sample messages contain public URL shorteners such as bit.ly or tinyURL are not permitted to be sent in 10DLC message content.
Sample message(s) use case does not match declared use case(s). The use case indicated in the sample messages must match the registered use case. Update the sample messages or register the campaign again with the correct use case and resubmit.
Sample message(s) indicate that message content is soliciting charitable donations, but selected use case is not charity. If the sample messages indicates that you're soliciting charitable donations through your message program, then the campaign use case should be Charity. Update the sample messages or register the campaign again with the correct use case and resubmit.
Sample message(s) indicate that message content is political, but selected use case is not political. If the sample messages indicates that you're sending political messages through your message program, then the campaign use case should be Political. Update the sample messages or register the campaign again with the correct use case and resubmit.

If your Terms and Conditions were rejected, use the following table to determine why it was rejected and what you can do to fix it. For overall guidance on how to create a compliant opt-in, see How to Build a Compliant SMS Opt-In Process. You can modify the existing registration to address the issue and resubmit. For more information on editing a registration, see Edit a registration.

Terms and Conditions rejection reasons
AWS End User Messaging SMS rejection short description AWS End User Messaging SMS rejection long description
Terms and Conditions do not contain registered brand name or Doing Business As (DBA) name. The company name in the Terms and Conditions should match or be close to the registered brand name or DBA name. Update the campaign description and resubmit.
Terms and Conditions link is missing or inaccessible for review. The Terms and Conditions URL provided is missing or inaccessible. Provide a compliant a compliant URL and resubmit.
Terms and Conditions are non compliant. The Terms and Conditions do not contain one or more of the following as mandated by US carriers: a statement that US carriers are not liable for delayed or undelivered messages, message frequency disclosure for recurring message program such as number of message a month, information on how the end user can opt-out of receiving messages from the campaign, customer care contact information, or information on how the end use can receive further support from the brand.
Terms and Conditions do not contain statement regarding carrier liability. The Terms and Conditions does not contain a statement that US carriers are not liable for delayed or undelivered messages.
Terms and Conditions do not contain customer care contact information. The Terms and Conditions do not contain one or more of the following as mandated by US carriers: customer care contact information, or information on how the end use can receive further support from the brand.
Terms and Conditions do not contain required message frequency disclosures. The Terms and Conditions do not contain one or more of the following as mandated by US carriers: message frequency disclosure for recurring message program such as number of messages a month.
Terms and Conditions do not contain opt-out language. The Terms and Conditions does not contain information on how the end user can opt-out of receiving messages from the campaign.
Terms and Conditions do not contain link to privacy policy. The Terms and Conditions must contain a link to the privacy policy. Update the Terms and Conditions and resubmit.
Terms and Conditions do not contain a description of the campaign use case. The Terms and Conditions must include a description of the purpose of the message program. Update the Terms and Conditions and resubmit.
Terms and conditions do not contain a program description or terms related to declared use case. The Terms and Conditions program description is not related to the campaign use case. Update the Terms and Conditions then resubmit.