Infobip needs a live, accessible brand website with a company description, services, contact details and business purpose. Your campaign needs a working terms link, a privacy policy or statement that excludes sharing mobile opt-in data, and an opt-in that requires a clear action such as an unchecked checkbox.
This page is for businesses that send US texts through Infobip on 10-digit local numbers. Infobip's flow is: get a number, register a brand, create a campaign, then send once the campaign is approved. Reviewers use your website to confirm the business is real and that people agreed to get your texts.
10DLC Site is not affiliated with or endorsed by Infobip. 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.
Infobip supports 10DLC, toll-free, and short code, and you submit the brand and campaign yourself. You can do it in the Infobip web interface or through Infobip's USA Number Registration API. Every campaign must belong to a brand. The Campaign Registry (TCR) marks the brand Verified or Unverified. Infobip's API docs say an Unverified brand cannot submit campaigns.
Infobip's campaigns guide lists what a campaign covers: use case, program description, expected volume and frequency, sample messages, STOP and HELP keywords, call-to-action, opt-in and opt-out flow, and support contact.
| URL | Where it goes in Infobip |
|---|---|
| Business website (homepage) | Brand registration. Infobip lists Website with Legal Company Name, DBA, Address, Business Information, and Contact Email. |
| Terms and conditions (with SMS terms) | Campaign. The API parameter is termsAndConditionsUrl (optional in the API, but code 3007 rejects missing or incomplete terms). |
| Privacy policy | Inside the call-to-action text. The API reference notes a separate privacyPolicyUrl only for toll-free campaigns. |
| Opt-in page or opt-in evidence | The campaign's opt-in flow and call-to-action. For keyword opt-in, the API uses optIns.keyword.callToAction. |
Infobip's API example puts a terms and privacy link at the end of the call-to-action text. That is the pattern to follow when your privacy policy has no field of its own.
Included in your Registration Kit: the program description, call-to-action and opt-in flow text with your terms and privacy links in place, and sample messages written for your use case, plus all your URLs and business details, ready to paste into Infobip. Build my order →
Infobip's rejection reason matrix spells out the website checks. In short:
These codes come from Infobip's rejection reference and matrix, paraphrased.
| Code | What it means (paraphrased) | Fix page |
|---|---|---|
| 1003 | Brand website is down, missing, or returns an error | Website not accessible |
| 1004 | Website lacks company, service, or contact details | Content pages |
| 2004 | Sample messages do not show the described use case | Sample messages mismatch |
| 2006 | Campaign brand name does not match the registered brand | Website does not match brand |
| 3001 | Call-to-action does not get enough consent | Opt-in not verifiable |
| 3007 | Terms and conditions are missing or incomplete | Missing SMS terms |
| 3008, 3009 | Privacy policy missing, or it does not exclude opt-in data from sharing | Privacy policy missing SMS language |
| 3012 | SMS consent is combined with email or phone consent | Opt-in form |
| 10600 | Checkbox is pre-selected | Opt-in form |
| 6012, 6013 | Samples lack your brand name, or use public link shorteners | Sample messages mismatch |
| 7002 | Lead generation or affiliate marketing | Prohibited content |
Infobip publishes timelines, but the docs reviewed here do not list 10DLC fee amounts. Its getting-started guide says:
| Step | Time in Infobip's docs |
|---|---|
| Brand validation | About 15 minutes |
| Brand with enhanced vetting | 1 to 3 business days |
| Campaign review at Infobip | 2 to 3 business days |
| Carrier review via TCR | 3 to 5 business days |
| Start to first send | About 1 to 2 weeks |
On cost, the guide says numbers carry a one-time and a monthly fee shown at checkout. Infobip's API docs say brand vetting is a paid service you can run only once every 30 days. Check Infobip's pricing or your account manager for current amounts.
10DLC Site builds these pages and gives you the exact URLs to use in Infobip. You still submit the registration yourself, and carriers make the final decision. For other providers, see the any-provider guide.
Not sure if your current site is ready? Run it through the compare your site with the checklist, or see pricing for a site built for 10DLC review.
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.
One-time price · 14-day money-back guarantee · Daily Compliance Watch
Code 1003 means the brand website is inaccessible, does not exist, or returns an error. Infobip's fix is to make the site live and repair DNS, SSL, or 404 and 503 errors. A site that does not load stops review before anything else is checked.
Code 1004 means your brand website does not show enough about your company. Infobip asks for a company description, product or service details, contact information, and a clear business purpose. A one-page form or placeholder site usually triggers it.
Not for 10DLC, based on Infobip's Create Campaign API reference. It has an optional termsAndConditionsUrl parameter, and the reference notes a separate privacyPolicyUrl only for toll-free campaigns. Put your privacy link in the call-to-action text instead.
Infobip's getting-started guide says brand validation takes about 15 minutes, or 1 to 3 business days with enhanced vetting. Campaigns take 2 to 3 business days at Infobip and 3 to 5 business days for carrier review, about 1 to 2 weeks overall.
Infobip's campaigns guide says to fix the issues and create a new campaign. Its rejection code reference marks many website and opt-in codes as fixable by editing. Follow the instruction for your code, and contact Infobip support to appeal a rejection you think is wrong.
No, Infobip rejection code 3012 asks for a single consent mechanism for SMS only. Do not combine SMS consent with email or phone call opt-ins. Give texting its own unchecked checkbox and disclosure.
The 8 website requirements reviewers check for A2P 10DLC: privacy policy, SMS terms, opt-in form, brand match, contact info, HTTPS...
The pages reviewers expect on a 10DLC website: About Us, Contact Us, Terms, Privacy, services, and your texting use case. No form-...
How to build an SMS opt-in form reviewers accept: unchecked checkbox, optional consent, disclosure next to the box, privacy and te...
Reviewers must open your site with no login, no errors, and no redirects. Learn why 'website not accessible' 10DLC rejections happ...
A 10DLC privacy policy needs a clear SMS no-sharing clause. See why campaigns get rejected for it, what reviewers check, and how t...
If reviewers cannot see how people agree to your texts, your 10DLC campaign gets rejected. Learn what proof they need and how to f...
The four website URLs every 10DLC registration uses: homepage, privacy policy, terms, and opt-in page. The TCR field model plus a...