If you keep getting rejected
About a 2-3 minute read.
If a campaign has come back rejected more than once or twice for what looks like the same issue, stop and read this before asking for another re-file. Re-filing the same thing just repeats the same result, the fix is to change the root cause, and if you can't see it, to bring in support. For how a rejection reaches you, see How rejections work.
Signs you're in a loop
Pause if any of these are true:
- This is your third pass on the same campaign.
- Your last two rejections cited overlapping issues (both mentioned the opt-in, or both the privacy policy).
- You're not sure what to change between attempts.
- You're changing things that weren't flagged while not addressing what was.
Each of those means another re-file would likely return the same reason.
Work it methodically before the next re-file
1. Read every rejection in full
Open each rejection on this campaign and list every issue cited. Don't filter, write down everything.
2. Group the issues
Most rejections come in clusters that share one root cause. "Missing brand name in the confirmation" and "missing brand name in the HELP reply" are one fix. "Policy doesn't carve out SMS data" and "policy allows sharing with consent" are one fix. Grouping shrinks a scary-looking list to a few real problems.
3. Find a concrete fix for each group
For every group, name the specific change you'll make. If you can't name one, that's your signal to contact support rather than guess.
4. Make sure your fixes are actually live
If a fix is on your website, privacy policy language, a new opt-in form, an age gate, terms, confirm it's published, not sitting in a draft. The reviewer fetches your URLs fresh, so unpublished changes don't count. Check each URL in a private/incognito window.
5. Sort out the structural pieces
If any rejection touched the use case or a content toggle (embedded links, embedded phone numbers, age-gated, direct lending), the fix is structural, the campaign has to be re-created rather than re-filed in place. AgentMessage handles that; contact support so it's done once, correctly.
6. Then, and only then, ask for the re-file
If you've worked through every cited issue in one pass, ask support to re-file. Fixing everything at once beats whack-a-mole, addressing one flag at a time tends to surface the next one and stretch the process out.
When to contact support instead
Contact support rather than asking for another re-file if:
- You've been rejected three or more times on what looks like the same root issue.
- The reason is vague or you can't tell what it's pointing at.
- You believe the rejection is incorrect, and you've already cleaned up anything on your site that could be triggering it.
- You're still getting the same reason after making what you believe is the correct fix.
When you reach out, include:
- The campaign (and its ID if you have it).
- The full text of every rejection on this campaign.
- The exact changes you've made between attempts.
- Why you think the most recent rejection is wrong, if that's the case.
That's the fastest way for us to read the pattern, interpret an unclear reason, and, when a rejection genuinely looks wrong, escalate it for human review.
How to avoid the loop next time
The best defense is not racking up rejections in the first place:
- Read Write a CTA that passes before you file, opt-in issues are behind most first-round rejections.
- Walk every disclosure location through Opt-in, opt-out, and HELP.
- Publish your privacy policy and terms first, with the SMS-specific language, before you submit. See Privacy policy rejections.
- Make your samples and content toggles match before filing. See The campaign form, field by field.
- If a rejection does come back, fix everything it cites in a single pass.
There's no charge for talking to support, and if you're several rejections deep, the quickest path forward is almost always to pause, gather everything, and reach out before the next attempt.