Skip to content
WirebirdTalk to sales

10DLC campaign rejected: the common reasons and how to fix each one

A rejected 10DLC campaign stops a business from texting until someone fixes it. Most rejections come from a short list of problems: unverifiable opt-in, missing privacy policy or terms, samples that don't match the use case, and website issues. This guide covers each one, how brand failures differ, and how resubmission and appeals work.

Updated

First, tell a brand failure from a campaign rejection

10DLC registration has two layers. The brand is the business's identity, checked against public records. The campaign is the messaging program, read by a human vetter. They fail for different reasons and get fixed in different places.

A brand failure means the identity check didn't pass. The legal name, tax ID (EIN), address or website didn't match what the vetters could verify. A campaign rejection means the identity is fine but the description of what the business will send, and how people agreed to it, didn't pass review.

Check the brand first. With Twilio, a brand can't be edited while a campaign is registered to it, so a brand problem may force you to delete the campaign before you can fix anything.

Fixing brand failures

Telnyx documents the most common brand failures in its 10DLC troubleshooting guide, and they match what most providers see:

  • Legal name doesn't match the EIN: submit the exact name on IRS records, including suffixes like "LLC" or "Inc." A trade name or DBA is not the legal name.
  • Address can't be verified: use the USPS-standardized address with suite numbers. PO boxes are generally not accepted.
  • Website can't be verified: the site must be live, use the business's root domain, and clearly identify the business. Placeholder and under-construction pages fail.
  • Duplicate brand: the EIN is already registered, possibly through another provider. You may be able to add campaigns as a secondary provider rather than registering again.
  • Low vetting score: the brand passed but scored low, which limits throughput. Fix inconsistent public data, then request a new vet. Each vetting attempt carries a fee.

Campaign rejection reasons and the fix for each

Twilio publishes specific rejection codes, and it began rolling out more granular ones in 2026. The reasons below are the ones platforms hit most, with Twilio's code where one exists.

  • Opt-in can't be verified (30896, 30909): describe every opt-in path end to end in the message flow field. For a web form, give a public URL. For paper, verbal or logged-in flows, host screenshots or the full script at a public URL. Any SMS checkbox should be optional and unchecked by default.
  • Call to action missing pieces (30568, 30544): the consent language must name the business and say what kind of messages people will get, such as appointment reminders.
  • Privacy policy problems (30908, 30933): the policy must be public and say that mobile numbers and opt-in data are not shared with third parties or affiliates for marketing. Since June 30, 2026, Twilio's API rejects campaigns that omit the privacy policy URL field entirely.
  • Terms problems (30882, 30934): provide a public terms URL. Terms that bundle texting consent into general terms, or that allow sharing opt-in data, fail. The terms URL field is also required in Twilio's API since June 30, 2026.
  • Vague description (30886): say who sends, who receives and why. For a platform registering its customers, the description must name the actual business, not your platform.
  • Samples don't match the use case (30893): if the use case is customer care, every sample must be customer care. Name the business in each sample and include opt-out language in at least one.
  • Public URL shortener in samples (30892): bit.ly and similar shared shorteners cause rejections. Use full links or a branded short domain the business owns.
  • Embedded links or phone numbers not declared: if samples contain links or phone numbers, the matching campaign attributes must say so.

Rejections you can't fix by editing

Some rejections are not eligible for a normal resubmission. Twilio lists content violations (30883), such as SHAFT content (sex, hate, alcohol, firearms, tobacco) or cannabis, and campaigns judged spam or phishing (30884) or high risk (30885). For these, editing the same campaign won't help.

Twilio's guidance is to appeal through support if you believe the rejection is wrong, or to submit a new campaign only if the use case and content have materially changed. Prohibited use cases like affiliate marketing or third-party lead generation can't be fixed by rewording.

Registration patterns also matter. Twilio says too many brands under one EIN can lead to campaign rejection during vetting, which is worth knowing if a multi-location business signs up each location separately.

What a passing opt-in description contains

Opt-in is the most common reason campaigns come back, because the vetter has to verify consent from outside your product. Twilio's guidance for the message flow field boils down to a checklist. A good description answers each item in plain sentences.

  • Who opts in and where: "Clients of Lakeside Tutoring opt in on the booking form at a public URL, or by telling staff at the front desk."
  • Every method the business uses. If clients can also text a keyword, say which keyword and to which number, and fill in the opt-in keywords and opt-in confirmation message.
  • The consent language itself, naming the business and the kind of messages, with message frequency, a "message and data rates may apply" notice, and STOP and HELP instructions.
  • Links to the privacy policy and terms.
  • For anything a vetter can't open, such as a form behind a login, a paper form or a verbal script, a public URL with screenshots, a photo or the full script.

Other reasons providers list

Telnyx's troubleshooting guide adds a few campaign problems that are easy to miss: submitting a campaign before the brand's vetting is complete, registering a campaign that duplicates one the brand already has, and too few or too similar sample messages. Telnyx recommends two to five samples that show the different messages the business will actually send, with realistic content instead of placeholders.

Resubmitting and appealing

Resubmit the existing campaign rather than creating a new one. Twilio charges the campaign vetting fee once per campaign and doesn't limit resubmissions, so a new campaign means a new fee. Standard campaigns can take up to five business days to review after resubmission.

With Twilio, editing a failed campaign through the API is a private beta. Without it, you edit in the Console, or delete and recreate the campaign and pay vetting again. Only some fields can be changed on resubmission. The use case can't, so a wrong use case means a new campaign.

Telnyx supports appeals for rejected campaigns through its portal and a campaign appeal API, and reports rejection reasons through 10DLC event webhooks. Whatever your provider, fix every cited issue before resubmitting. A partial fix usually comes back with the next reason.

Preventing rejections across hundreds of customers

A platform sees the same rejection many times, so fixes belong in the onboarding flow, not in one-off tickets:

  • Collect the privacy policy and terms URLs up front and check that they load and contain the required non-sharing language.
  • Check the legal name and EIN before filing the brand, so a typo doesn't cost a fee and a week.
  • Write campaign descriptions and samples from tested templates per industry, filled in with the business's own name.
  • Host a public page showing your product's opt-in form so vetters can see it, since many platforms collect consent behind a login.
  • Map provider rejection codes to plain-language messages your customers can act on, and keep the mapping current as codes change.

How Wirebird handles it

Wirebird collects business details through a white-label form in your product, checks the legal name and EIN before anything is paid for, and files brands and campaigns from templates written for your industry. When a campaign is rejected, we fix and resubmit it, and you get a status webhook with the reason at each step, so your team doesn't have to read rejection codes.

Sources

Rather not run this yourself?

Wirebird files, tracks and fixes registrations for every business on your platform.