Sister Florence signed up for a bulk SMS portal on a Wednesday with real optimism. A youth pastor at a sister church in Jinja had recommended it — "it's what schools and SACCOs use, very reliable" — and the sign-up itself took ten minutes: an account, a verified sender name, a small top-up by mobile money to test it. She sent her first message, a reminder about that Sunday's guest preacher, to a contact list she'd exported from an old spreadsheet, and it landed cleanly, all 210 numbers. For about a week, it felt like the upgrade everyone had promised.
The trouble started the following week, in the smallest possible way. A new couple had joined the church the previous Sunday, and Florence wanted to add them to the next reminder. That meant logging into the portal — a separate site from anywhere the church's actual member information lived — finding the spreadsheet on her laptop, adding two rows, re-exporting it, and re-uploading the whole list, because the portal had no way to add two names to what she'd already sent before. She did it. It took fifteen minutes for two people. She did the same thing again the week after that for three more names, and again the week after that when someone pointed out that a member who'd passed away in April was still on the list, because nobody had gone back to remove her.
By week three, Florence was maintaining two versions of the same information — the spreadsheet that fed the portal, and the real, living truth of who was actually part of the church that particular Sunday — and updating them by hand, separately, every single time either one changed. The portal itself never broke. It did exactly what it was built to do: take a list, send a message. The list was the part that kept falling apart.
The moment she actually cancelled
It wasn't a technical failure that ended it. It was a visitor follow-up she meant to send and didn't. A young man had visited twice, and Florence wanted to text him personally to invite him to the next fellowship meeting — but by the time she remembered, three days after his second visit, she'd have needed to go back into the spreadsheet, find his number among the week's cards, add him as a one-off entry, and send a separate message just for him. It was such a small task, and she still didn't do it in time, because "add one visitor to a system by hand" turned out to be exactly the kind of small task that loses to everything else on a Wednesday. He didn't come a third time. She never knew for certain whether the missed follow-up mattered, and that uncertainty is what actually got to her.
Why this wasn't really about the portal being bad
This is worth being fair about: nothing here suggests the portal itself was poorly built, overpriced, or unreliable — for a bank running a promotional blast, or a SACCO reminding members about a loan deadline from a list that barely changes, that same platform likely works exactly as intended. The problem Florence hit is structural to the whole category, not a defect in any one product. A generic bulk SMS portal — whether it's the one she used or any of the others operating in Uganda that name churches among their customers — has no concept of "visitor" or "member" or "someone who joined last Sunday." It knows a contact list you maintain yourself, somewhere else, and re-upload every time it changes. That's a perfectly good tool for a static list. A church's membership is never a static list.
What she actually needed, and what it costs
Florence cancelled the portal subscription and, a few weeks later, the church moved its messaging into FaithDash instead — not because the SMS itself got cheaper (it didn't; UGX 35 per part is the same market rate any of these platforms is ultimately paying through to a telco) but because the two new members and the twice-visiting young man were already sitting in the same member database the church used for attendance, no separate list to maintain. Adding someone to a segment took seconds, not a re-export.
If you've had your own three-week bulk SMS portal story, you're not alone, and it probably wasn't your fault either. The disappointment was never really about SMS pricing. It was about being handed a loudspeaker and told to keep the list yourself, forever, by hand.