A church texting app lives or dies on who agreed to be on the list.
A church texting app is the one piece of software a congregation notices the first week. Snow closes the building on a Sunday morning and four hundred people need to know inside ten minutes. Someone goes into hospital and the prayer chain needs one message, not forty phone calls. Text still does that better than anything else, because it lands on a locked screen with nothing installed and no account to remember. It sits alongside the rest of the church management apps a church already runs, and it is usually the piece they outgrow first.
This page covers the consent rules that decide whether you may send at all, what a blast really costs once messages are counted properly, how groups and replies work in practice, and why a message the carrier accepted never reached the phone.
Work out what a month of texting costsThe short version
Sending is the easy half, the list is the whole job.
Every church texting project starts as a sending problem and turns into a list problem. One message reaching many phones is a solved thing that costs fractions of a cent. Proving each of those phones agreed to receive it, and stopping the moment someone asks you to, is the part that takes the work.
The second surprise is that the phone network has opinions. US carriers decide what actually gets delivered, they want the sending organisation registered against the number, and they filter traffic that looks like it is going to people who never asked for it. A church SMS app that ignores this looks like it is working while a slice of every send quietly disappears.
Opt-in is the product, not a checkbox
Federal rules restrict automated calls and texts to mobile numbers, and the FCC has long treated a text as a call for this purpose. Under 47 CFR 64.1200, a call placed to a mobile number with an automatic telephone dialing system or an artificial or prerecorded voice needs the prior express consent of the called party, unless it is made for emergency purposes. Where the message includes or introduces an advertisement, or counts as telemarketing, the bar rises to prior express written consent.
Revocation is written into the same rule. A person may revoke consent by any reasonable method that clearly expresses a desire not to receive further calls or text messages, and the request has to be honored within a reasonable time not to exceed ten business days from receipt. In software terms that is not a preference screen. It is an inbound message handler watching for STOP and its cousins, writing the change straight away, and removing the number from every future send including the one already queued.
Whether your particular setup meets the legal definition of an automatic telephone dialing system is a contested question with real case law behind it, and this page is not legal advice. For a church it barely matters, because you need the opt-in regardless: carriers require it as a condition of delivering your traffic, and someone who gets a text they never asked for complains to the office long before they complain to anybody else. Collect consent on a form people sign or tap, store the date and the exact wording they agreed to, and keep it where you can produce it.
The awkward case is money. A message asking the congregation to give is not obviously encouraging the purchase, rental or investment that the telemarketing definition turns on, and charitable solicitation is treated differently again in places. We could not find one clean answer that covers every church, so take the conservative reading: word the opt-in so it names giving reminders explicitly, and get a lawyer's view before the first appeal goes out.
What a text blast actually costs
Per-message pricing is published, which makes this the easiest number in the project to get right. Twilio, the SMS API most of these builds end up on, lists US SMS at $0.0083 per message outbound and $0.0083 inbound, the same base rate for long codes, toll-free numbers and short codes. Carrier fees are charged on top of that per message and vary by carrier and number type. The published examples for the major carriers sit between $0.0035 and $0.0045 per outbound message.
Two things multiply it. Text is charged per segment, and a segment is 160 characters of plain GSM text, falling to 153 characters each once a message has to split. Put a single emoji or a curly apostrophe in it and the encoding changes: the limit drops to 70 characters, and 67 per segment when split. A chatty 300 character announcement to 400 people is 800 billable messages, not 400, and nobody notices until the invoice.
The other cost is the number you send from. US carriers treat everything coming from an application as A2P traffic and want the organisation and the campaign registered against the sending long code. Unregistered traffic gets filtered harder and picks up extra carrier fees, so registration is not optional in any practical sense, and it takes days rather than minutes. Budget the wait as well as the money. The messaging bill for a church sending weekly to a few hundred people lands in the tens of dollars a month, plus a small monthly fee for the number itself.
Twilio, published SMS pricing for the United States
Try it
What a month of texting costs
Billing is per segment, not per announcement. A long message and a single emoji both split one send into several.
$27.89 of messages
2 segments per person per send, so 3,360 billable messages at the published rate of $0.0083 each. Carrier fees are added per message: at $0.004 that is $13.44 more, plus a monthly fee for the number itself.
Groups, replies and the volunteer sending at 7am
The list is never one list. A church has the whole congregation, the youth parents, the worship team, the three people who unlock the building, and a prayer chain that has to move without waiting for anyone's approval. Each of those is a separate consent record and often a separate sender. A congregation messaging app built around one broadcast list gets worked around inside a month, usually by a volunteer starting a group chat on a personal phone.
Replies are what homegrown tools forget. If the message comes from a number nobody owns, a reply goes nowhere, and people do reply: to say they cannot make it, that their mother is in hospital, that they will bring the chairs. Decide early whether inbound messages land in a shared inbox that a named person is responsible for, or whether the number is announced as send only and the message says where to call instead. Both are defensible. Silence is not.
Who may send is the other decision, and it is a governance question wearing software clothes. A text that reaches four hundred phones at 7am is a serious instrument. Most churches want a couple of people who can reach everyone, more people who can reach only their own group, and a log of what went out under whose name. That is the same permission shape as a church giving app or a parent teacher communication app, so copy it rather than inventing a new one.
Why the message did not arrive
SMS delivery is not a guarantee, and the status your app gets back is weaker than it reads. A carrier can accept a message and never hand it to the handset, and the receipt will not always tell you. Filtering is the usual reason: an unregistered number, a public link shortener the carrier distrusts, wording that scans like a promotion, or a sudden spike in volume from a number that normally sends almost nothing.
Design around it instead of arguing with it. Send from a registered number, name the church in the first message anyone receives from it, keep the opt-out wording in recurring sends, and use your own domain in links rather than a shortener. Then watch the delivery receipts and treat a rising failure rate as an operational alarm with a person attached, not as a glitch that will settle down.
There is also a fair question about whether text is the right channel for everything. A weekly bulletin does not need to interrupt anybody, and once people have your app on their phone, a push instead of an SMS costs nothing per message and carries none of the carrier baggage. The catch is that push only reaches people who installed the app and left notifications switched on, which is why the emergency channel stays on SMS while the routine traffic moves off it.
What each way of texting the congregation gives you
| Option | One send reaches everyone | STOP handled for you | Replies reach a person | List stays yours |
|---|---|---|---|---|
| Group text from a personal phone | No | No | and everybody else | No |
| Facebook group or WhatsApp | only those who look | No | Yes | No |
| Texting inside a church platform | Yes | Yes | sometimes | held by the vendor |
| Bulk SMS provider plus a spreadsheet | Yes | Yes | No | Yes |
| A texting app you build | Yes | you wire it up | Yes | Yes |
Building one that fits your church
Church management platforms include texting, and if you already pay for one, start there and see how far it goes. What sends people looking elsewhere is rarely the sending itself. It is that the platform's idea of a group does not match how the church works, that texting sits behind a higher plan tier, or that the list lives somewhere the church cannot export from.
Newly is an AI app builder. You describe the app you want, including who may send to whom and what the opt-in wording says, and it writes a real React Native and Expo project you own, runs it on a cloud iPhone or Android simulator while it builds, and ships it to TestFlight and to Google Play internal testing. Plans are $25 a month and there is no free plan. iOS distribution needs your own Apple Developer account. It is not an SMS provider and it does not hand you a phone number, so the messaging account and the carrier registration stay yours to set up.
One honest scoping note. The genuinely hard parts of a church text blast app are consent and delivery, and no builder removes either. What a custom app removes is the mismatch: your groups, your roles, your wording, and a record of who agreed to what that you can actually produce when somebody asks.
Questions people ask about church texting apps
Software that sends one SMS to many people in a congregation, holds the record of who agreed to receive it, and handles opt-outs automatically. The useful ones also model groups, so the youth parents and the worship team are separate lists with separate senders, and they keep a log of what went out and who sent it.
Describe the lists your church actually has
Write down who may text whom, what the opt-in says, and the one message that can never be missed, then build the app around that.
Start building