SMS / 10DLC / Registration

Your Clinic's Texts Stop Delivering Until Your Website Says Who Is Texting

Carriers block texts from unregistered numbers, and the 10DLC review reads your website: the opt-in form, the privacy policy and the terms page. What each has to say.

Builds Shopify, WordPress, Webflow, landing pages, product pages, checkout flows, subscriptions, and intake paths.
Growth Meta, Google, TikTok, Reddit, SEO structure, Klaviyo, SMS, analytics, tracking, and campaign-ready pages.
Health HIPAA-conscious workflows, LegitScript-focused cleanup, telehealth forms, pharmacy disclosures, and compliance-aware site structure.
ToolBX Field Guide / Updated November 2026

The reminders stopped arriving and nothing in the phone system changed

A clinic's appointment reminders, a pharmacy's refill alerts, a brand's shipping texts: messages that worked for years from an ordinary local number start landing as "Spam Risk", or not landing at all. The phone system is fine. What changed is on the carrier side, and part of the fix is on your website.

The major US carriers now expect a business that texts from a ten digit local number, which the industry calls 10DLC, to be registered, and texts from an unregistered number can be blocked or marked as spam. Spruce's help center, written for the clinics on its platform, says the carriers "now require businesses to register and verify their phone numbers", and that calls and texts "from unregistered organizations could be blocked or marked as spam by the major carriers". The Campaign Registry, the database the carriers use, describes 10DLC as "an A2P messaging channel in which Brands and Campaign Service Providers (CSPs) are verified prior to being allowed to send messages."

What most descriptions leave out is that the verification reads your website. The brand registration asks for a live URL. The campaign registration asks how your patients or customers opt in and where. The reviewer then checks that the form, the privacy policy and the terms page say specific things. None of this is legal advice, and the rules are the carriers', not a statute.

Who decides whether my texts go through?

Registration has two layers. The brand is who you are: EIN, legal business name, address and website. The campaign is what you send and how people agreed to receive it. The Campaign Registry's own page: "Currently, direct registration with TCR is not available for Brands. Instead, you must work with one of the registered messaging service providers (CSP) who will handle your registration process on your behalf."

The registry also says who decides. "The Campaign Registry (TCR) does not review, approve, or reject campaigns. This is solely done by the CSPs and their upstream connection partners." Spruce tells its clinics the vetting "can take up to 8 business days to complete, under typical conditions", and that a new EIN means "generally a 4 week delay before we are able to submit your registration".

The principles behind the review come from CTIA, the wireless industry's trade association, whose Messaging Principles and Best Practices, May 2023, calls itself "a set of voluntary best practices" and says it does "not constitute or convey legal advice". Twilio's onboarding guide says campaign vetting exists to "make sure everything aligns with carrier requirements and CTIA guidelines." CTIA writes the principles, the carriers and registrars enforce them in the review, and a rejection is a private company's decision, not a fine.

What does the reviewer look at on my website?

Start with whether it loads. Twilio's guide, under its data consistency checks: "The URL you provide needs to be functional and represent the brand you're registering. Sites that don't load, return errors, or aren't live yet won't pass review." Spruce's version is that the website URL "must be active and cannot be set to private" or marked under construction.

Then whether it is yours. The same Twilio section says "Your brand name, website, and email domain should all clearly connect to the same business. If they point to different entities, reviewers will flag the mismatch". Links inside the messages have to be yours too: "Links within the messaging content must represent the registered brand. Third-party redirects aren't permitted."

CTIA's principles ask the same of any page a text links to. Section 5.3.2: web addresses in messages "as well as any websites to which they redirect should unambiguously identify the website owner (i.e., a person or legally registered business entity) and include contact information, such as a postal mailing address." A footer with the legal entity's name and a mailing address is not decoration. It is what the principles say a linked page should show.

The registration is reviewed against your website, not your phone. A form, a privacy policy page and a terms page are what get approved.

What does the opt-in form have to say?

Twilio's guide calls the message flow, the description of how people consent, "the heart of your registration", and says it is "where most rejections happen." The guide's list of what "A compliant web form must include", in its order:

  1. Phone number input field
  2. Checkbox for consent (must NOT be pre-selected)
  3. Clear description of the type of messages users will receive
  4. Message frequency information
  5. "Msg & data rates may apply" disclosure
  6. Instructions for getting help (reply HELP for help)
  7. Instructions for opting out (reply STOP to opt-out)
  8. Links to Terms of Service and Privacy Policy
  9. Submit button with clear language ("Yes, sign me up!")

Two notes follow. "Marketing and transactional message consent must be consented to separately with two checkboxes." And "A consent checkbox for privacy policy and terms of service must be separate from any messaging consent checkboxes". Three checkboxes, then, for a brand that sends both order updates and promotions, and a single "I agree" fails.

