Write Announcements People Actually Read
Decide what earns a notification and what doesn't, write for a phone lock screen, and set a sending rhythm your congregation won't mute.
The notification nobody opened
A church sends a push notification every time anything happens: a schedule change, a birthday, a reminder about the reminder. Within two months, a third of the congregation has turned notifications off, and now the one message that genuinely mattered — the service is cancelled, the roads are ice — doesn't reach them either.
The permission to interrupt someone's phone is finite. You spend it or you save it, and most churches spend it without noticing until it's gone.
The Foundations module on reaching your congregation diagnosed why messages get missed. This module is about writing and sending the messages themselves.
What earns an interruption
A simple filter: would you phone someone at home about this? If yes, it earns a notification. If no, it belongs somewhere people go looking — the app, the website, the bulletin — rather than somewhere that buzzes.
Things that clear the bar: cancellations, venue changes, genuine emergencies, and time-sensitive things people asked to be told about. Things that don't: routine reminders about recurring events, general encouragement, and anything that could as easily wait for Sunday.
One useful discipline is a weekly cap you commit to in advance — say two. A cap forces the ranking, and the ranking is the whole skill. Note too that free tiers on many platforms include a monthly sending limit, which is worth checking against your intended rhythm before you plan around it.
Writing for a lock screen
Most people will read your message as a truncated line on a locked phone, in about a second and a half, while doing something else. Write for that, not for the full-screen version you're composing in.
Front-load the actual news. "Sunday service moved to 9am this week" works; "An important update from the leadership team regarding this Sunday" wastes the only words that will be seen. If someone can act on it without opening the message, you have written it well.
Be specific about time and place, and never assume context. "Practice is cancelled" raises more questions than it answers — which practice, whose, when was it, is it rescheduled.
One more thing worth saying plainly: proofread the ones that go to everybody. A push notification cannot be recalled once sent.
Rhythm beats volume
A congregation learns your pattern faster than you'd expect. If messages arrive unpredictably, people either check constantly or tune out entirely — and it's almost always the second.
Pick a regular slot for anything routine, so people know when to expect it, and reserve unscheduled sends for things that genuinely can't wait. Where a platform supports scheduling ahead, that's what it's for: writing on Thursday and delivering Saturday morning, rather than sending whenever you happen to be at a desk.
Watch delivery and open figures if your platform reports them, but read them as a trend, not a scorecard. A steady decline over two months usually means you're sending too much, not that people stopped caring.
How the tools differ here
SMS services — Twilio-based tools, Text In Church. Highest open rates, real per-message cost, and people notice quickly when a church uses their phone number too freely.
Email platforms — Mailchimp and similar. Effectively free at church volumes, more room to write, and much lower urgency; wrong channel for a cancellation an hour before the service.
Church apps with push notifications — Subsplash, Tithe.ly, Breeze, and Faith Software's own myChelper among them. Push costs nothing per message and reaches only people who installed the app, which makes it strong for the committed core and weaker for the edges of your congregation. Sending limits and whether you can schedule ahead often depend on the plan, so check both against the rhythm you're planning.
Most churches end up using two of these deliberately rather than one exclusively — push for the people who opted in, and something else for everyone who didn't.
Your exercise
Look back at the last ten messages your church sent to everyone. For each, ask the phone-call test: would you have called someone at home about that? Count how many pass. Most churches find it's about half — which is exactly the ratio that trains people to ignore the other half.
Then write your next announcement twice: once as you normally would, once in under ten words with the news first. Send the second one.
Check Your Understanding
5 questions. Pass at 4 of 5. Your answers are scored on our server — so the correct answers aren't sitting in the page you're reading — and aren't linked to you unless you request a completion record below.
Answer all 5 questions to see your results.