10DLC by provider · Telnyx · Warning
Telnyx 10DLC rejected: Public URL shorteners in messages
Your Telnyx registration came back rejected and it points to public URL shorteners in messages. Telnyx did not make that call. Here is what the reason means and exactly how to fix it.
Telnyx showed your A2P 10DLC campaign as rejected, and the reason maps to "Public URL shorteners in messages". The part that trips people up: Telnyx did not decide this. It submitted your brand and campaign to The Campaign Registry (TCR) and the carriers, they returned the rejection, and Telnyx is relaying it back to you.
That is good news for the fix. Because "Public URL shorteners in messages" is a carrier and TCR requirement rather than a Telnyx rule, the correction is the same no matter which provider you registered through: Shared shorteners (bit.ly, tinyurl) are heavily filtered because they mask the destination.
Where Telnyx shows this rejection
Telnyx surfaces brand and campaign status in the Mission Control portal under its Messaging / 10DLC area, along with the reason returned for a rejected registration. That reason originates with TCR or the carriers.
Telnyx is the messenger, not the decider
Rejections can happen at the brand level or the campaign level, and they mean different things. A brand-level rejection is usually an identity problem such as an EIN and legal-name mismatch. A campaign-level rejection is usually a messaging problem such as opt-in or sample messages. The Telnyx status tells you which layer failed.
The fix
Use your own branded domain or a dedicated (non-shared) short link; avoid public shorteners in sample and production traffic.
Same rejection, different provider?
The reason is identical no matter who you registered through.
Common questions
Did Telnyx reject my 10DLC campaign for public URL shorteners in messages?
No. Telnyx submitted your campaign to The Campaign Registry and the carriers, who returned the rejection. Telnyx relays the reason. You resolve the underlying issue and resubmit through Telnyx. The fix here: Use your own branded domain or a dedicated (non-shared) short link; avoid public shorteners in sample and production traffic.
Why can't I use bit.ly in 10DLC messages?
Public shorteners hide the destination, which is a common spam tactic, so carriers filter them heavily. Links using shared shorteners can get a campaign flagged, rejected, or throttled.
How do I resubmit after a Telnyx rejection?
Correct the issue, then resubmit the campaign for review through Telnyx. Every resubmission is re-reviewed and re-review typically takes one to four weeks, so fix every problem before you resend rather than resubmitting to test it.