Documentation conflicts
Where the A2P documentation contradicts itself
Why this page exists
Every other page in this section gives you an answer. This one does not, on purpose.
On the codes below, the sources disagree. Sometimes Twilio and the platform help articles state opposite things. Once, the same vendor states opposite things in its own two help portals. Picking the more plausible side and presenting it as the answer would hide the fact that you are being told two different things by people who both have authority over the outcome.
So both sides are quoted, each is attributed, and nothing is resolved. Where a decision depends on one of these, the right move is usually to get the answer in writing from whoever will process the resubmission.
30882: correctable, or retired and not resubmittable
Twilio documents a concrete fix for this code. Both of the platform help articles place it on a list of codes that cannot be resubmitted at all.
Twilio
Add a TermsAndConditionsUrl to your campaign registration request. The URL must be publicly accessible, not behind a login, and point to terms and conditions relevant to your registered brand.Twilio error page for 30882
Platform help articles
Listed under "Legacy (Pre-March 23, 2026)" in the ineligible for resubmission section.
HighLevel article 155000007572 and LeadConnector article 155000004749
Worth knowing before you decide: Twilio has since published 30934 specifically for a missing terms and conditions URL, which is a different code for what sounds like the same problem.
The platforms do not reconcile these. Twilio says fix the field and resubmit. Both help articles say the code is not resubmittable. Neither side acknowledges the other.
30898: the same vendor contradicts itself
This is the one to be most careful with, because the disagreement is not between two companies. It is between two help portals run by the same vendor.
One portal says eligible
Listed in the eligible for resubmission section as "Same EIN for multiple brands".
HighLevel article 155000007572
The other portal says ineligible
Listed in the ineligible for resubmission section, alongside the forbidden category codes.
LeadConnector article 155000004749
Twilio, for its part, says not to resubmit until the underlying brand registration problem is corrected. A support answer on this code is unreliable regardless of which article the agent happens to be reading.
30995: two different limits under one code
This is a disagreement about what the code even means, not about how to respond to it.
Twilio
Messaging Service size limit reached. Twilio describes an account level cap of 10,000 Messaging Services.
Twilio error page for 30995
Platform help article
Listed as "Messaging Services phone number limit reached" with the remedy "Contact support".
HighLevel article 155000007572
A Messaging Service count and a phone number count are not the same thing, and the two sources describe different limits under the same number. No page in this section covers 30995, because it is not clear which of the two things it reports.
The campaign cap: five or one hundred
Twilio states both numbers, on different pages, without mentioning the other.
Five
Standard and Low-Volume Standard Brands can register up to five Campaigns.
Twilio error page for 30926
One hundred
Your A2P 10DLC campaign registration was rejected because the associated brand has already reached the maximum of 100 campaigns. The Campaign Registry enforces this limit per brand.
Twilio error page for 30930
Two further Twilio pages weigh in, and both say five. The A2P 10DLC onboarding guide states "A Brand can have up to five Campaigns associated with it" without distinguishing brand tier. The A2P 10DLC overview breaks it down by tier and adds a qualifier the others leave out:
| Brand tier | What the overview states |
|---|---|
| Sole Proprietor | One Campaign per Brand |
| Low-Volume Standard | Each Brand may register up to five Campaigns, unless a clear and valid business reason is provided for exceeding this limit |
| Standard | Each Brand may register up to five Campaigns, unless a clear and valid business reason is provided for exceeding this limit |
So three Twilio locations say five and one says one hundred. See 30926 and 30930.
No Twilio page states both figures, and none explains the relationship between them.
Age gating: whether a date of birth field is enough
Seven Twilio pages tell you to collect a full date of birth. One Twilio page names a date of birth field as insufficient. All eight are current.
Date of birth is what is required
Require users to enter their full date of birth in MM/DD/YYYY format, or use a third-party age-verification service. Do not rely on a simple "Yes" confirmation as your only control.Twilio error pages 30456, 30512, 30529, 30840, 30875, 30876, and 30888
A date of birth field does not meet the standard
The website uses a simple checkbox or date-of-birth field that does not meet the CTIA standard for robust age-gate verification.
Twilio error page for 30956
This is not a difference between toll-free rules and campaign rules. 30888 is a campaign code, and it is one of the seven that endorses collecting a full date of birth. The disagreement runs through the campaign family itself.
The two sides also cite different authorities. The seven pages attribute the date of birth requirement to Twilio. 30956 attributes its stricter position to CTIA.
30956 names no compliant method at all. It rejects a checkbox and rejects a date of birth field, then asks for a system that "meets CTIA standards" without saying what would qualify. There is no method on that page you can build to.
The platforms do not reconcile these. A single business website serving both a verified toll-free number and a 10DLC campaign cannot satisfy both readings at once.
Two ways forward
Have it handled for you
A2P registration is handled for you on Growth at $597/mo and on Scale at $1,197/mo. Registration, resubmissions, and the compliance work behind them are included.
Fix it yourself
Send your email and we will send the fix playbook for registration rejections.
Verified against Twilio documentation on 2026-08-10.