It was 6:47 on a Sunday morning, the kettle wasn't even done boiling, and Sister Immaculate was standing in her kitchen in Ntinda with her phone in one hand and her heart somewhere near her shoes. She had just sent "test test ignore" to 640 people.
Not a draft. Not a note to self. All members.
She'd logged into the bulk SMS portal the night before to get a head start on the 8am service reminder, typed a placeholder message the way you'd scribble on a notepad, and hit send to make sure the platform was actually working before she wrote the real thing. The portal didn't ask her to confirm the recipient count. It didn't show her a cost before it fired. It just took the message, took the list, and sent.
By 7am her phone would not stop buzzing. Not with typical replies, either — with the specific, wounded confusion of people who take their church seriously. "Who is this?" "Test what?" "Ignore what, the service?" One uncle, bless him, replied "Received. Noted." like it was an official memo. A choir member called to ask if the 8am service had been cancelled, because "ignore" sounded final. By the time Sister Immaculate got to church, three people had already asked the pastor directly if something was wrong.
If you've run church communications for more than a month, you already know this isn't really Sister Immaculate's story. It's everyone's. Ask any admin, secretary, or long-suffering pastor's assistant who has ever sent a bulk message in Uganda, and they'll have their own version — the wrong list selected, a message sent to "Youth" that should have gone to "Ushers," a funeral announcement with a typo in the burial time that nobody caught until condolence calls started asking which time was correct.
Why this keeps happening, and it isn't really about typing carelessly
Here's the part that doesn't get said enough: this isn't really a story about someone being careless. It's a story about the tools.
A typical bulk SMS portal — the kind built for banks, schools, SACCOs, and retailers as much as for churches — has no idea what a church actually is. It knows phone numbers on a list you uploaded. It doesn't know that "All Members" is a different, more sacred category than "People I Once Put In a Spreadsheet." There's often no built-in pause between composing and sending, no visible recipient count sitting right in front of you at the moment your thumb is over the send button, nothing that makes you actually look at what you're about to do before you do it. You compose, you pick a list, you send — and the platform trusts you to have already done the thinking it should be helping you do.
That's not a flaw unique to any one platform. It's structurally how the category works: you're managing your actual member records somewhere else — a notebook, a WhatsApp group, an old spreadsheet three people have edited differently — and the SMS tool is just the loudspeaker, disconnected from the truth of who's actually on the other end.
What actually helps, and what doesn't pretend to be magic
FaithDash doesn't claim to read your mind before you hit send. But because the recipient groups aren't lists you uploaded last Tuesday — they're the church's live member database, filtered by segments that already mean something (All members, Visitors only, Members only, Leaders only, or a tag like Choir or Youth) — the person sending sees exactly who "All Members" actually is, not a guess. And because the composer shows a live character count, the SMS part count, and the cost for that exact recipient group before you send, there's a natural, visible moment where the numbers in front of you say "640 people, X parts, this many shillings" — the kind of thing that makes most people glance up and re-read what they typed.
It won't stop every "test test ignore." Nothing stops human beings from being human beings on a Sunday morning before coffee. But it closes off the specific, structural version of the disaster — the one where the list itself was wrong, stale, or misunderstood, because nobody who set up the send actually had visibility into who was on it.
At UGX 35 per SMS part, even a mistaken send to the whole church isn't a financial catastrophe — it's an embarrassing one. The real cost of Sister Immaculate's Sunday wasn't the shillings. It was the ten minutes before the 8am service spent reassuring people that nothing was wrong, when she should have been reviewing the sermon slides.
If you've had your own "test test ignore" moment, you're in good company — nearly every admin has one. The goal isn't to never make a mistake again. It's to make the kind of mistake that's just a typo, not a whole misfired list. FaithDash won't write your Sunday reminder for you, but it'll at least show you who's about to read it before you find out the hard way.