Website guidance

TCR Error 30919: website evidence gaps.

A source-backed breakdown for agencies whose A2P campaign was rejected because the website did not give reviewers enough business, messaging, or opt-in context.

Last updated: May 27, 2026

What it means

This rejection points to insufficient public website evidence for business identity, messaging purpose, opt-in path, privacy policy, terms, or SMS disclosures.

  • Current A2P Desk status: usually eligible for correction and resubmission.
  • A2P Desk provides preflight workflow and evidence support only. This content is not legal advice and does not guarantee carrier, TCR, Twilio, HighLevel, or provider approval.

Common causes

  • The website is private, under construction, missing, or too thin for reviewers to validate the business.
  • The website does not clearly explain who receives SMS messages and why.
  • The opt-in page, privacy policy, terms page, or mobile opt-in data non-sharing language is missing or hard to find.

What to fix before resubmitting

  • Publish a public page that identifies the business, services, contact path, and SMS program.
  • Add visible opt-in context with message frequency, rates, HELP/STOP, privacy policy, and terms references.
  • Update the privacy policy so mobile opt-in data is not sold or shared for third-party marketing.

How A2P Desk helps

  • Capture website, privacy, terms, and opt-in evidence into the client evidence vault.
  • Run preflight to surface website and policy gaps before pasting fields into HighLevel.
  • Export a submission pack with reviewer notes, source-backed TCR authority, and current evidence references.

Source-backed references

  • twilio: Twilio error 30919 website business and messaging use case info (2026-05-27)
  • highlevel: HighLevel A2P campaign rejection reasons and required fixes (2026-05-27)