Rejected by carriers? The website is one of the most common reasons. Fix it today →

This page is for RingCentral RingEX admins whose TCR registration came back rejected, or who want to get it right the first time. RingCentral sends business texts from local numbers, so each brand and campaign goes through TCR and carrier review. RingCentral publishes a detailed list of rejection codes, and many of them are about your website.

10DLC Site is not affiliated with or endorsed by RingCentral. Provider names are used only to describe where information goes. This page describes the flow as documented at the time of writing (Updated September 2026). Screens change, so follow what you see in your account.

Which registration does RingCentral use, and who submits it?

RingCentral uses A2P 10DLC registration with TCR for local numbers. You, as the account admin, fill in the SMS Registration form in the Admin Portal. RingCentral passes it on, and TCR plus carrier vetting partners decide.

Toll-free numbers are different. RingCentral's FAQ says toll-free numbers need their own verification and cannot be assigned to a TCR campaign. The website checks for toll-free verification are close to the same, so one compliant site covers both.

Where do the website URLs go in RingCentral's registration?

RingCentral's docs describe what reviewers need to see, rather than listing every form field. Based on its consent and checklist articles, these are the URLs you should have ready:

URL What RingCentral uses it for
Brand website (homepage) Brand details. RingCentral says a working website is required for approval. Code 9110 fires if it is invalid or inactive.
Web form with SMS consent Consent details. RingCentral asks for the exact URL of the form (code 9105). If the consent sits in one section of a page, it says to use the "Other" method.
Privacy policy Must be linked from the website and from the form. Code 9108 covers missing or non-compliant policies.
Terms of Service (SMS terms) Can be its own page or part of the privacy policy. Code 9608 covers missing disclosures.
Screenshots of consent For non-web opt-in (verbal, email, paper), RingCentral asks for form screenshots or scripts (codes 9104 and 9107).

You also need your EIN, legal name and address exactly as they appear on the IRS SS-4, per RingCentral's registration page. A name mismatch is a brand problem, not a website problem. See brand and EIN mismatch.

What does RingCentral check on your website?

RingCentral's consent guide and checklist describe four things:

  • A real, working site. Your business details, products or services, address and contact info, with no broken links. Code 9304 flags thin sites and broken links.
  • A privacy policy with a no-sharing line. It should explain how you collect and use data, and say that mobile opt-in and text consent are not shared with third parties or affiliates.
  • SMS terms. Message types, "message frequency may vary," "message and data rates may apply," how to text STOP, and how to get help.
  • An SMS-specific opt-in. An optional, unchecked checkbox on the form, separate from other consent, with disclosure text and a privacy policy link nearby.

Why was my RingCentral SMS registration rejected?

These codes come from RingCentral's troubleshooting article. The fixes are paraphrased. Each links to the page on our site that explains the website side.

Code What it means (paraphrased) Fix page
9108 Privacy policy missing or not compliant Privacy policy missing SMS language
9110 Website URL invalid or site inactive Website not accessible
9304 Not enough business info, or broken links Missing contact info
9103 Web form lacks SMS opt-in language Opt-in form
9105 Exact opt-in URL not provided Opt-in not verifiable
9109 Opt-in language is not SMS-specific Opt-in form
9112 SMS checkbox prechecked or mandatory Opt-in form
9607 Unclear how consent is collected Opt-in not verifiable
9608 Terms lack SMS disclosures Missing SMS terms
9106, 9503, 9606 Samples lack opt-out, fewer than three samples, or opt-in/HELP/STOP replies incomplete Sample messages mismatch
2006, CR3018 Brand name differs across description, website and samples Website does not match brand
9209, CR3008, CR3012, CR3013 High-risk finance, lead generation, gambling Prohibited content

RingCentral marks the prohibited-content codes as "do not resubmit." For every other code, you fix the issue and resubmit. For a full walkthrough, see campaign rejected: next steps.

How long does review take, and what does it cost to resubmit?

RingCentral's checklist says the whole TCR process can take 20 to 30 business days. Its SMS registration page says up to four weeks.

On fees, RingCentral says it is not currently charging its own fee for TCR registration. The fees below are pass-through charges from TCR and vetting agencies, as listed at the time of writing:

Fee Amount listed Notes
Brand application and vetting $19 per registration Charged whether the brand is accepted or rejected
Optional third-party brand vetting $40 per registration Optional
Campaign vetting $15 one time Charged again on each resubmission
Low volume campaign $1.50 per month Three-month minimum
Standard campaign $10 per month Three-month minimum

Because each resubmission adds a $15 vetting fee and more waiting, it pays to fix the website before you submit. Check RingCentral's current fee article for amounts.

RingCentral-specific gotchas

  • Consent inside a page section. If your opt-in is part of a longer page, RingCentral says to pick the "Other" method and give the precise URL (code 9105).
  • At least three samples. Code 9503 flags fewer than three unique sample messages.
  • Separate SMS checkbox. A single "contact me by email, phone or text" box fails code 9109.
  • Brand name everywhere. Codes 2006 and CR3018 flag a name that differs across the description, samples and website.

How do I get a website that passes RingCentral review?

  1. The site is live, public, and shows your legal or DBA name. See brand name match.
  2. It lists your services, address, phone and email. See business contact info and content pages.
  3. It loads over https. See SSL and HTTPS.
  4. The privacy policy says text consent is not shared. See privacy policy.
  5. SMS terms cover frequency, rates, STOP and HELP. See SMS terms.
  6. The form has an optional, unchecked, SMS-only checkbox. See opt-in form.
  7. It is not parked or "coming soon." See no parked sites.

Included in your Registration Kit: the campaign description, consent details, and at least three sample messages written for your use case, plus your homepage, privacy policy, terms and opt-in page URLs, ready to paste into RingCentral's SMS Registration form. Build my order →

10DLC Site builds these pages and gives you the exact URLs. You still submit the registration yourself, and carriers make the final decision. For other providers, see the any-provider guide.

Sources

Not sure if your current site is ready? Compare your site with the checklist, or see pricing for a site built for 10DLC review.

Built to these requirements

Get a carrier-ready website, usually the same business day

A new .com with hosting, SSL, a privacy policy that covers SMS, SMS terms and a compliant opt-in form, built to the requirements on this page. You submit your own 10DLC registration, and no one can guarantee approval, but a reviewer will have nothing on your site to flag.

Build my order: from $149 →

One-time price · 14-day money-back guarantee · Daily Compliance Watch

From $149 per websiteBuild my order