Why This Rejection Happens
The disclosure text on your opt-in form (checkbox or footer) fails to specify the nature of the content the user is signing up for. It is not enough to say "I agree to receive texts." You must say "I agree to receive [marketing/alerts/reminders]."
Common Triggers: Disclosures that are too brief ("Receive SMS from us") or generic ("Receive updates") without defining the scope.
Root Cause Analysis
Primary Triggers
- Ambiguity: The disclosure leaves the user guessing. "Updates" could mean "Password Reset" (acceptable) or "Daily Ads" (spam). Carriers demand specificity.
- Mismatch: You registered a "Marketing" campaign, but the form only says "Order Updates." This is a deceptive opt-in.
- Omission: The sentence structure is incomplete: "I agree to receive messages from Brand X" (Missing the "what").
Required Elements
| Element | Required Language | Rationale |
|---|---|---|
| Content Scope | "promotional messages," "account alerts," "one-time code" | Defines the "value exchange" of the opt-in. |
| Context | "receive [Type] from [Brand]" | Links the sender to the specific type of traffic. |
| Consistency | Must match Campaign Use Case | If you send ads, you MUST disclose "marketing/promos" here. |
Step-by-Step Remediation
Determine Your Message Type
Refer to your TCR Campaign Registration. If you selected "Marketing," you must use the word "marketing," "promotional," "offers," or "deals."
✓ Compliant Disclosure
"I agree to receive marketing and promotional messages from [Brand]..."
✗ Non-Compliant Disclosure
"I agree to receive SMS from [Brand]..."
(SMS is the channel, not the message type.)
Update the Web Form Text
Log in to your website builder (WordPress, Shopify, etc.) and edit the small print near the checkbox or submit button.
Capture Proof
If your form is behind a login or not publicly crawlable, take a new screenshot showing the specific phrase (e.g., "marketing messages") and upload it to the portal.
Carrier-Specific Requirements
T-Mobile
- Requires a "Program Description" at the point of opt-in. "Receive texts" is not a description. "Receive weekly deals" is a description.
AT&T
- Flags opt-in forms that are "overly broad." If you say "updates" but send "third-party offers," you will be blocked for scope creep.
MyTCRPlus Tools That Can Help
Consent Form Builder
Generates compliant HTML with placeholders for "Marketing," "Alerts," or "2FA" depending on your need.
Screenshot Hosting Service
Host your updated form screenshots securely for the carrier vetting team.
Pre-Resubmission Checklist
- The form text includes a specific description (e.g., "marketing," "alerts").
- The description matches the actual content of my sample messages.
- The disclosure is visible near the submission point.
- I have updated the live site URL or screenshot provided to TCR.
Common Mistakes to Avoid
❌ "Important Information"
Phrases like "important info" or "news" are too vague. Be specific: "Account status changes" or "Service outage alerts."
❌ Hiding it in the Privacy Policy
The message type must be stated on the form itself (the "Call to Action"), not just buried in a linked policy document.
Expected Timeline
Related Rejection Codes
This guidance provides general information about 10DLC compliance requirements. Defining the scope of consent is critical to avoid "bait and switch" allegations. Organizations should ensure their opt-in disclosures accurately reflect the full range of content they intend to send. MyTCRPlus does not provide legal advisory services or regulatory representation.