The reply came in at 9:14pm, three words, no punctuation: "Stop texting me." Brother Wasswa, who handles messaging for a mid-sized parish in Mukono, read it twice before he understood what had actually happened. The number belonged to a man who'd visited the church exactly once, eight months earlier, filled out a visitor card out of politeness more than interest, and had been quietly annoyed ever since by the steady trickle of event reminders that followed — a Christmas service invite, an Easter one, a men's breakfast he had no intention of attending.
Brother Wasswa's first instinct was defensiveness — the messages weren't spam, they were church announcements, surely that's different. His second, more honest instinct, a few minutes later, was that it genuinely didn't matter how he categorized the messages in his own head. The man on the other end had asked, plainly, to stop. Whatever the message's category, ignoring that request was going to feel exactly like spam to him, because functionally, at that point, it was.
What actually happens when someone replies "STOP"
Here's the honest, slightly uncomfortable truth: FaithDash doesn't have a two-way SMS inbox where a "STOP" reply automatically flags itself and shuts off future messages to that number. Replies to an SMS sent from the system land as an ordinary text message on whichever number the church's SMS is sent from — visible on that phone, not inside the FaithDash dashboard, because FaithDash doesn't offer two-way SMS chat threads as a feature. That's worth being upfront about, because it would be easy to assume otherwise.
What that means practically is that the responsibility for noticing and honoring an opt-out request sits with a human being — whoever is watching the sending number, or whoever gets told about it. That's not a gap unique to FaithDash; it's true of essentially every bulk SMS platform in this category, generic portals included. None of them read incoming replies and automatically silence a number on your behalf unless you've built that logic yourself, and a non-technical church admin generally hasn't.
What Brother Wasswa actually did about it
Once he'd gotten past his own defensiveness, the fix was straightforward. The man's contact was a member record like anyone else's, tagged as a visitor from eight months back. Brother Wasswa opened the record and removed him from the segments that had been triggering the reminders — pulled the visitor-follow-up tag, made a note in the record that he'd asked not to be contacted. From that point forward, any send to "Visitors" or the relevant tags simply wouldn't include him, the same way it wouldn't include a member who'd never had that tag in the first place.
It took about two minutes. It wasn't a feature so much as a consequence of the fact that recipients aren't a static exported list — they're live records you can actually edit, individually, the moment you need to. A generic bulk SMS portal, working off an uploaded contact list, would have required either manually deleting the number from every relevant list you'd exported, or maintaining a separate "do not contact" list yourself and remembering to filter against it every single time you compose a new send — genuinely easy to get wrong, especially months later when the original request has faded from memory.
The part that's just about being decent
There's a version of this where the "correct" answer feels purely procedural — remove the tag, move on. But the more honest lesson from that Tuesday night wasn't procedural at all. It was that a text from a church, even a well-meaning one, can genuinely feel like an intrusion to someone who never meant to sign up for a relationship with the place — he came once, was curious, and eight months of reminders about services he had no plans to attend had, reasonably, worn on him. Respecting "STOP" isn't really about compliance. It's the same respect you'd want extended to you if a shop you visited once kept texting you about sales.
What this actually costs
There's no cost angle here worth dwelling on — removing a tag from a member record doesn't cost anything, and not sending to that person going forward simply means one fewer recipient at UGX 35 per part on future sends. The real cost of getting this wrong isn't financial. It's a person who came once, quietly decided the church didn't listen, and never came back to find out otherwise.
If someone in your church's world has ever asked, bluntly or gently, to be left alone — the right response isn't a feature. It's just doing it, quickly, and meaning it.