Carrier A2P 10DLC in 2026: Costs and Compliance for marketing automation

TL;DR

Carriers tightened A2P 10DLC enforcement in the United States in 2026, which changes how teams plan budgets, throughput, and registration workflows. This piece explains the cost stack, the failure modes that trigger filtering, and the architecture patterns that scale oversight across many brands. It also includes a pragmatic playbook to operationalize compliance and measurement. If marketing automation drives a meaningful share of your pipeline, treat 10DLC governance as a first class function and not a last mile send button.

What changed in 2026 and why it matters

The big shift in 2026 is not a single headline policy but a steady ratcheting of carrier scrutiny on brand identity, consent proof, and campaign declarations. Registration went from recommended to table stakes, and vetting quality now influences throughput and surcharge levels for similar use cases. For growth teams that rely on SMS for lifecycle moments like post purchase updates, reactivation, and service alerts, the practical outcome is a new operating model that allocates capacity by program, not just by channel.

This matters because SMS remains a rare direct path to attention. Deliverability loss compounds quickly when registration lags or when content drifts away from the declared purpose. Engineering and operations teams need shared primitives for brand registration, template governance, consent evidence, and per carrier throttling. That work pays back in delivery rate, lower complaint risk, and fewer manual exceptions.

If you build on a platform like ButterGrow, you already have a central place to coordinate agents, playbooks, and message orchestration. Use that control plane to standardize declarations and proofs across all the teams that send messages, then connect those controls to inbox outcomes you can measure.

The 10DLC cost model that finance will ask you to defend

The modern 10DLC cost stack has five components you should model explicitly. Some are one time and some are ongoing. Treat them as variables in a forecast, not fixed fees you can take for granted.

• Brand registration and optional or required vetting
• Campaign registration per use case or program
• Monthly campaign fees that vary by carrier and tier
• Per message carrier surcharges on top of your CPaaS transport
• Compliance and engineering time to maintain registrations and proofs

You can explain the structure with a simple formula.

# Illustrative 10DLC monthly cost model
brands = 8                      # distinct legal entities you text under
campaigns_per_brand = 3         # promotional, transactional, service
msgs_per_campaign = 120_000     # monthly outbound messages

brand_fee = 15                  # monthly amortized brand registration and vetting
campaign_monthly_fee = 10       # monthly campaign fee
carrier_surcharge = 0.015       # per message carrier surcharge
cpaas_transport = 0.006         # per message CPaaS transport
governance_overhead = 900       # monthly internal time and tools

monthly_cost = (
    brands * brand_fee
    + brands * campaigns_per_brand * campaign_monthly_fee
    + brands * campaigns_per_brand * msgs_per_campaign * (carrier_surcharge + cpaas_transport)
    + governance_overhead
)
print(f"Estimated monthly cost: ${monthly_cost:,.0f}")

Numbers above are placeholders so you can wire the model into your planning tool. Swap them with the most recent carrier and CPaaS rates from your contracts. The key is to expose each lever and tie approvals to scenario ranges rather than a single point estimate.

Cost components and control levers

Component	What drives it	Control lever
Brand registration and vetting	Legal entity information quality and risk tier	Maintain consistent EIN, address, website, and public presence. Avoid mismatched DBA names.
Campaign registration	Use case scope and template quality	Keep campaign purpose narrow. Pre approve templates and links.
Monthly campaign fee	Carrier policy, tier, and review outcomes	Consolidate duplicative campaigns. Archive dormant programs.
Per message surcharges	Carrier schedules and risk category	Improve list hygiene and consent so you qualify for better tiers.
CPaaS transport	Vendor pricing and volume breaks	Negotiate breaks and use multi vendor routing where allowed.

Finance teams will ask why the same message can land in different cost bands. The answer is that vetting outcomes and carrier schedules vary. Your control is the quality of identity signals, consent and content discipline, and consolidation of programs to reduce the number of active campaigns.

Risk model: how filtering decisions get made

Filtering is not random. Carriers score traffic against the registration you filed, the brand reputation they infer, and outcomes like opt out and complaint rates. When those signals degrade, throughput drops, surcharges rise, or messages are blocked altogether. The good news is that each signal can be improved with process and instrumentation.

Common triggers:

• Consent and disclosure language that is vague or missing
• Content that does not match the declared campaign use case
• High link density, excessive URL shorteners, or redirect chains
• Sudden volume spikes without a warming plan
• Recycled numbers and recycled lists without new opt in proofs
• Low inbox engagement relative to volume, such as few replies on two way programs

Two questions help you isolate root cause fast. Did we send what we said we would send. Did users expect to get this message based on an explicit opt in. If either answer is no, fix consent and templates before debating throughput caps.

For a deeper policy context on content and consent, review the CTIA guidance in the references. The definitions there map to the checks your ops team enforces in templates and playbooks.

Architecture patterns that scale registration and control

Growing companies rarely have a single brand or a single use case. You might operate regional entities with local teams and vendors. Re creating registration on every team invites drift and repeated mistakes. Centralize three things and expose them as a service to anyone who sends messages.

1. A brand registry service. Store legal entity data, vetting status, phone number inventory, and ownership. Issue identities to campaigns by reference, not by copy paste.
2. A campaign metadata model. Keep purpose, consent proofs, approved templates, link domains, and policy flags in one place. Require a reference to this model in any workflow that sends SMS.
3. A consent and frequency ledger. Track opt in source, timestamps, double opt in status, message frequency, last send, and user initiated help or stop events.

If you are on ButterGrow, start by mapping these to the feature set. Use built in objects where they exist and store the rest behind a thin service that your agents call before they send. The goal is to move policy into code and let teams build quickly without risking drift.

Step by step compliance playbook

Step 1Map your sending brands and owners

