November 14, 2026. Twilio's changelog entry dated November 13 says that, starting December 9, 2026, it plans to introduce more specific error codes for rejected US A2P 10DLC campaign registrations. The entry lists 22 codes in three groups: 5 about the campaign description, 10 about how people sign up, and 7 about the Privacy Policy and Terms and Conditions pages. Each code has a one-line meaning in the changelog.
Key numbers
| Item | Number |
|---|---|
| Date Twilio plans to introduce the codes (Twilio changelog) | December 9, 2026 |
| Codes listed in the changelog (5 description, 10 sign-up, 7 policy pages) | 22 |
| Codes about how people sign up (the largest group) | 10 |
| Code pages that loaded on November 14 (of the 22 linked; 17 returned Page not found, before the planned start date) | 5 |
| Changelog entry dated (Twilio Changelog header: Nov. 13, 2026) | November 13 |
Twilio Changelog, New error codes for A2P 10DLC campaign rejections, Nov. 13, 2026, read November 14, 2026
What Twilio announced
The changelog entry says the codes "will provide more detailed feedback about campaign descriptions, opt-in methods, and Privacy Policy and Terms and Conditions pages". It also says the release "includes additional codes and the A2P 10DLC mapping for error 30569, which already exists in the Twilio error dictionary."
More specific codes are not new this year. Twilio's help article on rejected A2P 10DLC campaigns says: "From September 15, 2026, new shared error codes identify more specific rejection reasons for A2P 10DLC and Toll-Free Verification."
Campaign description: 5 codes
| Code | What Twilio says it means |
|---|---|
| 30977 | Campaign description doesn't name the business you registered |
| 30984 | Description has unfilled template text |
| 30985 | Marketing content in a campaign type that doesn't allow it |
| 30986 | Campaign type doesn't match the texts in your description |
| 30969 | Marketing campaign also describes texts that aren't marketing |
How people sign up: 10 codes
Twilio calls this group "Message flow (how people sign up)". It is the largest of the three.
| Code | What Twilio says it means |
|---|---|
| 30965 | Sign-up proof doesn't open or can't be read |
| 30966 | Consent was collected for affiliates or by another business |
| 30978 | No link or screenshot of your text-to-join instructions |
| 30979 | Verbal or phone opt-in script missing or incomplete |
| 30980 | Website sign-up form has no phone number field |
| 30982 | Paper sign-up form doesn't ask people to agree to get texts |
| 30983 | Paper sign-up form wasn't provided |
| 30987 | Sign-up consent doesn't match the texts this campaign sends |
| 30988 | Chat widget named in Message flow isn't on your site |
| 30569 | Call-to-Action is missing the message and data rates disclosure |
Twilio's changelog says code 30569 already exists in its error dictionary. Its error page says it "applies to both Toll-Free Verification and A2P 10DLC registration", and that the call to action "does not disclose that message and data rates may apply to the messaging program."
Privacy Policy and Terms pages: 7 codes
| Code | What Twilio says it means |
|---|---|
| 30973 | Privacy Policy page didn't load |
| 30974 | Privacy Policy page has too little text |
| 30975 | Terms and Conditions page didn't load |
| 30976 | Terms and Conditions page has too little text |
| 30981 | Privacy Policy doesn't name the business you registered |
| 30967 | Two Privacy Policy links open different policies |
| 30968 | Two Terms and Conditions links open different terms |
What Twilio says to do after a rejection
The changelog's instruction is short: "If your campaign is rejected, review every returned code and its linked guidance. Correct the identified issues, then follow the registration workflow available for your campaign. Resubmit an existing campaign only when it is eligible and the required changes are supported. Some corrections require a new campaign with the appropriate campaign type."
Two limits from Twilio's own pages are worth knowing before you plan a fix. Its troubleshooting guide says "Edits are available only for Campaigns with a FAILED status", and that the Console edit screen covers nearly all text fields "but NOT the use case itself". If the use case has to change, the guide says the campaign "would still need to be deleted and recreated." The help article adds: "A shared error code does not automatically make an A2P 10DLC campaign eligible for resubmission."
This is general information, not legal advice.
What we checked on November 14
The changelog links each of the 22 codes to a page in Twilio's error dictionary. When we opened all 22 on November 14, before the planned start date, 5 pages loaded (30569, 30973, 30974, 30975 and 30976) and 17 returned "Page not found". The help article on rejected campaigns did not mention December 9 yet. We did not check other Twilio pages.
Our read: using the list as a pre-submission checklist
You do not have to wait for December 9 to read the list. The grouping below is ours, not Twilio's, and a campaign that clears it can still be rejected. Here is what we would check before submitting or resubmitting a campaign, with the codes each check maps to:
- The registered business name appears in the campaign description and in the Privacy Policy (30977, 30981).
- The description has no leftover template text and matches the campaign type you picked (30984, 30985, 30986, 30969).
- Every sign-up method you describe is backed by something a reviewer can open, and it is complete: the web form has a phone number field, the text-to-join instructions are linked or shown in a screenshot, the verbal script is complete, the paper form is provided and asks people to agree to get texts, and the chat widget is on your site (30965, 30978, 30979, 30980, 30982, 30983, 30988).
- Consent was collected by your business, for the kind of texts this campaign sends (30966, 30987).
- The call to action says message and data rates may apply (30569).
- The Privacy Policy and Terms pages load, have enough text, and every link to them opens the same page (30973, 30974, 30975, 30976, 30967, 30968).
Related on our site: why A2P 10DLC campaigns get rejected, how the 10DLC daily message limit works and what 10DLC registration costs. If you also call the people you text, see how we set up AI calling built around TCPA consent.
Frequently Asked Questions
Twilio's changelog entry of November 13, 2026 says it plans to introduce the more specific codes starting December 9, 2026. They apply to rejections of US A2P 10DLC campaign registrations.
The changelog lists 22 codes: 5 about the campaign description, 10 about how people sign up, and 7 about the Privacy Policy and Terms and Conditions pages. The changelog says one of them, 30569, already exists in Twilio's error dictionary.
Sometimes. Twilio says to resubmit an existing campaign only when it is eligible and the required changes are supported, and that some corrections require a new campaign. Its troubleshooting guide says edits are available only for campaigns with a FAILED status, and that the Console edit screen does not let you change the use case. In that case the guide says the campaign has to be deleted and recreated.
Twilio's error page titles it "Call-to-Action is missing the message and data rates disclosure". The page says the error applies to both Toll-Free Verification and A2P 10DLC registration.