What Is a DID Message?

SMS-Enabled DID Numbers Explained

A DID message is an SMS sent or received through a Direct Inward Dialing (DID) number that has been provisioned with messaging capability. Also referred to as an SMS-enabled DID, a messaging-capable long code, or DID SMS, this configuration allows a single phone number to handle both voice calls and text messages. For carriers, CPaaS platforms, and enterprises building unified communication infrastructure, SMS-enabled DIDs eliminate the need to manage separate number inventories for voice and messaging.

What Makes a DID Number "Message-Capable"

Not every DID number supports SMS by default. Messaging capability depends on three layers that all have to align: the originating carrier’s network support, the destination country’s regulatory framework, and the wholesale provider’s platform configuration.

The Three Requirements for SMS on a DID

Carrier-level support: The carrier holding the original numbering allocation must support SMS routing on that specific number range. Not all number ranges are built for messaging traffic.
Regulatory permission: The destination country’s telecom regulator must permit SMS traffic on the number type in question. Some markets restrict messaging to specific number categories.
Platform enablement: The wholesale provider must have SMS functionality activated on their platform for that number, including SMPP or API connectivity to handle inbound and outbound messages.

When all three align, the DID becomes a true dual-channel number: capable of receiving phone calls and sending or receiving SMS through the same ten-digit identifier.

DID SMS vs. Long Code vs. 10DLC: Clarifying the Terminology

These terms get used interchangeably in the industry, which creates confusion when evaluating providers or comparing technical documentat

Term	What It Refers To	Where It Applies
DID SMS / DID Message	Generic term for SMS sent over a Direct Inward Dialing number	Global, used across markets and providers
SMS-Enabled DID	A DID specifically provisioned with messaging capability	Global, common in wholesale provider terminology
Long Code	A standard 10-digit number used for SMS, as opposed to a short code	Used globally, especially outside the US/Canada compliance context
10DLC	10-Digit Long Code; specifically the US carrier framework requiring campaign registration	United States only

Why the Distinction Matters

“Long code” is the broader technical term used worldwide; “10DLC” is the specific US regulatory framework that governs how long codes must be registered for A2P traffic
A DID message sent from a US long code requires 10DLC campaign registration before it can carry A2P traffic at scale
Outside the US, long code SMS requirements vary by country, with some markets requiring no registration and others mandating Sender ID approval
Confusing these terms during a vendor conversation often leads to incorrect compliance assumptions, particularly when expanding into the US from a market with lighter messaging regulation

How a DID Message Works at the Network Level

The Routing Path for an Inbound DID SMS

A sender composes a message to the DID number
The message enters the SMS network and is routed to the carrier holding the number allocation
The carrier checks whether SMS routing is enabled for that specific number
If enabled, the message is forwarded via SMPP or HTTP API to the wholesale provider’s messaging platform
The platform delivers the message to the configured destination, which may be a CRM, a contact center application, or a CPaaS workflow
A Delivery Receipt (DLR) confirms successful handling back through the chain

This is the same underlying SMPP infrastructure that handles standard A2P messaging traffic. The difference is that the number itself is also configured for voice, which requires the provider’s platform to correctly route inbound traffic by type, voice to the PBX or SIP endpoint, SMS to the messaging application, without conflict.

Why Enterprises Use SMS-Enabled DIDs

The business case for DID messaging centers on consolidation: one number, multiple channels, simpler customer experience.

Primary Use Cases

Unified customer contact: Customers call and text the same number, eliminating confusion about which number to use for which channel
Two-way SMS support: Contact centers enable customers to text a support line instead of calling, reducing call volume while maintaining the same number on record
Appointment and notification workflows: Healthcare, financial services, and professional service businesses send reminders and confirmations from the same number clients already recognize and have saved in their contacts
CPaaS and platform deployments: Developers provision DIDs with messaging through APIs to support applications that need both voice and SMS functionality per user or per account
Local presence strategy: A business operating internationally provisions geographic DIDs per market, enabling both local calling and local-format SMS, which performs better for engagement than messages sent from international long codes

DID Messaging vs. Short Code Messaging: When to Use Each

