FAQ
Common questions from developers, agencies, and SaaS teams dealing with 10DLC rejections, compliance gaps, post-approval setup, and implementation failures.
The most common causes are use case descriptions that don't match the actual campaign, sample messages with content TCR won't approve, missing or incomplete opt-in documentation, and website policies that don't align with what the campaign claims. Vague rejection feedback makes it hard to know which issue is the real one — which is usually all of them at once. See the full breakdown of rejection causes for what to check first.
It means the campaign type you selected — Low Volume Mixed, Customer Care, Marketing, or another — doesn't match how the use case description actually describes the messaging. A marketing campaign described in vague or generic terms, or a use case that contradicts what the sample messages show, will get flagged every time. The fix is aligning the campaign type, the use case description, and the sample messages so they all tell the same story. TCR reviewers read all three together.
Opt-in rejections almost always come down to one of three things: the opt-in point doesn't include clear disclosure language, the privacy policy doesn't reference SMS specifically, or the website describes opt-in differently than the campaign submission does. Pre-checked boxes don't count as consent. Implied consent doesn't count. Every opt-in form needs to explicitly state what the user is consenting to receive, who is sending it, and include an SMS-specific privacy reference. The website and campaign submission have to match.
Don't resubmit without addressing the specific rejection reason — a resubmission that doesn't fix the actual issue just resets the clock. Before resubmitting: identify which gap caused the rejection (use case, opt-in, website, or sample messages), make the specific correction, and verify that the fix actually closes the gap TCR flagged. If the rejection reason is vague, that itself needs to be interpreted before anything is changed. Resubmitting a broken submission faster doesn't help.
The user needs to clearly understand what they're consenting to receive, who is sending it, and that consent is required. The opt-in point — whether a web form, checkout, or paper form — needs to capture that explicitly. Pre-checked boxes don't count. Implied consent doesn't count. The privacy policy needs to reference SMS specifically. If your website doesn't show all of this clearly, it will get flagged in review.
Approval from TCR means the campaign record is accepted — it doesn't mean messages will send. Numbers still need to be assigned to the correct Messaging Service. API parameters need to match the approved campaign type. Webhooks need to be configured for delivery receipts and status callbacks. Without all of that in place, approved campaigns still fail silently.
At minimum: company name and EIN, website URL, privacy policy and terms links, opt-in page URL, use case description, sample messages, messaging platform, and current TCR registration status. The more complete the submission, the faster the review moves. Partial submissions are fine to start — but gaps will need to be filled before anything can be submitted to TCR.
Brand registration typically clears in hours to a couple of days. Campaign registration review by TCR can take anywhere from a day to several weeks depending on campaign type, volume, and how clean the submission is. Re-reviews after rejections add time. The fastest path through is a complete, accurate submission — not a fast resubmission of a broken one.
Share the rejection feedback, campaign details, and website URL. A focused review will identify the specific issue.