A2P 10DLC for Nonprofits: Registration, Explained

You set up texting. You wrote the messages. And then nothing. Or worse, some messages land and some vanish, and nobody can tell you which ones or why.

One nonprofit told us exactly how that went: "it just kept getting like auto denied... So we weren't actually able to ever get our phone number verified." They never sent a single campaign.

This problem is usually not your fault, and it is also not a mystery. It is a registration process called A2P 10DLC, and most of it happens between your provider and the phone carriers. You just need to know enough to make sure it gets done right.

You should NOT have to become a lawyer to send a text.

The short version

A2P stands for application-to-person: messages sent by software rather than a person thumbing a phone. 10DLC refers to the standard 10-digit local number those messages go out on.

US carriers require that this kind of traffic be registered before it flows. Registration tells the carriers who you are and what you intend to send. Unregistered or mis-registered traffic gets filtered, throttled, or blocked.

That is genuinely it. The rest is detail, and most of the detail is your provider's job.

How nonprofits get stuck

From what we see, denials and delays usually trace back to a handful of things:

• Your registered details do not match your public record. Legal name, EIN, address, website. If the form says one thing and the IRS record says another, it stalls. And the legal name is often not the name anybody uses. One customer had to explain: "That's just our legal name, AdoptAClassroom.org."
• The use case description is vague. Carriers want to know what you are actually going to send and how people signed up for it. "Nonprofit updates" is not an sufficient answer.
• Your opt-in cannot be shown. This is the big one. You need to be able to point at how people consented, what they saw when they did it, and where that record lives.
• Your sample messages look like spam to a filter. Sending a text with two links, or worse yet, sending them a link through a URL sharing service like tinyurl or bit.ly is a flag. A person once replied: "It looked like phishing, like you were trying to send me to some random site I didn't recognize."
• Nobody owns it. As one prospect admitted, "we admittedly don't have this SMS compliancy infrastructure built out." Most nonprofits do not, and should not have to.

What you need to have ready

Gather these before you start and the whole thing goes faster.

• Legal organization name exactly as registered, plus EIN
• Registered business address
• A website that clearly shows who you are
• A contact person with an email at your domain
• A plain description of what you will send, to whom, and how often
• Two or three real sample messages
• Your opt-in method and the exact wording people see when they subscribe

Who does what

This is the part worth asking every vendor, and the answers will vary. Take this list into the conversation and get the answers in writing.

Piece	Ask your provider
Submitting brand and campaign registration	Do you submit it, or do we?
Responding to carrier questions or rejections	Who handles the back-and-forth?
Maintaining opt-in records	What do you store, and what stays with us?
Handling STOP and HELP replies	Is this automatic, and can we see it?
Re-registering when your use case changes	Who notices, and who files it?

At Rally we handle the carrier registration and the compliance plumbing so your team does not have to learn it. Ask us where the line sits for your setup and we will walk you through it.

How long does it take?

Timelines shift, and anyone who quotes you a firm number without knowing your situation is guessing. Ask us and we will tell you what we are seeing this month.

Consent is the part that is actually yours

Registration gets your messages moving. Consent is what keeps them moving, and it is the piece no vendor can do for you.

People need to knowingly opt in. They need to know what they signed up for. They need an easy way out. That is not just a rule, it is the difference between a list that gives and a list that leaves. One director put the stake plainly: "we're not in the market to irritate them."

If you want the deeper version of this, we wrote it up separately: how to text without legal compliance issues.

Related reading

• Mobile messaging for nonprofits
• How to text without legal compliance issues
• Easy text message sign-up: getting opt-ins that convert
• Text messaging basics for nonprofits
• Get started

FAQ

Is A2P 10DLC required for nonprofits?
The requirement is about the kind of traffic, not your tax status. If you are sending messages from software, it applies to you.

Does it cost anything?
Fee structures vary by provider and they change. Ask us what applies to your setup rather than working from a number you read somewhere.

What happens if we skip it?
Messages get filtered or blocked, usually silently, which is the worst version. You will think texting does not work for your audience when really it never left the building.

We already have registered numbers with another provider. Can we bring them?
This comes up constantly. One customer asked it word for word: "if we already have registered and approved phone numbers, can we bring those with us?" It depends on how they were originally registered. Ask before you migrate and we will tell you what is portable in your case.

Is a shortcode different?
Yes. Shortcodes are a separate track from 10DLC, with their own process and their own reasons to choose them.

Who fixes it if we get rejected?
Ask any vendor this before you sign, and get the answer in writing. A rejection you have to solve alone is a very different product than one your provider owns.

Heads up: we make texting software, not legal rulings. This is general info, not legal advice. Rules shift and every org is different, so verify the current TCPA/A2P 10DLC requirements and check with an attorney before you act. That said, book a call with us, and we'll loop in our compliance team to help. They do it all day, every day.