You need a live, public website that clearly belongs to the same business you registered. It should have a privacy policy that says you do not share mobile numbers for marketing, SMS terms, a compliant opt-in form, contact details, real business pages, and HTTPS. Reviewers check these before approving your campaign.
You submit your own 10DLC registration · No one can guarantee campaign approval
Each item has its own page with the exact wording, the provider rules behind it and what a reviewer sees.
Why parked, for-sale, under construction, login-only, and redirecting websites get 10DLC campaigns rejected, and what to do before you submi...
Read the requirement →Why your 10DLC website and links should use HTTPS: Plivo requires SSL, and Twilio flags http links in samples and wants an https terms URL.
Read the requirement →Why your website, legal name, DBA, domain, and email must line up for A2P 10DLC, and how Twilio and Plivo check brand name matches.
Read the requirement →What business contact info reviewers look for on a 10DLC website: business name, email on your domain, phone, services, and a Contact Us pag...
Read the requirement →What your privacy policy must say for A2P 10DLC approval: the no-sharing SMS clause, frequency and rates, one policy only, plus sample langu...
Read the requirement →How to build an SMS opt-in form reviewers accept: unchecked checkbox, optional consent, disclosure next to the box, privacy and terms links....
Read the requirement →The pages reviewers expect on a 10DLC website: About Us, Contact Us, Terms, Privacy, services, and your texting use case. No form-only landi...
Read the requirement →What SMS terms need for A2P 10DLC: program name, message types, frequency, rates, HELP, STOP, and a public https page. Includes sample terms...
Read the requirement →When you register an A2P 10DLC campaign, your messaging provider sends it to The Campaign Registry (TCR) and on to carriers for review. Someone, or an automated check, opens your website. Twilio says TCR runs automated verification that captures a screenshot of your site. If the site is down, parked, behind a login, or shows a different business name, the campaign can be rejected. If the privacy policy, SMS terms, or opt-in form is missing or weak, it can be rejected too. The good news: the rules are published, and they are mostly the same across providers.
10DLC Site builds carrier-ready websites for A2P 10DLC registration.
| Question | Answer | Source |
|---|---|---|
| Who reviews my campaign? | Your provider (the CSP), TCR, carriers, and vetting partners such as Aegis Mobile and WMC | TCR CSP User Guide |
| What URLs do I submit? | Homepage, privacy policy, terms and conditions, and your opt-in page (in the message flow) | Twilio, Telnyx, Vonage |
| What is now required at Twilio? | Privacy policy URL and terms URL for new API campaign submissions after June 30, 2026 | Twilio changelog |
| How many sample messages? | At least 1 and up to 5 in TCR; Marketing and Mixed need at least 2. Twilio asks for 2 to 5 | TCR, Twilio |
| Campaign vetting fee | $15 per vetting event (Vonage), $15 when sent for carrier review (Telnyx), $15 (Plivo) | Vonage, Telnyx, Plivo |
| Brand registration fee | $4.50 one time (Plivo, Vonage) | Plivo, Vonage |
| Monthly campaign fee | $10 for most standard use cases; Low Volume Mixed $1.50 (Plivo, Vonage) | Plivo, Vonage |
| How long does review take? | Twilio: several days, currently 10 to 15 days. Telnyx: about 72 business hours after Telnyx approval. SignalWire: 3 to 5 business days | Twilio, Telnyx, SignalWire |
Fees and timelines change. Always check your own provider's current page.
Each item below has its own page with sample language, checklists, and common mistakes.
Carriers want to know a real business is sending the texts, and that people agreed to get them. CTIA's Messaging Principles ask senders to get consent, show a clear privacy policy, and make opt-in terms easy to find. Your website is where a reviewer checks all of that. The Campaign Registry says it is "not a compliance house" and points to CTIA guidance, so the details come from CTIA and from each provider.
The rules got stricter and more specific. Here is what the sources show:
Most providers ask for the same four links. Field names differ a little.
| What | Example | Where it goes |
|---|---|---|
| Homepage | https://yourbusiness.com | Website field on the brand or campaign |
| Privacy policy | https://yourbusiness.com/privacy | Privacy Policy URL field |
| Terms (with SMS terms) | https://yourbusiness.com/terms | Terms and Conditions URL field |
| Opt-in page | https://yourbusiness.com/contact | Message flow or call-to-action description |
A few tips from the sources:
Step-by-step guides by provider:
You get a rejection reason, fix it, and resubmit. Your provider shows the reason. Twilio uses numbered error codes, and Plivo shows an error code and reason on rejected campaigns. Twilio says to edit the rejected campaign instead of deleting it.
Resubmission costs are different at each provider. Twilio says it charges the vetting fee once per campaign, so resubmitting the same campaign adds no new fee. Vonage charges $15 for each vetting event. Bandwidth and Telnyx describe a $15 fee on resubmission. Check your provider before you resubmit.
Find your rejection reason:
No one can guarantee approval. Carriers and their vetting partners make the final call, and they look at more than your site: your brand details, sample messages, use case, and message flow all count. A compliant website removes one big set of reasons to reject you. It does not promise the result. Be careful with anyone who says otherwise.
Not sure if your current site passes? Run the free site check. Want all eight requirements built for you on a new .com in about 15 minutes? See pricing.
Start from the exact reason your provider gave you, fix it on your site, then edit and resubmit the same campaign.
10DLC sample messages must match your use case, name your brand, and avoid public link shorteners. See why they fail, wi...
If reviewers cannot see how people agree to your texts, your 10DLC campaign gets rejected. Learn what proof they need an...
Reviewers must open your site with no login, no errors, and no redirects. Learn why 'website not accessible' 10DLC rejec...
Your 10DLC website must show the same business you registered. Learn why the 'website does not match brand' rejection ha...
A 10DLC privacy policy needs a clear SMS no-sharing clause. See why campaigns get rejected for it, a sample clause, and...
Parked, for-sale, and coming-soon pages cannot pass 10DLC review. See why they get rejected, what counts as a real site,...
10DLC campaigns need public SMS terms on your own domain. Learn why missing terms cause rejection, what to include, and...
10DLC reviewers need to see who runs your site and how to reach you. Learn why missing contact info causes rejections an...
A new .com with hosting, SSL, a privacy policy that covers SMS, SMS terms, a compliant opt-in form and real business pages, live in about 15 minutes, then checked every day. You submit your own registration through your provider.
One-time price · 14-day money-back guarantee
For most businesses, yes. Vonage says website information became required for all brands except sole proprietors in 2025, and Twilio rejects campaigns when the site is unreachable, parked, or behind a login. Some providers, like Telnyx and Bandwidth, say a social media or business profile link may work if you have no site.
You usually paste four URLs: your homepage, your privacy policy, your terms (with SMS terms), and the page with your opt-in form. The homepage goes in the website field, the policy and terms go in their own fields, and the opt-in page link goes in your message flow or call-to-action description.
At Twilio, yes, for new campaigns. Twilio says new A2P 10DLC campaigns submitted through the API after June 30, 2026 without a privacy policy URL and a terms and conditions URL are rejected. The Campaign Registry lists those link fields as optional in its own system but says a compliant policy and terms are required.
No. Carriers, The Campaign Registry, and their vetting partners make the final decision, and no website builder or provider can promise the outcome. What you can do is meet the published website requirements so the reviewer has nothing on your site to flag.
It depends on the provider. Twilio's quickstart says campaigns typically take several days and currently 10 to 15 days, and Twilio says standard campaigns can take up to several weeks. Telnyx says carrier review is typically 72 business hours after Telnyx approves it. SignalWire says 3 to 5 business days overall.
What your privacy policy must say for A2P 10DLC approval: the no-sharing SMS clause, frequency and rates, one policy only, plus sa...
How to build an SMS opt-in form reviewers accept: unchecked checkbox, optional consent, disclosure next to the box, privacy and te...
Why your website, legal name, DBA, domain, and email must line up for A2P 10DLC, and how Twilio and Plivo check brand name matches...
The four website URLs every 10DLC registration uses: homepage, privacy policy, terms, and opt-in page. The TCR field model plus a...
Your 10DLC website must show the same business you registered. Learn why the 'website does not match brand' rejection happens and...
Straight answers about 10DLC websites, timing, renewals and refunds.