Writing Compliant Sample Messages: Avoid Rejections
Discover the anatomy of a perfect 10DLC sample message. From mandatory disclosures to brand identification, learn exactly what Direct Connect Aggregators (DCAs) look for when approving your campaign.
Key Takeaways
Mandatory Brand Identity
Learn why failing to include your exact TCR-registered Brand Name in your sample messages will trigger an automatic 'Sender Identity' rejection.
Opt-Out Disclosures
Discover the exact syntax required for STOP and HELP commands within your samples to prove CTIA compliance to the manual reviewers.
URL & Link Hygiene
Understand the rules around submitting sample messages with links, including why public shorteners (like bit.ly) result in instant campaign denial.
Are Your Sample Messages Compliant?
Don't let a missing keyword delay your campaign launch. Use our diagnostic tool to verify your sample message syntax against current DCA review protocols.
Validate Sample ContentDetailed Breakdown
When submitting a new campaign to The Campaign Registry (TCR), businesses are required to provide 2 to 5 "Sample Messages." Many marketers treat this as a simple formality, quickly typing out generic placeholders like "Here is a discount code" or "Your appointment is confirmed." This is a critical error. The sample messages you provide are not just placeholders; they are binding declarations of your intent. They are manually scrutinized by human reviewers working for Direct Connect Aggregators (DCAs), and they serve as the ultimate litmus test for whether your business understands and complies with Cellular Telecommunications Industry Association (CTIA) guidelines.
Failing to properly format these sample messages is one of the top three reasons for A2P 10DLC campaign rejections. Reviewers are looking for specific, non-negotiable elements within these short text blocks. If any of these elements are missing, or if the tone of the message contradicts the Use Case you selected, the campaign will be kicked back, delaying your messaging capabilities and potentially requiring you to pay new registration fees. To ensure first-time approval, you must master the anatomy of a compliant sample message.
The Anatomy of a Perfect Sample Message
Every sample message submitted must contain three fundamental components: Context, Brand Identification, and Opt-Out Mechanics.
1. Brand Identification: The CTIA strictly mandates that a consumer must always know who is texting them. The reviewer needs to see this proven in your sample text. You must include your exact TCR-registered Brand Name. For example, if you are a dental office, a bad sample message is: "Your appointment is set for Tuesday at 2 PM." A compliant sample message is: "Hi [Name], your appointment with Smith Family Dental is set for Tuesday at 2 PM."
2. Opt-Out Mechanics: You must explicitly demonstrate how a consumer can revoke their consent. At least one (and ideally all) of your sample messages must conclude with industry-standard opt-out language. If you fail to include "Reply STOP to opt out" or "Text STOP to cancel" in your samples, the DCA reviewer will reject the campaign for lacking mandatory compliance disclosures.
"[Brand Name]: Hi [First Name], [Insert specific reason for messaging that matches your use case]. Reply STOP to cancel, HELP for info. Msg&Data rates may apply."
Congruency with the Call-to-Action (CTA)
Reviewers do not look at your sample messages in a vacuum; they cross-reference them against your declared "Call-to-Action / Message Flow." The CTA is the section where you explain exactly how consumers opt-in to receive texts.
If your CTA states: "Consumers opt-in by entering their phone number on our website to receive shipping updates," but your sample message reads: "Acme Corp: Flash sale! 50% off all shoes today only. Reply STOP to cancel," your campaign will be rejected for a "Use Case Mismatch." The reviewer will note that the consumer consented to transactional shipping alerts, but the sample message proves you intend to send promotional marketing. Your sample messages must be a logical, direct continuation of the promise made in your opt-in CTA.
Handling URLs and Dynamic Variables
Many modern SMS campaigns rely on sending links. If you intend to send links, you must include them in your sample messages. However, never use public URL shorteners like Bit.ly, TinyURL, or Ow.ly in your samples. Carriers view these as severe security risks used by phishers. If a reviewer sees a public shortener, it is an instant rejection. You must use the full URL associated with your brand (e.g., https://yourbrand.com/sale) or a dedicated, branded shortener (e.g., https://links.yourbrand.com).
Furthermore, DCAs understand that modern messaging is automated. They prefer to see dynamic variables in your samples. Using brackets—such as [Customer Name], [Date], or [Tracking Number]—shows the reviewer that you are utilizing a structured API framework.
By treating your sample messages as a rigorous compliance exercise rather than a casual afterthought, you build immediate trust with the human reviewers at the Direct Connect Aggregators. Flawlessly structured samples containing brand identification, mandatory opt-outs, and perfect congruency with your web forms are the fastest route to getting your 10DLC campaigns approved and active.
Frequently Asked Questions
Do I have to send the exact sample messages I provide to the TCR?
Can I use dynamic variables like [Customer Name] in my sample messages?
Do I need 'Reply STOP to cancel' in every single message I send?
My campaign was rejected for 'Missing Brand Identity.' How do I fix it?
Related Tools & Resources
Sample Message Validator
Paste your sample messages into our tool to verify they contain all mandatory disclosures before submitting to TCR.
Access ResourceRejection Remediation Tool
Was your campaign kicked back? Let our software analyze the rejection code and generate compliant sample messages for your resubmission.
Access ResourceA2P 10DLC Compliance Hub
Browse hundreds of pre-approved sample message templates for Marketing, Customer Care, and 2FA use cases.
Access Resource