10 Digit Long Code, Explained for Teams That Send Bulk SMS
A 10-digit long code is a 10DLC, the standard ten-digit phone number businesses use as the sender ID for application-to-person messaging, and it only behaves well after brand and campaign registration. Treat it as three things at once: a number, a registration record, and a throughput tier the carriers police. Get one wrong and the other two stop mattering.
What a 10-digit long code is, and what it is not
A 10DLC is a ten-digit local number provisioned for A2P traffic, registered against your business, and assigned to a messaging campaign. 10DLC (10-Digit Long Code) is an industry standard for A2P (Application-to-Person) messaging, per ServiceTitan’s registration documentation. It looks like a normal local line to the person receiving it. It is not one: behind it sits a business identity record and a campaign declaration that carriers read before your first message lands.
What it is not: it is not a short code. A short code is a 5- or 6-digit code assigned by the Short Code Registry and used as the Sender ID for business messages under the ATIS industry standard. Nor is it toll-free traffic, which lives under its own verification regime. The long code is the middle rung: cheap, familiar to the recipient, and slower to provision than either. Picking one is a throughput decision dressed up as a number choice.
What separates a healthy long code from a throttled one
The number itself is the easy part. The difference between a long code that delivers and one that silently drops sits in the registration and the message content. When you evaluate a provider or a setup, look at these, in this order:
- Brand status. Is your business vetted by The Campaign Registry, or still in review? A campaign attached to an unvetted brand is a campaign carriers can throttle at will.
- Campaign use case. Your declaration (conversational, marketing, OTP, mixed) has to match what you actually send. Declare “conversational” and then push promotions, and filtering tightens.
- Throughput tier. Every 10DLC carries a daily message-per-second allowance set by the carriers based on vetting and use case. Know your tier before you plan a blast.
- Opt-in evidence. Registrants must be able to show how subscribers consented. Platforms that capture consent at signup give you a defensible record; a spreadsheet of pasted numbers does not.
- Inbox ownership. Inbound replies need a place to land. A provider that hands you a number but no shared inbox leaves half the conversation outside your view.
Register, vet, then send
The sequence matters more than the speed. Sending before registration clears is the single most common reason a new long code starts life filtered. Brand registration approval with The Campaign Registry typically takes two to three business days, according to Microsoft’s Azure Communication Services documentation, and campaign review can run longer.
- Submit your business identity: legal name, EIN, address, and the entity that will send. Mismatched names between your brand and your LLC registration are a slow-review trigger.
- Declare your campaign use case and attach sample messages that match it. Write the samples from what you will actually send, not the sanitized version.
- Capture opt-in evidence before the first send: the web form, the keyword reply, the point-of-sale check box. Store the timestamp and source.
- Wait for approval. Provision the number, wire it into your platform, and send a small test batch to your own team first.
- Monitor filtering and reply rates after you scale. If throughput drops, check the campaign declaration before blaming the carrier.
If you also handle certificate and key material for your own software, the same discipline of registering an identity before you trust the channel applies to code signing certificate management. Different registry, same pattern: prove the entity, then act.
Picking the sender ID your volume can pay for
Choose a long code when your sending is conversational, spread across a day, and mostly replies to people who started the thread. That is where the ten-digit number earns its keep: recognized by the recipient, inexpensive to run, and simple to fit into a shared inbox. The trade-off is throughput. Daily caps and per-second limits mean a long code will not carry a burst campaign without lead time.
Choose a short code when you send high-volume, time-sensitive campaigns and the brand recall of a memorable five or six-digit number is worth the provisioning cost and the longer approval cycle. Choose toll-free verification when you want a number that reads as toll-free and you can accept a different registration path. If you cannot say which of those describes your traffic, look at your last month’s send log: the shape of the curve tells you more than any plan on paper.
For teams building the conversation layer on top, the sender ID is only half the picture. A link or a QR code generator that thinks about the destination solves the first click; a registered long code and an inbox solve everything after it.
Where teams get long codes wrong
One mistake is treating the long code as the registration. The number provisions in minutes; the brand and campaign vetting sit behind it and gate whether that number delivers at all. Teams send a test, see it arrive, and ship a campaign while the brand record is still pending. Then the filtering hits and volume collapses. Provision and registration are separate clocks, and the second one is the one that matters.
Another is declaring a conversational use case for a marketing program. Carriers filter on the mismatch, and once your campaign’s reputation bends, recovery is slower than the original vetting. Declare what you send. If you send both, register the marketing campaign you actually need.
The confusion with QR codes deserves a line. A QR code that opens a WhatsApp chat is a click, not a channel; it gets a customer into a conversation, and the conversation still needs a managed inbox on the other side. Teams chase a QR generator and treat the scan as the whole job, then wonder why the chat goes unanswered. The scan is the front door. Someone has to be in the room.
A last habit to break is measuring a long code by delivery rate alone. Delivery tells you the message reached the handset; reply rate and opt-out rate tell you whether the campaign was welcome. Watch both or you will optimize for a metric that flatters a program customers are muting.
Where Sociocs fits after registration
Registration gets you a working long code. It does not build the inbox the replies come back to. Sociocs is a business texting and omnichannel customer engagement platform, and business text messaging runs through Twilio or Telnyx with MMS support, so the long code you registered plugs into a shared team inbox instead of a single phone. That means every inbound reply, from SMS to a WhatsApp click-to-chat, stays in one place your team can answer.
The same inbox carries the other channels: WhatsApp Business messaging, Facebook Messenger for comments, direct chat, and web chat, Instagram direct messages and story replies, Telegram business bot messaging, Google Reviews and Google Q&A, and online forms with spam blocking. If you point customers at a chat with a free WhatsApp QR code tool, the landing stays inside the same tool your team already works in. Plans start on the free tier with no credit card required, and you can see current plans on the pricing page before you scale your sending. If you are still weighing a sender ID against your volume, tell us what you send and we will help you size it.
Frequently Asked Questions
What is a 10-digit long code?
It is a standard ten-digit phone number that businesses use as the sender ID for application-to-person messaging, registered against their business identity and a declared campaign. It reads as a local number to the recipient but is treated as A2P traffic by the carriers, which is why brand vetting and campaign registration decide whether it delivers. Outside the industry it is known simply as a 10DLC, and it sits between a short code and a toll-free number on throughput.
Does a 10-digit long code work without registration?
It provisions, but it does not reliably deliver at volume. Carriers filter unregistered or unvetted A2P traffic, often by dropping messages silently rather than rejecting them, so a test send can succeed while a real campaign disappears. Register the brand and campaign, capture opt-in evidence, and wait for approval before your first large send. Skipping registration moves the failure from setup to production, where it costs more.
How long does 10DLC registration take?
Brand registration approval with The Campaign Registry typically takes two to three business days, according to Microsoft’s Azure Communication Services documentation, and the campaign review that follows can take longer depending on use case and the clarity of your samples. Mismatched business details are the usual cause of a slow review. Submit the legal entity that will send, and match it exactly to your EIN record.