Sample messages are the reviewer's preview of what will land on people's phones. They compare each sample with your chosen use case, your campaign description, and your website. If a "Customer Care" campaign shows sale coupons, or the samples talk about a business the website never mentions, the pieces do not fit and the campaign is rejected.

What does this rejection mean?

It means your samples failed a content check. Twilio error 30893 says samples are missing, unclear, or do not match the use case. Error 30892 covers public URL shorteners or links that are not https. Error 30907 says a website can fail review when it does not match the sample messages.

See campaign use case for how use cases work, and the content pages requirement for what your site should show.

Why does it happen?

1. Wrong use case. Promotional samples in a non-marketing campaign, or the reverse.
2. Placeholder text. "Test message" or "Hello" does not show real content (Twilio 30893).
3. No brand name. Twilio's guide says samples should include it.
4. Public shorteners. TCR does not accept bitly or tinyurl, and Twilio 30892 flags them.
5. Non-https links (Twilio 30892).
6. No opt-out language in any sample (Twilio 30893, Telnyx).
7. Too few samples. Counts differ by provider; see the table below.
8. Mismatch with the website. Services in the texts do not appear on the site (Twilio 30907).

How do I fix it?

1. Confirm your use case fits what you actually send.
2. Write samples that copy your real messages.
3. Start each sample with your brand name.
4. Use [square brackets] for variables like names, dates, and links.
5. Add opt-out instructions that mention STOP to at least one sample.
6. Use full https links on your own domain, or a branded shortener (Vonage allows custom branded ones).
7. Keep each sample between 20 and 1,024 characters (Twilio's guide).
8. Make sure your website describes the same services.

What a failing sample looks like

This is a made-up example of a sample that is likely to be rejected:

Hey! Big savings this week, check it out bit.ly/abc123

Problems: no brand name, a public shortener, no opt-out, and promotional content that may not fit the use case.

A sample that passes does the opposite. It opens with your brand name, reads like a real text you will send, fits the use case you picked, uses [bracketed] fields for names and dates, links to your own https domain, and at least one sample in the set explains how to opt out. Reviewers also check that each sample lines up with your campaign description and your website.

Included in your Registration Kit: 3 to 5 sample messages written for your use case and matched to your website and campaign description, plus the campaign description itself, ready to paste. Build my order →

How do I resubmit?

Twilio says to edit the rejected campaign rather than delete it, and that its vetting fee is assessed once per campaign. Vonage lists $15 per vetting event, Telnyx describes $15 per submission or resubmission, and Bandwidth says a $15 fee applies to rejected campaigns that need resubmission. Twilio says standard campaigns can take up to several weeks.

What error code will I see?

See the 10DLC website requirements hub for everything else.

Sources

• Twilio Error 30893: Sample messages
• Twilio Error 30892: Public URL shorteners or unsecured URLs in sample messages
• Twilio Error 30907: Website URL validation issue
• Twilio: Collect business information for A2P 10DLC
• Twilio Error 30922: Website does not meet campaign verification requirements
• The Campaign Registry CSP User Guide (October 2025)
• Telnyx: How to create a 10DLC campaign
• Telnyx: 10DLC Campaign Compliance Requirements
• Vonage: 10DLC Register a campaign via the dashboard
• Vonage: 10DLC Campaign requirements
• Vonage: 10DLC Pricing and Fees
• Bandwidth: 10DLC campaign vetting tips and tricks
• Telnyx: 10DLC Campaign Compliance Guide

A website that matches your messages makes the whole campaign easier to review. Compare your site with the checklist, or see pricing for a site built for 10DLC.