Free tool

Check a sender registration before you submit it.

A checklist of the documented reasons a text-message sender registration is rejected: 10DLC campaigns and toll-free verification. Tick what you have. The list beside it shows what to fix.

What happens to what you enter

  • Runs entirely in your browser.
  • What you type or tick is not stored and is not sent to us or to anyone else.
  • Page visits are counted as the privacy policy describes.
  • Close the tab and your answers are gone.

The checklist

Tick what you already have

Five groups. Most documented rejection reasons concern opt-in proof and policy wording, so those groups are the longest.

Tick what is true for this registration

0 of 27 ticked

Business identity
Opt-in proof
Message samples
Privacy policy and terms wording
Website

Nothing ticked yet

Tick each statement that is true for the registration you are about to submit. Whatever is left unticked will be listed here with what to do about it.

A clean result here does not guarantee approval by a carrier or a registry, and it does not mean a business complies with any law or rule. Someone else decides that.

The requirement

Why registrations are rejected

Business text messages sent from ordinary ten-digit numbers have to be registered. Twilio says unregistered 10DLC messages to US numbers have been fully blocked since 1 September 2023. Toll-free numbers go through a separate verification, and providers report that it now asks for much of the same information.

These are carrier and registry requirements set by contract. They are not a statute. The providers that submit registrations publish the reasons a campaign is rejected, and most of them concern proof of opt-in and the wording of the privacy policy and terms: a missing policy, a policy that allows mobile data to be shared with third parties, a consent box that is checked in advance, an opt-in that cannot be declined, a vague campaign description, and samples that do not match the use case.

No authoritative rejection rate is published. Twilio moved to new, more specific rejection codes for both 10DLC and toll-free verification on 15 September 2026, so the exact code you see depends on your provider.

Carriers and registries decide. Passing this list does not guarantee approval, and an approved registration does not by itself mean messages will be delivered.

Sources

  1. Vetting rejection reasons list (VoIP docs)
  2. Bandwidth: campaign vetting tips
  3. Twilio error 30925
  4. Twilio error 30931
  5. Twilio: unregistered 10DLC shutdown
  6. Twilio: new rejection codes
  7. Telnyx: toll-free verification
  8. Bandwidth: toll-free registration number

Reviewed 12 November 2026

Every item comes from a rejection reason published by a messaging provider or from a provider’s help page listing registry vetting codes. These are provider documents, not carrier rule text, and providers word the reasons differently.

The list is not complete and it changes. Check your own provider’s current rejection codes before you rely on it.

Consentra is software. Nothing on this site is legal advice, and using Consentra does not by itself make a business compliant with any law or carrier rule. Whether a rule applies to your business is a question for your counsel.

Related

Where to go next

Module

Sender Check

Text-message sender registration and opt-in proof

Keep the record a reviewer asks for.

Consentra Sender Check runs this kind of pre-check against a registration draft and stores a consent record per subscriber.