A2P 10DLC · Carrier compliance · Twilio ISV architecture
We spent four months inside an A2P 10DLC rejection loop on a platform we built and operate, and came out with a working Twilio ISV architecture and a list of every way a registration fails. That list is what we sell.
Who this is for
If you are sending your first message next month and nothing is broken yet, you do not need us. Read the articles instead.
What we fix
The call to action in the wrong field. Sample messages that fight the flags set on the campaign. Opt in proof that cannot be opened. A sole proprietor brand carrying LLC in the name. A privacy policy link that returns 404 to a vetting reviewer.
Registration is approved and messages still do not arrive. Error 30007 is carrier content and reputation filtering. Registering harder does not fix it, and most people spend a month finding that out.
Subaccount per customer, brand and campaign per legal entity, numbers and Messaging Service scoped to the account that owns them, shared parent balance. One brand across a downline shares one T-Mobile daily cap and one throughput pool, and one customer's violation takes down everybody.
A parent account approved for attestation A does not give subaccount numbers attestation A. Each subaccount needs its own Secondary Business Profile and its own SHAKEN/STIR Trust Product with the numbers assigned to it.
Architecture
We built and we operate a Twilio ISV platform: master account, subaccount per customer, brand and campaign per subaccount, numbers and Messaging Service scoped to the owning subaccount, SHAKEN/STIR attestation on subaccount numbers, programmatic registration through the A2P APIs, and a manual review gate on every compliance submission.
Proof
Getting there took four months of rejections. Along the way we hit and fixed, in production:
You do not have to lose those four months. That is the entire offer.
We are not affiliated with Twilio. Not certified, not a partner, not endorsed. We are an independent practice and the work speaks for itself.
FAQ
The most common cause we see is the call to action sitting in the campaign Description field instead of MessageFlow. Reviewers read MessageFlow for consent. A beautifully written Description with the opt in story in it fails, every time, and the rejection text does not say which field is wrong.
Yes, though not the way most people are told. Low Volume Standard is a Standard brand registered with secondary vetting skipped, so requesting secondary vetting retroactively converts it into a scored Standard brand. It is a manual process through Twilio Support and it takes time. What genuinely cannot be converted is Sole Proprietor, which needs a new Customer Profile, a new brand and a new campaign. The number that should drive the decision is the cap: Low Volume Standard is limited to 2,000 segments a day to T-Mobile and 12 MPS, and a Low Volume Mixed campaign drops that to 3.75 MPS. If your twelve month plan crosses those, register Standard now rather than converting later.
If you are seeing error 30007, that is carrier content or reputation filtering, not a registration fault. Registration will not fix it. The fix is in message content, sending patterns, link handling and number reputation, and it is a different piece of work from an approval.
One brand per legal entity. Registering one brand across a downline or a group of producers forces them all to share a single T-Mobile daily cap and one throughput pool, and one customer's violation blocks everybody. If two of your customers genuinely share one legal entity, the separation has to happen in your application with per seat quotas and separate campaigns, not by registering twice against the same EIN.
Yes, there is a sole proprietor path. It fails for predictable reasons: LLC or Inc in the brand name when there is no such entity, sample messages that read as marketing, a missing privacy policy or terms link, and opt in proof that a reviewer cannot open without logging in.
A parent level approval does not reach subaccount numbers. Each subaccount needs its own Secondary Business Profile, the numbers assigned to it, and its own SHAKEN/STIR Trust Product with those numbers assigned. Five steps, no code required, and it is the single most common voice surprise for platforms running an ISV setup.
As of September 2026: Standard brand around $44 one time plus $10 a month, Low Volume Standard around $4.50 plus $1.50 a month, sole proprietor around $4.50 plus $2 a month. Campaign vetting is $15 one time on every path. Secondary vetting is around $40, an appeal is $11, enhanced vetting is around $101.50. Carrier fees per message are a fixed pass through and are never discounted. We will tell you the real number for your setup in the audit.
Only a read only API key scoped to the subaccount we are working in, never a master auth token, and we revoke it the day the engagement closes. For an audit we can usually work from console screenshots and your campaign payload alone.
Start here
Paste what the carrier sent back and what you have in MessageFlow. If the cause is something we can name in five minutes we will tell you on the call and you will not need to hire anyone.
Book a call