Website rejected for A2P or toll-free: what reviewers need to see
Short answer
Reviewers open your website to confirm the business is real and matches the registration. It must load publicly over HTTPS, show the same business name, what you sell, and contact details, and have privacy and terms pages. A bare landing page, a “coming soon” page or a login wall gets rejected.
What you'll see
| Where | Code | Wording |
|---|---|---|
| Twilio (10DLC) | 30891 | “Campaign vetting rejection - Invalid Website URL” |
| Twilio (10DLC) | 30907 | “Campaign vetting rejection - Website URL Validation Issue” |
| Twilio (10DLC) | 30919 | “Campaign rejected: Website lacks sufficient business or messaging use case info” |
| Twilio (10DLC) | 30920 / 30921 / 30922 | “Website is only a form; insufficient business context” / “Website requires authentication and cannot be reviewed” / “Website does not meet campaign verification requirements” |
| Twilio (toll-free) | 30473 / 30489 / 30526 | “Cannot validate business website URL” / “Website must be established and active” / “High-risk domain issues” |
| Telnyx, Bandwidth | 804 / 807 | Need a working website (or full CTA if opt-in is off-site) / inauthentic website |
| Toll-free (Bandwidth, Sinch) | 1201-1205 | “Website Must Be Established and Active”; “Website Is Password Protected or Requires Login”; “Business website URL must display branding” |
Text in curly quotes is the provider's wording; the rest is our summary.
Why it happens
- The site is down, has an expired certificate, redirects elsewhere, or is under construction.
- Only a lead-capture page or form, with no information about the business (30920).
- The site shows a different business name than the registration, or the agency's site was submitted.
- No contact details, no description of services, no privacy policy or terms.
- Template real estate or insurance sites with no business-specific details (Telnyx 807).
- A newly registered domain with no history (Twilio 30526 is not eligible for resubmission with the same domain).
How to fix it
- Submit your main business website on its own domain, over HTTPS, loading without a login.
- Show the business name as registered (or the DBA, with the legal name in the footer), what you offer, a physical address or service area, a phone number and an email on your domain.
- Add Privacy Policy and Terms pages with SMS sections, linked from every page's footer.
- Put your SMS opt-in on the site, or describe in the message flow where it happens and link a screenshot.
- Remove anything that suggests lead selling, CBD or other prohibited content. Reviewers read the whole site.
- If the site isn't live yet, say so in the description and provide public screenshots, but expect a slower review. A live site is far more reliable.
Small businesses without a website can sometimes use a social page or Google Business Profile for toll-free verification. Twilio's guide accepts them only if they are public and active: Newly created, inactive, or 'ghost' pages ... are not acceptable.
For 10DLC, a real website is the norm.
Check before you resubmit. Every rejection costs days, and often another $15 vetting fee. Paste your description, message flow, samples and policy text into the free preflight check, or generate a consistent set with the campaign builder.
Frequently asked questions
Can I use a free website builder subdomain?
It may work if the site is complete and matches the business, but reviewers prefer a custom domain, and Vonage asks for one. A domain whose email matches the brand contact email helps brand verification too.
Does the website need to mention text messages?
Twilio's 30919 asks for enough information to validate the messaging use case, and HighLevel suggests mentioning the SMS program. A visible opt-in form or a short 'Text updates' section is the easiest way to show it.
Can I use a subdomain for the opt-in form?
HighLevel says subdomains like form.yoursite.com are fine if the brand match and the path from the main site are clear. Otherwise they can look like a compliance front and get rejected.
Sources
- Twilio error 30919 (accessed 2026-10-03)
- Twilio error 30920 (accessed 2026-10-03)
- Twilio error 30921 (accessed 2026-10-03)
- Twilio error 30922 (accessed 2026-10-03)
- Twilio error 30891 (accessed 2026-10-03)
- Twilio: Toll-Free Verification Onboarding Guide (updated 2026-09-24)
- Bandwidth: DCA2 vetting rejection reasons (2026-03-17)
- Telnyx: 10DLC carrier error codes explained (accessed 2026-10-03)
- Bandwidth: Toll-free verification rejection reasons (modified 2026-09-15)
- LeadConnector: Website compliance guide (modified 2026-08-31)
- HighLevel: How to get your phone number A2P approved in 2026 (modified 2026-07-30)
- Vonage: 10DLC campaign requirements (page dated 2025-03-17)
Rules change often and providers sometimes disagree; where they do, this page says so. This is general information, not legal advice, and no one can guarantee approval. See the disclaimer.
Related problems
- Twilio 30795, 30799, 30796, 30894, 30918, 30898, 30971 · DCA 603, 710, 711, 713 · TCR BRAND_INCONSISTENCIESBrand registration failed: EIN and legal name mismatch (Twilio 30795)
- Twilio 30908, 30932, 30536, 30477, 30519, 30550 · DCA 805, 851, 852 · TF 1207, 1501-1503Privacy policy rejections: the SMS clause carriers require
- MESSAGE_FLOW · Twilio 30909, 30896, 30917, 30924 · DCA 806MESSAGE_FLOW rejection: fix an opt-in the reviewer can't verify
- Twilio 30951, 30932, 30468, 30916 · DCA 708 · Proxy 7002Rejected for lead generation or affiliate marketing (Twilio 30951, DCA 708)
The Approval Kit adds industry template packs, opt-in and policy page templates, and an agency checklist.