Church text messaging: what to send, how often, and who owns it
A church should text for three reasons only: a reminder inside 48 hours of an event, a same-day change, and a personal follow-up to one person. Everything else belongs in email or the bulletin, and one named person, not the whole staff, should hold the send button.
Text for three reasons only: a reminder inside 48 hours of an event, a same-day change, and a personal follow-up to one person. Cap frequency, name one owner with an approval step, and confirm current opt-in rules with counsel before building a list.
Somebody complained the church texts too much. Or the opposite happened: half the volunteer team never showed up because the reminder never went out, and everyone is now blaming a system that never existed in the first place. Either way, you are looking for the actual rule, not another list of general texting best practices.
This is one page in our guide to the church operations playbook. Most of what gets written about church texting says "keep it short" and "don't overdo it," which is true and useless. Here is the actual policy: three categories, a stated cap, one named owner.
What should a church actually text people about?
Three categories cover almost everything a text should carry:
- A reminder inside 48 hours of an event. "Nursery volunteers, we start at 8:45 tomorrow, not 9." Timely, specific, tied to something already on the calendar.
- A same-day change. A room swap, a weather cancellation, a service time shift discovered that morning. Text is the only channel fast enough to matter.
- A personal follow-up to one person. A guest who visited Sunday, a volunteer who missed their slot, a family the office wants to check on. One person, one message, not a blast.
Everything outside those three, a monthly newsletter, a general announcement about a sermon series, a request for donations, belongs in email or the bulletin, where the reader controls when they open it. That is not a smaller channel. It is the right channel for content that is not urgent.
How often is too often?
The frequency cap is simple: no more than one reminder text per event inside the 48-hour window. If a second touch is genuinely needed, a call or a personal text from a real person, not a second mass send, is the better move. Blasting the same list twice in one day for two different ministries is how a church earns the "texts too much" complaint, even when each individual message was reasonable.
Basic opt-out etiquette matters here too. Every list-based text should carry a clear way to stop receiving them, and a request to stop should be honored immediately, not just noted for later.
Text, email, or announcement, which channel for which message?
| Message type | Best channel | Typical timing |
|---|---|---|
| Event reminder | Text | 24 to 48 hours before |
| Same-day change | Text | As soon as it's confirmed |
| Personal follow-up | Text or call | Same day to 72 hours |
| Weekly announcements | Email or bulletin | Standing weekly cycle |
| Ministry updates, sermon series | Email or newsletter | Monthly or as scheduled |
| Stage or in-service announcement | Live, from the platform | During the service itself |
A starting framework for channel assignment. Adjust timing for your own service schedule and staff capacity.
Notice the pattern: text handles anything time-sensitive and short. Every other channel handles anything that can wait for the reader's own schedule. Confusing the two is the root of both complaints, texting too much and missing the reminder that actually mattered.
A stage announcement lands in the same window as a text reminder, live during the service, but it reaches a different audience: the people already in the building, not the ones deciding whether to come. Treat the two as complements, not substitutes. A same-day change announced from the platform still needs a text to reach the people who haven't arrived yet.
Who should own the church's text messaging?
One named person, with an approval step before any mass send goes out. Not the whole staff with equal access to the send button, and not a rotation that changes week to week. Whoever runs the weekly office rhythm is usually the right owner, since text reminders are one more recurring task tied to the calendar, not a separate communications function.
The approval step does not need to be heavy. A same-day change might not have time for a second set of eyes, and that is fine, name the exception in advance rather than discovering it under pressure. Everything else, a standard reminder or a scheduled send, should get a quick look from a second person before it goes to the full list.
Ownership also means someone is watching the pattern over time, not just approving one message at a time. If three ministries each send their own reminder in the same week and nobody notices until the complaints roll in, that is an ownership gap, not a texting problem. One person seeing every outgoing message, even briefly, is what catches that before it becomes a pattern worth complaining about.
Why one owner beats a rotation
A rotation means no one person notices the pattern: the same ministry sending three texts a week, or a reminder going out at 6 a.m. because whoever was on duty that week didn't think about the time. One owner catches both.
CoLabor Staffing places full-time Christian co-laborers with churches and Christian-owned businesses, and a fixed communication channel like this is exactly the kind of recurring, well-defined task that transfers cleanly to one person who runs it the same way every week.
What are the compliance basics a church needs to know before texting a list?
This is not legal advice, and no blog post should try to give you legal advice on this. Rules around consent, opt-in, and quiet hours for text messaging exist, apply to organizations sending to a list, and change over time. Confirm the current requirement with your church's counsel before you build or expand a text list, not after.
What you can do in the meantime: capture consent when someone provides a phone number, whether that is a guest card checkbox or a volunteer sign-up form, and track that opt-in status somewhere reliable, usually inside your church database alongside the rest of that person's record. A clean, current record of who agreed to receive texts is the foundation any compliance requirement gets built on top of. Guessing at consent after the fact is the position nobody wants to be in.
Quiet hours are worth naming even before counsel weighs in on anything more specific: sending a reminder at 6 a.m. or 10 p.m. is a bad idea on its own merits, independent of any rule requiring otherwise. Building the habit of sending within a reasonable daytime window protects the relationship with the recipient regardless of what the legal minimum turns out to be.
How does text messaging fit into guest follow-up specifically?
Guest follow-up is the single best use case for a personal text, and it runs on its own tighter clock. The first 72 hours after a first-time guest visits determine most of what happens next, and a short, personal text without an ask attached is usually the first touch in that window. The full timeline, hour by hour, is in our post on the 72 hours that decide whether they come back.
The distinction matters: a guest follow-up text is a personal message to one person, not a mass send to a list, so it does not carry the same list-consent questions as a group text campaign. Keep that line clear in how your team thinks about texting, because the two situations look similar on a phone screen and are not the same thing operationally.
If texting is one piece of a bigger communications puzzle at your church, a bulletin deadline, an email newsletter, a social post, all competing for the same announcement, see our post on building a church communications calendar for how those channels fit together. And if the newsletter itself has gone stale, church newsletter ideas people actually open covers the fix for that specific channel.
Running this policy every week, the same three categories, the same cap, one named owner, is exactly the kind of recurring work a co-laborer runs on a fixed schedule, so it never depends on someone remembering to hit send. Here is how it works.
Common questions
How often should a church text its members?
For reminders, no more than once inside a 48-hour window per event. Anything more frequent than that should be a personal, one-to-one message, not a mass send.
Who should be allowed to send church text messages?
One named owner with an approval step before any mass send goes out, not the whole staff with access to the send button.
Is it legal to text church members without their consent?
Rules around consent and opt-in vary and change. Confirm the current requirement with counsel before building a text list, rather than relying on general advice from a blog post.
What should a church never text about?
Anything that is not a time-bound reminder, a same-day change, or a personal follow-up belongs in email or the bulletin, which the recipient can read on their own schedule instead of on the church's.
Should church text messages include a way to opt out?
Yes. A clear opt-out option on every list-based text is standard practice and something to confirm meets current requirements with counsel, not something to skip because the list is small.