Why This Rejection Happens
The "Call-to-Action" (CTA) or opt-in instructions you provided describe how users join but fail to specify what they are joining. Consumers must know the nature of the messages (e.g., "marketing alerts," "appointment reminders") before opting in.
Common Triggers: Writing "Enter your number to sign up" without adding "for promotional SMS," or using generic terms like "updates" for a marketing campaign.
Root Cause Analysis
Primary Triggers
- Omission of Detail: The description says "User opts in for messages" but leaves out the crucial adjective (marketing, support, etc.).
- Scope Mismatch: The description says "Account Alerts" but the sample messages contain "Sales Offers." This mismatch flags the opt-in description as insufficient/inaccurate.
- Assumed Context: Thinking that because the form is on a "Deals" page, you don't need to explicitly state "marketing messages" in the description text field.
Required Elements
| Campaign Type | Required Phrasing | Why? |
|---|---|---|
| Marketing | "promotional messages," "marketing alerts," "offers" | Discloses commercial intent. |
| Transactional | "account notifications," "order updates," "reminders" | Sets expectation for service-based traffic. |
| Mixed | "marketing and support messages" | Covers both use cases. |
Step-by-Step Remediation
Check Your Registered Use Case
Go to your Campaign details. Did you select "Marketing," "Customer Care," or "Mixed"? Your description must use words that match that selection.
Rewrite the CTA Description
Edit the text in the "Message Flow" or "Call-to-Action" field. Insert the specific message type.
✓ Compliant Description
"Customers enter their phone number on our website checkout page to receive shipping notifications and delivery alerts from North Star Logistics."
✗ Non-Compliant Description
"Customers enter their number to receive SMS."
(SMS is the channel, not the content type.)
Verify Against Visual Proof
If you uploaded a screenshot of your form, ensure the form also says "shipping notifications." If the form says "marketing" but your description says "shipping," you will be rejected for inconsistency (Code 2132).
Carrier-Specific Requirements
T-Mobile
- Requires a "Program Description" to be part of the opt-in disclosure. "Receive texts" is not a program description.
AT&T
- Flags "bait and switch" tactics. If the description implies service alerts ("updates") but the samples show ads ("buy now"), the description is considered deceptive and incomplete.
MyTCRPlus Tools That Can Help
Campaign Description Generator
Generates a robust description that automatically includes the correct terminology for your selected Use Case.
Consent Form Builder
Ensures your actual form text matches the description you are writing.
Pre-Resubmission Checklist
- The description includes specific words (e.g., "marketing," "alerts").
- The terminology matches my registered Use Case.
- The terminology matches my Sample Messages.
- I have avoided generic terms like "info" or "updates" without qualification.
Common Mistakes to Avoid
❌ "Important Information"
Phrases like "important info" are subjective and vague. Use objective terms like "account balance alerts" or "emergency notifications."
❌ Disconnect from Samples
Don't write "We send appointment reminders" if your sample messages are "Happy Birthday! Here is a coupon." The description must cover ALL content types.
Expected Timeline
Related Rejection Codes
This guidance provides general information about 10DLC compliance requirements. Clear communication of message content is essential for informed consent. Organizations should ensure their descriptions accurately reflect the full scope of their messaging program. MyTCRPlus does not provide legal advisory services or regulatory representation.