Short codes are built for high-throughput, one-way or limited two-way bulk messaging: OTP campaigns, mass notifications, marketing blasts. They carry higher carrier trust for volume but cost more to lease and require dedicated registration.
SMS-enabled DIDs are built for one-to-one, conversational, or moderate-volume messaging tied to an identifiable business number. They are the right choice when the number needs to support both voice and SMS, or when the use case is relationship-based rather than mass broadcast.
Mixing the two incorrectly, sending bulk marketing volume through a DID built for conversational traffic, is a common cause of carrier filtering and throughput limitations.

Compliance Considerations for DID Messaging

SMS-enabled DIDs inherit the compliance requirements of both DID provisioning and A2P messaging, which means organizations need to satisfy both frameworks simultaneously.

10DLC registration (US): Long codes used for A2P traffic in the United States require campaign and brand registration through The Campaign Registry before carriers will reliably deliver messages at volume
TCPA consent (US): Marketing or promotional messages sent via DID require prior express written consent, independent of the number’s voice capability
KYC for the underlying DID: The same identity verification requirements that apply to voice DID provisioning apply to the number before messaging is enabled
Per-country Sender ID rules: Outside the US, many markets have their own registration frameworks for long code SMS that must be satisfied before messaging traffic flows reliably

Treating DID messaging compliance as “the same as regular SMS” misses the voice-side requirements; treating it as “the same as DID provisioning” misses the messaging-side requirements. Both apply.

Choosing a Provider for SMS-Enabled DIDs

Not every wholesale DID provider supports messaging, and not every provider that claims SMS support has it across their full inventory. This connects directly to the inventory depth and Tier 1 versus Tier 2 sourcing questions that apply to wholesale DID provisioning generally.

Confirm SMS capability per country and per number type before committing, since geographic DIDs in some markets do not support messaging at all
Ask whether SMS enablement requires a separate provisioning step or comes activated by default on voice-capable numbers
Request documentation on throughput limits (TPS) for DID messaging, since these are typically lower than dedicated short code throughput
Verify DLR reporting is available for the messaging side, not just call detail records for the voice side
Confirm 10DLC registration support if deploying in the United States, since unregistered long codes face aggressive carrier filtering

FAQs

What is a DID message?

A DID message is an SMS text message sent or received through a Direct Inward Dialing (DID) number that has been configured with messaging capability. The same phone number that handles incoming voice calls is also enabled to send and receive SMS, making it a dual-channel number. This requires the originating carrier, the destination country’s regulations, and the wholesale provider’s platform to all support SMS on that specific number.

Can every DID number send and receive SMS?

No. SMS capability on a DID depends on three factors aligning: whether the carrier holding the number allocation supports messaging on that number range, whether the destination country’s regulatory framework permits SMS on that number type, and whether the wholesale provider has activated messaging functionality on their platform for that number. Geographic DIDs in some countries do not support SMS at all, while non-geographic and mobile-format DIDs more commonly do. This should always be confirmed during provisioning rather than assumed.

What is the difference between a DID message and a long code?

Why would a business want a number that handles both calls and SMS?

The primary reason is customer experience consolidation. When a business uses the same number for calls and texts, customers do not need to remember or save two different numbers for the same point of contact. This matters most in unified contact center deployments, appointment and notification workflows in healthcare and financial services, and local presence strategies where a business provisions one geographic number per market for both calling and texting. It also simplifies number management on the provider side, since the organization is tracking one inventory instead of separate voice and messaging number pools.

What is the difference between DID messaging and short code messaging?

Short codes are 5 or 6 digit numbers built for high-throughput, high-volume A2P messaging such as mass notifications, OTP delivery at scale, and marketing campaigns. They carry higher carrier trust for bulk traffic but cost more and require dedicated registration. SMS-enabled DIDs are standard 10-digit numbers that support both voice and SMS, designed for conversational, one-to-one, or moderate-volume messaging tied to a recognizable business number. Choosing the wrong format, such as routing bulk marketing volume through a DID instead of a short code, is a common cause of carrier filtering and delivery throughput problems.

We are C3ntro

Stay

Connected

Privacy Policy