10DLC Campaign Stuck In Review? What to Do While You Wait

Your campaign has said pending or in review for two weeks and the launch date is approaching. Is that normal? (Usually yes.) Can you speed it up? (Mostly no.) Can you make it worse? (Absolutely, and people do, daily.) Here is the realistic playbook for a stuck review.

What counts as "stuck"

Campaign review runs through TCR and a DCA’s human review queue; one to four weeks is the normal band, with ~2 weeks typical. Calibrate:

• Under 2 weeks: normal. Do nothing.
• 2–4 weeks: slow but within range, especially for Mixed/Marketing use cases and after industry-wide surges. Prepare, don’t poke.
• 4+ weeks: legitimately stalled. Time for the escalation path.

What NOT to do (these make it worse)

• Do not delete and resubmit. The intuitive move is the worst one: you lose your queue position, pay campaign vetting again, and can create conflicting records that need support to untangle.
• Do not submit a duplicate campaign "in parallel just in case": same conflicts, plus it looks like evasion.
• Do not edit the pending campaign cosmetically. Material edits can reset review. Edit only if you have discovered an actual defect (see below).

The one useful intervention: pre-empt a rejection

While you wait, audit your submission against the known rejection causes, especially your website. If you find a real defect (privacy policy missing the non-sharing clause, opt-in language not yet live), fix the website now: reviewers check your site at review time, so a fix that goes live before the reviewer arrives converts a rejection into an approval without touching the submission. Our free scanner shows you in 30 seconds what the reviewer will see.

The escalation path (4+ weeks)

1. Open a ticket with Twilio support including the campaign SID, submission date, and a short note that the campaign has exceeded typical review time.
2. Support can query the review status with the DCA/TCR and surface stuck states that never propagate to the Console (it happens; reviews occasionally sit in limbo after upstream system hiccups).
3. If a systemic backlog is the answer, you at least get a realistic ETA to plan against.
4. For genuinely launch-critical traffic in the meantime, a verified toll-free number is the compliant stopgap. Its verification often completes faster, and traffic migrates to 10DLC after approval.

Make the wait free: the launch checklist

Everything downstream of approval can be built during review, so approval day is launch day:

• Messaging Service created; sender pool populated with your numbers.
• Sending code paths using the Messaging Service SID; STOP/HELP handling tested end-to-end.
• Templates finalized against sample-message standards (brand name, opt-out line, branded links).
• Quiet-hour scheduling and per-carrier volume plans in place.
• Monitoring wired: delivery rate per carrier, error-code alerts, opt-out tracking.

Handled this way, a slow review costs calendar time but zero launch readiness, and a fast one becomes a pleasant surprise instead of a scramble.

Frequently asked questions

Does contacting support speed up a normal review?

Within the normal 1–4 week band, no. Support cannot jump the DCA queue. Escalation is for reviews that have exceeded the normal band, where support can query for stuck states and give realistic timelines.

My brand was approved instantly but the campaign has been pending for days. Is something wrong?

No, this is the standard shape. Brand vetting is largely automated; campaign review involves human reviewers with queues. Instant brand + days-to-weeks campaign is the normal experience.

Can I send any messages at all while the campaign is pending?

Not from the pending 10DLC numbers, because unregistered sends fail with error 30034. A verified toll-free number is the compliant interim channel if you truly cannot wait.