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

30919: Campaign rejected: Website lacks sufficient business or messaging use case info

Twilio Messaging DocumentationMessaging
Twilio Phone Numbers DocumentationPhone Numbers

Description

description page anchor

Your A2P 10DLC Campaign registration was rejected because the website URL you submitted does not give reviewers enough information to validate your business and messaging use case. When you use a website to support registration or collect opt-in, make sure it is publicly accessible and clearly shows who you are, what your business does, and how customers consent to receive messages.

Possible causes

possible-causes page anchor
  • The website is empty, under development, private, password-protected, misspelled, or otherwise inaccessible to reviewers.
  • The website does not clearly identify the business, such as the business name, contact details, or a description of the services you provide.
  • The website does not explain the messaging program, including who receives messages and why messages are sent.
  • The website-based opt-in flow is incomplete or unclear. Reviewers cannot verify how end users consent to receive messages.
  • Required compliance disclosures are missing from the opt-in experience or linked policies, such as message frequency for recurring programs, "message and data rates may apply," opt-out instructions, privacy policy details, or terms and conditions.
  • The privacy policy does not clearly state that mobile opt-in data will not be shared or sold to third parties or lead generators.
  • Update the website so it clearly shows your business name, contact information, and a clear description of your products or services.
  • Make the messaging use case explicit. Explain what messages you send, who receives them, and how customers opt in. Align this with the Campaign description you submit.
  • If customers opt in on your website, include a publicly accessible link to the opt-in page, a privacy policy link, and terms and conditions.
  • Add the required opt-in disclosures to the call to action. Include the program or brand name, message frequency for recurring programs, "message and data rates may apply," and opt-out instructions such as replying STOP.
  • Update the privacy policy so it is easy to find and states that mobile opt-in data will not be shared with third parties or affiliates for marketing or promotional purposes.
  • If the relevant opt-in flow or disclosures are not publicly accessible at the main website URL, provide a URL with hosted screenshots of the relevant pages.
  • Correct any broken or misspelled URL. Remove login requirements or other access restrictions before you resubmit the Campaign.
  • If your main website is unavailable or still under construction, provide a publicly available business page that reviewers can use to validate your business presence.

Edit the rejected campaign rather than deleting and recreating it. Resubmitting triggers a fresh review by The Campaign Registry (TCR).

  • Vetting fee: A vetting fee is assessed only once per campaign. Resubmitting the same campaign does not incur a new fee.
  • Timeline: Sole Proprietor campaigns are typically approved or rejected within hours to days. Standard campaigns go through several layers of vetting and can take up to several weeks.
  • Check status: Monitor your campaign status in Console > Messaging > Regulatory Compliance > Campaigns, or fetch the UsAppToPerson resource and check the campaign_status field.

For detailed resubmission steps, see Troubleshooting and rectifying A2P Campaigns.

Additional resources

additional-resources page anchor