Communication

Church texting rules: consent, opt-in, STOP, and getting your number verified

Texting your congregation isn’t exempt from the rules just because they’re your members. Here’s what consent looks like, how STOP has to work, how toll-free verification and 10DLC registration differ, and why some church texts never arrive.

The Sanctuary teamSanctuary9 min read

What does a church need before it texts people?

Three things: permission from each person for that kind of message, a clear way for them to stop, and a sending number the carriers have verified or registered. Being a church, and texting people who already attend, changes some of the legal details. It doesn’t remove any of those three.

Most church texting problems aren’t lawsuits. They’re messages that never arrive because a carrier filtered them, often without anyone noticing. The habits that keep you within the rules are the same ones that keep your texts getting delivered.

Why “it’s just our members” isn’t an exemption

Churches often assume these rules are for marketers. Here’s why they apply to you too:

  • The federal rule. The FCC’s rule under the Telephone Consumer Protection Act, 47 CFR 64.1200, requires prior express consent for calls to a mobile number made with an autodialer or a prerecorded voice. The same section’s opt-out paragraph applies to “calls or text messages”. Its exceptions for tax-exempt nonprofits are narrow. They relax the written-consent requirement for telemarketing, and they leave nonprofits out of the definition of a “telephone solicitation”. They don’t remove the need for consent. Whether a particular texting tool counts as an autodialer is a question for your attorney.
  • The carriers. CTIA lists non-profit organizations among the senders its best practices apply to. It says senders are expected to get consent and offer a way to revoke it, whether or not the legal rules apply. Carriers enforce this by filtering messages, not in court.
  • The number they gave you. Someone put their number in your directory so the church could reach them, not so you could add them to a broadcast. Ask before the first text, even if you’ve had the number for years.

Another common mistake is a staff member group-texting two hundred people from their own phone. CTIA treats texts from organizations, including non-profits, as non-consumer traffic. And a personal phone keeps no record of who agreed or who asked to stop.

What good opt-in wording looks like

CTIA says a call to action should make clear what the program is, which number the texts come from, who’s sending them, any fees, and how to opt out and get help, with a link to a privacy policy. For a church, that fits in two sentences next to a checkbox that isn’t already checked:

  • Save the wording the person saw, plus when and how they agreed. CTIA lists the timestamp, the method, the language used, the campaign and the phone number among the records to keep. Twilio requires proof of consent when it asks for it.
  • After someone opts in to recurring texts, send a confirmation that names the program, how often you text, and how to stop. CTIA recommends sending this before any other message.
  • Never buy, borrow or merge in a list.

STOP, HELP and opting out

The FCC’s rule spells this out. A reply of “stop”, “quit”, “end”, “revoke”, “opt out”, “cancel” or “unsubscribe” revokes consent. So does a reply in other words that a reasonable person would understand as a request to stop. You can’t insist on one particular way to opt out, and you have to honor the request within a reasonable time, no more than ten business days. In practice, stop right away.

  • Tell people how to stop. Twilio requires opt-out wording such as “Reply STOP to unsubscribe” in the first message, and CTIA recommends standard STOP wording.
  • Confirm once. Both CTIA and Twilio allow one last message confirming the opt-out. After that, don’t send anything.
  • When someone texts HELP, reply with who you are and how to reach a person.
  • Make sure a STOP applies to every ministry that uses the number.
  • Read the replies. “Please take me off this” is a stop, even without the keyword.

Quiet hours

The federal rule’s 8 a.m. to 9 p.m. window, in the recipient’s local time, is written for telephone solicitations. The same rule says that term doesn’t cover calls by or on behalf of a tax-exempt nonprofit. Some states have their own rules, and they may be different. Whatever applies to you, follow that window anyway as a courtesy. Don’t text before 8 or after 9 in the recipient’s time zone unless it’s an urgent change to something happening soon, and if it is, say so in the message.

Toll-free vs 10DLC

When you text from software instead of a phone, you send from one of three kinds of number: a toll-free number, a regular ten-digit local number (10DLC), or a short code. This guide doesn’t cover short codes. The other two have to be verified or registered before Twilio will deliver to US phones.

Toll-free and 10DLC numbers for church texting, based on Twilio’s documentation
QuestionToll-free number10DLC (local number)
What you fileToll-free verification: business details, address, the use case and the opt-in flowA Brand (who you are, and standard brands need a tax ID such as an EIN) and a Campaign (purpose, opt-in, opt-out and help)
If you skip itTwilio blocks traffic from unverified toll-free numbers to the US and CanadaTwilio blocks messages to US numbers from unregistered 10DLC numbers
Good fit whenYou want one number for the whole church and a single filingA local number matters to your members, and you can manage brand and campaign registration

