How to Write a Strong 10DLC Use Case A strong 10DLC use case clearly explains who you are, who you’re messaging, how they opted in, what type of messages you’ll send, and how often you’ll send them — with realistic examples that match your actual traffic. Most 10DLC rejections happen because use cases are vague, inconsistent, or misaligned with live behavior. If your use case is weak, approval gets delayed. If your use case is misleading, filtering happens later. Here’s how to write it correctly. Why the 10DLC Use Case Matters When you register through The Campaign Registry, carriers evaluate: Your business identity Your campaign category Your opt-in method Your message examples Your expected volume and frequency Your use case description becomes the baseline carriers use to compare live traffic. If your real messages don’t match what you declared, filtering risk increases. The 5 Components of a Strong 10DLC Use Case A strong use case answers five operational questions. 1. Who Is Sending the Messages? Start with a clear description of your business. Bad example: We send updates to customers. Strong example: ABC Logistics LLC sends shipping notifications and delivery updates to customers who place orders on our website. Be specific about: Business type Services provided Relationship to recipients Carriers want clarity, not marketing language. 2. Who Is Receiving the Messages? Define your audience precisely. Examples: Customers who completed checkout Users who signed up via website form Subscribers who texted a keyword Account holders who requested alerts Avoid: “Leads” “Prospects” “Partner databases” “Purchased lists” Lead generation without clear consent is one of the fastest rejection triggers. Under standards from CTIA, explicit consent must be obtained. 3. How Do Users Opt In? This is where many use cases fail. You must clearly explain: Where opt-in occurs What language is shown How consent is captured Whether frequency is disclosed Strong example: Users opt in via a website checkout page by checking an unchecked box labeled: “I agree to receive SMS order updates and promotional offers (up to 4 msgs/month). Msg & data rates may apply. Reply STOP to cancel.” Weak example: Users opt in on our website. Carriers need detail. 4. What Type of Messages Will Be Sent? Choose the correct campaign category: Marketing Informational Customer care Mixed use Do not attempt to disguise promotional traffic as informational. If you send discounts, sales, or offers — it’s marketing. Misclassification often leads to rejection or filtering after approval. 5. What Is the Expected Frequency? You must disclose approximate frequency. Examples: 2–4 messages per month 1–2 weekly updates Real-time alerts triggered by user activity Avoid unrealistic claims like: Messages sent occasionally. Frequency clarity reduces complaint risk modeling. Writing Strong Message Examples Your sample messages must: Reflect real traffic Include opt-out language (if recurring) Match your declared campaign type Avoid exaggerated marketing copy Example (Marketing Use Case) ABC Fitness: Get 20% off all memberships this week. Offer ends Sunday. Reply STOP to opt out. Example (Informational Use Case) ABC Bank: Your account ending in 1234 has a deposit of $250. Reply STOP to opt out of alerts. Samples must align with your declared intent. If live traffic differs later, filtering risk increases. Common Mistakes That Cause Rejection Vague opt-in explanation No frequency disclosure Promotional language under informational category Missing opt-out language in examples Using purchased or affiliate-generated leads Inconsistent business branding Overly broad campaign descriptions Rejections usually trace back to one of these. High-Risk Industry Considerations If you operate in: Lending Insurance Financial services Lead generation Affiliate marketing Carriers apply additional scrutiny under guidance enforced by the Federal Communications Commission. Be especially detailed about: Consent capture process Data ownership Frequency control Opt-out handling Vague descriptions in high-risk industries almost always delay approval. A Simple Strong 10DLC Use Case Template Here’s a clean structure you can follow: [Business Name] sends [type of messages] to customers who [how they opt in]. Users opt in via [specific method] where they see the following disclosure: “[insert opt-in language].” Messages include [examples: order updates, promotions, reminders]. Message frequency is approximately [X per month/week]. All messages include STOP instructions and opt-outs are processed immediately. This structure covers the essential compliance elements. Final Takeaway A strong 10DLC use case is: Clear Specific Transparent Realistic Aligned with actual traffic Carriers are not looking for marketing copy. They are looking for behavioral predictability. If your use case accurately describes what you will send — and you follow it operationally — approval is smoother and filtering risk is lower. 10DLC is a reputation framework. Your use case is the foundation of that reputation.
