A2P 10DLC Website Requirements: What Reviewers Check (With a Real Approved Example)

If your A2P 10DLC registration got rejected and you're not sure why, start with your website. It's the most common reason we see registrations bounce. The fix is usually a few paragraphs of text and one form, not a redesign.

Reviewers don't care whether your site is pretty. They visit it to answer three questions:

1. Is this a real business that matches the registration?
2. Will this business protect the phone numbers it collects?
3. Did the people being texted actually agree to it, and do they know how to stop?

Everything below is about answering those three questions clearly enough that a reviewer can say yes in a couple of minutes.

To make it concrete, we'll use a real site that passed: purevida-water.vercel.app, a one-page site we built for PureVida Water Technologies, a commercial water filtration company in Texas. It went live on August 27. The texting registration that used it was approved on August 28.

1. The Business Has to Match

The first thing a reviewer checks is that the website and the registration describe the same business.

That means:

• The legal business name appears on the site, spelled exactly as it is on your registration and your EIN paperwork. PureVida's site says "PureVida Water Technologies LLC", the same as its IRS record, not just "PureVida".
• Contact information is visible: an email address, a phone number, and a business address. They should match what you put in the registration.
• The site explains what you do in a sentence or two. That should line up with the kind of texts you say you'll send. A water filtration company texting about service appointments and invoices makes sense. A water filtration company texting about loan offers doesn't.

What fails here: a "coming soon" page, a site for a different business name than the one registered, a Linktree or Facebook page instead of a website, or a site with no contact details at all.

2. A Privacy Policy That Covers Text Messages

Almost every small business site that has a privacy policy has a generic one, and generic isn't enough. Reviewers look for specific language about mobile numbers.

The non-negotiable part is a clear statement that you don't share or sell phone numbers or opt-in data with third parties for marketing. PureVida's privacy policy puts it right at the top, in its own section:

PureVida Water Technologies LLC ("we," "us," or "our") DOES NOT share customer opt-in information, including phone numbers and consent records, with any affiliates or third parties for marketing, promotional, or any other purposes unrelated to providing our direct services.

Beyond that clause, the policy should cover:

• what information you collect (name, phone number, email);
• how you use it (scheduling, billing, customer support);
• that you keep records of consent;
• how someone can contact you about their data.

What fails here: no privacy policy, a policy that says you "may share information with partners", or a template policy that never mentions text messages.

3. SMS Terms (or a Text Messaging Section in Your Terms)

Reviewers want to see that customers are told how your text program works before they join it. This can be its own page, or a clearly labeled section of your terms of service. PureVida uses a dedicated section at the top of its terms page.

It needs to cover:

• What the program sends: for example, "appointment confirmations, billing notifications, and account updates."
• How often: "Message frequency varies" is fine, or give a number like "up to 4 messages per month."
• "Message and data rates may apply."
• How to stop: "Reply STOP to unsubscribe."
• How to get help: "Reply HELP for help", plus an email or phone number.
• That carriers aren't liable for delayed or undelivered messages.

What fails here: terms that never mention texting, or SMS terms missing the STOP or HELP instructions.

4. An Opt-In Form That Proves Consent

This is the part most small business sites are missing entirely, and it's where reviewers spend the most attention.

If your registration says customers opt in through a web form, that form has to exist on your site. It also needs to be built the right way. On PureVida's contact form:

• The phone number field is optional. Texting isn't a condition of doing business.
• The consent checkboxes start unchecked. A pre-checked box doesn't count as consent.
• There are separate checkboxes for separate kinds of messages: one for service and billing texts, and a second, optional one for promotional texts. Customers can agree to one without the other.
• Each checkbox spells out the details right next to it: the business name, what kind of messages, how often, "Msg & data rates may apply", and "Reply STOP to opt out, HELP for help."
• The privacy policy and terms are linked on the same page, in a short "SMS Program" section below the form.

PureVida's first checkbox reads:

I consent to receive non-marketing messages from PureVida Water Technologies LLC, including service appointment confirmations, billing and invoice notifications, account updates, and customer support communications. Message frequency varies, up to 4 messages per month. Message & data rates may apply. Text HELP for assistance, reply STOP to opt out.

That one checkbox answers nearly every question a reviewer has about consent.

What fails here: no form at all; a form where the phone number is required with no consent language; a single pre-checked "I agree to everything" box; or a form that collects numbers with no mention of texts.

5. Make the Registration and the Website Tell the Same Story

The last check isn't on the website itself. It's whether the website agrees with what you wrote in the registration.

• If your registration says "customers opt in via the form on our website", the form has to be there.
• If your sample messages are billing reminders, the consent checkbox should mention billing.
• The privacy policy and terms URLs you submit should be the actual pages, and they need to load.

This is where a lot of rejections hide. The website is fine and the registration is fine, but they describe slightly different programs, and the reviewer flags the gap.

The Checklist

Before you submit (or resubmit), open your site and confirm:

• Legal business name matches your registration and EIN exactly
• Email, phone, and address are visible
• A short description of what the business does
• A privacy policy that says you don't share or sell phone numbers or opt-in data
• SMS terms covering what you send, how often, msg & data rates, STOP, and HELP
• An opt-in form with an optional phone field and unchecked consent checkboxes
• Consent language that names your business and the type of messages
• Privacy and terms linked on the same page as the form
• Every page loads (no "coming soon", no password, no 404)

If all nine are true, your website won't be the reason you get rejected. For what to expect after you submit, see how long A2P approval actually takes.

Don't Have a Website? We'll Build One.

A lot of the businesses we work with run entirely on referrals, Google Business, or Facebook. They don't have a website, or they have one they can't easily edit. That's a real obstacle for A2P registration, and it's why we stopped asking customers to fix it themselves.

When you get a business phone number with Reach, you fill out a short intake in the app: your business details, what you'll text about, and how customers reach you. We generate a compliant site like PureVida's, with your business information, a privacy policy, SMS terms, and an opt-in form. We host it for you and use it for your registration. Then we file the registration, and the fees are covered by your plan.

You don't have to write a privacy policy or figure out what a consent checkbox should say. It's included.