30920: Campaign rejected: Website is only a form; insufficient business context
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.
- 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.
Before you submit or resubmit, confirm your website meets all of these requirements:
- The home page clearly states your business name and what your company does.
- A dedicated About or Contact page provides a phone number, email address, or physical address.
- The website is publicly reachable without a login, VPN, or IP allowlist.
- If you collect opt-in on the site, the opt-in page is linked from the main navigation or footer and loads without authentication.
- A privacy policy page is linked from the opt-in page or site footer and explicitly states that mobile opt-in data will not be shared with or sold to third parties.
- A terms and conditions page is linked from the opt-in page or site footer.
- The business name on the website matches the Brand name in your A2P 10DLC registration.
- The messaging use case described on the site is consistent with the
message_flowand campaign description you submitted.
Warning
The following website would be rejected:
A URL that loads a standalone lead-capture form with fields for name, email, and phone number — but no company name, no description of services, and no navigation to other pages.
Fails because it does not identify the business behind the campaign. A form alone does not give reviewers enough context to validate the Brand or the messaging program.
Info
The following website would pass review:
www.acmesandwich.com — Homepage identifies the business ("Acme Sandwich Company — fresh lunch delivery in Austin, TX"), links to an About page with a phone number and email, and includes a footer with Privacy Policy and Terms of Service links. The opt-in form lives on a dedicated /sms-signup page that explains the SMS alerts program.
Passes because the site provides business context beyond the form itself, allowing reviewers to verify the Brand and understand the messaging use case.
Edit the rejected campaign rather than deleting and recreating it. A vetting fee is assessed only once per campaign, so resubmitting the same campaign avoids a new fee.
- Console: go to Messaging > Regulatory Compliance > Campaigns, click the failed campaign, then click Edit Campaign to correct the fields and resubmit.
- API: update the campaign resource with corrected field values. See Troubleshooting and rectifying A2P Campaigns for detailed instructions.