A2P 10DLC campaign rejection

30919: your website did not say enough

This one is not about a missing page. It is about a reviewer landing on your site and being unable to answer three questions: who is this business, what do they do, and how does a customer agree to receive texts from them.

What the reviewer could not find

The mechanical causes, which are the most common

A site that is still under construction. A URL with a typo in it. A page behind a login. A staging link that returns 404 from outside your network. In every one of those cases the reviewer sees nothing and rejects, and the rejection reads like a judgement about your business when it was a broken address.

If your opt-in is behind a login

Plenty of real businesses collect consent inside a portal a reviewer cannot reach. That is allowed. Host screenshots of the form and its consent wording at a public URL, and submit that URL as the evidence.

What to change

Put your business name, what you do, and how to contact you somewhere a stranger reads in ten seconds. Describe the messaging program in one paragraph and make it match your campaign description. Link your privacy policy and terms from the page where the form lives. Then check the URL you registered actually loads in a private browser window.

Source: Twilio's own documentation for error 30919, last updated 27 October 2026.

See which of these your own site would fail

We run the same checks a carrier review runs, on the public pages of your website, in about a second. No sign-in and nothing installed.

Scan my website free →

If you would rather hand the list to whoever built your site, that is a perfectly good outcome. If you would rather we built the pages, that is what we do.

We are not lawyers and this is not legal advice. It is a screening tool, the same one we run over our clients' marketing before it ships.