--- title: "10DLC registration without tears" summary: "US carriers block unregistered A2P traffic outright. The process is two layers, it takes longer than your launch date assumes, and most rejections are avoidable." canonical: https://cpaas.co/en/insights/10dlc-without-tears kind: use-case depth: applied origin: original published: 2026-07-26T11:34:07.986Z updated: 2026-09-08T11:34:08.123Z topics: ["A2P", "Compliance", "Messaging"] language: en --- # 10DLC registration without tears If you send business SMS to United States numbers from a standard ten-digit number, you must register. Since February 2025 the major carriers block unregistered 10DLC traffic entirely rather than throttling it — there is no degraded path to launch on. ## The two layers **Brand.** Who you are. Legal entity name, tax identifier, address, website. Registered once, and reused. **Campaign.** What you send and why. Registered per use case, so a clinic sending appointment reminders and running a separate fundraising programme registers two campaigns under one brand. Both go through The Campaign Registry, generally via your messaging provider rather than directly. ```diagram:layers # What sits on what Legal entity | The company as it exists on a tax filing. Nothing above this is portable to a different one. Brand | Registered once. Name, tax identifier, address, website — checked against each other. Campaign | One per use case, not one per programme. Appointment reminders and fundraising are two. Sample messages | The evidence the campaign is what it claims. Reviewed by a human who will notice a discount code. Traffic | Only reaches a handset once every layer beneath it has been accepted. > A rejection at any layer stops everything above it. This is why the calendar has to be planned from the bottom. ``` ## What actually gets you rejected Nearly all of it is avoidable, and nearly all of it comes down to consistency. - **Sample messages that do not match the campaign type.** If the use case says "account notifications" and a sample contains a discount code, that is a marketing campaign filed as a service one. - **A website that does not corroborate the brand.** Reviewers look. If the site does not obviously belong to the registered entity, or does not mention messaging at all, expect friction. - **No visible opt-in.** You must be able to show how consent is collected. A privacy policy that never mentions SMS is not evidence. - **Missing opt-out language.** Every campaign needs a documented STOP path, and it has to work. ## Plan the calendar backwards Vetting takes time — campaign review can run to roughly ten business days, and a rejection means correcting and resubmitting rather than appealing. The failure mode is not the delay itself. It is discovering the delay in the week you intended to launch. Register during development, not during rollout. ## Trust scores Once approved, a campaign gets a trust score derived from the legitimacy of the business, its web presence and its compliance history. That score influences throughput. The practical implication: throughput is not something you buy at the moment you need it. It accrues from a clean record, which means the cheap thing to do is behave well from the first message, when nobody is watching. ## The wider point This is a preview of where business messaging is going everywhere. Identified senders, registered use cases, and traffic that has to declare itself. India's DLT platform got there earlier, the Gulf has its own version, and the direction of travel is unambiguous. Build the registration data — brand, use case, consent evidence — as first-class records in your system rather than as a one-off form somebody filled in. You will fill it in again. ## A submission that passes first time The reviewer is checking one thing: does the story hold together. Everything below is a way of making sure it does. **Use the exact legal name.** Not the trading name, not the name on the website header. It has to match the tax record, because that is what gets verified against. **Pick the narrowest use case that covers the traffic.** A "mixed" campaign invites scrutiny of every message in it. Two narrow campaigns clear faster than one broad one, and they fail independently. **Write samples from real traffic.** Take four messages you have actually sent, or intend to send on day one. Include the brand name and the opt-out. Do not write an idealised sample that your production template does not match — the mismatch surfaces later, during an audit, when it is more expensive. **Publish the opt-in before you submit.** The reviewer will look at the page where consent is collected. If it does not exist yet, the submission is asking them to take your word for it. ## What the numbers look like ```diagram:stats 10 | Business days | A campaign review can run this long. Rejection restarts it rather than appealing it. 2 | Layers | Brand and campaign. Both must be accepted before a single message moves. 0 | Unregistered throughput | Since February 2025 the major carriers block rather than throttle. > The only number here you control is how early you start. ``` ## Registration as data, not paperwork The instinct is to treat this as a form somebody fills in once. That instinct costs a rewrite when the second country arrives. Model it instead: a brand record, a set of campaign records each with a use case and a consent basis, and a link from every outbound message to the campaign it belongs to. India's DLT wants the same shape. The Gulf's sender-ID registration wants the same shape. When the next regime appears, you are mapping fields rather than inventing a concept. The tell that you have it right: you can answer "which campaign was this message sent under, and what consent covered it" from a query, for any message you have ever sent. ## What to take away The process is slow, mostly predictable, and rejects for consistency failures rather than for anything technical. Register during development. Keep campaigns narrow. Make the registration data a first-class record, because you will be asked for the same facts by the next regulator, in a different form. ## Sources - [Ten-Digit Long Code (10DLC) Registration Guidelines](https://learn.microsoft.com/en-us/azure/communication-services/concepts/sms/ten-digit-long-code-guidelines) — Microsoft Learn --- Published by the company behind five products in this category. Those products appear in this site's directory alongside competitors under the same published criteria and are labelled as its own. Editorial content does not recommend them.