Texting residents: 10DLC registration, consent, and opt-out rules

Reference article · 6 min read

Text messaging has become a default channel for reaching residents: appointment reminders, benefit redetermination notices, court dates, utility shutoff warnings, road closures, and jury summons follow-ups. The messages themselves are simple. The infrastructure underneath them is not. United States wireless carriers treat application-to-person messaging sent over ordinary ten-digit phone numbers as a registered category commonly called 10DLC, and traffic that is not registered correctly gets throttled, filtered, or silently dropped without any error your staff will notice.

An agency running a texting program has to settle four things: what kind of number it sends from, how its sending identity is registered with carriers, how consent is captured and honored, and how the resulting messages are retained and transferred if the vendor changes. Most of these are difficult to unwind after launch, which makes them procurement decisions rather than implementation details.

Choose the number type before you pick a vendor

10DLC (standard ten-digit long code). A local area code number, lowest cost, supports two-way conversation, and can usually be ported between providers. Throughput is limited and depends on how your brand and campaign are registered and vetted.
Short code. A five or six digit number leased through the industry administrator with carrier approval. Highest throughput and the most predictable deliverability for large alert blasts. It costs substantially more, takes considerably longer to provision, and cannot receive voice calls, so residents who try to call back reach nothing.
Toll-free. Supports messaging after a separate verification process run through the carriers and aggregators. Unverified toll-free messaging traffic is widely blocked. It works for statewide programs but reads to residents as a call center rather than a local office.

A common pattern is a short code for high-volume emergency and mass notifications, with local 10DLC numbers for conversational program work.

How 10DLC registration actually works

Registration happens in two layers through the industry registry, usually mediated by your messaging vendor. First you register a brand: the legal entity name, tax identification number, address, and a responsible contact. Then you register one or more campaigns, each describing a use case, sample message text, the opt-in flow, and the opt-out and help language you will send.

Practical points that matter for agencies:

Register the brand under your agency's own legal identity and tax ID, not the vendor's. This is the single most consequential portability decision you will make.
Government entity types exist in the registration process and, after vetting, generally support better throughput and lower filtering risk than a generic small business registration.
Sample messages must match what you actually send. Traffic that does not resemble the registered campaign is a common filtering trigger.
Separate campaigns for genuinely separate purposes. A campaign registered for appointment reminders should not carry program marketing.
Expect one-time and recurring registration fees plus carrier pass-through surcharges per message. Ask for these as line items.

Why carriers filter messages that look like marketing

Carriers and aggregators apply their own content and behavior rules on top of any legal requirement. Messages are commonly blocked or throttled for public link shorteners, content touching the restricted categories carriers enforce, sudden volume bursts above your provisioned throughput, high opt-out or complaint rates, and promotional phrasing in a campaign registered as transactional. Delivery is not guaranteed by acceptance: a platform can report a message as sent while a carrier discards it downstream. Require delivery-level and filtering-level reporting, not just send counts.

Use your own domain for links, keep message frequency close to what you registered, and avoid all-caps urgency formatting outside genuine emergencies.

Capture consent as a record, not a checkbox state. Store who consented, the mobile number, the date and time, the channel, and the exact disclosure language shown at the time. Keep it retrievable years later, because the question will come from counsel or a complaint, not from your vendor.

Carrier and industry messaging guidance requires that you honor STOP and its common variants, respond to HELP with identification and contact information, and stop sending promptly. Treat opt-out broadly: if a resident types a plain-language request to stop in a two-way thread, honor it even though it is not the keyword. Maintain the opt-out list at the agency level across every campaign and vendor.

The extent to which the federal Telephone Consumer Protection Act and its consent rules apply to state and local government entities, and to vendors texting on their behalf, has been addressed in agency rulings and litigation and is not uniform across situations. The requirements also change. Confirm your position with your counsel rather than relying on a vendor's summary, and assume carrier rules apply regardless of the legal analysis.

Emergency notification is a separate track

