A2P 10DLC before your SMS automation: the builder's guide
The registration step that blocks every missed call text-back build: brand before campaign, the sole proprietor route, real fees and why campaigns fail.
What you get from this guide
- Why unregistered SMS automation fails silently rather than erroring, and what that costs you
- The brand-then-campaign order, and what each one is actually asking for
- The sole proprietor route, its documented daily caps, and who it is genuinely for
- Twilio's published fees as of August 2026, with the caveats they deserve
- The opt-in evidence and privacy policy language that decide whether you are approved, by error code
What A2P 10DLC is and why it blocks you
Every guide to missed call text back, appointment reminders, and quote follow-up by SMS has the same hole in it. They describe the trigger, the message, the branching, and the calendar booking, and they skip the step that determines whether any of it reaches a phone. This page is that step.
Twilio defines A2P 10DLC as the standard United States telecom carriers have put in place to ensure that SMS traffic to US end users through long code phone numbers is verified and consensual. A2P means application-to-person: a message sent by software rather than typed by a human. 10DLC means a ten-digit long code, which is an ordinary phone number as opposed to a short code or a toll-free number.
Put together: if your automation sends a text from a normal US phone number, carriers want to know who you are and that the recipient agreed to hear from you. Registration is how you tell them.
The failure mode that wastes weeks
Two things this does not cover. Toll-free numbers use a separate verification process rather than 10DLC registration. And this is a US regime - other countries have their own rules, and sending internationally means researching each destination separately.
Brand first, then campaign
Registration has two objects and they are not interchangeable. Twilio's documentation is explicit that you create a Brand first, then establish a Campaign under that Brand.
| Object | What it establishes | What you submit |
|---|---|---|
| Brand | Information about your organisation identifying you as a legitimate sender to carriers. | Legal business name, tax ID where applicable, address, website, and an authorised representative. |
| Campaign | Details about how users opt in and out, get help, and what the messaging is for. | Use case, campaign description, sample messages, and the full message flow or call to action. |
The order matters practically, not just procedurally. A brand rejection blocks the campaign entirely, and brand problems are usually data problems - Twilio notes that brand registrations may fail if the business information is incomplete, formatted incorrectly, or does not match existing records. That means the legal name and tax ID you submit have to match your tax registration exactly, not the trading name on your van.
Campaign rejections are different in character: they are content and evidence problems, and they are the ones that come back repeatedly if you do not fix the underlying issue. Most of this guide is about those.
Get the website and privacy policy right first
Both are checked before you are approved and both are trivially fixable in advance. The business URL must be publicly accessible with real content - Twilio lists websites that are empty, under development, password-protected, inaccessible, misspelled, or not matching the business name as common rejection causes. If you genuinely have no website, Twilio's guidance allows substituting a verified social media page such as LinkedIn.
Pick the correct brand type
Twilio's guidance is direct: sole proprietor brands require no tax ID, while businesses with an EIN must register as Standard brands, and mismatched applications get rejected. Do not choose the sole proprietor route because it looks cheaper or faster if you have an EIN. Choose based on what your tax records say.
Submit the brand and wait for approval
Copy details from official documents rather than typing them from memory. An abbreviation, a missing suffix like LLC, or a suite number formatted differently from your registration is enough to fail the match. Some brands trigger secondary vetting, which adds time and, in some cases, a fee.
Only then register the campaign
With the brand approved, submit the campaign: use case, description, samples, and message flow. The next two sections are entirely about getting this submission right first time, because the resubmission loop is where projects lose their week.
The sole proprietor route
Twilio describes the sole proprietor option as suiting a student, a hobbyist, someone working at an organisation, or someone trying out Twilio messaging products for the first time. It does not require a business tax ID, which is what makes it attractive to owner-operators who have not incorporated.
The documented limits, as of August 2026:
| Limit | Figure | What it means in practice |
|---|---|---|
| Campaigns per brand | One | All your messaging shares one campaign. Reminders, follow-ups, and text-back all sit under a single registered use case. |
| Daily volume to T-Mobile | 1,000 SMS segments and MMS per day | The binding constraint, since T-Mobile carries a large share of US mobile numbers. |
| Daily volume across US carriers | Approximately 3,000 SMS segments and MMS per day | Twilio's own approximation derived from the T-Mobile cap. |
| Throughput | Reported at around one message per second | Fine for conversational and triggered messaging. Not fine for a bulk send to a list. |
| Tax ID | Not required | The reason the route exists. Identity is verified another way. |
Count segments, not messages
For a single trades business running missed call text back and appointment reminders, these caps are comfortable. They become real if you run one number across multiple client businesses, or if you are sending marketing broadcasts rather than triggered conversational messages. If you have an EIN, register as a Standard brand instead - you get more campaigns and higher throughput, and it is the correct classification anyway.
What it costs
Registration fees are small enough that cost is almost never the reason not to register. Twilio's published figures for the sole proprietor route as of August 2026 are a one-time brand registration fee of $4, a one-time campaign vetting fee of $15, and a monthly campaign fee of $2. Twilio applies a $15 campaign verification fee at the time of vetting across brand types, and low volume standard brands carry their own registration and higher monthly campaign fees.
Separate from registration, there are per-message carrier fees on every segment. Twilio describes both categories as charged by carriers as part of the A2P 10DLC system and passed through to customers with no added cost.
| Fee | Type | Notes |
|---|---|---|
| Brand registration | One-time | $4 for sole proprietor. Standard and low volume standard brands are priced differently and have been repriced by The Campaign Registry more than once. |
| Campaign vetting | One-time | $15 at the time of vetting, applied to Standard, low volume standard, and sole proprietor campaign registrations. |
| Campaign monthly | Recurring | $2 per month for sole proprietor. Higher for other brand types. |
| Carrier per-message fees | Per segment | Charged by carriers on top of your provider's messaging rate and passed through. Varies by carrier and message type. |
| Secondary vetting | Situational | Some brands are put through additional vetting, which can carry its own fee. |
Treat every figure here as dated. Carrier and Campaign Registry pricing has changed several times, sometimes with a month's notice, and Twilio's pricing page is the authority rather than this one. The planning point that does not change: registration is tens of dollars, and the real cost of A2P 10DLC is the calendar time a rejection costs you.
Opt-in evidence: the thing that gets you rejected
If you read one section of this guide, read this one. Twilio names opt-in requirements as a major cause of A2P 10DLC campaign rejections, and error 30909 - message flow or call to action incomplete or unverified - fires when reviewers cannot verify how users consent to receive messages.
The reviewer is a human who needs to be able to go and look at the place where consent happens. That means three things have to be true.
The consent flow must be publicly reachable. A form behind a login, a flow that only exists in your CRM, or a description of something offline all fail. Where the opt-in genuinely happens offline - a paper form, a verbal script at the end of a service call - host screenshots or a copy of the script at a public URL and cite it.
The disclosures must all be present. The documented requirements are the program or brand name, message frequency disclosure, the "message and data rates may apply" language, links to your privacy policy and terms, and clear opt-out instructions such as "Reply STOP".
The privacy policy must contain the mobile data language. Twilio's guidance is that the policy must state that mobile information of the end user opting in to the message program will never be shared or sold to third parties, or equivalent language, and describes the absence of this statement as a major rejection source. This single paragraph is missing from most small business privacy policies.
Opt-in text under your web form
By providing your mobile number you agree to receive
text messages from {Business Name} about your enquiry,
quote, and scheduled appointments. Message frequency
varies. Message and data rates may apply. Reply STOP
to opt out or HELP for help.
See our Privacy Policy [link] and Terms [link].Privacy policy paragraph you are probably missing
Mobile Information and SMS
Mobile information collected when you opt in to
receive text messages from {Business Name} will never
be shared or sold to third parties or lead generators
for marketing or promotional purposes. Information
sharing with subcontractors that support our services,
such as our messaging provider, is limited to what is
required to deliver those messages.When you write the message flow field itself, describe every opt-in path you have in that one field, name the actual URL, and list the disclosures present at that URL. Twilio's documentation is explicit that vague descriptions like "end users opt in on our website" fail review while specific descriptions naming URLs and listing all disclosures pass. The same applies to the campaign description: say who sends messages, who receives them, and why, rather than "sends messages to customers".
Why campaigns get rejected, by error code
Twilio publishes error codes for campaign rejections, which is genuinely useful because it turns a vague refusal into a specific thing to fix.
| Code | Meaning | The actual fix |
|---|---|---|
| 30909 | Message flow or call to action incomplete or unverified. | Make the consent flow publicly reachable, list every opt-in path in the message flow field, and include all required disclosures. |
| 30927 | Opt-in evidence is for a different company. | The consent language, website, or opt-in flow names a company that is not the registered brand. Align the trading name, the website, and the brand registration. |
| 30912 | A2P 10DLC is for application-to-person messaging only. | The campaign as described looks like person-to-person traffic. Describe the automated, application-driven nature of the messaging explicitly. |
| 30902 | A carrier rejected the campaign registration request. | A carrier-level refusal rather than a Twilio one. Read the specific reason returned and work through Twilio's campaign troubleshooting guidance. |
- Business URL that is empty, under development, password protected, misspelled, or does not match the business name.
- Legal name or tax ID that does not match official records - the leading cause of brand rather than campaign failure.
- A privacy policy with no statement that mobile information is not shared or sold.
- Sample messages that do not carry the business name or opt-out instructions.
- Sample messages describing traffic different from the campaign description.
- Applying as a sole proprietor when the business has an EIN.
- One opt-in path documented when several exist.
The pattern across all of them is consistency. The reviewer is checking that your brand, your website, your opt-in flow, your campaign description, and your sample messages all describe the same business sending the same kind of message to people who agreed to receive it. Every rejection is some version of those five things not matching.
Planning the build around the wait
The practical consequence of everything above is a change to your project order. Registration is not a deployment task, it is the first task.
- Day one: fix the website and add the privacy policy paragraph. Publish the opt-in page. These are the prerequisites, and they take an afternoon.
- Day one: submit the brand. Nothing else can start until it is approved, so it should never be waiting on you.
- While the brand is in review: build the automation. The workflow logic, the classification, the calendar integration, and the escalation path are all independent of registration.
- Brand approved: submit the campaign with the message flow written to the standard in the opt-in section above.
- Campaign approved: attach your numbers, then send a real test to a handset on a major carrier and confirm arrival. Do not trust an accepted API response.
- Go live, and keep STOP handling working on every workflow that can send, not just the one you tested.
One last thing worth internalising: registration is permission to send, not permission to send anything. The campaign you registered describes particular traffic to people who consented to it. Reusing that number for a different kind of message later - a promotional broadcast under a campaign registered for appointment reminders, say - is the sort of drift that gets numbers filtered again, and it is easy to do by accident when a second workflow reuses an existing credential.
With registration done, the builds themselves are covered elsewhere on this site: the missed call text back with n8n guide for the full workflow, Housecall Pro's text-back gap if you already run HCP, and AI appointment reminders for the reminder cadence. The HVAC and plumbing and cleaning company pages cover which SMS workflows are worth registering for first. For budgeting, see what an automation build actually costs and AI automation cost.
FAQ
- What is A2P 10DLC?
- Twilio describes it as the standard United States telecom carriers have put in place to ensure that SMS traffic to US end users through long code phone numbers is verified and consensual. It applies to messages sent by an application to a person, as opposed to a person texting another person. In practical terms, if a workflow sends the text rather than a human typing it, it is A2P traffic and it has to be registered.
- Do I really have to register, or can I just send?
- You can send, and carriers can filter it. That is the trap: your provider accepts the message, the API returns success, and the message never reaches the handset. Unregistered application-to-person traffic on a US 10-digit number is subject to carrier filtering, and because the failure is silent your automation looks like it is working while the leads go nowhere. Register first.
- Which comes first, the brand or the campaign?
- The brand. Twilio's documentation is explicit that you create a Brand first and then establish a Campaign under that Brand. The brand carries information identifying your organisation as a legitimate sender; the campaign carries the messaging purpose and how users opt in and out. A campaign cannot exist without an approved brand above it, which is why a brand rejection stops everything.
- What are the sole proprietor limits?
- Twilio documents the sole proprietor route as suited to a student, hobbyist, someone at an organisation, or someone trying Twilio messaging for the first time, and it does not require a business tax ID. The documented limits are a maximum of one campaign per brand and a daily volume of 1,000 SMS segments and MMS per day to T-Mobile, which Twilio puts at approximately 3,000 SMS segments and MMS per day across US carriers. Sole proprietor throughput is also reported at around one message per second. Those figures are as of August 2026 - confirm current limits with Twilio before committing, as carrier rules change.
- How much does A2P 10DLC cost?
- Twilio's published fees for the sole proprietor route are a one-time brand registration fee of $4, a one-time campaign vetting fee of $15, and a monthly campaign fee of $2, as of August 2026. Campaign vetting at $15 applies across brand types. On top of registration there are per-message carrier fees, which Twilio describes as charged by carriers and passed through to customers without markup. These figures move when carriers and The Campaign Registry change their pricing, so treat them as an order of magnitude rather than a quote and check Twilio's current pricing page.
- How long does approval take?
- Twilio does not publish a guaranteed timeline in the documentation we could verify, and the honest answer is that it varies with brand type, whether secondary vetting is triggered, and how clean your submission is. Plan for it in days rather than minutes, submit it as the first task of the project rather than the last, and build everything else while it is in review. A rejection and resubmission cycle is where the real delay lives, which is why the opt-in section of this guide is the longest one.
- What is the single most common reason campaigns get rejected?
- Opt-in evidence. Twilio's own guidance names opt-in requirements as a major cause of A2P 10DLC campaign rejections, and the specific error codes back it up: campaigns are rejected when the message flow or call to action does not give reviewers enough information to verify how end users consent, and separately when the opt-in evidence identifies a company that does not match the registered brand. A vague description like end users opt in on our website fails review.
- Does my privacy policy really matter?
- Yes, and this catches almost everyone. Twilio's guidance is that the privacy policy should confirm mobile information will never be shared or sold to third parties or lead generators, and describes the absence of that language as a major source of 10DLC rejection. It also needs to be reachable through a clearly labelled link from the opt-in call to action. Adding one paragraph to your privacy policy is the cheapest thing on this page and one of the most likely to be missing.
Done for you
Want the registration handled alongside the build, so nothing waits on a rejected campaign?
We do A2P 10DLC registration as part of any SMS automation we build - the opt-in page, the privacy policy language, the message flow written to pass first time, and the workflow behind it. The audit that scopes it is free.
The consult is free, and you keep whatever we build.
Keep building
The rest of the cluster
Missed Call Text-Back with n8n (Free Build Guide)
Twilio trigger, business-hours guard, AI qualification, calendar booking, and the A2P 10DLC registration step.
Read the guideHousecall Pro Missed Call Text Back: Setup and Gaps
One text, then silence: what HCP documents, and the two-way build that answers the reply.
Read the guideAI Appointment Reminders That Cut No-Shows
Two-way confirm and reschedule, waitlist backfill, cadence, and SMS compliance basics.
Read the guideFree AI Automation Audit Template
Score every recurring task and rank the top three worth automating before you build anything.
