Reverend Nsubuga oversees three congregations under one parish — the main church in Mukono town, a smaller fellowship out toward Seeta, and a third that meets in a rented hall near the market in Goma. Three services, three offering baskets, three admins, and — until last year — three completely different ways of telling people what was happening on Sunday.
The Mukono admin used a bulk SMS portal she'd signed up for herself, paid from her own mobile money and reimbursed later, when anyone remembered. The Seeta fellowship ran on a WhatsApp broadcast list that had been created in 2022 and never fully updated since — half the numbers belonged to people who'd since moved churches or switched SIMs during a network promotion. Goma didn't really have a system at all; the youth pastor there just phoned the group leaders and asked them to pass the word.
When Reverend Nsubuga tried to announce a joint parish conference — one event, all three congregations invited, same Saturday — it became obvious how badly this was working. The Mukono list got it Tuesday. The Seeta list, sent from someone's personal phone as a WhatsApp forward, went out Thursday, and half the recipients said they'd never received it. Goma found out on Friday, secondhand, from someone who'd heard it from someone else. Three different admins, three different timelines, one confused parish trying to figure out if the conference was even still happening.
Why "just get everyone on the same app" is easier said than done
The instinct is obvious: put everyone on one system. The harder part is that each congregation had built its own habits around its own broken tool, and nobody wanted to be the one who lost "their" list in the switch. The Seeta admin, in particular, was nervous — her WhatsApp broadcast list, messy as it was, at least lived where she could see it. Handing that over to something new felt like handing over control.
What actually made the difference wasn't a feature so much as a decision: instead of three separate contact lists living in three separate tools, the parish moved its member records — visitor sign-ins, group tags, leader roles — into one shared database, with each congregation's members tagged separately (Mukono, Seeta, Goma) alongside their existing tags like Choir or Youth. That meant Reverend Nsubuga could message all three congregations at once for a parish-wide event, or any single congregation for something local, from the same place, without three separate logins or three separate exports.
A generic bulk SMS portal doesn't really have a concept of "congregation" at all — it's built to blast a list, any list, whether that list belongs to a bank's customers or a parish's third campus. Getting the Mukono, Seeta, and Goma numbers organized as distinct, taggable segments inside one system, rather than three separate uploaded spreadsheets in three separate accounts, was the actual unlock — not a cleverer send button.
What actually happened, and what didn't go smoothly
It wasn't instant. The Goma youth pastor, who'd never used any messaging portal before, needed two sit-downs before he trusted the "Goma" tag to actually reach his people and not, God forbid, blast the entire parish by mistake — a fear every admin who's heard the "test test ignore" story develops fast. There was a genuinely tense week where the Seeta admin insisted on running her old WhatsApp list in parallel "just in case," which meant some members got the conference announcement twice, once by SMS and once as a WhatsApp forward that arrived a day later and said something slightly different.
The relief came a month later, at the actual conference. Reverend Nsubuga sent one announcement to all three tags at once — sent, watched the background job tick through "X of Y processed," and had a completion breakdown by the time he'd finished his tea. All three congregations got the same message, worded the same way, on the same day. Nobody asked "is it true" three separate times.
What this actually costs across three congregations
The billing didn't split into three accounts either — one prepaid parish balance, topped up via mobile money, covers all three congregations' SMS, at the standard UGX 35 per part regardless of which campus the recipient belongs to. The Billing page shows last-30-days usage broken down by channel, so Reverend Nsubuga can see total spend across the whole parish rather than three admins each guessing at their own portion.
There's no special "multi-campus" feature — just tags, a shared member database, and one balance instead of three. If your parish is quietly running three different systems held together by goodwill and forwarded WhatsApp messages, that's usually the actual problem to solve first, before worrying about which platform is fanciest.