Content Not in English
Why This Rejection Happens
TCR and carrier vetting teams primarily operate in English. If your sample messages, website content, or privacy policy are entirely in a foreign language without translation, reviewers cannot verify compliance with CTIA guidelines, leading to automatic rejection.
Root Cause Analysis
While 10DLC supports multi-language messaging, the vetting process requires English documentation to prove that your content is not prohibited (SHAFT) and that your opt-in methods are compliant.
Common Scenarios
- Sample messages provided solely in Spanish, French, or Chinese without English translation.
- Website linked for verification does not have an English version or translation toggle.
- Privacy Policy is exclusively in a non-English language.
Remediation Steps
-
Translate Sample Messages
You do not need to change the actual messages you send to customers. However, in the Sample Message fields of your registration, you must provide the English translation alongside the original text.
Format for Submission: [Original Language]: Su código de verificación es 1234. [English Translation]: Your verification code is 1234.
-
Verify Website Accessibility
If your primary website is non-English, ensure there is a visible language toggle or provide a direct link to an English version in the "Campaign Description" or "Notes" field. If no English site exists, provide a brief summary of the business nature in English in the brand description.
-
Privacy Policy Compliance
The Privacy Policy is a legal document used for vetting. If it is not in English, provide a translated version or a second policy specifically for US compliance purposes that vetting teams can review.
Need Help with Translations?
Our experts can help format your international campaign for US carrier approval.