Why This Rejection Happens
The "Call-to-Action" (CTA) or opt-in instructions you provided are too vague, incomplete, or confusing. The vetting agent cannot determine how a consumer actually enrolls in the program based on your description.
Common Triggers: Writing "See attached" without attaching anything, providing a description that contradicts the evidence (e.g., saying "Text JOIN" but the flyer says "Scan QR"), or omitting key steps in the user flow.
Root Cause Analysis
Primary Triggers
- Lack of Detail: You wrote "User opts in" instead of explaining how (e.g., "User enters number in web form").
- Circular Logic: You said "Users opt in via SMS," but didn't explain how they get the number to text in the first place (e.g., "Signage in store tells users to text JOIN").
- Inconsistent Flow: The description says "Web Opt-in" but the uploaded image shows a "Paper Form."
Required Elements
| Opt-in Method | Required Description Detail |
|---|---|
| Keyword (Text-to-Join) | "Consumers see a flyer/sign/ad that says 'Text JOIN to 12345'. They send the keyword to opt in." |
| Web Form | "Consumers visit [URL], enter their phone number in the form, check the consent box, and click Submit." |
| Verbal/POS | "At checkout, the agent reads the script [Script Text]. The customer verbally agrees, and the agent enters the number." |
Step-by-Step Remediation
Map the User Journey
Write down the exact steps a user takes to sign up, starting from "Where do they see the offer?" to "How do they agree?"
Rewrite the Description
Be verbose. Assume the vetting agent knows nothing about your business. Use the formula: Context + Action + Consent Mechanism.
✓ Compliant Description
"Potential customers visit our website [URL]. They navigate to the 'Subscribe' page. They enter their mobile number into the field labeled 'Mobile Phone.' They check a box that says 'I agree to receive marketing SMS...'. They click the 'Join Now' button to complete the opt-in."
✗ Non-Compliant Description
"Users sign up on the site."
(Too vague. Which site? How?)
Align with Evidence
Ensure your description matches the URL or Image you uploaded. If you describe a web form, the URL must lead to a web form.
Carrier-Specific Requirements
T-Mobile
- Rejects "ambiguous" flows. If it's unclear whether the opt-in is single or double, or if it happens online or offline, they will reject it.
AT&T
- Looks for the "Call-to-Action" (CTA) to be fully described. The CTA is the invitation to opt-in (e.g., the sign, the web text), not just the act of opting in.
MyTCRPlus Tools That Can Help
Consent Form Builder
Helps you structure the correct legal language for your opt-in flow description.
Campaign Description Generator
Use our template wizard to generate a comprehensive "Message Flow" description that carriers love.
Pre-Resubmission Checklist
- The description explains where the user finds the opt-in.
- The description explains what action the user takes.
- The description mentions the legal disclosures (privacy, fees) are present.
- The text matches the visual proof provided (URL/Image).
- No "See attached" shortcuts are used.
Common Mistakes to Avoid
❌ "See attached"
Never write only "See attached image." The text field is indexed for searching and automated checks. You must write out the description and attach the image.
❌ Confusing Opt-in with Message Flow
This section is about how they join, not what you send later. Focus on the intake process.
Expected Timeline
Related Rejection Codes
This guidance provides general information about 10DLC compliance requirements. A clear and accurate description of the opt-in process is essential for carriers to verify that consent is being collected lawfully. MyTCRPlus does not provide legal advisory services or regulatory representation.