10DLC
10DLC, short for 10-digit long code, is the U.S. carrier framework for application-to-person text messaging sent through standard 10-digit local phone numbers. It connects a verified business identity, a declared messaging use case, and the numbers used for that traffic so carriers can distinguish registered business messaging from unregistered traffic.
How 10DLC works
A business first registers its brand through the messaging ecosystem used by its provider. It then describes a campaign: what messages will be sent, how recipients consent, and how they can opt out or request help. Approved phone numbers are associated with that campaign before the application sends messages through them.
Carriers and messaging providers use the registration data when applying routing, filtering, and throughput policies. Registration does not mean every message will be delivered, and it does not grant blanket permission to contact anyone. Message content and actual operating practices need to match the registered use case, while consent records and opt-out handling remain the sender's responsibility.
10DLC applies to messaging rather than voice authentication. A local number may support both calls and texts, but the systems governing those channels are different. STIR/SHAKEN concerns caller-ID authentication for voice calls; 10DLC concerns registered application-originated messaging. CNAM or branded calling also does not replace messaging registration.
Why 10DLC matters around AI phone calls
An AI phone workflow may sit beside a separate messaging workflow for confirmations, reminders, or requested follow-up. If software initiates those texts, the business needs to evaluate the messaging path on its own terms. Permission to place a call does not automatically establish permission to send every kind of text, and a recipient asking for a text does not erase opt-out obligations.
When evaluating a phone-agent project, map each channel explicitly: which system places the call, which system sends a message, which number appears, where consent is recorded, and where opt-outs are enforced. That separation prevents a voice deployment from accidentally treating messaging registration as a generic property of the phone number.