The error “We detected the contents of this message may violate carrier acceptable use policies” when helping Customers via SMS/text is typically caused by one of the reasons below.
There are words automatically flagged as objectionable or forbidden by carriers and are not allowed on SMS and MMS transmissions in the United States or Canada. Outbound SMSes containing forbidden words will be blocked.
– Payday loans – Short term high-interest loans – New loan soliciting – Third-party loans – Student loansCryptocurrencyStocks and investing platforms
Any third-party use cases are strictly forbidden. Consent must be obtained directly from end-users. Political use case customers sending SMS messages cannot use voter registration databases to collect consent and outreach end-users. Any business with a term of service or privacy policy that mentions sharing or selling consumer data/opt-in information is considered non-compliant.
Third-party lead generation services and marketing
– Companies, NGOs or political campaigns that buy, sell, or share consumer information. – Affiliate lending – Affiliate marketing – Deceptive marketing
Any third-party use cases are strictly forbidden. Consent must be obtained directly from end-users. Political use case customers sending SMS messages cannot use voter registration databases to collect consent and reach end-users. Any business with terms of service or privacy policy that mentions sharing or selling consumer data/opt-in information is considered non-compliant.
This differs from outreach about employment due to compliant opt-in practices, messages from brokerages to their members, investment news alerts, or other investment-related messages.
Cannabis, CBD, Kratom, or drug paraphernalia product businesses are prohibited from utilizing SMS/MMS messaging on Twilio in the US and Canada, regardless of content. These restrictions apply regardless of the federal or state legality. All use cases for these are disallowed from sending SMS, whether it contains cannabis content or not. Even for 2FA purposes, it is not permissible for such entities.
Cannabis, CBD, Kratom, or drug paraphernalia product businesses are prohibited from utilizing SMS/MMS messaging on Twilio in the US and Canada, regardless of content. These restrictions apply regardless of the federal or state legality. All use cases for these are disallowed from sending SMS whether it contains cannabis content or not. Even for 2FA purposes, it is not permissible for such entities.
Prescription drugs
Drugs that require a prescription
Offers for drugs that cannot be sold over-the-counter in the US/Canada are forbidden regardless if the business is a licensed professional.
How to communicate with Customers if outbound SMS is blocked #
Remove forbidden words from outbound SMS
If the “We detected the contents of this message may violate carrier acceptable use policies” error appears, find any forbidden words triggering the error and remove them. You must close the existing message and start a new one to attempt to resend the edited version of your text without the forbidden word. If you’re still unable to send the message, contact Gladly Support.
Redirect inbound SMS to a different channel if it contains forbidden words
Create an SMS auto-reply Rule for messages containing forbidden keywords that your Customers may contact you about (e.g., if you’re a beauty company with CBD products), and tell Customers to reach out on a different Channel, such as email or voice.
You are missing the required consent language in your SMS communications, like your company name in your initial SMS reply. See SMS Consent and Compliance Guidelines for more information.
Note – Contact Gladly Support if the violation error persists
The phone number generating the violation error may stop working and fail to send and receive SMSes which requires it to be unblocked by the carrier. Contact Gladly Support for assistance.
The carrier thinks the message sent by the Agent is spam. If this error is a common occurrence, below are a few options you can consider to avoid this issue.
Use a 10-digit local number for SMSes to switch to if you encounter this message and the Customer does not receive it. This number acts as a backup number if outbound SMSes fail to be delivered.
Use a toll-free number for SMSes that you can also use with Customers. In general, carriers are less stringent in filtering messages via toll-free numbers than standard, long code (10 digits) SMS traffic.
Keep in mind that toll-free doesn’t support MMS (images).
If you’re already using a toll-free number, contact Gladly Support to verify the number on the Carrier side to reduce the risk of filtering Toll-Free SMS to the US and some networks in Canada.
Consider purchasing a short code if you have many outbound SMSes. We don’t recommend this since options one and two (above) are usually the best routes to take if you’re using text to help Customers versus bulk outbound/marketing text.
Review Types of SMS Numbers to learn the differences and pros and cons of using long, toll-free, and short code numbers.
This occurs if a message is identified as spam or unwanted or flagged as objectionable and blocked by a wireless carrier, as defined by the filtering system.
This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
Cookie
Duration
Description
__cf_bm
29 minutes
This cookie, set by Cloudflare, is used to support Cloudflare Bot Management.
_wpfuuid
1 year 1 month 4 days
This cookie is used by the WPForms WordPress plugin. The cookie is used to allows the paid version of the plugin to connect entries by the same user and is used for some additional features like the Form Abandonment addon.
BIGipServer*
session
Marketo sets this cookie to collect information about the user's online activity and build a profile about their interests to provide advertisements relevant to the user.
cookielawinfo-checkbox-advertisement
1 year
Set by the GDPR Cookie Consent plugin, this cookie records the user consent for the cookies in the "Advertisement" category.
cookielawinfo-checkbox-analytics
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".
cookielawinfo-checkbox-functional
11 months
The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
cookielawinfo-checkbox-necessary
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
cookielawinfo-checkbox-others
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.
cookielawinfo-checkbox-performance
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".
CookieLawInfoConsent
1 year
CookieYes sets this cookie to record the default button state of the corresponding category and the status of CCPA. It works only in coordination with the primary cookie.
PHPSESSID
session
This cookie is native to PHP applications. The cookie stores and identifies a user's unique session ID to manage user sessions on the website. The cookie is a session cookie and will be deleted when all the browser windows are closed.
viewed_cookie_policy
11 months
The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data.
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
Cookie
Duration
Description
li_gc
5 months 27 days
Linkedin set this cookie for storing visitor's consent regarding using cookies for non-essential purposes.
lidc
1 day
LinkedIn sets the lidc cookie to facilitate data center selection.
UserMatchHistory
1 month
LinkedIn sets this cookie for LinkedIn Ads ID syncing.
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
Cookie
Duration
Description
_ga
1 year 1 month 4 days
Google Analytics sets this cookie to calculate visitor, session and campaign data and track site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognise unique visitors.
_ga_*
1 year 1 month 4 days
Google Analytics sets this cookie to store and count page views.
_gd_session
4 hours
This cookie is used for collecting information on users visit to the website. It collects data such as total number of visits, average time spent on the website and the pages loaded.
_gd_visitor
1 year 1 month 4 days
This cookie is used for collecting information on the users visit such as number of visits, average time spent on the website and the pages loaded for displaying targeted ads.
_sp_id.*
1 year 1 month 4 days
Snowplow sets this cookie to store user information that is created when a user first visits a site and is updated on subsequent visits.
_sp_ses.*
30 minutes
Snowplow sets this cookie to store user information that is created when a user first visits a site and is updated on subsequent visits.
AnalyticsSyncHistory
1 month
Linkedin set this cookie to store information about the time a sync took place with the lms_analytics cookie.
mf_user
3 months
Mouseflow sets this cookie to identify whether a visitor is new or returning.
vuid
1 year 1 month 4 days
Vimeo installs this cookie to collect tracking information by setting a unique ID to embed videos on the website.
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
Cookie
Duration
Description
_mkto_trk
1 year 1 month 4 days
This cookie, provided by Marketo, has information (such as a unique user ID) that is used to track the user's site usage. The cookies set by Marketo are readable only by Marketo.
bcookie
1 year
LinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser IDs.
bscookie
1 year
LinkedIn sets this cookie to store performed actions on the website.
li_sugr
3 months
LinkedIn sets this cookie to collect user behaviour data to optimise the website and make advertisements on the website more relevant.