CTIA's call to action principle, section 5.1.1, asks for the same disclosures, the program, the number texts come from, who is sending, the opt-in language with any fees, and the other terms including how to opt out and the privacy policy, then adds the line that catches the most common shortcut: "opt-in details should not be obscured in terms and conditions (especially terms related to other services)." Twilio's guide says its reviewers are "checking to make sure that the call-to-action and the right disclosures are displayed at the time of phone number collection".

The form also has to remember what happened. CTIA names "Entering a telephone number through a website" as an opt-in mechanism and says senders "should also document opt-in consent by retaining" the "Timestamp of consent acquisition", the medium, the wording shown, the campaign, the "IP address used to grant consent", the phone number and who consented. A form that posts a phone number to a spreadsheet keeps one of seven.

Marketing is the exception. CTIA: "Before a Non-Consumer sends promotional messages, the Consumer should agree in writing to receive promotional texts." Twilio: "Verbal consent is not enough for marketing use cases." If the form sits behind a patient login, Twilio asks for "a publicly accessible URL link to a screenshot or image of your webform", plus one of the form after submission.

What do the privacy policy and the terms page have to carry?

Twilio's guide says "Every registration needs to include both a privacy policy and terms and conditions". The privacy policy must disclose what data you collect and how it is used, explain that mobile information and opt-in consent "won't be shared with third parties or affiliates for marketing or promotional purposes", include the sentence "We do not sell or share your SMS opt-in data or personal information with third parties for marketing purposes.", sit on a page titled "Privacy policy", and "Mention the registered brand name". That last one is the quiet failure: a policy written for a trading name that differs from the legal entity in the registration.

The terms must carry the program or brand name, a program description, the message and data rates disclosure, message frequency, customer support contact information, "Complete opt-out instructions (HELP and STOP), displayed in bold", a link to the privacy policy, and a disclosure that states "Carriers are not liable for any delayed or undelivered messages". The links in the registration "should match the links included in your opt-in".

CTIA's principle behind this is section 5.2.1: "All applicable privacy policies should be referenced in and accessible from the initial call-to-action." Spruce's own list for a clinic with a custom opt-in process asks for the same carriers-not-liable statement, "A disclosure that SMS opt-in and consent data will not be shared with any third parties" and "Links to your SMS Terms of Service and SMS Privacy Policy". Three sources, one page.

Who registers, me or my platform?

You. Twilio's guide names the mistake: "If you provide software for dentists, don't register your software company. Register the specific dental practice that's actually sending the messages." Its failing campaign description reads "Messages are sent by {ISV Name} to dental patients", with the note "ISV registered instead of the actual dental practice". So a clinic texting from a telehealth platform, or a brand texting from an SMS app on its store, registers its own legal entity, EIN, address and website, and describes its own opt-in, even when the platform submits the form. Spruce says the requirement "includes organizations that do not have a federal tax ID or formal business structure".

What happens when I switch platforms?

The registration stays behind. Spruce: "Business registration information does not transfer with your phone number when you change service providers. This is not under the control of Spruce or any other service provider." The Campaign Registry says the same from its side: "Each CSP must register the Brands that they are working with, whether or not they have already been registered by another CSP." A vetted brand can hand over its vetting token, but the campaign is registered again, and the registration fees are paid again. The number ports with you and the registration does not, so the website, the form and the two policy pages are the only part of the SMS setup you carry from one platform to the next.

What to have on the site before you submit

  1. A live page at the URL you register, in the registered business's name, with the legal entity and a postal address in the footer. Not a holding page, not behind a password.
  2. An opt-in form with Twilio's nine items, separate checkboxes for transactional and marketing consent and a third for the terms, none pre-checked.
  3. Consent storage that keeps the timestamp, the medium, the exact wording shown, the campaign, the IP address, the number and who consented.
  4. A page titled Privacy policy that names the registered brand and carries the no-sell, no-share sentence.
  5. An SMS terms page with the program name, description, frequency, rates disclosure, support contact, HELP and STOP in bold, a privacy policy link and the carriers-not-liable sentence. What a later STOP has to do is the FCC's rule, and it has its own post.
  6. A confirmation text for any recurring campaign, written before launch, which CTIA's section 5.1.2.1 says should name the program, a customer care contact, how to opt out, that the messages recur and how often, and any fees.
  7. A campaign description that says who sends, who receives and why, in the brand's name, matching the website and the email domain.

