Decode a 10DLC rejection · Critical
Your rejection said something like this
“Sample messages are not realistic or appear to be placeholders”
A rejection like this means your samples read like tests or templates ('Hello', 'This is a test') instead of real messages. Reviewers judge your traffic by the samples, so vague ones fail.
What this maps to
A rejection worded like that is the known 10DLC reason Sample messages are placeholders or too generic. Samples like 'Hello, this is a test' or vague templates get rejected. Samples must reflect real traffic and match the use case.
The fix
Provide 2-3 realistic messages that match the declared use case, include the brand name, and show any {variables} you actually use.
Other ways this rejection is worded
Providers, TCR and the carriers phrase the same reason differently. If yours read more like one of these, it still maps to Sample messages are placeholders or too generic:
- “Sample messages are too generic”
- “Samples do not reflect actual message traffic”
- “Sample content is insufficient”
Common questions
What does the 10DLC rejection "Sample messages are not realistic or appear to be placeholders" mean?
A rejection like this means your samples read like tests or templates ('Hello', 'This is a test') instead of real messages. Reviewers judge your traffic by the samples, so vague ones fail. It maps to the known rejection reason "Sample messages are placeholders or too generic". The fix: Provide 2-3 realistic messages that match the declared use case, include the brand name, and show any {variables} you actually use.
How many sample messages do I need for 10DLC?
Two to three realistic samples is the norm. They should reflect your actual traffic, name your brand, match your declared use case, and include at least one message with opt-out language.