Skip to contentSkip to navigationSkip to topbar
Page toolsOn this pageProducts used
Looking for more inspiration?Visit the
Error
Application error

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

Twilio Messaging DocumentationMessaging
Twilio Phone Numbers DocumentationPhone Numbers

Description

description page anchor

Your A2P 10DLC campaign registration was rejected because the website URL in your submission does not provide enough public business context for review. When you use a website in campaign registration, submit a real, functional business website and provide a verifiable opt-in flow with publicly accessible privacy policy and terms information when required.

Possible causes

possible-causes page anchor
  • The submitted URL points to a landing page or standalone form and does not clearly identify the business behind the campaign.
  • The page does not provide enough information to validate the brand and messaging program in the registration.
  • If you use the website for opt-in, the opt-in flow or required disclosures are missing or not publicly accessible.
  • Submit your main business website instead of a campaign-specific landing page or lead capture form.
  • Add clear business information that identifies the brand behind the campaign and explains how end users consent to receive messages.
  • If the website is used for opt-in, make sure the opt-in flow is publicly accessible and include links to your privacy policy and terms of service.
  • If the relevant pages are behind a login or are not yet public, provide a publicly accessible URL with hosted screenshots of the opt-in flow and required disclosures.
  • Make sure your campaign description and sample messages match the business and use case shown on the website.

Pre-submission checklist

pre-submission-checklist page anchor

Run through this list before submitting or resubmitting your campaign:

  • message_flow names every opt-in method used for this campaign (website, keyword, paper form, verbal, QR code, or other mechanism).
  • message_flow includes a link to your privacy policy and a link to your terms and conditions.
  • Your privacy policy states that mobile numbers are not shared with third parties, includes message frequency, and includes a "message and data rates may apply" disclosure.
  • If opt-in happens on a website, the URL is publicly accessible. If it is not public, you have provided a URL with hosted screenshots of the full consent flow.
  • If end users opt in by texting a keyword, opt_in_keywords and opt_in_message are populated. The opt_in_message includes the brand name, confirmation of enrollment, message frequency, and opt-out instructions.
  • If the campaign uses multiple opt-in paths, all paths are described in the same message_flow field.
  • Sample messages match the declared use case, identify the brand by name, and include opt-out language.
  • The submitted URL is your main business website, not a standalone form or landing page.
  • The website clearly identifies the brand behind the campaign and explains how end users consent to receive messages.

URL is a form-only page with no business context

url-is-a-form-only-page-with-no-business-context page anchor
(warning)

Warning

The following submission would be rejected:

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

Reviewers cannot validate the brand or messaging program from a form alone.

(information)

Info

The following submission 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.

Passes because the website provides enough context for reviewers to validate the brand and messaging use case.