A text message is only as trustworthy as the business sending it. When a reviewer opens your site, they look for the basics any customer would want: who you are, what you sell, and how to get in touch. If those are missing, the reviewer has no way to link your messages to a real company.

What does this rejection mean?

It means the reviewer could not find enough identifying details. Twilio error 30919 says a site is rejected when it does not show the business name, contact details, or a description of services. Twilio error 30881 covers a support email that does not fit the brand. CTIA says websites linked in messages should clearly identify the owner and include contact information, such as a postal mailing address.

See the full requirement at business contact info.

Why does it happen?

1. No Contact page. Plivo asks for a Contact Us page, along with About Us, terms, and privacy pages.
2. No business name on the site. Only a logo or a product name appears (Twilio 30919).
3. No description of services. Reviewers cannot compare the site with your campaign (Twilio 30919).
4. Free or mismatched email. A Gmail address, a disposable address, or an email domain that does not line up with the company name or website (Twilio 30881, Plivo).
5. Weak HELP message. Twilio 30890 says the help reply must include your brand name and a phone number or email.
6. No phone number match. Plivo says the site should ideally mention the phone number used in brand registration.

How do I fix it?

1. Create a Contact page and link it in the header or footer.
2. List your business name exactly as registered, plus any DBA.
3. Add a support email on your own domain, like [email protected].
4. Add the phone number you used in brand registration.
5. Add a postal mailing address if you have one you can publish. CTIA recommends contact info such as a postal address for sites linked in messages.
6. Describe your products or services on the homepage.
7. Update your HELP message to include your brand name and a phone or email.
8. Make sure the email in your brand registration matches the one on the site. Twilio notes the same email address can be used for at most 10 TCR registrations.

Your HELP reply is where contact details show up inside the texts themselves. It should name your brand and give a phone number or an email on your own domain, and it helps to remind people how to opt out. The contact details in the reply should match the ones on your website and in your brand record.

Included in your Registration Kit: your HELP and STOP replies written with your brand name and the same contact details shown on your site, plus your business details laid out for the brand form, ready to paste. Build my order →

How do I resubmit?

Edit the rejected campaign rather than deleting it, which is what Twilio advises. If the problem is your brand support email, update the brand details too. Twilio says the vetting fee is charged 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?

Other providers describe this in their own words. See the 10DLC website requirements hub for every page reviewers expect.

Sources

• Twilio Error 30919: Website lacks sufficient business or messaging use case info
• Twilio Error 30881: Invalid brand support email
• Twilio Error 30890: Subscriber help
• Twilio: Collect business information for A2P 10DLC
• Twilio Error 30922: Website does not meet campaign verification requirements
• CTIA Messaging Principles and Best Practices (May 2023)
• The Campaign Registry CSP User Guide (October 2025)
• Plivo: A2P 10DLC registration guidelines
• Vonage: 10DLC Pricing and Fees
• Telnyx: 10DLC Campaign Compliance Requirements
• Bandwidth: 10DLC campaign vetting tips and tricks

To see whether your contact details are easy for a reviewer to find, compare your site with the checklist. Our sites include a Contact page by default; see pricing.