You already know that there are federal and state (or provincial) laws regulating texting that you must comply with, not to mention the CTIA Messaging Principles and Best Practices imposed by the various carriers. You're ready to send a message that complies with all of those, but now you're wondering if there's anything else you should think about that could impact deliverability.

When composing a Broadcast message, the Prompt.io platform will analyze your message for content known to lead to deliverability issues such as carrier filtering. The platform will also help to flag best practices. In most cases, the algorithm used by carriers is not published and is constantly evolving. Our deliverability check will evolve as best practices and new markers for potential issues become available.

Note that we will not programmatically restrict the ability to actually send the broadcast, even when red-flag warnings are surfaced. Ultimately, the messages you send are completely in your control and compliance is your responsibility.

Deliverability checks for Personalization, Flagged Content, Links, MMS Size, Message Length, and Compliance wording will be displayed in one of three states:

⬤ No potential issue detected.

⬤ An issue exists that is known to have the potential to cause deliverability issues.

⬤ An issue exists that will almost definitely lead to deliverability issues.

<aside> ⚠️ Even if no potential issues are detected, we cannot guarantee delivery of texts. Carriers can block any message at any time without warning or explanation.

</aside>

Personalization

Personalized messages lead to the highest engagement as well as the highest deliverability. Consider using field merge to personalize each outbound text.

https://s3-us-west-2.amazonaws.com/secure.notion-static.com/c9fd62f0-787f-465c-bce2-e299e0e4c9d4/Untitled.png

Note that in cases where field merge is used and there is missing data associated with contacts to be texted, a warning will be surfaced letting you know that an incomplete field merge may result.

Flagged Content

T-Mobile has indicated that they will start levying penalties for traffic that is offside their Code of Conduct. This would include SHAFT (Sex, Hate, Alcohol, Firearms, Tobacco) violations, spam, phishing, and messaging that meets the Severity 0 violation threshold per the CTIA Short Code Monitoring Handbook.

It should therefore come as no surprise that some keywords will lead to aggressive carrier filtering (across the board):