What reviewers check
- Your business name is in the message
- The content matches the use case you registered
- It reads like a real text, not a template or a test
- At least one sample shows how to opt out
- Variables are clearly marked, like [first name] or [date]
- Links use your own domain, not a public shortener
Appointment reminders
Bright Smile Dental: Hi [first name], reminder of your cleaning on [date] at [time]. Reply C to confirm or call (555) 010-0199 to reschedule. Reply STOP to opt out.
Bright Smile Dental: Your appointment is tomorrow at [time]. Please arrive 10 minutes early. Questions? Call (555) 010-0199.
Service and order updates
Fix-It Plumbing: [first name], [tech name] is on the way and should arrive by [time]. Reply STOP to opt out.
Fix-It Plumbing: Your invoice for [job] is ready at [your website]/pay/[invoice id]. Questions? Reply here or call (555) 010-0142.
Marketing
Main Street Pizza: Tuesday deal! 2 large pizzas for [price] all day. Order at [your website]/order. Reply STOP to opt out.
Main Street Pizza: [first name], thanks for being a regular. Take 15% off your next order with code THANKS15. Reply STOP to end.
Marketing samples need a marketing campaign and an opt-in that mentions offers. On a reminders-only campaign, these get you rejected.
Samples that get rejected
- "Hello, this is a test." Not a real message.
- "Hi [name], [message]." A template with nothing in it.
- "Don't miss our sale!" No business name, no opt-out, and it is marketing on what may be a reminders campaign.
- "Click bit.ly/3xYz to confirm." Public shorteners hide the destination and get filtered.
- Samples about products or services your website doesn't mention
Make the whole form tell one story
Reviewers read your samples against everything else you submit. If a sample has a link, answer yes to embedded links. If it has a phone number, answer yes to embedded phone numbers. If you registered for reminders, every sample should be a reminder. The opt-in, the use case, and the samples have to describe the same texts.
Check them before you submit
Clear writes samples that fit your use case and audits them alongside your opt-in and website. Send checks any single message for compliance before it goes out. Either one catches a mismatch before a reviewer does.
Common questions
How many 10DLC sample messages do I need?
Most providers ask for two to five. Write two or three strong ones that cover the different texts you will send instead of padding to five.
Do sample messages need to include STOP?
At least one should, usually the first. Including opt-out language in the first text a new subscriber gets is standard practice anyway.
Can I use placeholders in sample messages?
Yes, for the parts that change, like [first name] or [date]. The rest should be your real wording. A sample that is mostly placeholders reads as generic.
Do I have to send exactly my sample messages?
No. They show the type and tone of what you will send. Your real texts still have to stay inside the registered use case. Sending promotions on a reminders campaign can get you flagged later.