The bride's mother called the church office four times in one week, which is how Sister Grace, the admin, knew the wedding invite hadn't gone out properly the first time. "Church people are asking me directly," she said, "as if I'm the one who forgot them." Nobody had forgotten anybody. The invitation had gone out — just not to everybody, not all at once, and not in a way anyone could point to and say "yes, it's done."
The couple wanted the whole congregation to know: ceremony at 11am, reception after at the hall behind the primary school, everyone welcome, no need to RSVP, just come. Simple message. The problem was where the "everyone" actually lived. Some numbers were on a list from the youth ministry. Some were only in the choir WhatsApp group. A few of the older members didn't have numbers recorded anywhere current — someone had to physically ask around after Sunday service to update three of them, one of whom had switched to her son's Airtel line after her old MTN number stopped working.
By the time Sister Grace had cobbled together a list from three sources, pasted it into the bulk SMS site the church used to use, and sent, it was Thursday — five days before a Saturday wedding — and the delivery had been so gradual and unconfirmed that she genuinely couldn't tell you if it had reached 600 people or 400. The bride's mother's four phone calls were essentially her, politely, checking whether the church had actually done its job.
Where the friction actually lived
It wasn't the writing. "You're invited" is not a hard message to compose. The friction was entirely in assembling a reliable "everyone" out of three fragmented sources and then trusting that a send to a pasted, half-verified list had actually worked — with no visible confirmation beyond a vague "sent" notice on a portal she'd have to log back into to check.
This is the quiet cost of managing your real member list somewhere other than your messaging tool. A generic bulk SMS portal will happily blast whatever numbers you paste into it — it has no opinion on whether that list is current, deduplicated, or complete. It's built the same way for a bank's promotional blast as it is for a church wedding, and it shows: no concept of "the whole congregation," only "the numbers you gave me."
What the second wedding looked like
Nine months later, a different couple, same church. This time Sister Grace picked "All Members" — the church's actual live member list, the same one used for attendance and everything else — typed the invite, watched the composer show her the character count, the SMS part count, and the total cost for roughly six hundred recipients, and sent. No exporting. No cross-referencing three lists. No hunting for whose number was current.
The send ran as a background job. She didn't have to sit and stare at the screen — she got a live "X of Y processed" readout while she went back to finishing the wedding programme, and a completion notification with the sent, partial, and failed breakdown once it was done. By lunchtime the same day she'd sent it, it was done — not "probably done," done, with numbers to prove it. Four people with disconnected numbers showed up in the failed count, which she flagged for someone to follow up on physically. Everyone else had it in their pocket before the bride had even finished her hair appointment.
The bride's mother didn't call once. That, more than anything, told Sister Grace it had worked.
What this actually costs
A short wedding announcement in plain English fits comfortably in a single SMS part at UGX 35 — six hundred recipients at one part each runs a small, predictable cost against the church's prepaid balance, the same wallet used for every other message the church sends, topped up via mobile money whenever it runs low. There's no special "event package" or per-invite pricing — it's the same rate as any other SMS, whether it's a wedding, a funeral, or a reminder about choir practice.
What changed wasn't the cost. It was not having to build "everyone" from scratch every single time something worth celebrating came up. If your church has ever spent the week before a wedding stitching together three contact lists instead of enjoying the run-up to it, that's the actual problem worth solving — not finding a cheaper way to send the same fragmented list.