Register the brand before you send: the 10DLC rule that silently blocks church texts

Nine inches of snow fell overnight. At 6:40am the pastor sends one message to 300 people saying there is no service. By 8:15, forty families are standing in an unplowed parking lot, because the message was accepted by the platform, billed to the church, and never delivered.

Nobody sent an error. That is the part churches do not expect. In the American mobile network, a message that fails carrier filtering usually fails quietly.

Why the message did not arrive

Text sent by software to a person is application-to-person messaging, and since the carriers moved it onto standard ten-digit numbers it runs through a registration system called A2P 10DLC. The Campaign Registry, which operates the registry behind it, describes 10DLC as “an A2P messaging channel in which Brands and Campaign Service Providers (CSPs) are verified prior to being allowed to send messages.”

Two facts follow, and both surprise churches.

You cannot register yourself. The Campaign Registry states that brands do not register directly. A registered Campaign Service Provider submits the brand, then registers the campaign, which returns a Campaign ID that permits delivery. Your texting vendor is that provider. If they have not completed it for you, your traffic is unregistered traffic.

Both the sender and the content are declared in advance. In the registry’s own framing, “Brands, CSPs, and messaging content are all known upfront, meaning both the ‘Who’ and the ‘What’ of a campaign are traceable.” Your registered campaign describes what kind of messages you send and what your opt-in looks like. Sending outside that description is how a church that registered for service reminders gets throttled the week it starts sending a fundraising appeal.

Trace the snow message through the whole path and the failure point is one gate, three steps in.

Ask your vendor three questions before the next storm, and get the answers in writing.

1. Is our brand registered, and under what legal name and EIN?
2. What campaign use case are we registered under, and what does it permit?
3. What is our current per-minute throughput, and what happens to a 900-person send at 6:40am?

If the church has a texting platform and nobody at the church can answer question one, the church does not know whether its emergency channel works. Test it on a clear Tuesday, not on the first bad Sunday.

Pricing, throughput, and the vendors themselves are compared in church texting services priced by congregation size. This page is the policy that sits behind the platform.

Consent, and the carve-out that does not save you

The Telephone Consumer Protection Act at 47 U.S.C. 227 restricts automated calls and texts to a “telephone number assigned to a paging service, cellular telephone service, specialized mobile radio service, or other radio common carrier service” without the required consent.

There is a nonprofit carve-out and it is narrower than church staff assume. The statute’s definition of “telephone solicitation” at 227(a)(4)(C) excludes messages made “by a tax exempt nonprofit organization.” That exclusion is about solicitation. It is not a general license to text anyone whose number you hold, and it does nothing about the carrier layer, which is where your message actually dies.

The industry rules are the ones that bite first. CTIA, the wireless industry body, publishes Messaging Principles and Best Practices built on consent, opt-out keywords, and clear identification of the sender. Carriers enforce those principles by filtering. There is no appeal, no notice, and no refund.

Which produces one working rule: collect consent as though you will have to prove it, and identify yourself in every message as though the reader has forgotten who you are.

The consent sentence, and the five-field record

Put this on the connection card, the website form, and the class registration:

I agree to receive text messages from [Church]. Message frequency varies. Message and data rates may apply. Reply STOP to opt out, HELP for help.

Then keep a record the church owns, not a record that lives only inside the vendor. Five fields per number.

1. The phone number.
2. The date consent was given.
3. The method it came through: card at the welcome desk, web form, class signup, spoken request logged by a named person.
4. The exact wording the person saw when they agreed.
5. The date and method of any opt-out.

When a member says they never signed up, the record ends the conversation in ten seconds. When you change platforms, the record is the thing you carry across. Platforms are replaceable. A list you cannot prove is a list you rebuild from zero.

Filled in, one row looks like this, and the fourth field is the one that does the work.

Never add a visitor to a recurring list because they filled out a card asking about the nursery. Consent is to a purpose, not to the church in general.

What a church should text

Use SMS for messages that lose their value if they wait until Thursday.

• Closures and emergencies. “Sunday worship is cancelled, ice on the roads. Next Sunday 10:30. Please phone an older member near you.”
• Schedule changes inside 24 hours. Evening service moved, pickup delayed, entrance closed.
• Prayer chain requests, to the group that opted into the prayer chain, not to the whole roster.
• Care coordination. A deacon asking three named people to bring meals, without broadcasting the medical detail.
• Reminders for things people registered for. Baptism class tonight at 7, nursery volunteers report at 8:45.

Everything else belongs in the newsletter, the bulletin, or the Sunday announcements.

What a church should never text

• Daily devotional messages to people who asked for closure alerts.
• Fundraising appeals to a list that opted in for emergencies. This is the fastest route to a filtered number.
• Doctrinal argument, political comment, or anything about a member that is not already public.
• Photographs of minors, or medical detail with identifying information attached.
• A serious pastoral matter that requires a person in a room.

HIPAA does not protect your prayer chain

Church staff often reach for HIPAA when a prayer request goes too far. It does not apply. Under 45 CFR 160.103, a covered entity is a health plan, a health care clearinghouse, or a health care provider transmitting health information electronically in connection with a covered transaction. A congregation is none of those.

The absence of a federal rule raises the standard rather than lowering it. Nothing outside the church will stop a prayer chain from turning a diagnosis into gossip, so the church has to. Give the chain a moderator with authority to strip last names, to hold a message, and to end a thread that has moved from prayer to speculation. Send what the family approved, in the family’s words, and nothing further.

Quiet hours and volume

Default sending window: 8:00am to 8:00pm local time, and outside it only for something that changes what a person will do in the morning.

One message per situation. If nothing has changed since the last one, do not send another. A list that gets five updates about one cancelled service is a list that stops reading the sixth, and the sixth is the one about the funeral.

Who is allowed to press send

Name two people who can send a closure: the pastor and one designated elder or administrator. Pastoral crisis messages go through the pastor. Volunteers do not text the congregation on their own initiative.

Write the sending policy on one page and keep it beside the platform login. It names who approves, what hours are acceptable, which topics require an elder, and how the consent record is updated. A one-page document is what stops a well-meaning volunteer texting 300 people at 11:00pm about a change of potluck venue.

Document who holds platform access, and remove it the week a staff member or volunteer rotates off. Review the list quarterly: drop numbers that bounce, mark members who have moved or died, and confirm each segment still matches its stated purpose.

Do this in the next two weeks

Email your vendor and ask whether your brand and campaign are registered, under what name, and for what use case. Put the consent sentence on every form the church uses. Start the five-field record from the next number you collect. Then send one test message to yourself at 6:40am on a weekday and confirm it lands.

Match the sending schedule to the content calendar so texts reinforce the rest of what the church is saying rather than arriving on top of it.

Sources

• The Campaign Registry, homepage and A2P 10DLC overview. Checked 29 July 2026.
• CTIA, Messaging Principles and Best Practices. Checked 29 July 2026.
• Legal Information Institute, Cornell Law School, 47 U.S.C. 227, Restrictions on use of telephone equipment. Checked 29 July 2026.
• Legal Information Institute, Cornell Law School, 45 CFR 160.103, Definitions. Checked 29 July 2026.
• The FCC’s own consumer guidance on unwanted texts was refused to our fetch (HTTP 403) on 29 July 2026, so the statute is cited directly rather than the agency summary.