If you've been rejected for Toll-Free Compliance, below you will find a list of error codes, the causes, and possible solutions.
30437
Toll-Free verification rejection - Edit time expired
The rejected toll-free verification time window has reached the 7-day expiration. An edit is accepted, but the toll-free number remains unverified, and the submission is no longer prioritized, so the time to process is similar to a new submission. Effective Nov 8, 2023, messaging traffic on this Toll-Free number is blocked until it's verified.
Possible Causes
There were no edits to the verification within 7 days of its rejection.
Possible Solutions
Edit and resubmit the toll-free verification. The resubmission will still be received, but it is handled as a new submission, so the review will take slightly longer.
30440
Toll-Free verification rejection - Unknown Error
The toll-free phone number cannot be verified due to an unknown error. Messaging traffic on this Toll-Free phone number is blocked.
Possible Causes
Unknown
Possible Solutions
Contact customer support to learn more.
30441
Toll-Free phone number verification rejection - Disallowed: SHAFT - Sex
Verification is one component of ensuring A2P SMS is used by businesses in a legal and compliant manner. The review process looks at the business sending messaging (not the software powering it), the use case, sample content, the web presence, the opt-in/consent collected, and associated website terms and privacy policies.
Possible Causes
The toll-free phone number cannot be verified because the submission indicated that the business is associated with or the toll-free verification submission indicated a forbidden messaging category - (SHAFT: Sex).
Call Loop does not allow Hate speech, harassment, exploitative, abusive, or any communications that originate from a hate group.
Possible Solutions
If you are confident that your business and messaging use case does not fit into forbidden message categories, contact Call Loop Support to provide Additional Information that explains your use case.
30442
Toll-Free phone number verification rejection - Disallowed: Spam
Verification is one component of ensuring A2P SMS is used by businesses in a legal and compliant manner. The review process looks at the business sending messaging (not the software powering it), the use case, sample content, the web presence, the opt-in/consent collected, and associated website terms and privacy policies.
Possible Causes
The toll-free phone number cannot be verified because the business or message content was found to be associated with a known spam or fraudulent campaign.
Possible Solutions
If you are confident that your business and messaging use case does not fit into forbidden message categories, contact Call Loop Support to provide Additional Information that explains your use case.
30443
Toll-Free verification rejection - Disallowed: Loan Marketing
Verification is one component of ensuring A2P SMS is used by businesses in a legal and compliant manner. The review process looks at the business sending messaging (not the software powering it), the use case, sample content, the web presence, the opt-in/consent collected, and associated website terms and privacy policies.
Possible Causes
The toll-free phone number cannot be verified because the submission indicated that the business is associated with or the toll-free verification submission indicated a forbidden messaging category (High-risk financial services: New loan soliciting).
New loan soliciting, Payday loans, Short-term high-interest loans, Third-party loans, and Student loans are disallowed content.
"Third-party" means originating from any party other than the one that will service the loan. Examples of third-party loans could include: auto, mortgage, personal, etc. First-party loan content is acceptable if it is not promotional messaging.
Note: Any business with a terms of service or privacy policy that mentions sharing or selling consumer data/opt-in information is considered noncompliant.
Possible Solutions
If you are confident that your business and messaging use case does not fit into forbidden message categories, contact Call Loop Support to provide Additional Information that explains your use case.
30444
Toll-Free verification rejection - Disallowed: Fraud
Verification is one component of ensuring A2P SMS is used by businesses in a legal and compliant manner. The review process looks at the business sending messaging (not the software powering it), the use case, sample content, the web presence, the opt-in/consent collected, and associated website terms and privacy policies.
Possible Causes
The toll-free phone number cannot be verified because the submission indicated that the business is associated with or the toll-free verification submission indicated Fraud.
Possible Solutions
If you are confident that your business and messaging use case does not fit into forbidden message categories, contact Call Loop Support to provide Additional Information that explains your use case.
30445
Toll-Free verification rejection - Could not validate business information
Possible Causes
The Toll-Free phone number cannot be verified because of invalid information. The Business Information, such as business name or address, that was submitted could not be verified, or the website URL could not be validated because it is not accessible or available.
Possible Solutions
Ensure all business information fields are valid and accurately represent the business that manages the opt-in and has a relationship with the consumer:
30446
Toll-Free verification rejection - Opt-in not sufficient: express consent required
Verification is one component of ensuring A2P SMS is used by businesses in a legal and compliant manner. The review process looks at the business sending messaging (not the software powering it), the use case, sample content, the web presence, the opt-in/consent collected, and associated website terms and privacy policies.
Possible Causes
The Opt-in workflow provided in the toll-free verification is not sufficient. Express Consent is required. Express Consent is more than collecting a phone number - it is a voluntary, informed end-user choice for a specific purpose - it requires upfront disclosure and intentional action. Explicit opt-in leaves no ambiguity for why the customer gave the phone number, and for how they expect the company will communicate with them.
Every end business must have consent from each recipient they send a message. Consumers may permit text, on a form, on a website, or verbally. Consumers may also give written permission. Listing “SMS” in your Terms of Service or Privacy Policy is not Express Consent.
Note: If there is promotional messaging on this toll-free phone number, it requires express written consent.
Opt-in refers to the process of getting a consumer's permission to send them text messages. According to TCPA law, businesses must have "express written consent" from the consumer before texting them. NonConsumer (A2P) Message Senders should:
Obtain a Consumer's consent to receive messages generally.
Obtain a Consumer's express written consent to specifically receive marketing messages;
Ensure that Consumers can revoke consent.
Possible Solutions
Correct your opt-in process to collect a consumer's express consent via the CTIA guidelines and resubmit the toll-free verification.
Note: An opt-in call-to-action (CTA) with a checkbox must be unchecked by default
30447
Toll-Free verification rejection - phone number not provisioned to Call Loop
Verification is one component of ensuring A2P SMS is used by businesses in a legal and compliant manner. The review process looks at the business sending messaging (not the software powering it), the use case, sample content, the web presence, the opt-in/consent collected, and associated website terms and privacy policies.
Possible Causes
The toll-free verification was submitted before the toll-free phone number completed porting to Call Loop.
The toll-free phone number is not provisioned to Call Loop.
Possible Solutions
If the number is/was with another messaging provider at the time of verification, please ensure the porting or hosting process has been initiated and is complete. Then, delete the rejected toll-free verification and submit a new request after the port completes.
If it's not a porting scenario, contact Call Loop Support.
30448
Toll-Free phone number verification rejection - Age Gate
Verification is one component of ensuring A2P SMS is used by businesses in a legal and compliant manner. The review process looks at the business sending messaging (not the software powering it), the use case, sample content, the web presence, the opt-in/consent collected, and associated website terms and privacy policies.
Possible Causes
The Toll-Free phone number cannot be verified because an Age Gate is not present or is not acceptable on your website and/or opt-in policy.
Possible Solutions
Add a robust age gate to your website or opt-in policy. Resubmit the toll-free verification with the updated age gate information.
30449
Toll-Free phone number verification rejection - Age Gate
Verification is one component of ensuring A2P SMS is used by businesses in a legal and compliant manner. The review process looks at the business sending messaging (not the software powering it), the use case, sample content, the web presence, the opt-in/consent collected, and associated website terms and privacy policies.
Possible Causes
The toll-free phone number cannot be verified because the website URL in the sample message that you submitted was either from a public URL shortener or is non-secure.
Links to websites embedded within a message cannot conceal or obscure the Message Sender's identity and are not intended to cause harm or deceive Consumers. A website URL used in messaging must be a dedicated custom domain that belongs to your business, not a free shared public link shortener. The domain must align with the message sender identified in the text message itself.
Web addresses contained in messages, as well as any websites to which they redirect, should unambiguously identify the website owner (i.e., a person or legally registered business entity) and include contact information, such as a postal mailing address.
Possible Solutions
Replace the call to action (CTA) in the sample message with a branded URL. Resubmit the toll-free verification with an updated sample message.
Ensure that any URLs sent in messages are not sent from a public URL shortener.
Consider utilizing Call Loop's Link Shortening to programmatically shorten long links.
30448
Toll-Free phone number verification rejection - Age Gate
Verification is one component of ensuring A2P SMS is used by businesses in a legal and compliant manner. The review process looks at the business sending messaging (not the software powering it), the use case, sample content, the web presence, the opt-in/consent collected, and associated website terms and privacy policies.
Possible Causes
The Toll-Free phone number cannot be verified because an Age Gate is not present or is not acceptable on your website and/or opt-in policy.
Possible Solutions
Add a robust age gate to your website or opt-in policy. Resubmit the toll-free verification with the updated age gate information.
30451
Toll-Free phone number verification is unable to process - the address is invalid.
Call Loop is unable to process your Toll Free Verification request because it could not be validated by Call Loop and could not be submitted for verification review.
Possible Causes
The toll-free phone number cannot be verified because the address is invalid. It could be due to:
The provided address is not a valid US or Canadian address.
Invalid State or Region
Invalid Country
Invalid House Number (or Unit/Apartment/Suite Number)
Invalid City
Invalid Postal Code
Invalid Street
Invalid Address - multiple issues
Possible Solutions
Correct the address and resubmit the verification in Console or via the Messaging Compliance API. It is not recommended to delete the verification to resolve the address validation issue.
30452
Toll-Free phone number verification unable to process - email invalid
Call Loop is unable to process your Toll Free Verification request because it could not be validated by Call Loop and could not be submitted for verification review.
Possible Causes
The toll-free phone number cannot be verified because the email address is invalid. It could be due to:
Incorrectly formatted email address
Unknown email domain
Email is a suspected disposable address.
Email is invalid
Possible Solutions
Correct the email address and resubmit the verification in Console via the Messaging Compliance API. It is not recommended to delete the verification to resolve the email validation issue.
30455
Toll-Free phone number verification rejection - Disallowed: SHAFT - Hate
Verification is one component of ensuring A2P SMS is used by businesses in a legal and compliant manner. The review process looks at the business sending messaging (not the software powering it), the use case, sample content, the web presence, the opt-in/consent collected, and associated website terms and privacy policies.
Possible Causes
The toll-free phone number cannot be verified because the submission indicated that the business is associated with or the toll-free verification submission indicated a forbidden messaging category - (SHAFT: Hate).
Call Loop does not allow Hate speech, harassment, exploitative, abusive, or any communications that originate from a hate group.
Possible Solutions
If you are confident that your business and messaging use case does not fit into forbidden message categories, contact Call Loop support to provide Additional Information that explains your use case.
30456
Toll-Free phone number verification rejection - Disallowed: SHAFT - Hate
Verification is one component of ensuring A2P SMS is used by businesses in a legal and compliant manner. The review process looks at the business sending messaging (not the software powering it), the use case, sample content, the web presence, the opt-in/consent collected, and associated website terms and privacy policies.
Possible Causes
The toll-free phone number cannot be verified because the submission indicated that the business is associated with or the toll-free verification submission indicated a forbidden messaging category (SHAFT: Alcohol).
Alcohol traffic is allowed on Toll Free, Short Code, and Long Code in the US, as long as proper age-gating procedures are in place. Age gating means that website users must input their date of birth. It cannot be a yes or no question.
All age-gated content in Canada must be blocked across Toll Free, Short Code, and Long Code. The only way to send age-gated traffic into Canada (even with proper age-gating) is to receive a special carrier exemption. Allowed age-gated content in Canada includes: pocket knives, lighters, and non-alcoholic beverages.
Possible Solutions
Add an Age Gate for your US business website. Resubmit the verification and provide proof in your opt-in workflow documentation that you have measures in place to ensure compliance.
30457
Toll Free verification rejection - Disallowed: SHAFT - Firearms
Possible Causes
The toll-free phone number cannot be verified because the submission indicated that the business is associated with or the toll-free verification submission indicated a forbidden messaging category (SHAFT: Firearms and accessories).
Firearms and accessories, Tobacco, Vape, and E-cigarettes are not allowed on Toll Free, Short Code, or Long Code regardless of age gating.
Possible Solutions
If you are confident that your business and messaging use case does not fit into forbidden message categories, contact Call Loop Support to provide Additional Information that explains your use case.
30473
Toll-Free verification rejection - Cannot validate business website URL
Possible Causes
The toll-free phone number cannot be verified because the business website submitted is not accessible or available. The business website URL must pertain to the website the consumer is engaging with. In any of the following cases, the business website won't be reviewable:
The business website does not load or is not operational.
The business website is in a private state that requires a login/password.
The business website provided is a generic or unrelated URL, such as google.com, example.com, or similar placeholders.
Possible Solutions
Check that the business website URL is a live website. Resubmit once it is live.
Make sure that the business website URL is not in a private state that requires a login/password.. Resubmit after it is corrected. Categories, contact Call Loop Support to provide Additional Information that explains your use case.
30483
Business name and office record mismatch
Possible Causes
The business name provided in your submission does not match what appears on your corporate website or other official documents. This may include situations where:
A different business name is displayed on your website.
You're operating under a "Doing Business As" (DBA) name, but didn't clarify this in the submission.
Possible Solutions
Update the business name to exactly match what appears on your website or official documentation.
If you operate under a DBA name, update the DBA field in your submission and provide supporting documentation.
Ensure consistency between your verification submission and your web presence.
30481 – Customer Requested Cancellation
Description:
The verification request was withdrawn before processing was completed.
Possible Causes:
The request was manually canceled by you or someone in your organization.
Duplicate or erroneous submissions were identified and canceled.
Possible Solutions:
Submit a new verification request when ready.
Review all submission details carefully to avoid repeated cancellations.
Resubmittable? No
30482 – Business Email Must Use an Official Domain
Description:
The email provided for the contact does not use the official business domain.
Possible Causes:
Using a personal or free email provider (e.g., Gmail, Yahoo, Hotmail).
The email domain does not match the registered business domain.
Possible Solutions:
Provide an email address associated with your registered business domain.
Update company email settings to issue official addresses to staff.
Resubmittable? Yes
30483 – Contact Must Be a Business Representative
Description:
The listed contact is not recognized as an authorized representative of the business.
Possible Causes:
Contact is an unrelated third-party individual or consultant.
Submitted contact information is outdated or incorrect.
Possible Solutions:
Provide details for an owner, officer, or employee of the business.
Ensure the contact’s title and email match official business records.
Resubmittable? Yes
30484 – Business Name and Official Records Do Not Match
Description:
The submitted business name does not match official legal registration documents.
Possible Causes:
Typographical errors in the business name.
Using a trade name instead of the registered legal name.
Possible Solutions:
Use the exact name from official registration documents.
Correct spelling, punctuation, and formatting to match legal records.
Resubmittable? Yes
30485 – Official Business Registration Documents Required
Description:
Verification failed because proof of legal business registration was not provided or was incomplete.
Possible Causes:
No registration documents uploaded.
Documents submitted are incomplete, illegible, or outdated.
Possible Solutions:
Upload valid government-issued registration certificates or licenses.
Ensure all scans or photos are clear, complete, and legible.
Resubmittable? Yes
30487 – Charitable Organization Must Provide Nonprofit Verification
Description:
Nonprofit organizations must provide valid proof of charitable status.
Possible Causes:
Nonprofit verification documents were not provided.
Submitted documents have expired or are invalid.
Possible Solutions:
Provide recognized nonprofit proof, such as a 501(c)(3) certificate.
Ensure all documents are current and legible.
Resubmittable? Yes
30488 – Doing Business As (DBA) Name Must Be Accurately Provided
Description:
The DBA (Doing Business As) name provided is missing, incorrect, or incomplete.
Possible Causes:
Entered an abbreviated or partial DBA name.
No official DBA registration record was provided.
Possible Solutions:
Enter the full registered DBA name exactly as listed in official records.
Upload proof of DBA registration if applicable.
Resubmittable? Yes
30527 – Business Registration Number Missing or Invalid
Description:
A valid business registration number is required, but it was either missing or incorrect.
Possible Causes:
Registration number not included in the submission.
The number entered is incorrect, expired, or mismatched.
Possible Solutions:
Retrieve the correct registration number from official records.
Enter it exactly as registered.
Resubmittable? Yes
30489 – Website Must Be Established and Active
Description:
The submitted website must be functional and publicly accessible.
Possible Causes:
The website is under construction or inactive.
The domain has expired or is not properly hosted.
Possible Solutions:
Publish the business website before submission.
Confirm that the site loads correctly and is accessible.
Resubmittable? Yes
30490 – Social Platform Must Be Established and Active
Description:
The provided social media profile is inactive or inaccessible.
Possible Causes:
Account has no content or recent activity.
Profile is set to private or restricted.
Possible Solutions:
Provide a link to a public, active profile.
Post relevant content to demonstrate activity.
Resubmittable? Yes
30491 – Website Is Password-Protected or Requires Login
Description:
The website content is not publicly accessible due to login or password protection.
Possible Causes:
Content hidden behind authentication.
Restricted site access is preventing verification.
Possible Solutions:
Make the website publicly viewable.
Provide an alternate public link showing your business information.
Resubmittable? Yes
30492 – Business Website Must Display Branding
Description:
The website must show clear business branding for verification purposes.
Possible Causes:
No company name or logo visible.
Using a generic template without branding.
Possible Solutions:
Add your business name, logo, and contact information.
Ensure branding is visible on the main pages.
Resubmittable? Yes
30493 – Privacy Policy or Terms URL Missing or Inaccessible
Description:
Required privacy policy or terms of service URLs are missing, broken, or inaccessible.
Possible Causes:
No policy pages published.
URLs provided are incorrect or unreachable.
Possible Solutions:
Publish privacy policy and terms pages.
Test links to ensure they are functional.
Resubmittable? Yes
30494 – Independent Software Vendor (ISV) or Reseller Name Must Be Provided
Description:
The ISV or reseller name is missing in the submission.
Possible Causes:
Field left blank.
The provided name is incomplete or incorrect.
Possible Solutions:
Include the full ISV or reseller name in the submission.
Verify accuracy before submitting.
Resubmittable? Yes
30495 – Projected Message Volume Exceeds Use Case Limits
Description:
Expected message volume is higher than allowed for the stated use case.
Possible Causes:
Overestimating message traffic.
Use case not suited for high-volume messaging.
Possible Solutions:
Adjust projected volume to realistic limits.
Provide justification if a higher volume is required.
Resubmittable? Yes
30496 – Use Case and Use Case Summary Are Inconsistent
Description:
The detailed use case description does not match the submitted summary.
Possible Causes:
Contradictory information in the form.
Incorrect category selected.
Possible Solutions:
Align the summary with the detailed description.
Ensure consistency across all submission fields.
Resubmittable? Yes
30497 – Use Case Summary Is Incomplete
Description:
The use case summary is missing key details required for verification.
Possible Causes:
Short or vague description provided.
Essential information omitted.
Possible Solutions:
Provide a clear, detailed overview of your messaging purpose.
Include all necessary information to fully describe the use case.
Resubmittable? Yes
30498 – Opt-In Workflow Must Match Submission Details
Description:
The opt-in process submitted does not match the workflow described in the use case.
Possible Causes:
Using an outdated consent form or process.
Example messages do not align with the actual workflow.
Possible Solutions:
Update submission to accurately reflect the current opt-in flow.
Ensure all examples and forms match the live process.
Resubmittable? Yes
30499 – Message Content Doesn't Align with Use Case
Description:
Sample messages provided do not reflect the stated purpose of the campaign.
Possible Causes:
Placeholder or unrelated content submitted.
Sample messages are inconsistent with the use case category.
Possible Solutions:
Provide real examples that match the use case.
Ensure message content accurately represents the campaign purpose.
Resubmittable? Yes
30486 – HELP Keyword Response Must Meet Requirements
Description:
The automated HELP response is incomplete or non-compliant.
Possible Causes:
Missing required information, such as business name or contact info.
Template does not meet required guidelines.
Possible Solutions:
Update HELP message to include full business name, contact info, and instructions.
Verify that the message meets all compliance requirements.
Resubmittable? Yes
30501 – Political Campaign Must Have a Campaign Verify Token
Description:
Political campaigns must provide a valid verification token to proceed.
Possible Causes:
Token not submitted.
Submitted token is invalid or expired.
Possible Solutions:
Obtain a valid verification token for your campaign.
Include the token in the resubmission.
Resubmittable? Yes
30502 – Political Campaign Must Submit Federal Election Commission (FEC) ID
Description:
A valid FEC ID is required for political campaign verification.
Possible Causes:
FEC ID not provided.
Incorrect or invalid FEC ID submitted.
Possible Solutions:
Retrieve your registered FEC ID.
Submit the correct ID along with the request.
Resubmittable? Yes
30503 – Confirmation Message Missing Required Details
Description:
The opt-in confirmation message is missing necessary details, such as terms or sender identity.
Possible Causes:
Omitting mandatory information from the confirmation message.
Using a generic or incomplete template.
Possible Solutions:
Include all required information in confirmation messages.
Ensure message content identifies the sender and includes terms.
Resubmittable? Yes
30504 – Single Opt-In Cannot Cover Multiple Use Cases
Description:
A single opt-in is being used for multiple unrelated campaigns.
Possible Causes:
Combining different marketing campaigns under one consent.
Using a generic opt-in form for multiple purposes.
Possible Solutions:
Separate opt-ins for each distinct use case.
Ensure each campaign has its own consent process.
Resubmittable? Yes
30505 – Opt-In Must Be Optional, Not Mandatory
Description:
Consent cannot be mandatory for using a service or product.
Possible Causes:
Linking opt-in to purchase or service usage requirement.
Forcing users to accept messages to access the service.
Possible Solutions:
Make opt-in optional.
Allow service use without mandatory consent.
Resubmittable? Yes
30506 – Opt-Ins Must Clearly Reflect End Business
Description:
The opt-in form must clearly indicate the sending business.
Possible Causes:
Showing only a third-party name in consent.
Omitting the end business from the consent message.
Possible Solutions:
Display your business name clearly on the opt-in form.
Ensure consent clearly links to your organization.
Resubmittable? Yes
30507 – Opt-In Does Not Match Use Case
Description:
The opt-in flow provided does not align with the stated purpose.
Possible Causes:
Generic or unrelated consent text.
Mismatch between the opt-in process and messaging purpose.
Possible Solutions:
Tailor the opt-in text to the specific use case.
Ensure examples and workflow are consistent with the submission.
Resubmittable? Yes
30508 – Pre-Selected Opt-In Checkbox Not Allowed
Description:
Pre-checked opt-in checkboxes are not allowed in consent forms.
Possible Causes:
Using forms with pre-ticked checkboxes.
Attempting to simplify consent collection by pre-selecting options.
Possible Solutions:
Require users to manually select opt-in.
Update forms to remove pre-checked boxes.
Resubmittable? Yes
30509 – Opt-In URL Not Accessible
Description:
The link to the opt-in form cannot be opened or accessed.
Possible Causes:
Broken or incorrect URL.
The website or form is restricted or offline.
Possible Solutions:
Test the link to ensure it is functional.
Correct the URL or provide an alternate accessible link.
Resubmittable? Yes
30510 – Opt-In Example Must Be Complete and Branded
Description:
The sample opt-in example is missing required branding or information.
Possible Causes:
Missing logo, business name, or consent text.
An incomplete sample form was provided.
Possible Solutions:
Provide a complete, branded example.
Include all required elements such as business name and logo.
Resubmittable? Yes
30511 – Verbal Consent Script Must Be Provided
Description:
A script used to collect verbal consent must be submitted.
Possible Causes:
No script provided.
The script is missing necessary details or clarity.
Possible Solutions:
Submit the exact verbal consent script.
Ensure it meets all consent requirements.
Resubmittable? Yes
30512 – Age Gate Required for Age-Restricted Content
Description:
Content targeted at specific age groups requires verification of age.
Possible Causes:
No age check implemented.
Content accessible to all without restriction.
Possible Solutions:
Implement an age gate before submission.
Ensure only appropriate users can access age-restricted content.
Resubmittable? Yes
30513 – Opt-In Not Sufficient: Language Unclear
Description:
Consent text is ambiguous, confusing, or incomplete.
Possible Causes:
Vague wording or legal jargon.
Users cannot clearly understand what they are consenting to.
Possible Solutions:
Use plain-language, clear consent wording.
Ensure all necessary information is easy to understand.
Resubmittable? Yes
30515 – Valid Opt-In Required for All Submissions
Description:
Consent proof is missing or not provided for submission.
Possible Causes:
No opt-in process submitted.
Consent records are incomplete or invalid.
Possible Solutions:
Include documented proof of user consent.
Verify that the opt-in process is fully compliant.
Resubmittable? Yes
30516 – Double Opt-In Required for This Use Case
Description:
A two-step confirmation process is required for this specific use case.
Possible Causes:
Only a single opt-in step was implemented.
Confirmation step missing or incomplete.
Possible Solutions:
Implement double opt-in via email or SMS.
Ensure both steps are documented.
Resubmittable? Yes
30517 – Shopping Cart Reminders Must Follow Specific Guidelines
Description:
Shopping cart reminder messages do not comply with regulatory or policy requirements.
Possible Causes:
Missing required disclosures.
Non-compliant message content or timing.
Possible Solutions:
Update reminder messages to meet compliance standards.
Include all legally required disclosures.
Resubmittable? Yes
30518 – Call-to-Action Missing Required Disclosures
Description:
Marketing messages lack mandatory legal or regulatory text.
Possible Causes:
No mention of terms, charges, or disclosures.
Generic CTAs are used without compliance review.
Possible Solutions:
Add required disclosures to the call-to-action text.
Review compliance guidelines before submission.
Resubmittable? Yes
30519 – Privacy Policy Required for Personal Data Collection
Description:
A privacy policy is missing when collecting personal data.
Possible Causes:
No privacy policy page published.
URL provided is broken or inaccessible.
Possible Solutions:
Publish and link to a compliant privacy policy.
Test URL accessibility before submission.
Resubmittable? Yes
30520 – Privacy Policy Mentions Sharing Opt-In Data
Description:
Privacy policy allows sharing of consent or opt-in data with third parties.
Possible Causes:
Policy is outdated or non-compliant.
Intentional or accidental mention of data sharing.
Possible Solutions:
Update privacy policy to prohibit sharing opt-in data.
Review all policy statements for compliance.
Resubmittable? Yes
30521 – Opt-In Data Cannot Be Shared with Third Parties
Description:
Consent data is being shared outside of the end business.
Possible Causes:
Agreements to share leads or opt-in records.
Third-party marketing involvement.
Possible Solutions:
Stop sharing opt-in records outside your business.
Ensure all consent is kept internal and compliant.
Resubmittable? Yes
30522 – SMS Terms Must Be Accessible and Compliant
Description:
The SMS terms page is missing or not compliant.
Possible Causes:
No terms page published.
Page contains errors or is inaccessible.
Possible Solutions:
Publish compliant SMS terms and conditions.
Test link accessibility before submission.
Resubmittable? Yes
30523 – High-Risk Domain Reputation Detected
Description:
The domain used has a poor trust or spam reputation.
Possible Causes:
Domain previously blacklisted.
Associated with spam, phishing, or abuse.
Possible Solutions:
Use a reputable domain with a clean reputation.
Check the domain reputation before submission.
Resubmittable? No
30524 – Potential Fraud Risk Identified
Description:
The submission has been flagged for suspicious activity.
Possible Causes:
Unusual patterns in messaging or contact info.
Mismatched business information.
Possible Solutions:
Review all data for accuracy.
Correct any inconsistencies before resubmission.
Resubmittable? No
30525 – Public URL Shorteners Not Allowed
Description:
Public URL shorteners (e.g., bit.ly, tinyurl) cannot be used in submissions.
Possible Causes:
Using a public URL shortening service.
Shortened links obscure the destination or brand.
Possible Solutions:
Use a branded short link or full domain URL.
Avoid public URL shorteners.
Resubmittable? Yes
30526 – High-Risk Domain Issues
Description:
The linked domain is considered unsafe or high-risk.
Possible Causes:
Domain associated with malicious or fraudulent activity.
Poor security or trust issues with the domain.
Possible Solutions:
Replace with a safe, verified domain.
Ensure the domain is trusted and secure.
Resubmittable? No
30528 – Disallowed: Non-Federally Compliant Use Case
Description:
The campaign violates federal regulations.
Possible Causes:
The messaging category is legally restricted.
Non-compliant content submitted.
Possible Solutions:
Adjust the use case to meet federal compliance standards.
Ensure all campaigns are legally permissible.
Resubmittable? No
30529 – Disallowed: Alcohol Promotions Without Age Verification
Description:
Marketing alcohol-related content without an age gate or verification.
Possible Causes:
No age verification implemented.
Accessible to all users regardless of age.
Possible Solutions:
Add an age gate to restrict access.
Only submit campaigns with proper age verification.
Resubmittable? No