A long code is simply a standard telephone number, ten digits in the United States, used to send and receive text messages. The name only exists by contrast: when five and six digit short codes became the premium tool of mass texting, the industry needed a term for ordinary full-length numbers, and "long code" stuck. Every personal cell number is a long code. So is the main line of a business that has enabled texting on it.

That ordinariness is the long code's superpower and, historically, its problem. This article explains how long codes work, the crucial split between person-to-person and registered application-to-person use, and where long codes fit against the other number types. It completes the set alongside our guides to short codes and the full short code vs 10DLC vs toll-free comparison.

The Anatomy of a Long Code

In the North American Numbering Plan, the system administered under Federal Communications Commission authority that governs US and Canadian phone numbers, a long code is a ten-digit number: a three-digit area code plus a seven-digit local number. Because it is a real, routable phone number, a long code can do things no short code can:

  • Carry voice calls. The same number can ring a phone and hold a text conversation, so one number can serve as an organization's complete contact identity.
  • Present a local identity. A number in your own area code signals local presence, which matters to a church, a clinic, a school district, or a city department texting its own community.
  • Cost very little. Long codes are provisioned for a small monthly cost, a fraction of what a dedicated short code lease runs.
  • Be ported. Under FCC number portability rules, you can move a long code between providers and keep the number, so your texting identity is an asset you own rather than rent.

The Two Lives of a Long Code: P2P and A2P

The single most important thing to understand about long codes is that the same ten digits can operate under two entirely different regimes.

Person-to-person (P2P) is the native mode: a human with a phone texting other humans, at human pace. Carrier systems expect P2P traffic from consumer numbers and police it against automation. The unwritten contract is conversational volume, roughly balanced sending and receiving, and no bulk blasts.

Application-to-person (A2P) is software sending messages through the number: appointment reminders, alerts, campaigns, autoresponses. For years, organizations quietly ran A2P traffic over plain long codes because it was cheap, and carriers fought back with aggressive filtering, because unregistered bulk traffic on consumer channels is indistinguishable from spam. That era ended with the creation of 10DLC, ten-digit long code, the carrier framework under which businesses register their identity and campaigns through The Campaign Registry and receive sanctioned A2P throughput on ordinary ten-digit numbers.

The distinction is not optional. Unregistered application traffic on a long code today faces heavy filtering and per-message carrier penalties. A registered 10DLC number carries the same ten digits but travels approved lanes with documented throughput. Our explainer on A2P 10DLC walks through the registration system itself.

Long Code vs Short Code vs Toll-Free

The three number families divide the messaging world by trade-offs:

AttributeLong code (10DLC)Short codeToll-free
Digits10, local area code5 or 610, prefixes like 800 and 833
Voice capableYesNoYes
Local identityYesNoNo
Cost profileLowestHighestLow to moderate
Approval pathBrand and campaign registration (TCR)Full carrier vetting of the code leaseToll-free verification
ThroughputRegistration-dependent, suits most organizationsVery high, built for mass volumeModerate, verification-dependent

The practical sorting: national brands blasting millions of time-sensitive messages lease short codes; organizations wanting a recognizable, texting-enabled identity at moderate scale, which describes most nonprofits, clinics, schools, and local agencies, register 10DLC long codes; toll-free suits national customer-service lines, subject to its own verification process.

Choosing and Setting Up a Long Code Well

  1. Decide the number's identity first. You can provision a new local number or text-enable an existing organizational line through a hosted messaging arrangement, so the number your community already knows becomes the number that texts them.
  2. Register before you send. Complete brand and campaign registration through your messaging provider. Sending first and registering later is how numbers earn filtering reputations that take months to shed.
  3. Match volume to your registration. 10DLC throughput reflects your registered campaign standing. Plan sends within it, and let your provider queue larger sends over time rather than burst past limits.
  4. Keep it conversational. The abiding advantage of a long code is two-way texting from a number people can also call. Build workflows that answer replies rather than broadcasting into a void; that is where reminders become confirmations and questions become resolved cases.
  5. Own the asset. Confirm the number is portable and registered to your organization, not locked inside a platform. Number portability rules exist so your identity can move with you.

How a Message Actually Reaches a Long Code

Understanding the path a text takes explains most of the problems organizations run into with long codes:

  1. Your platform accepts the send and attaches the sending number plus the registered campaign identity behind it.
  2. The message enters an aggregator or carrier gateway. This is where the registration record matters: the campaign registered through The Campaign Registry tells the carrier who is sending and why.
  3. Carrier filtering evaluates the traffic against the registered use case, the sending pattern, and reputation history. Unregistered application traffic and content that looks unsolicited are stopped here, which is why filtering feels invisible and arbitrary from the sender's side.
  4. The recipient carrier delivers to the handset and, where supported, returns a delivery receipt to your platform.
  5. Replies travel the reverse path to whatever inbox or workflow your platform routes them into, which is the part a broadcast-only setup wastes.

