It was 9:40 on a Wednesday morning when the call came in — a beloved elder of the church, Mzee Ssebunya, had passed in the night. The burial committee needed to move fast: viewing at the home that evening, funeral service Friday, transport arrangements to be communicated before people started making other plans for their weekend. Sister Immaculate, who'd only been handling church communications for about six weeks, opened FaithDash, went straight to Messages, selected All Members, typed the announcement with hands that weren't quite steady, and hit send.
Nothing happened. A banner sat across the top of the page: the church's phone number needed to be verified before any message could go out, with a link straight to Settings to fix it.
She stared at it for a full ten seconds, genuinely furious. People needed this information now, not after some verification step nobody had mentioned to her.
Why the block exists at all
It turns out the church's number had never been verified — not because anyone was hiding anything, but because verification is exactly the kind of one-time administrative step that gets skipped in the rush of setting up a new system, and nobody had circled back to it. FaithDash enforces this on purpose, on both the interface and the backend: no SMS or email goes out, for any reason, urgent or otherwise, until the sending number is confirmed to actually belong to the church account sending it.
In the moment, that felt like an obstacle standing between a grieving congregation and information they needed. But sit with why it exists for a second. A church's messaging balance, its member database, its ability to reach hundreds of phones at once — that's real reach, and real reach is exactly the kind of thing that gets abused if there's no check on who's allowed to use it. An unverified number sending bulk messages is how spam operations work, how phished accounts get used to blast strangers, how a church's own goodwill gets borrowed by someone who has no business borrowing it. The verification step isn't there to slow down a funeral announcement. It's there so that when a message does land in three hundred people's phones claiming to be from the church, it actually is from the church.
The five minutes that felt like fifty
Sister Immaculate called the pastor, got the church's registered line, went to Settings, and worked through the verification — a short process, but every second of it felt like an hour with a funeral to announce. She kept refreshing the Messages page, willing the banner to disappear.
And then it did. The banner cleared, the compose box unlocked, and the message she'd already written was sitting there waiting, unchanged, ready to go. She hit send again, watched the recipient count start climbing on the progress readout, and the announcement went out to the whole church within a few minutes of the number finally clearing — not the ten minutes she'd wanted, but nowhere near the disaster she'd briefly imagined either.
What this compares to
This is one guardrail a generic bulk SMS portal handles differently, and not necessarily better or worse — most platforms in this category (EgoSMS, RedSMS, and others) have their own onboarding and sender ID processes, since sending bulk SMS in Uganda generally involves some registration with the gateway regardless of which platform you're using. The difference with FaithDash is less about whether verification exists somewhere in the process, and more about where it sits: front and centre, enforced before your very first send, with a direct link to fix it rather than a support ticket you have to wait on. You can't accidentally skip it, and you can't have it quietly lapse without knowing — the banner is right there on the page you're already trying to use.
What this actually costs, and what it doesn't
Verification itself doesn't cost anything beyond the few minutes it takes to complete — it's not a paid step, it's a one-time confirmation tied to your church's account. It's also not something you'll hit twice; once the number is verified, it stays verified, and every message after that — funeral announcements, event reminders, the ordinary Sunday logistics text — goes through without the banner ever reappearing.
Sister Immaculate verified the number that Wednesday morning under the worst possible pressure to do it. Every message since — Friday's funeral service reminder, the harvest Sunday announcement two months later, a dozen ordinary Sunday logistics texts — has gone out without a second thought about whether the number behind it was real. She still thinks about that ten minutes sometimes, mostly with relief now instead of frustration: better to lose ten minutes to a guardrail than to send from a number nobody could vouch for, on the one day it mattered most that people believed what they were reading.