Wireless Emergency Alerts sent through the federal alerting system are a geographic broadcast, require designation as an alerting authority, and do not depend on resident opt-in. They are not SMS and should not be the backbone of routine outreach. Opt-in mass notification lists, and in some jurisdictions resident contact data drawn from 911 systems under specific state restrictions, are the usual complement.

Statutory emergency exceptions to consent requirements are narrower than people assume and do not cover general program communication. Register an appropriate emergency use case so alerts are not throttled, and test the path on a non-emergency day.

Two-way texting is a staffing commitment

If residents can reply, someone has to read replies. Decide coverage hours, publish them in an auto-response, define escalation to phone or in-person service, and plan for languages other than English and for accessibility. Keep sensitive personal information out of SMS, which is not encrypted end to end; use the text as a prompt to a secure portal.

Inbound and outbound messages are typically agency records subject to your state's public records law and your retention schedule, including messages on staff devices. Configure retention in the platform deliberately, confirm it can be placed under legal hold, and confirm export works before you need it.

What to require in the contract

Ownership. The agency is the registered brand and the owner or lease holder of every number and short code.
Portability. The vendor cooperates with number porting and short code lease transfer on request, within a defined number of days, at no exit fee.
Data export. Opt-in records, opt-out lists, and full message history exportable in a documented, machine-readable format at any time and at termination, not only as a PDF.
Reporting. Delivery, failure, and filtering visibility by carrier, plus notice when a campaign registration status changes.
Fees. Registration, per-message carrier surcharges, and vetting costs disclosed as pass-through line items.
Subprocessors. Disclosure of aggregators and downstream providers, with no secondary use of resident data.
Transition. A defined assistance period after termination.

HQT works with state and local agencies on resident communication systems, including messaging platform selection, integration, and records handling.

Frequently asked questions

Do government agencies have to register for 10DLC?

If your agency sends application-to-person text messages from a standard ten-digit phone number to United States mobile subscribers, carriers expect that traffic to be registered through the industry registry as a brand and one or more campaigns. Registration is enforced by the carriers rather than by a statute, but unregistered traffic is routinely throttled or blocked. Government entity types exist in the registration process and generally receive better treatment after vetting. Short codes and toll-free numbers use different but comparable approval processes.

What is the difference between a short code and a 10DLC number for agency alerts?

A short code is a five or six digit number leased with carrier approval that supports very high message throughput and the most reliable delivery for mass notifications, but it costs more, takes longer to provision, and cannot receive voice calls. A 10DLC is an ordinary local ten-digit number that costs less, supports two-way conversation, and can usually be ported between vendors, but has lower throughput that depends on your registration and vetting. Many agencies use a short code for emergency and high-volume alerts and local 10DLC numbers for program-level conversations.

Are text messages sent by a government agency public records?

In most states, messages sent and received by agency staff in the course of official business are records subject to the state public records law and the applicable retention schedule, regardless of the device or platform used. That generally includes inbound resident replies and messages sent from personal devices for agency business. Configure retention and export in your messaging platform deliberately and confirm the platform supports legal holds. Retention periods and exemptions vary by state, so confirm the specifics with your records officer and counsel.

Can we send emergency alerts without collecting opt-in consent first?

Wireless Emergency Alerts sent through the federal alerting system are a geographic broadcast to devices in an area and do not depend on resident opt-in, but they require designation as an alerting authority and are not ordinary SMS. Statutory emergency exceptions to consent requirements exist but are narrower than commonly assumed and do not cover routine program communication. Carrier filtering also still applies, so register an appropriate emergency use case and test the delivery path in advance. Confirm the boundaries of any exception with your counsel.

What happens to our phone number and opt-in list if we switch texting vendors?

That depends entirely on what your contract says, so address it before award. Require that your agency is the registered brand under its own legal identity and tax identification number, and the owner or lease holder of every number and short code. Require vendor cooperation with number porting and short code lease transfer within a defined timeframe at no exit fee, plus machine-readable export of opt-in records, opt-out lists, and message history at any time and at termination.