Inventory every entity that sends SMS. Capture EIN or equivalent, legal name, DBA, address, website, and live support contacts. Record the relationship between each brand and the teams or agencies that operate it. This map defines who is allowed to register campaigns and who approves changes.

Step 2Define campaigns by purpose, not by audience

Campaigns should describe a program purpose and a set of templates that fit that purpose. Avoid umbrella definitions that cover both promotions and service alerts. Narrow purpose reduces review friction and makes it easier to prove that content matches your declaration.

Step 3Write and store consent language and proofs

For each acquisition path, draft explicit opt in language that names the program, includes frequency, data rates notice, and a link to terms and privacy. Store screenshots or HTML captures, the URL and timestamp of the form, and any double opt in event. When users reply STOP, honor it across all campaigns for that brand unless the context requires per program scope.

Step 4Register brands and campaigns and schedule vetting

Complete registration in your CPaaS and make vetting part of your release checklist for new programs. Keep a change log for templates and links. When you adjust content, update the campaign declaration before you send. Use a single team to coordinate registrations so you avoid duplicates and mismatched details.

Step 5Warm up throughput and watch early outcomes

Ramp new campaigns with a gradual schedule and an expectation for higher early opt out. Track delivery rate, complaints, and help requests in near real time. If early outcomes look off, pause new cohorts and fix consent or content before you scale volume.

Step 6Automate pre send checks in your workflows

Add policy checks as gates in your workflow automation. Verify that the brand and campaign IDs are valid, that the template version is approved, that the destination country matches registration, and that the recipient has an active consent record. Block sends when checks fail and route to a human queue.

Step 7Build incident playbooks for filtering and blocks

When filtering hits, speed matters. Keep a runbook that defines who reads carrier feedback, who adjusts rates, and what evidence you gather for review. Include known issues like link domains that are flagged or templates that drifted from declarations. Tie these runbooks to incident automation in your platform so responders have context.

If you need a platform that already wires policy checks into workflows, you can get started in minutes with ButterGrow and map your registry, campaign metadata, and consent ledger to agents that enforce checks automatically.

Forecasting and measurement: how 10DLC changes your funnel math

SMS rarely lives alone. It amplifies email and paid media and supports service flows that reduce churn. Registration raises the fixed overhead to launch, but it also increases your confidence in delivery and attribution. Treat the cost stack and the governance stack as investments with measurable return.

Key metrics to track:

• Delivery rate by brand and campaign, not just at the channel level
• Opt out rate segmented by acquisition source and first touch template
• Complaint rate and help event rate per thousand messages
• Link click rate with a policy on shorteners and redirects
• Reply rate on two way programs that rely on human or agent responses

Tie these to business outcomes like reactivation rate, repeat purchase rate, and support resolution time. Then compare the pre registration baseline to the post registration cohort. When the model is healthy, the cost per incremental conversion stabilizes or improves as filtering incidents drop.

What good looks like: governance, documentation, and culture

High performing teams make compliance part of the developer workflow and part of the growth ritual. Engineers own the primitives. Marketers own the content and consent sources. Legal and privacy audit and advise. Everyone can see the same registry and the same outcomes.

Documentation to keep current:

• A single source of truth for brand identities and numbers
• A catalog of campaigns with purpose, templates, and link domains
• A consent policy that maps each acquisition path to recorded evidence
• A change log that ties template edits to campaign updates
• A carrier and CPaaS schedule of fees and throughput that finance maintains

Culture practices that compound:

• Regular creative reviews that include a check for consent and clarity
• Post incident reviews that close the loop with template or registry changes
• Quarterly registry sweeps that archive dormant campaigns and consolidate overlaps
• A budget review that models cost by program and exposure to fee changes

For related context on how regulators and carriers are reshaping messaging programs, see our analysis of what the FCC robocall crackdown means for compliance. The enforcement climate for unwanted calls influenced expectations for unwanted texts, which is why identity, consent, and content alignment now sit at the center of SMS strategy.

Buyer guidance: when to consider short code or toll free

10DLC is a strong default for many programs, but it is not the only path. If you forecast very high volume or need the most resilient identity for a flagship program, evaluate short codes and toll free.

• Short codes. Highest throughput and broad recognition. Longer setup and higher fixed cost. Strong fit for one to many alerts, loyalty programs, and national promotions.
• Toll free. Moderate throughput and fast setup. Useful for service use cases and two way programs where trust and brand name recognition matter.
• 10DLC. Balanced cost and setup time. Strong fit for regional or brand specific programs where identity and purpose are narrow and well documented.

Map these to your roadmap and your traffic concentration. A single program that carries a large share of volume can justify short code investment. A portfolio of many small programs often fits 10DLC well when registrations and governance are solid.

How to explain this to executives

Executives should expect SMS to remain a high return channel when teams do the unglamorous work on identity and consent. The line items for registration and vetting may be new, but they buy fewer incidents, higher delivery, and a better brand experience. The board level message is simple. You are moving from casual sending to regulated infrastructure with auditable controls.

Plan conversations with three artifacts.

• A one page cost model that shows levers and ranges
• A process map for registration, template review, and incident response
• A dashboard that ties delivery and opt out rates to reactivation and revenue

Those artifacts make approvals predictable and help you avoid late surprises when a promotional launch collides with a policy gap.

If you want a control plane that bakes these practices into your workflows, ButterGrow can help. Start with the onboarding flow, connect your brand registry and campaigns, and wire pre send checks into your automations. If you need a quick product overview before you decide, skim the feature set and save answers to common questions for procurement.

References

• Twilio A2P 10DLC registration guide - Official documentation on brand and campaign registration for U.S. SMS.
• CTIA Messaging Principles and Best Practices PDF - Industry guidance on consent, content, and messaging practices.