Error code

30920: Campaign rejected: Website is only a form; insufficient business context

Eligible for resubmission. Stated by: GHL 155000007572.

What this error means

You submitted a landing page or lead-capture form instead of a business website.

Causes, most likely first

The URL points to a landing page or standalone form and doesn't identify the business.
The page doesn't provide enough to validate the brand and messaging program.
If used for opt-in, the flow or required disclosures are missing or not public.

Fields Twilio names for this error

Twilio’s page for this error names these submission fields:

message_flow
opt_in_keywords
opt_in_message

Twilio's own pass and fail example

Twilio publishes a worked example on this error page. Quoted from Twilio's documentation:

Would be rejected

A URL that points to a standalone lead-capture form with no business name, navigation, or description of services.

Twilio's stated reason: "Reviewers cannot validate the brand or messaging program from a form alone."

Would pass review

Submit your main business website (www.acmesandwich.com) that includes your business name, description of services, and navigation to a clearly labeled opt-in page with the required disclosures.

Twilio's stated reason: "Passes because the website provides enough context for reviewers to validate the brand and messaging use case."

How this differs from 30891 and 30922

Three separate codes concern the website. They are not interchangeable.

30891: The URL is invalid, or the site does not load, or the opt-in flow is not on the site at all.
30920: The site loads. The objection is to the type of page: a landing page or standalone form that does not identify the business.
30922: The superset. Either the site does not load, or it loads but does not match the brand, sender, or use case in your registration.

Twilio states no precedence between these three. Its documentation does not say which code a reviewer issues when more than one applies, so do not read the code you received as ruling the others out.

How to fix it

If your numbers are managed by a platform

If your numbers sit inside a reseller platform, for example LeadConnector numbers inside GoHighLevel, you do not have access to the Twilio Console, and the interface shows the rejection without the code. Ask that platform's support team for the Twilio rejection error code, in writing, before you change anything. You can also read it yourself from your browser, which is faster: see how to get the code.

The substance of the fix is yours to make: the business details, the website, and the opt-in flow described in the Twilio path all belong to you, not to the platform. Make those changes first, confirm they are live, then ask support to resubmit. A resubmission filed before the underlying facts change will fail again on the same reason.

If you own the Twilio account

Submit your main business website instead of a campaign-specific landing page or lead capture form. Add clear business information identifying the brand and explaining how end users consent. If the site is used for opt-in, make the flow publicly accessible with privacy policy and terms links. If relevant pages are gated or not yet public, provide a public URL with hosted screenshots. Make description and samples match the business and use case on the site.

Timing and resubmission

Edit and resubmit with a proper business website.

Twilio publishes an indicative review timeline for campaigns: Sole Proprietor campaigns are typically approved or rejected within hours to days, and Standard campaigns go through several layers of vetting and can take up to several weeks. Twilio also states that the vetting fee is assessed only once per campaign, so editing and resubmitting the same campaign does not incur a new fee, while deleting and recreating it does.

Two ways forward

Have it handled for you

A2P registration is handled for you on Growth at $597/mo and on Scale at $1,197/mo. Registration, resubmissions, and the compliance work behind them are included.

See Growth and Scale

Fix it yourself

Send your email and we will send the fix playbook for registration rejections.

Verified against Twilio documentation on 2026-08-10.