SMS registration rejection codes, explained

Plain-English fixes for A2P 10DLC campaign rejections and toll-free verification denials: what the reviewer saw, why it fails, and exactly what to change. Covers Twilio, Telnyx, Bandwidth, HighLevel/LeadConnector and The Campaign Registry's categories.

Changed on September 15, 2026

Twilio replaced about 40 registration codes, and 30493 now covers Terms of Service only. New toll-free requests also need separate Privacy Policy and Terms URLs.

Opt-in, call to action and keywords

Privacy policy and terms

Description, samples and content

Brand, website and fees

Toll-free verification

Specific error codes

Platforms

Not sure which one applies? Paste your campaign text into the free preflight check. It flags the same problems these pages describe, with the codes reviewers use.

Run the preflight check

Frequently asked questions

Who actually rejects A2P 10DLC campaigns?

Not The Campaign Registry. Third-party vetting partners (DCAs) and the carriers review campaigns. Your provider (Twilio, Telnyx, Bandwidth, HighLevel and others) passes their decision on with its own code.

Why do the same problems have different codes?

Each provider wraps rejections in its own numbering: Twilio uses 30xxx codes, Telnyx and Bandwidth show DCA numbers such as 806, Bandwidth and Infobip show Proxy codes such as 3001A, and toll-free reviewers use 1000-1806. These pages group them by the underlying problem.

How current is this?

Every page was checked against the providers' own documentation on 2026-10-03, including Twilio's September 15, 2026 code changes. Each page lists its sources with dates.