Bandwidth 10DLC rejected? Here's how to fix it
A rejection in the Bandwidth Dashboard is a fixable 10DLC issue relayed from the registry and carriers, not a call Bandwidth made. Here is how to resolve it.
Bandwidth submits your 10DLC brand and campaign to The Campaign Registry (TCR) and the carriers. A rejection shown in the Bandwidth Dashboard is the carriers' or TCR's decision passed back to you. Bandwidth is the messenger, not the decider.
The fix does not depend on the fact that you are on Bandwidth. Match the rejection to the known reason behind it, correct that, and resubmit. The reason is universal even though the dashboard is Bandwidth's.
Where Bandwidth shows the rejection
Bandwidth shows brand and campaign registration status in its Dashboard (and via the Dashboard API), including the reason for a rejected registration. That reason comes from TCR or the carriers.
Bandwidth is the messenger, not the decider
As a direct carrier-connectivity provider, Bandwidth passes registry and carrier decisions straight through. Treat the rejection text as the carriers' words: it maps to one of the known 10DLC rejection reasons, and that is what you fix before resubmitting.
What the reason actually means
Whatever Bandwidth showed you maps to one of the known 10DLC rejection reasons. Pick the one that matches for a Bandwidth-specific walkthrough of that rejection and its fix:
- Bandwidth rejected: Opt-in / consent not described →
- Bandwidth rejected: Opt-in language does not match the use case →
- Bandwidth rejected: Sample messages are placeholders or too generic →
- Bandwidth rejected: Sample messages missing opt-out language →
- Bandwidth rejected: HELP response not provided or non-compliant →
- Bandwidth rejected: STOP response not provided or non-compliant →
- Bandwidth rejected: Privacy policy missing or does not mention SMS →
- Bandwidth rejected: Website missing, dead, or under construction →
- Bandwidth rejected: Legal business name / EIN mismatch →
- Bandwidth rejected: Sole proprietor treated as a standard brand →
- Bandwidth rejected: Prohibited or restricted content (SHAFT / high-risk) →
- Bandwidth rejected: Public URL shorteners in messages →
- Bandwidth rejected: Low brand trust score / vetting needed for throughput →
Common questions
Why was my 10DLC campaign rejected on Bandwidth?
The rejection came from The Campaign Registry or the carriers, and Bandwidth relayed it. You resolve the underlying rejection reason and resubmit through Bandwidth.
Where does Bandwidth show the rejection reason?
In the Bandwidth Dashboard on the rejected brand or campaign, and via the Dashboard API. The reason shown originates with TCR or the carriers.
How do I fix a Bandwidth 10DLC rejection?
Identify which known rejection reason applies, correct it, and resubmit. Fixing every issue before resubmitting avoids another multi-week review cycle.