Two consequences follow. First, delivery is a permission granted by carriers, not a purchase you make, so registration accuracy is operationally more important than send volume. Second, reputation attaches to the number, so a number that once carried unregistered blasts can arrive with a history it did not earn under your ownership.

Throughput, Segments, and What Slows a Long Code Down

Organizations usually discover long code limits mid-campaign, so it helps to know the mechanics in advance:

  • Throughput is per second, not per day. A registered campaign is allotted a message-per-second rate. A large list is not blocked by that rate; it is spread across time by your platform's queue, which is why a send to thousands of recipients completes in minutes rather than instantly.
  • Length costs segments. A single SMS segment holds 160 characters in the standard GSM-7 alphabet. Longer messages split into multiple segments, and each segment consumes throughput and, on most pricing models, cost.
  • Special characters shrink the budget. Curly quotes, accented letters, and emoji push a message into a wider encoding that holds roughly 70 characters per segment, so one pasted character can double the segment count of an otherwise short message.
  • Images change the product. Sending pictures makes the message an MMS, which has its own pricing and handling.
  • Opt-out language is not optional overhead. Help and stop instructions belong in the message flow, and industry messaging guidelines expect them.

Edge Cases and Exceptions

  • Text-enabling a landline. Many main business lines can be text-enabled without disturbing voice service, so the number on your door becomes the number that answers texts. Not every line qualifies, and the check happens before the campaign is built.
  • Numbers that cannot be text-enabled. Some carrier arrangements and certain number types do not support hosted messaging. Verify before printing the number on materials.
  • Emergency and crisis numbers. Long codes are not a substitute for 911, and crisis lines have their own routing. Never present an organizational texting number as an emergency channel.
  • Shared numbers. Multiple programs sending from one number blur consent records and opt-outs. Separate programs with genuinely different audiences are usually better served by separate registered campaigns.
  • Area code identity versus reach. A local area code reads as local to the community that shares it and as out of town to everyone else. Multi-region organizations sometimes choose toll-free for neutrality instead.
  • Porting timelines. Moving a number between providers takes coordination and paperwork, and messaging registration usually has to be rebuilt on the receiving side. Our guide to number porting for SMS covers the sequence.
  • Sole proprietors and very small organizations. Registration paths exist for entities without the tax records a large brand supplies, with lower throughput allowances attached.

What to Ask a Provider About Your Number

  1. Is the number registered to our organization, and can we see the brand and campaign records?
  2. What throughput does our registered campaign carry, and how does the platform queue larger sends?
  3. Is the number portable, and what is the process and timeline if we leave?
  4. Was this number newly provisioned, or does it have prior sending history?
  5. Do you support text-enabling our existing main line, and can you check eligibility before we commit?
  6. How are opt-outs stored, and do they persist if the number moves to a different campaign?
  7. What visibility do we get into delivery receipts and error codes when messages fail?
  8. Who pays and files for registration, and what happens if a campaign is rejected?
  9. Can we export message history and contact consent records at any time?

Frequently Asked Questions

What is a long code in texting?

A long code is a standard ten-digit telephone number used for SMS. The term distinguishes ordinary full-length numbers from five and six digit short codes. Long codes support both voice and text, carry a local area code, and, when registered under the 10DLC framework, are sanctioned for business messaging.

What is the difference between a long code and 10DLC?

They are the same ten-digit number type in different regimes. A plain long code handles person-to-person texting. 10DLC, ten-digit long code, is the carrier framework in which a business registers its brand and campaigns through The Campaign Registry, converting that ordinary number into an approved application-to-person sender with documented throughput.

Can you send mass texts from a long code?

Yes, if the number is registered for A2P 10DLC through your messaging provider. Registered long codes carry throughput suited to most organizational messaging, with larger sends queued over time. Bulk sending from an unregistered long code triggers carrier filtering and penalties, and is the classic mistake of do-it-yourself mass texting.

Are long codes cheaper than short codes?

Substantially. A long code carries a modest monthly cost plus one-time and recurring registration fees, while a dedicated short code lease through the Short Code Registry costs substantially more per month. Check current provider and registry pricing. Short codes buy very high throughput; long codes buy identity, voice capability, and economy.

Can I text-enable my organization's existing phone number?

Usually yes. Hosted SMS arrangements add texting capability to an existing voice number without disrupting phone service, and FCC number portability rules let you move numbers between providers. This lets the main line your community already recognizes become your texting identity as well.

Can two platforms send from the same long code at the same time?

Generally no. A number is provisioned to one messaging route at a time, and splitting it across platforms breaks reply routing and opt-out records even where it appears to work. Consolidate on one platform, or use separate numbers for separate programs.

What happens to a long code if we change providers?

The number itself can usually move, since number portability rules exist for that purpose, but the messaging registration behind it typically has to be re-established with the new provider, and there is a coordination window to plan around. Confirm ownership and portability at signup rather than at departure, and keep an export of consent records so opt-outs survive the transition.

One Local Number, Every Conversation

FRANSiS provisions or text-enables your ten-digit number, completes 10DLC registration end to end, and puts an AI Powered Helper on the replies. Contact us to make your organization's own number its best communication channel.