Whichever you pick, the reviewer will look for the opt-in you describe. Have a public page or form that shows exactly how people agree to texts, what they’ll get and how to stop. Make sure the church name and address match what the reviewer will find elsewhere.

What gets church texts filtered

Carriers filter messages that look unwanted, no matter who sent them. These are the most common reasons:

  • Unverified or unregistered numbers, as covered above.
  • Public link shorteners. CTIA says that if a sender uses a shortener, it should be one dedicated to that sender, and links should clearly identify who owns the website. A free, shared shortener fails both. Use your own domain, written out in full.
  • Links that hide who’s sending, or that go to a page that doesn’t name the church.
  • Messages that don’t say who they’re from. Twilio requires each message to identify the sender, except replies in a conversation.
  • Sending the same message from lots of numbers to get around limits. CTIA calls this snowshoeing and says senders shouldn’t do it.
  • Texting people who never agreed, or who said stop.

Links are usually the first thing to get filtered, and that includes ours. Before you send an important text with a link to everyone, test it on a few staff phones on different carriers.

A church texting compliance checklist

  1. 1Decide what you’ll text about and write it down: announcements, serving, giving, events.
  2. 2Get your toll-free or 10DLC number verified or registered before you send anything.
  3. 3Publish an opt-in form or page with clear wording, an unchecked box and a link to your privacy policy.
  4. 4Record each yes with the date, method and wording. Ask separately for each purpose.
  5. 5Send a confirmation when someone signs up for recurring texts.
  6. 6Put opt-out wording in the first message, and remind people regularly.
  7. 7Honor STOP right away across every ministry using the number, and reply once to confirm.
  8. 8Answer HELP with the church’s name and a way to reach a person.
  9. 9Keep texts between 8 a.m. and 9 p.m. in the recipient’s time zone.
  10. 10Use your own domain for links, never a public shortener.
  11. 11Review delivery failures every month, and stop texting numbers that keep failing.

How Sanctuary handles this

Sanctuary Texting gives each church its own US toll-free number. Sanctuary fills in the toll-free verification from your church’s details, you check it, and then we file it. The number doesn’t send anything until the carriers approve it. Each church also gets a public page that describes its texting program: how people join, what they’ll get and how to stop. Both the reviewer and your members can see it.

Consent is kept per phone number, separately for announcements and for serving texts. If there’s no record of a yes, Sanctuary treats it as a no. A texting checkbox on a Core form saves the exact wording each person agreed to, and staff can record a yes someone gave in person. A STOP silences that number for every app the church uses, and nobody on your team can override it. START lifts the STOP, but it doesn’t sign anyone back up for announcements or serving. The church has to ask again. Announcements and serving texts get “Reply STOP to opt out.” added when that person hasn’t seen it in the last 30 days. Each text shows whether it was delivered. If one fails, it tells you why and gives the credit back.

The same number handles text giving. Someone texts GIVE and an amount, finishes setup through a link the first time, and the gift goes to the church’s own Stripe account, within limits the church sets. Links Sanctuary sends, such as a Family Pass, point to onesanctuary.app instead of a public shortener.

What texting software can’t do, including ours

  • No software makes you compliant. It can keep records and enforce the rules it knows about, but what you text and who you text it to is still your decision.
  • Sanctuary only offers toll-free numbers. If a local number matters to your church, you’ll need a provider that registers 10DLC.
  • Sanctuary doesn’t hold texts for quiet hours. When you press send, it sends.
  • Sanctuary records STOP and the other standard keywords when they start a reply. If someone opts out in other words, like “please stop texting me”, a person has to read it and record the no.
  • Texting is billed separately from every plan. The number is a monthly charge, and messages use credits the church buys.

Sources

  • Federal Communications Commission rule 47 CFR 64.1200, Delivery restrictions, Electronic Code of Federal Regulations, ecfr.gov (current text, opened November 15, 2026).
  • CTIA, Messaging Principles and Best Practices, May 2023, ctia.org (opened November 15, 2026).
  • Twilio, Messaging Policy, twilio.com (opened November 15, 2026).
  • Twilio, Toll-free verification console onboarding guide, twilio.com/docs (opened November 15, 2026).
  • Twilio, Programmable Messaging and A2P 10DLC, twilio.com/docs (opened November 15, 2026).
  • Twilio, Error 30032 (toll-free number not verified) and Error 30034 (message from an unregistered 10DLC number), twilio.com/docs (opened November 15, 2026).

See how Sanctuary keeps the work connected

Sanctuary keeps people, serving and giving on the same record. Core is free, with no limit on how many people you keep in it.