- July 26,2026
- 1 month ago
Yes. Message samples matter for 10DLC because they show reviewers what a registered campaign is actually expected to send.
A campaign description explains the messaging program in words. Samples make that description concrete.
If a business registers a campaign for appointment reminders but submits samples promoting discounts, the reviewer now sees two different purposes. If the campaign describes customer support but the samples look like lead-generation messages, the same problem appears.
This is why message samples should not be treated as filler added at the end of registration.
For businesses using TextTorrent’s guided A2P 10DLC setup, samples should be prepared alongside the use case, campaign description, and opt-in process. Teams planning bulk SMS campaigns should use examples that realistically represent the messages they expect to send after approval.
This becomes particularly important in compliance-sensitive industries. An insurance messaging workflow sending policy or appointment updates should not submit samples that make the campaign appear to be unrelated promotional outreach. Similarly, an MCA messaging program should make sure its message examples accurately reflect the customer interaction and campaign purpose being registered.
Businesses unfamiliar with the process should first understand why businesses use 10DLC for application-to-person messaging.
The practical rule is:
Your samples should look like realistic examples of the traffic the registered campaign will actually send.
Reviewers need to understand what a campaign will look like in production.
Consider this campaign description:
We send appointment confirmations and reminders to customers who schedule appointments with our business.
Now consider this sample:
Great news! You may qualify for our newest offer. Apply today at [URL]. Reply STOP to opt out.
The sample introduces a completely different messaging purpose.
Now compare it with:
Northstar Dental: Hi [First Name], your appointment is scheduled for [Date] at [Time]. Call [Phone] to reschedule. Reply STOP to opt out.
The second message supports the description.
That is the core function of samples. They help demonstrate whether the campaign being described and the messages being proposed actually belong together.
A sample should never be reviewed by itself.
Think about the registration as a chain:
Use Case → Campaign Description → Opt-In Process → Message Samples → Production Traffic
Each part should support the next.
Suppose an insurance business says consumers opt in to receive policy servicing and appointment-related communication.
Its sample says:
Northstar Insurance: Your appointment with [Agent Name] is confirmed for [Date] at [Time]. Reply STOP to opt out.
That is coherent.
Now suppose the sample says:
Northstar Insurance: Get a new policy today and save 20%. Apply at [URL].
Even if the business legitimately sells insurance, that message represents a different purpose from the one described.
The useful question is not:
"Could our company ever send this message?"
Ask:
"Does this message belong to the campaign we are registering?"
That distinction catches many avoidable problems.
A good sample should make the expected traffic understandable without requiring someone to guess what the sender meant.
Recipients should be able to understand who is contacting them.
Weak:
Your appointment is tomorrow at 2 PM.
Better:
Northstar Dental: Your appointment is tomorrow at 2 PM. Reply STOP to opt out.
The first message provides context only if the recipient already recognizes the number.
The second identifies the business.
Do not assume that the sending number alone makes the sender obvious.
A sample should reveal why the recipient is receiving the message.
Weak:
Hi [First Name], we have an update for you.
What update?
Why is the business contacting the person?
A stronger example is:
Northstar Auto: Hi [First Name], your service appointment is confirmed for [Date] at [Time]. Call [Phone] if you need to reschedule. Reply STOP to opt out.
The operational purpose is immediately understandable.
If the campaign is promotional, the sample should look promotional.
If it sends order notifications, show an order notification.
Do not deliberately make samples vague because you think vague messages are safer.
Ambiguity can make the campaign harder to understand.
Real business messages frequently contain dynamic fields.
Examples include:
First name
Appointment date
Appointment time
Order number
Account reference
Agent name
Tracking information
Represent those fields naturally.
For example:
Acme Supply: Hi [First Name], order #[Order Number] has shipped and is expected by [Date]. Track it at [URL]. Reply STOP to opt out.
This shows the structure of the message while making it clear which information changes for each recipient.
TextTorrent’s message templates and campaign tools can then help teams maintain consistent message structures when campaigns move from registration into production.
Samples should also reflect the opt-out experience used by the messaging program.
For example:
Reply STOP to opt out.
The important operational point is that this language cannot exist only in the sample.
If recipients are told that STOP ends messages, production workflows need to honor that preference.
TextTorrent’s blacklist and opt-out management can help teams keep suppressed contacts out of future campaigns, including situations where old contact lists are imported again.
Registration copy and production behavior should agree.
If production messages regularly contain URLs or phone numbers, samples should realistically represent that behavior.
For example:
Northstar Dental: Your appointment is confirmed for [Date]. Manage your appointment at [URL] or call [Phone]. Reply STOP to opt out.
Do not submit:
Your appointment is confirmed.
if the real production template routinely contains a portal link, telephone number, and additional instructions.
The goal is to show representative traffic, not a sanitized version that will look different once sending begins.
Use legitimate domains associated with the real business rather than unrelated or unexplained links.
Most sample problems are not sophisticated. They come from teams treating samples as a minor registration field.
Avoid examples such as:
Test message.
Sample customer message.
This is our promotional SMS.
These describe a message rather than showing one.
Write the sample as if a real customer were receiving it tomorrow.
Avoid:
Your application has been updated.
A clearer version is:
Northstar Funding: Hi [First Name], your application #[Application ID] has been updated. Reply here if you have questions. Reply STOP to opt out.
The recipient can identify both the sender and the context.
Suppose the description says:
Delivery and order-status notifications.
But a sample says:
Flash sale! Buy today and save 30%.
The sample does not merely need better wording.
It represents another messaging purpose.
Fix the mismatch rather than rewriting the promotional message to sound transactional.
Avoid:
This is where the appointment reminder goes.
or:
Example financing message.
The registration needs representative message content.
Show what customers are likely to receive.
Usually, samples should demonstrate meaningful variations in the traffic when the campaign genuinely sends different types of messages.
Consider an appointment workflow.
One sample could show confirmation:
Northstar Dental: Your appointment is confirmed for [Date] at [Time]. Reply STOP to opt out.
Another could show a reminder:
Northstar Dental: Reminder—your appointment is tomorrow at [Time]. Call [Phone] to reschedule. Reply STOP to opt out.
Another could show a schedule change:
Northstar Dental: Your appointment has been moved to [Date] at [Time]. Reply here with questions. Reply STOP to opt out.
All three serve the same overall purpose while demonstrating different operational messages.
Do not create artificial variation merely to make the registration look detailed.
Show the actual variations the campaign is expected to send.
What About Mixed Messaging?
Mixed messaging needs additional care because one business can legitimately have several reasons to contact the same customer.
Imagine an e-commerce business.
Order notification:
Acme Home: Order #[Order Number] has shipped. Track it at [URL]. Reply STOP to opt out.
Customer support:
Acme Home Support: We've updated support request #[Ticket Number]. Reply here if you still need help.
Promotion:
Acme Home: Save 20% on selected products through Sunday. Shop at [URL]. Reply STOP to opt out.
These messages come from the same company, but they do not all serve the same purpose.
Do not hide promotional traffic inside transactional samples because you may want to market to those customers later.
The registered campaign, messaging flow, and samples should accurately represent the intended program.
This is one of the most important checks before submission.
Suppose a customer sees:
Receive text updates about your upcoming appointments.
But the submitted sample says:
Save 25% on our newest service. Book today.
The problem is bigger than the sample.
The consumer expectation created during signup does not clearly support the message being demonstrated.
Use this test:
If a consumer saw the opt-in disclosure and then immediately received this sample message, would the message make sense?
If the answer is uncertain, investigate the campaign before submitting.
Do not solve a consent mismatch by simply making the sample less explicit.
Message Samples Should Match Production Traffic After Approval
Samples are representative examples. That does not mean every production message has to be character-for-character identical.
Variables will change.
Businesses may use several templates within the same messaging purpose.
For example:
Acme Dental: Your appointment is confirmed for [Date].
and:
Acme Dental: Reminder—your appointment is tomorrow at [Time].
can reasonably belong to the same appointment workflow.
The important issue is purpose.
If a campaign registered around appointment notifications later starts sending unrelated promotional offers, the problem is not that a few words changed.
The traffic changed.
When using TextTorrent’s campaign automation tools, teams should review new automated messages against the registered purpose rather than assuming every message added to the workflow automatically belongs there.
Two-Way Conversations Can Continue the Original Context
Some campaign messages naturally generate replies.
For example:
Can I move my appointment to Friday?
or:
Where is my order?
TextTorrent’s two-way texting tools can help teams continue those conversations directly.
But a reply does not erase the original messaging context.
An appointment reminder can naturally become a scheduling conversation.
An order notification can become a delivery-support conversation.
That does not automatically justify moving the recipient into an unrelated promotional sequence.
The same purpose discipline used when preparing message samples should continue after launch.
Do Good Message Samples Guarantee Approval?
No.
Message samples are only one part of the campaign.
A campaign can have excellent samples and still encounter problems because:
Business information cannot be verified
The website does not support the registration
The opt-in process is unclear
The campaign description conflicts with the workflow
Required policy information is incomplete
The underlying messaging purpose creates another issue
That is why teams should not "fix the samples" without checking the rest of the submission.
A strong sample cannot repair a fundamentally inconsistent campaign.
Do Approved Samples Guarantee Deliverability?
No.
10DLC registration and live deliverability are related but separate problems.
Samples show what the campaign says it intends to send.
Production traffic shows what the business actually sends.
An approved campaign can still encounter filtering if live messages introduce problems such as:
Traffic outside the registered purpose
Unrelated or suspicious URLs
Poor recipient targeting
Complaint activity
Unexpected content changes
Other carrier risk signals
Teams scaling campaigns should therefore combine accurate registration with practical carrier-filtering controls.
Approval is not a permanent exemption from carrier filtering.
A Pre-Submission Message Sample Checklist
Before submitting a 10DLC campaign, check every sample against the following:
Does it clearly identify the sender?
Does it represent a message we genuinely expect to send?
Does it match the selected campaign purpose?
Does it match the campaign description?
Does it make sense based on the opt-in process?
Would the recipient understand why they received it?
Are variable fields represented appropriately?
Are links shown when the real traffic will contain links?
Are phone numbers shown where relevant?
Is opt-out language represented appropriately?
Do multiple samples show meaningful variations where needed?
Does every sample belong to the same registered program?
Would the samples still make sense to someone who knows nothing about the business?
If several answers require explanations such as "the reviewer will probably understand what we mean," revise the samples.
The reviewer should not have to infer the campaign.
What If a Campaign Is Rejected Because of Its Samples?
Do not immediately rewrite only the rejected message.
Compare the entire chain:
Use Case → Campaign Description → Opt-In → Message Samples
Then identify where the story changes.
If the description is accurate but the samples are wrong, correct the samples.
If the samples accurately represent the messages the business intends to send but contradict the description, the description or campaign structure may need correction.
If the samples reveal promotional traffic that the consent process does not support, changing a few words in the samples does not resolve the underlying issue.
Use this troubleshooting sequence:
Rejection Reason → Intended Traffic → Consent → Description → Samples → Correction
Then review the complete submission before resubmitting.
The goal is not to make the examples look safer.
The goal is to make them accurately represent the same messaging program described everywhere else.
Final Takeaway
Message samples matter for 10DLC because they turn an abstract campaign description into concrete examples of expected traffic.
Good samples identify the sender.
They show the real messaging purpose.
They represent variables, links, and phone numbers where appropriate.
They make sense alongside the opt-in process.
And most importantly, they agree with the campaign the business is registering.
Before submitting, ask one final question:
If these samples were the only messages a reviewer saw, would they correctly understand what our campaign does—and would that understanding match our use case, description, opt-in process, and actual sending plan?
If the answer is yes, the samples are doing their job.
