A2P 10DLC Compliance: Why DIY Email-to-SMS Is Harder Than It Looks

Building your own email-to-SMS system sounds easy — until you hit A2P 10DLC compliance. Here’s what’s involved and a simpler alternative.

You’re looking for an email-to-SMS tool.

And in this era, you’re probably thinking: I should just build this myself.

I’d think the same thing. Spinning up a Twilio integration to send yourself SMS alerts is doable if you’ve got some technical savvy.

But among the usual reasons (What’s your time worth? Do you really want another system to maintain?), there’s another big blocker from creating a DIY email-to-text solution.

And that’s compliance. Specifically, A2P 10DLC compliance. And unless you’ve had to deal with it before, you probably don’t know what you’re signing up for. (Or what those acronyms even stand for.)

In this article, I’ll cover what A2P 10DLC compliance is, why you need it, what’s required to set it up yourself — and a really low-cost email-to-SMS alternative so you don’t have to bother.

A2P 10DLC Compliance: Table of Contents

• What Is A2P 10DLC Compliance?
• The A2P 10DLC Registration Process
• But That’s Not All… The Ongoing Obligations
• The Simpler Alternative: Using text.email

What Is A2P 10DLC Compliance?

A2P stands for Application-to-Person.

10DLC stands for 10-digit long code; that’s a standard phone number like 555-555-5555, as opposed to a short code like 55555.

In 2021 (and fully enforced by 2024), the U.S. cell phone carriers implemented a registration and vetting system for any business sending SMS from 10DLC numbers. Verizon’s vtext.com, AT&T’s txt.att.net, T-Mobile’s tmomail.net, and all the rest are dead.

The stated goal was reducing spam. And while that was one of the goals, it wasn’t the only one. The practical effect was that carriers now have control over — and revenue from — business messaging that previously flew under the radar.

If you send SMS from an unregistered 10DLC number today, your messages will get filtered, throttled, or blocked entirely.

This isn’t a theoretical risk or a terms-of-service technicality. It’s actively enforced.

Which means if you want to create an app that sends texts — even a tiny app that sends texts just to yourself — you’ve got to register.

The A2P 10DLC Registration Process

Here’s what registering for A2P 10DLC involves.

And yes, the compliance requirements are identical whether you’re sending 50 messages a month or 50,000.

Business verification

You need to verify your legal business entity. That means you need your EIN, legal business name, and address (validated against third-party databases). If you’re a solo developer or your business info doesn’t match what’s in the verification databases, this step can trip you up.

Brand registration

Your business gets submitted to The Campaign Registry (TCR), which is the central clearinghouse the carriers use. TCR vets your business and assigns a trust score that affects your messaging throughput. This takes a few days to a couple weeks.

Campaign registration

You register the specific “campaign,” which, in carrier terminology, means how you’ll use SMS.

You’ll provide your use case, sample messages, and documentation of how recipients opt in and opt out. For alerting, especially self-alerting, this is pretty straightforward.

Carrier review

After TCR approval, individual carriers (T-Mobile, AT&T, Verizon) review and approve your campaign. They can reject it, request changes, or impose restrictions.

Total timeline: a few weeks if everything goes smoothly. Longer if there are verification hiccups or your use case raises questions.

But That’s Not All… The Ongoing Obligations

Registration is a one-time thing — but it’s not the end of your responsibilities.

Once you’re in the system, you’re on the hook for:

STOP/HELP handling

Recipients must be able to text STOP to opt out and HELP to get assistance. You need to process these keywords and respond appropriately. And log it.

Content guidelines

Even for alerts, there are restrictions on what you can send. Carriers can and do audit message content.

Keeping registration current

If your business details change — name, address, ownership — you need to update your registration. Stale registrations can get flagged.

Nurturing throughput limits

Your message volume is capped based on your trust score. Low-trust brands start with significant restrictions. Building trust takes time and message history.

None of this is insurmountable. But it’s not nothing, either.

The Simpler Alternative: Using text.email

So if you don’t want to go through the compliance registration and maintenance process and you don’t want to have to build and manage your own system… text.email is the alternative.

It’s simple: send an email to a specific address, receive an SMS. There’s no API required or any other integrations — and no registration process.

If your monitoring tool, NAS, cron daemon, server, or anything else can send email, it can send you a text.

We handle the A2P 10DLC registration, carrier relationships, STOP/HELP, and ongoing compliance obligations.

And all of that is less than $10/month — the equivalent of a fraction of a single hour of your time.

You can get set up in less than a minute with text.email (or try it out by sending a sample alert to yourself at yournumber@text.email).