A clinic's intake flow collects the phone number at step one, which is where the checkbox and the storage have to live. For a brand on Shopify, the same form sits beside the subscription checkout and its disclosures. Either way the build is the website, and the SMS-ready version of a CPG and ecommerce site is one where the registration can be submitted on launch day instead of after the first blocked text.

Common questions

Why are my business texts not being delivered or being marked as spam?

Check whether the number was ever registered. The major US carriers now require a business that texts from an ordinary ten digit number to be registered as a brand, with its EIN, legal name, address and website, and to register each messaging campaign, with a description of what it sends and how people opt in. Spruce's help center puts it plainly: calls and texts from unregistered organizations could be blocked or marked as spam by the major carriers. The registration is done through your messaging platform, not with the carriers directly.

What does my website need before a 10DLC campaign is approved?

A live page at the URL you register, in the name of the business you register. Twilio's onboarding guide says the URL needs to be functional and represent the brand you are registering, and that sites that do not load, return errors or are not live yet will not pass review. Spruce says the URL must be active and cannot be set to private or under construction. CTIA's principles add that any site a message links to should unambiguously identify the website owner and include contact information such as a postal mailing address. Beyond that, the reviewer looks for the opt-in form, a privacy policy and a terms page.

What has to be on the SMS opt-in form?

Twilio's guide lists nine items for a compliant web form: a phone number field, a consent checkbox that is not pre-selected, a description of the message types, message frequency, the words Msg & data rates may apply, HELP instructions, STOP instructions, links to the Terms of Service and Privacy Policy, and a submit button with clear language. Marketing and transactional consent need two separate checkboxes, and the checkbox for the privacy policy and terms must be separate from the messaging consent. CTIA's principles say the opt-in details should not be obscured in terms and conditions, and that the sender should keep the timestamp, medium, campaign and IP address of each consent.

What does my privacy policy have to say for 10DLC?

Twilio's guide says the privacy policy must disclose what data you collect and how it is used, explain that mobile information and opt-in consent will not be shared with third parties or affiliates for marketing, include the sentence We do not sell or share your SMS opt-in data or personal information with third parties for marketing purposes, sit on a page titled Privacy policy, and mention the registered brand name. CTIA's principles say every applicable privacy policy should be referenced in and accessible from the initial call to action. The terms page carries its own list, including the sentence that carriers are not liable for any delayed or undelivered messages.

Who registers for 10DLC, me or the software platform I text from?

You. The Campaign Registry says a company that wants to text its customers is a brand, that brands cannot register with it directly, and that a registered messaging service provider handles the registration on the brand's behalf. Twilio's guide is explicit about the common mistake: if you provide software for dentists, do not register your software company, register the specific dental practice that is actually sending the messages. The brand in the registration is your legal entity, your EIN and your website, even when the platform submits the form for you.

Does my 10DLC registration move with my phone number when I switch platforms?

No. Spruce's help center says business registration information does not transfer with your phone number when you change service providers, and that this is not under the control of Spruce or any other provider. The Campaign Registry says each service provider must register the brands it works with, whether or not another provider has already registered them, though a brand that has been vetted can hand its vetting token to the new provider. Plan for a fresh brand and campaign registration, and new registration fees, every time you move.

Sources

Want this costed for your build?

Tell us what you already have and what is not working, and we will come back with the shape of the work and what drives the number.

Talk to ToolBX Media
Discovery / Build Map / Next Step

Answer a few questions. We’ll find the cleanest path to launch or scale.

A stepped project quiz gets better answers than a blank contact form. Tell us what you are building, where the friction is, and what needs to happen next.

How we qualify the work

Not every project needs the same build path.

Some brands need a clean launch. Some need a conversion rebuild. Some need intake, checkout, tracking, and follow-up fixed before scaling ads. The quiz helps separate the real need from the surface request.

01

Offer

What are you selling, launching, or trying to make clearer?

02

Friction

Where is the current site, funnel, or backend slowing the business down?

03

Stack

Which tools, platforms, ads, checkout, intake, or email systems are involved?

04

Next move

We map whether this is a focused fix, full build, or ongoing growth system.

Project Type / Timeline / Scope

Map the build before we talk.

Five quick steps. No giant table form. Your answers get packaged into one project inquiry so we can reply with a clearer next step.

Step 1 / 5
Project type

What are we helping you build or improve?

Pick the closest fit. You can explain the details at the end.

Business stage

Where is the brand right now?

This helps us understand whether you need foundation, cleanup, or growth support.

What needs attention

Which parts need the most work?

Select all that apply. This gives us a better picture than one broad message.

Timing and scope

How urgent is this and what kind of scope are you expecting?

This does not lock you into anything. It helps us avoid wasting your time.

Contact details

Where should we send the next step?

Add the basics and anything important we should know before replying.