Why A2P 10DLC Campaigns Get Rejected, and the Fixes

Updated

Short answer: Most A2P 10DLC campaigns are rejected because a reviewer could not verify something: how people opt in, your website, your privacy policy or terms, or whether your description and samples match your brand and use case. Fix every issue the rejection code names, then edit and resubmit the same campaign. Content in a forbidden category is different, because new wording will not change the outcome.

How campaign review works

A2P 10DLC registration has two parts. For the brand, Twilio says "You provide information about who is sending these messages so that carriers know you are a legitimate sender". For the campaign, "You provide information about how end users can opt-in, opt-out, and receive help. It also involves providing a description of the purpose of your messages."

Every new campaign is checked before it can send. Twilio's onboarding guide says: "All new A2P 10DLC Campaigns go through a vetting process to protect the messaging ecosystem for everyone and make sure everything aligns with carrier requirements and CTIA guidelines."

Two facts help when a rejection arrives:

  • The Campaign Registry (TCR) is not your reviewer. TCR says it "does not review, approve, or reject campaigns. This is solely done by the CSPs and their upstream connection partners." The provider you registered through receives the reason and guides the fix.
  • Review takes time. Standard campaigns go through "several distinct layers of vetting, which takes up to 5 business days for standard use cases."

Filling in every field is not enough. HighLevel puts it this way: "A Campaign can contain values in every required field and still be rejected if those values conflict with official business records, the selected use case, the website, sample messages, or the way recipients actually opt in."

These are carrier and industry rules, not legal advice.

The common reasons, and the fix for each

What reviewers foundExample Twilio codesThe fix
The opt-in description is unclear or leaves out a method30909, 30896, 30917Describe every opt-in path, step by step, including the consent wording people see
The consent wording is missing an element30544, 30545, 30547, 30568, 30569, 30570Show the brand, message type, frequency, rates, STOP and HELP where people consent
The website does not load, needs a login or does not match the brand30891, 30907, 30919, 30921Submit a live, public site that shows your business and its opt-in
The privacy policy or terms are missing required parts30908, 30882, 30932Add the no-sharing statement and an SMS section to your terms
The description is vague30886Say who sends, who receives and why
The samples do not match the use case30893Rewrite them to show the messages you will really send
A link uses a public shortener or http://30892, 30963, 30964Use a full HTTPS link or a branded short domain you own
The brand details do not match the business30894Use the same business name, website and email domain throughout

The opt-in description

Twilio's onboarding guide says of the message flow: "This is the heart of your registration, and it's also where most rejections happen." Twilio's registration docs set the rules:

  • The field "Must be between 40 and 2048 characters in length."
  • "At each point of opt-in, the consent language shown to users must identify the brand and state the types of messages users agree to receive."
  • "If multiple opt-in methods can be used for the same campaign, they must all be listed."

If your form is not live yet or sits behind a login, the onboarding guide asks for a public link to a screenshot, and to "include a screenshot of what the form looks like after it has been submitted."

Consent must also be optional. Error 30923 applies when "your opt-in flow makes consent to receive messages a required condition for using your service, creating an account, or completing a transaction." The opt-in language guide has wording and checkbox examples.

The website

Twilio's docs list the website URLs that TCR rejects. They are URLs that:

  • "Are not reachable (for example, the URL returns an error or times out)."
  • "Point to a parked domain or to a domain that is listed for sale."
  • "Require a login to view content."
  • "Redirect to a different brand or an unrelated domain."

The site must also represent the brand you register. Twilio says: "Sites that don't load, return errors, or aren't live yet won't pass review."

The privacy policy and terms

TCR rejects privacy policies that need a login, that are not public at the URL you give, or that lack "a statement about not sharing mobile numbers". Your terms need their own SMS section. The guide to privacy policy and terms for A2P 10DLC lists every item.

A description and samples that don't line up

Twilio's onboarding guide says: "Your campaign description also needs to match the campaign type you selected and your sample messages." It adds: "Double-check that your campaign description matches your brand registration." Each sample must name you too: "The Brand must be identified by name and/or website in each message." See the guides to the campaign description and sample messages.

Brand details that don't match

If you register one name and your messages use another, Twilio says reviewers "will flag that mismatch." Links count too: "Links within the messaging content must represent the registered brand. Third-party redirects aren't permitted." Problems with your EIN or legal name are covered in A2P brand registration failures.

Content that no wording can fix

Twilio warns: "Some types of messaging will result in immediate rejection." For an ineligible or prohibited use case, its advice is: "Do not resubmit the same prohibited messaging with a different description. Contact Support if you believe the decision is incorrect." The guide to SHAFT and restricted content lists the categories.

How to fix and resubmit

  1. Read the code. Each Twilio code names a specific problem. In HighLevel, every rejection reason has a "View required fixes" link that shows the error code, the rejection category, what it means and the correction needed.
  2. Fix everything listed, not only the first item. Twilio's guidance for a correctable issue is: "Fix all identified issues and use the resubmission procedure available for your campaign." A correction improves your chances, but the reviewers still decide.
  3. Put each disclosure where people consent. "A required disclosure in the CTA must appear where consent is collected; putting it only in Terms of Service may not resolve the CTA error."
  4. Edit and resubmit instead of starting over. "If your Campaign fails review, edit and resubmit it rather than deleting it and creating a new one. The vetting fee is only charged once per Campaign, at its first vetting decision, and resubmitting keeps that fee from being charged twice."
  5. Expect a new review. Twilio says a resubmission "starts a new review that takes up to 5 business days for standard use cases."
  6. Appeal only if you think the decision is wrong. Twilio asks you to contact Support "with the campaign identifier, business name, error code, rejection details, and evidence supporting the appeal" and to use the subject "10DLC Campaign Appeal for [business name or number]".

Before you resubmit, you can paste your samples into the free A2P 10DLC sample checker. It checks that you have at least two samples, that each one names the brand and that at least one has an opt-out instruction. It also flags public link shorteners, Unicode characters that cost extra segments and samples longer than 3 segments. It does not check use-case fit, opt-in, your website or your privacy policy.

After approval

Approval does not end the checks. Twilio lists reasons carriers suspend live campaigns, starting with "Campaign-to-traffic mismatch: In-market traffic does not match with the campaign registered". Spam, excessive complaints, affiliate marketing and a missing age gate are also on the list. Keep what you send in line with what you registered.

Sources

Not legal advice. Carrier rules and provider documentation change, so check the linked sources before you rely on them.