Twilio A2P 10DLC Registration Guide: Why Campaigns Get Rejected & How to Pass
Your Twilio A2P 10DLC campaign came back rejected. You fixed the one thing they flagged, resubmitted, and it failed again on something completely different.
That isn't bad luck. That's how the process works.
An executive at a home health care agency walked me through this in his Twilio console this summer. He'd been fighting the same registration for weeks.
Fix the one flagged item, resubmit, watch a different one fail.
"So is there a rhyme or reason to that?" he asked. Everything comes back fine except one field, he said, and then you fix that field, and something else breaks. "I don't get it."
There is a reason. It's mechanical.
Rejections come back one issue at a time, never as a complete list. Every correction resets the review clock and adds at least another 48 hours.
Two bad fields found in sequence cost you at least four days. Five cost you two weeks, and you never see the full list.
Meanwhile, you can't send anything.
For an operations business, that means shift coverage, appointment reminders, and dispatch all sit frozen while you wait in a queue you can't see.
Which is why I wrote this Twilio A2P 10DLC guide. Below I cover:
- Who actually reviews your Twilio registration, and why it isn't Twilio
- How Twilio Trust Hub splits your profile, brand registration, campaign registration, and number registration
- The Twilio 10DLC requirements checklist, and what gets campaigns rejected
- Exactly what to write in every campaign registration field, with templates
- Why texting your own staff needs the same consent as texting customers
- How to register 10DLC phone numbers so you can actually start sending
By the end, you'll know which fields to fix before you hit submit again. All of them, in one pass.
Let's get into it.
Key Takeaways
- Twilio isn't the one rejecting you. It passes your submission upstream to The Campaign Registry and the Direct Carrier Aggregators, and they decide.
- Every correction and resubmission resets the review clock. Each one adds at least another 48 hours.
- Twilio A2P registration has four parts: your customer profile, brand registration, campaign registration, and number registration.
- Twilio names the consent field as the place where most rejections happen. Get your opt-in documentation right before you worry about anything else.
- Consent doesn't transfer between campaigns. One checkbox can't enroll someone in both order updates and marketing.
- Texting your own employees requires the same documented consent as texting customers. There's no internal exemption.
- Carriers match your brand identity byte for byte against IRS records. A missing "LLC" fails it.
- Unregistered 10DLC traffic to US numbers doesn't send slowly. Carriers block it, and Twilio bills you for the blocked messages.
- Twilio publishes five different review timelines across its own documentation, ranging from five business days to 15 days.
Who Actually Reviews Your Twilio A2P 10DLC Registration
Twilio doesn't approve your campaign. It submits it on your behalf.
A2P 10DLC is the US carrier system for Application-to-Person (A2P) messaging sent from 10-digit long code numbers. Before you can start sending SMS messages to US numbers, registration tells carriers who you are and what you send.
Who sits where in the messaging stack
Mobile network operators sit at the top: AT&T, Verizon, T-Mobile.
Beneath them sit the Direct Carrier Aggregators. DCAs are vetting partners. They review campaigns and route traffic into carrier networks.
Beneath the DCAs sit Campaign Service Providers. Twilio is one. MessageDesk is one. So are most other platforms that sell you a text message.
At the bottom is your brand.
You submit through Twilio Trust Hub. Twilio hands your registration to The Campaign Registry, which passes it upstream to the DCAs.
Those aggregators decide whether to verify your brand and whether to approve your campaign. They also set your messages-per-second ceiling for each carrier once you pass.
MessageDesk submits into that same pipeline, as a CSP, on the same terms Twilio does. Neither of us approves anything.
Why Twilio support can't tell you what went wrong
Every new ticket starts from scratch. The rep picking it up has to reconstruct your opt-in method, your declared message types, and your samples before they can advise you.
That's structural, not a competence problem. Nobody in this industry has registration fully solved.
Here's the answer to keep in your head. Twilio submits your A2P 10DLC registration. The Campaign Registry and the Direct Carrier Aggregators review it and approve it.
Twilio is a Campaign Service Provider in that chain, not the approver. That's why Twilio support can rarely tell you why the DCAs declined your campaign.
Twilio Trust Hub, Brand Registration, and Campaign Registration
Twilio A2P registration has four separate requirements. People routinely finish three and wonder why they still can't send.
You complete all four in Twilio Trust Hub, under Messaging and Regulatory Compliance in the console.
One thing to sort out first: only account owners and administrators can submit these forms. If you're not one, you'll get through the whole flow and stall at the end.
The carrier network reviews each stage separately, and each one can fail on its own.
Step 1: Create your customer profile
Your customer profile is the Trust Hub container that holds your business identity.
Enter your legal business name, physical business address, and Tax ID or EIN. Everything downstream inherits from this, so an error here will propagate to your brand and your campaign.
Your contact email and physical address both carry ecosystem-wide limits. Most people don't find out until they hit one.
Step 2: Twilio brand registration
Brand registration tells the carrier network who your business is, and it's where you pay the one-time registration fee.
Carriers match your legal name, EIN, and address against IRS records.
Twilio offers three brand types, and picking the wrong one is its own category of failure.
Read the first row carefully, because it runs opposite to intuition. The Twilio sole proprietor path is for businesses without a tax ID.
If you have an EIN, the Campaign Registry requires a Low-Volume Standard or Standard Brand instead. Twilio's docs warn that registering as a Sole Proprietor anyway incurs fees and hurts your ability to send.
Brand registration is usually the fast part. Twilio's quickstart says The Campaign Registry approves most brands within a few minutes, and we see 10 to 30 minutes on correct submissions.
Treat that window as a diagnostic. If your brand is still pending well past 30 minutes, check your EIN and legal company name, because it's almost always one of those.
A genuine discrepancy sends your brand to manual secondary vetting, which Twilio says takes up to seven days.
Step 3: Twilio campaign registration and your campaign use case
Campaign registration is where most rejections happen, and one field causes most of them.
Your Twilio campaign use case is the first thing you pick, and it shapes every rule that follows. Then you describe your campaign, document how people opted in, and provide sample messages.
Carriers compare every part of it against every other part.
Twilio offers eleven standard use cases. The common ones are 2FA, account notifications, customer care, delivery notifications, fraud alerts, marketing, and security alerts.
The rest cover higher education, polling and voting, public service announcements, and mixed.
Pick the one that honestly matches what you send. Mixed exists for genuinely multi-purpose programs, but Twilio notes it costs more and has lower throughput.
A brand can carry up to five campaigns.
Twilio campaign approval is the gate that actually unblocks sending. The DCAs can verify your brand and decline your campaign in the same week, and that's what makes people think the system is broken.
Step 4: Twilio number registration
This is the one people miss.
Approval doesn't automatically apply to your 10DLC phone numbers. Twilio requires every number to be associated with the approved campaign before it can send.
That means adding it to the Messaging Service attached to that campaign. Every number you send from needs this, not just the first one.
If you didn't already have a Messaging Service, Twilio creates one when you register the campaign. Check for it before you make a second one.
You'll see the same thing in MessageDesk, and the error text is specific.
"Phone number is not registered, please register number to send messages." You haven't tied the number to an approved campaign yet.
"Number is pending association with campaign; this can take up to 24 hours." It's linking, and you don't need to do anything.
Why Your Twilio 10DLC Campaign Keeps Getting Rejected
Carriers reject most Twilio A2P 10DLC campaigns over consent issues. Twilio's own campaign onboarding guide calls the message flow field the heart of your registration. Twilio says that's where most rejections happen.
Carriers return one issue per review cycle, never the full list. A campaign with three problems takes three rounds to surface all three.
Here are the causes in rough order of how often they happen.
1. Incomplete or undocumented consent. Your opt-in description doesn't show a reviewer what the user actually saw when you collected their number. If a reviewer can't see the process, they can't approve it.
2. Bundled, forced, or pre-checked consent. Twilio rejects three versions of this. Opting in as a condition of buying something or creating an account. Consent you've buried in your terms of service. A checkbox you've already ticked for the user. Consent also doesn't transfer between campaigns, so one checkbox can't enroll someone in both order updates and promotions.
3. Mismatched sample messages. Your samples don't match your campaign description or declared use case. On our side, as a CSP running registrations, this is the single most common thing we have to fix before submitting.
4. Brand identity mismatch. Carriers match your EIN byte-for-byte against IRS records. Your legal name, EIN, and address must match your filings exactly, including suffixes. "Acme Services" fails when the IRS has "Acme Services LLC."
5. Missing or incomplete website compliance. Twilio flags sites that don't load, return errors, or aren't live yet. It also flags privacy policies missing the mobile data clause.
6. Inconsistent brand details. Your brand name, website, and email domain must all point to the same business. Twilio calls out corporate brands using Gmail or Yahoo addresses instead of a company domain.
7. PII in your registration fields. Don't put real customer names or phone numbers in your descriptions or samples. Use placeholders.
8. Forbidden content categories. Carriers reject cannabis, firearms, gambling, adult content, and the rest immediately. Repeat violations can lead to permanent blocklisting.
9. Reused contact details across brands. Each phone number can validate three brands or fewer, and each email or physical address 10 or fewer. Those caps run across the entire ecosystem, so registrations through another vendor count against them.
10. Registration fields in another language. Twilio rejects campaigns whose description, message flow, or samples aren't in English.
Corrections and resubmissions reset the review clock to zero, adding at least another 48 hours each.
So don't fix one thing and resubmit. Audit everything below, fix it all, then submit once.
If you'd rather have someone run the submission with you, talk to our team.
I personally help larger customers with these registrations, and this is what costs people the most time. Not the difficulty of any individual field. The serial discovery of which fields are wrong.
What to Write in Every Twilio Campaign Registration Field
Twilio tells you which fields exist. It doesn't tell you what to put in them, and that gap is where most registrations die.
The governing principle is simple. What your customer sees is what Twilio needs to see, with no daylight between the two.
Below is the language MessageDesk submits on behalf of customers, mapped to Twilio's console labels. We spend most of our time on these four fields before any submission goes out.
Campaign description
Twilio's reviewers want three questions answered: who is sending, who is receiving, and why.
Messages are sent by [ORGANIZATION NAME] to [WHO RECEIVES THEM] who have opted in. Messages include [YOUR ACTUAL MESSAGE TYPES, e.g., appointment reminders, rescheduling options, and post-visit care instructions].
One vocabulary trap sinks operational senders here. In carrier language, a campaign is any registered messaging use case, including staff coordination and appointment reminders. Business owners read "campaign," think marketing, and describe an operational program in promotional language.
That mismatch fails vetting on wording alone. Describe what you actually send, in plain operational language, and pick the matching use case.
Two other things will fail this field.
First, keep real customer names and phone numbers out of it.
Second, direct lending has its own rule. If you're a financial institution doing first-party lending, the description has to say "Direct Lending," even if you only send one-time passcodes.
How do end-users consent to receive messages?
This is the message flow field, and Twilio says it's where most registrations die.
Your job is to show a reviewer exactly what the user saw or heard when you collected their number. Your Twilio opt-in documentation has to match what your website actually does, not describe it in the abstract.
Reviewers want to see how users opt in. Each method needs its own flow, and documenting only one is grounds for rejection.
Whichever method you describe, the disclosure has to carry five things:
- What the program is
- "Message and data rates may apply"
- How often you'll text
- How to get help
- How to opt out
US carriers require "Message and data rates may apply" verbatim. They won't approve wording that says "standard rates," because that implies premium-rate messaging, which no longer exists here.
Some opt-ins aren't publicly visible: behind a login, on paper, in an IVR script, or inside an app. Host a screenshot publicly and link it here. A reviewer can't approve it if they can't see it.
Here's the language for the two methods that need it most.
Web form:
[ORGANIZATION NAME] collects opt-ins through the form at [LINK]. Users manually check a consent box that states: [PASTE THE EXACT OPT-IN TEXT FROM YOUR FORM]. The box is unchecked by default, and the phone number field is optional. Privacy policy and terms links appear on the same page.
Verbal. Open with one line naming the method, then give the script itself:
[ORGANIZATION NAME] collects opt-ins verbally. Staff read the following script:
"As part of our service, we can send you text messages regarding [MESSAGE TYPES]. We will send [FREQUENCY]. Message and data rates may apply. At any time, you can get more help by replying HELP, or opt out completely by replying STOP. Our terms are at [URL], and our privacy policy is at [URL]. Would you like to receive these messages?"[ORGANIZATION NAME] records consent in [CRM OR CALL RECORDING].
Verbal consent works for transactional messaging.
Marketing is different. Twilio requires a written method, unless you add a double opt-in on the user's handset to complete express written consent.
Sample messages
Provide two to five. Twilio's console asks for at least two.
Here's a caregiver shift reminder written the way Twilio wants it:
[ORGANIZATION NAME]: Hi {Name}, you're scheduled for the {Date} shift, {Start} to {End}. Reply Y to confirm or call {Phone number}. Reply STOP to opt out.
Here's how that renders once the placeholders fill in:
EverGreen Home Care: Hi Marcus, you're scheduled for the Tue 3/12 shift, 7:00 AM to 3:00 PM. Reply Y to confirm or call (555) 010-2020. Reply STOP to opt out.
Use brackets for anything dynamic, keep the brand name visible, and include opt-out language. Twilio treats real names and numbers in samples as PII and flags them, so the placeholder style isn't cosmetic.
MessageDesk publishes approved and rejected sample messages by use case covering appointment reminders, order updates, invoices, promotions, and account notifications. Model yours on the pattern rather than copying the text, because carriers reject samples that don't match your real business.
If you need a starting point for the wording itself, our sample text message templates are a reasonable place to begin.
Check the boxes that apply: embedded links, embedded phone numbers, direct lending content, and age-gated content.
On a mixed use case, include samples of every message type you send. Showing the appointment reminder but not the promotion is grounds for rejection.
Use full URLs rather than shorteners, and make sure any link points to your own registered brand. Carriers don't permit third-party redirects.
Opt-in confirmation
Every recurring campaign needs one, no matter how the person opted in. The first message someone receives has to tell them how to get help and how to quit.
Welcome to [ORGANIZATION NAME]! You'll receive up to [N] msgs/month regarding [MESSAGE TYPES]. Msg & data rates may apply. Reply HELP for help, STOP to cancel.
Opt-in, opt-out, and HELP keywords
Twilio requires opt-in keywords and a message only if people can text a keyword to subscribe; if they can't, leave those fields empty.
You need opt-out and HELP fields if you manage those yourself rather than using Twilio's defaults or Advanced Opt-Out. Twilio recommends keeping the defaults unless you have a reason not to.
Either way, a Twilio STOP message has to work automatically the moment you go live. Carriers test this.
Opt-out message:
You are unsubscribed from [ORGANIZATION NAME] messages. No more messages will be sent. Reply HELP for help.
Help message:
[ORGANIZATION NAME]: For help, email [SUPPORT EMAIL] or call [PHONE]. Msg & data rates may apply. Reply STOP to cancel.
Texting Your Own Employees Still Needs Consent
This catches operations businesses all the time, and almost nothing written about 10DLC mentions it.
If you're texting staff rather than customers, the rules don't relax. Twilio is explicit about this. The consent and disclosure requirements are identical whether the recipient is a customer or a staff member.
You might own the account. You might even own the phones. It doesn't matter.
A dispatcher texting drivers needs the same documented opt-in as a retailer texting shoppers. So does a coordinator texting placed workers, and a home care agency texting caregivers.
MessageDesk sees this fail most often in staffing and home care, where the entire contact list is employees and nobody thought to collect consent.
Most assume the employment relationship covers it. It doesn't, and a campaign description that says "we text our employees about shifts" with no consent flow attached will fail.
In practice, it's straightforward.
Add SMS consent to your onboarding paperwork. It needs the same five disclosures, an unchecked box or a signature line, and a link to your privacy policy.
Photograph it and submit that as your opt-in proof. If you onboard verbally, use a script and record consent in your HR system or ATS.
One more thing. Because consent doesn't transfer between campaigns, consent to shift reminders isn't consent to recruiting messages or company announcements. Send both, and you need both opt-ins.
Twilio SMS Compliance: The Exact Website Changes Carriers Check
Carriers don't take your word for your website. A reviewer opens it and reads it.
Twilio 10DLC requirements split into two halves. Everything above happens inside the console. Everything below happens on your site, before you submit.
The privacy policy clause reviewers look for
Your existing privacy policy is fine. You don't need a separate one for SMS, though Twilio suggests messaging-specific documents are easier to keep current.
Reviewers scan for one specific promise about mobile data. Twilio's documentation gives this as the language it looks for:
All the above categories exclude text messaging originator opt-in data and consent; this information won't be shared with any third parties.
A plainer version that also passes:
No mobile information will be shared with third parties or affiliates for marketing or promotional purposes.
Leave that promise out, and carriers reject your campaign. The requirement comes from CTIA's Messaging Principles and Best Practices, not from Twilio.
One point of confusion worth clearing up. This doesn't stop you from sharing data with vendors who help you run your business, like your CRM or your texting platform. The prohibition is on sharing for marketing or promotional purposes.
Beyond that clause, your policy needs four things:
- What data you collect and how you use it
- Your opt-in method
- Opt-out instructions
- A support contact
MessageDesk publishes the full SMS privacy policy requirements and a downloadable template you can adapt.
What your SMS terms and conditions have to include
These can live on their own page or inside your privacy policy, as long as a reviewer can reach the language.
Twilio checks for eight things:
- Program or brand name
- Program description
- "Message and data rates may apply"
- Message frequency, or a recurring message disclosure
- Customer support contact information
- Complete opt-out instructions covering HELP and STOP, displayed in bold
- A link to your privacy policy
- A statement that carriers are not liable for delayed or undelivered messages
Bold formatting for opt-out instructions is a real requirement, not a style note.
Where to link both documents
The footer isn't enough on its own, and this trips up submissions that otherwise look clean.
Link your privacy policy from the global footer. Then link it from every place you collect a phone number:
- Opt-in forms and checkouts
- Chatbot flows
- Landing pages and popups
- Paper or in-store signups, via a QR code or short link
A reviewer who finds a form collecting phone numbers with no policy link next to it has found a reason to decline you.
Before you submit
Run this against your live site:
- Click every link you submitted and confirm it loads publicly from anywhere
- Website live, no 404s, showing the same legal name you registered
- Privacy policy published with the mobile data clause
- SMS terms published, covering all eight points
- Both linked from the footer and from every phone number collection point
- Consent checkbox present, unchecked by default, and separate from your terms of service
- Phone number field optional, and the form submits with the SMS box left blank
- Separate consent for marketing and transactional messages
- Your company domain on your website and your contact email
Our SMS compliance checker scans your site for part of this automatically. If you're starting from nothing, generate an SMS privacy policy and terms first.
None of this is legal advice, and MessageDesk isn't a law firm. Review the language with your own counsel and make sure it describes what your business actually does.
How Long Twilio A2P 10DLC Registration Takes
A clean submission with zero errors clears carrier review in about 48 hours. Everything past that comes from your own resubmissions.
Here's the published timeline for what carrier registration requires through MessageDesk:
The Twilio path skips the MessageDesk review step and goes straight to the same upstream carrier review.
How long does Twilio A2P take according to Twilio?
Five different answers, depending on which Twilio page you land on.
Twilio's A2P 10DLC Campaign Vetting FAQ says up to five business days for standard use cases. Twilio's Campaign Onboarding Guide currently carries a banner saying the same.
Twilio's "What is A2P 10DLC" article says about seven business days, with a banner warning of up to 10. The registration quickstart says 10 to 15 days, and the throughput and Trust Score article says five to 10.
Five numbers, five Twilio properties, one process.
That spread isn't Twilio being careless. It reflects a queue nobody downstream controls, so don't build a launch date around any single published figure.
What makes Twilio registration take longer
Every resubmission adds at least another 48 hours. They compound, because you only learn about one problem per cycle.
A brand-new EIN can also fail identity verification for reasons unrelated to your submission. If yours is less than about 30 days old, carrier records may not have caught up, so wait roughly 30 days and resubmit.
I won't promise you an approval date, because approval isn't ours or Twilio's to give. What I can tell you is what the process takes when it goes right and what makes it take longer.
Twilio Toll-Free Verification vs 10DLC Registration
All of the above assumes local numbers. If you're on toll-free, the process is different.
Not sure which you have? Toll-free numbers start with 800, 888, 877, 866, 855, 844, or 833. Anything else is a local 10-digit number.
Send from a local number to register for A2P 10DLC. Send from a toll-free number, and you complete toll-free verification instead. Run both, and you complete both.
The same website and privacy expectations apply to toll-free. Different form, same reviewer reading your site.
There's a third sender type worth naming so you can rule it out. A short code is a five- or six-digit number used mostly for high-volume marketing programs.
Short code traffic skips A2P 10DLC brand and campaign fees but carries its own application process and pricing. Almost every operations business reading this will want a traditional 10DLC number.
Twilio 10DLC Pricing, Fees, and Throughput Limits
Twilio A2P 10DLC pricing and fees
Twilio A2P 10DLC pricing sits on top of your per-message cost.
Twilio 10DLC fees fall into three buckets:
- A one-time brand registration fee
- A campaign vetting fee
- A recurring per-campaign carrier fee
Twilio's documentation calls the campaign vetting fee non-refundable, and it applies to post-approval campaigns too.
If you're registering through MessageDesk, we don't charge extra. We bundle carrier and campaign fees into your subscription price.
What happens if you don't register
Carriers block unregistered A2P traffic to US numbers. Twilio returns error 30034, "Message from an Unregistered Number," and that's been a full block since August 2023, not a filtering penalty.
Twilio still bills you for those blocked messages. Unregistered traffic also carries higher per-message carrier fees.
You may have read that unregistered numbers just send slowly, at one message per second. That was Twilio's standard rate for US long codes before A2P 10DLC, and it no longer applies.
There's no slow lane now. You're either registered or blocked.
Throughput limits and why more numbers won't help
Twilio allocates throughput per campaign, based on your brand type, your use case, and, for Standard Brands, your Trust Score from zero to 100.
Two consequences follow. Adding more phone numbers to a campaign won't raise its throughput ceiling, because the ceiling belongs to the campaign. And Trust Scores are static, so they don't drift upward as you build sending history.
Sending more than 2,000 messages per day requires enhanced carrier vetting and may incur additional fees.
Sole Proprietor and Low-Volume brands skip secondary vetting entirely. They never receive a Trust Score, so their use case permanently sets throughput.
Outgrow those limits, or add an EIN, and Twilio requires a move to a Standard or Low-Volume Standard Brand. That's a separate customer profile, brand, and campaign. Not an edit to what you have.
On the MessageDesk side, the answer is simpler and more restrictive. Registration requires a legal entity with an EIN, and MessageDesk doesn't register sole proprietorships.
What to Do If You Don't Want to Run Twilio Registration Yourself
You have three real options. All three are legitimate, and only one involves us doing your registration.
1. Finish with Twilio. Everything above is what it takes.
Your registration, numbers, and billing stay in your Twilio account. Once carriers approve you, you can connect your Twilio numbers to a shared team inbox without registering again. That takes your Account SID and Auth Token, plus the numbers you want to add.
2. Register through MessageDesk instead. MessageDesk is a Campaign Service Provider. It runs carrier registration as a guided, managed submission on its own carrier providers.
This is a new submission on different numbers. It isn't a rescue if you're stuck with Twilio.
3. You're already registered and just need somewhere to work the replies. Connect the numbers you have to a Twilio SMS inbox, with no second registration.
Note that MessageDesk does not register Twilio BYOC numbers with the carrier network. You register those yourself through your Twilio account.
If you've completed that registration, your numbers already carry an approved campaign when you connect them. If you haven't, connecting them to MessageDesk won't register them.
We can't take over a pending Twilio submission or fix one mid-review. We can tell you what to change before you resubmit.
If you want help figuring out which path fits your setup, talk to our team.
Frequently Asked Questions About Twilio A2P 10DLC Registration
Why does my Twilio A2P 10DLC campaign keep getting rejected?
Most rejections trace to consent. Twilio's own campaign onboarding guide calls the message flow field the heart of your registration, and says that's where most rejections happen.
Mismatched sample messages, brand identity mismatches against IRS records, and website problems come next. Rejections come back one issue at a time, so fix everything you can find before you resubmit.
Who actually reviews a Twilio A2P 10DLC registration?
Twilio passes your submission upstream. The Campaign Registry and the Direct Carrier Aggregators do the vetting. They sit between messaging providers and the mobile carriers.
Twilio is a Campaign Service Provider in that chain, not the approver. That's why Twilio support can rarely tell you why the DCAs declined your campaign.
What happens if I send from an unregistered Twilio number?
Carriers block the message. Twilio returns error 30034, and the block has been total since August 2023, not a partial filter.
Twilio still charges you for blocked messages, and unregistered traffic carries higher carrier fees on top of that.
Do I need consent to text my own employees?
Yes. Twilio is explicit here. The rules are the same whether the recipient is a customer or a staff member.
Add SMS consent to your onboarding paperwork, with the standard disclosures and an unchecked box or signature line. Submit that as your opt-in proof.
Consent to shift reminders also isn't consent to recruiting messages. Send both, and you need both opt-ins.
Can I use verbal opt-in for A2P 10DLC?
For transactional messaging, yes, with a verbatim script and a record of consent in your CRM or call recordings.
For marketing, verbal alone isn't enough. Twilio requires a written method. The exception is a double opt-in on the user's handset, which completes express written consent.
What is Twilio Trust Hub?
Twilio Trust Hub is where you complete regulatory compliance work in the Twilio Console. That covers your customer profile, brand registration, and campaign registration.
You'll find it under Messaging and Regulatory Compliance. Only account owners and administrators can submit these forms.
How long does Twilio A2P 10DLC registration take?
A clean submission typically clears carrier review in about 48 hours. Twilio's own documentation publishes figures ranging from five business days to 15 days across five different pages.
All of those assume no errors. Every correction resets the clock and adds at least another 48 hours, which is how registrations stretch into weeks.
How long does Twilio 10DLC verification take for the brand specifically?
Brand registration is usually the fast part. Twilio says The Campaign Registry approves most brands within a few minutes, and we see 10 to 30 minutes on correct submissions.
If yours is still pending well past that, check your EIN and legal company name first. A genuine discrepancy sends the brand to manual secondary vetting, which takes up to seven days.
Can I register a sole proprietorship for A2P 10DLC?
On Twilio, yes, through the Sole Proprietor Brand path, but only if you don't have an EIN. If you do have an EIN, register as a Low-Volume Standard Brand or Standard Brand instead.
Twilio warns that registering as a Sole Proprietor anyway incurs fees and limits your sending. MessageDesk doesn't register sole proprietorships at all.
Why can't I send after my Twilio campaign was approved?
Approval doesn't automatically apply to your phone numbers. You have to associate every 10DLC number with the approved campaign. That means adding it to the Messaging Service attached to that campaign.
Linking a number to a campaign can take up to 24 hours.
Can MessageDesk fix a Twilio registration that keeps failing?
Not directly. If you bring your own Twilio numbers, carrier registration stays in your Twilio account.
You can register through MessageDesk as a separate submission with our carrier providers. Or finish with Twilio and connect your numbers to a shared inbox afterward, with no second registration.
Sources and Further Reading
- The Campaign Registry: the registry that holds brand and campaign records for US A2P messaging
- CTIA Messaging Principles and Best Practices: the industry guidelines carriers vet against
- Twilio: A2P 10DLC Campaign Onboarding Guide: field-by-field requirements and common rejection reasons
- Twilio: How do I register to use A2P 10DLC messaging: Twilio's own registration guide
- Twilio: Message throughput and Trust Scores for A2P 10DLC: brand types, throughput tiers, and Trust Score mechanics
- Twilio: Error 30034, message from an unregistered number: what happens when you send before registering
- Twilio: A2P 10DLC Sole Proprietor Brands FAQ: eligibility and limits for sole proprietor registration
- MessageDesk: what carrier registration requires
- MessageDesk: registration errors and how to fix them
- MessageDesk: SMS privacy policy requirements
The privacy policy and SMS terms guidance here is general information. It's meant to help you meet carrier registration requirements. It isn't legal advice, and MessageDesk isn't a law firm. Review your policies with your own counsel and make sure they describe what your business actually does.