FaithDash
← All articles
Story ·FaithDash

Her First Week Running Church Communications

A new volunteer inherits church communications and spends her first week learning the difference between a contact list and an actual system.

A person typing on a laptop keyboard at a desk
Photo by RDNE on Pexels

Grace's handover meeting lasted eleven minutes. Sister Rebecca, who had run communications for the parish in Mbale for six years before her husband's transfer to Kampala, slid a school exercise book across the table, a laptop with a cracked hinge, and a sticky note with three passwords written in blue biro. "The members list is in the laptop somewhere," she said. "I think it's called Members Final, or Members Final 2. Use Final 2." Then she hugged Grace, wished her God's blessing, and was gone by Friday.

Grace opened the laptop that Sunday night to send Monday's reminder about the youth committee meeting. There were four files that could plausibly be "Members Final 2." Two had the same 380-odd rows but different phone numbers for a dozen names. One was missing the entire Youth tab. She picked the one with the most recent "date modified," typed the reminder, and pasted in what she hoped were the right numbers, bracing for the kind of morning-after confusion she'd heard other admins joke about in the church WhatsApp group.

It went out fine, mostly. Except three numbers bounced back as "not registered" — old SIMs, probably — and two people who'd left the youth group eighteen months ago got a meeting reminder for a committee they'd never joined, and replied asking politely to be removed from whatever this was.

The part nobody tells you when you inherit the phone

What Grace ran into that first week wasn't really about her. It's the structural problem every incoming church admin in Uganda meets on day one: the "member list" usually isn't a database, it's an artifact — a spreadsheet somebody built years ago and everyone since has edited slightly differently, sitting on whichever laptop the previous volunteer happened to own. Nobody hands you a system. They hand you a file and a set of passwords and trust that you'll figure out which version is true.

A generic bulk SMS portal doesn't fix this, because it was never built to. Those platforms — the ones marketed at banks and schools and SACCOs as readily as at churches — expect you to arrive already knowing who you're texting. You upload a list, you send. If the list itself is wrong, stale, or missing a tab, the portal has no opinion about that; it's not its job to know. Onboarding into one of those tools mostly means learning a new login screen, not inheriting anything more trustworthy than what Grace got in that exercise book.

What actually changed for her, three weeks in

The parish had started using FaithDash a few months before Grace took over, mostly for attendance tracking, and it was Sister Rebecca's one genuinely useful parting gift that the member records already lived there. Grace's second week looked nothing like her first. When the youth leader asked her to remind "just the committee" about a rescheduled meeting, she didn't hunt for a tab — she picked the Youth tag, watched the composer show her exactly eleven names it would reach, checked the character count and the small cost figure sitting next to it, and sent. No file to find, no version to guess at, no risk of texting two people who'd quietly left the group in 2024, because the group itself lived in the same place as everything else the church tracked.

She still made mistakes that first month — a reminder sent an hour later than planned, an event location she typed slightly wrong and had to follow up and correct. But they were her mistakes, the ordinary kind any new admin makes, not inherited ones baked into a spreadsheet she'd never seen before Sunday night. She could also, for the first time, actually check her own work — message history showed her every SMS the parish had sent, including the ones from before she started, so when someone asked "did we already remind people about harvest Sunday" she could answer in ten seconds instead of asking around the WhatsApp group.

What it costs to actually get this right

None of this changed what an SMS costs — it's still UGX 35 per part, paid from the same prepaid church balance whether Grace sends to eleven people or four hundred, topped up by mobile money whenever it runs low. FaithDash didn't make texting cheaper for the parish. What it changed was how much Grace had to already know, on day one, before she could safely send anything at all.

If you're the one who just got handed the church phone, the sticky note, and a folder called Members Final 2 — you're not behind, and you're not bad at this. You inherited a system that was never really a system. It might be worth asking, gently, whether the church's member records could live somewhere that the next admin won't have to guess at either.

Send from your member list, not a spreadsheet.

FaithDash keeps visitors, members, attendance and messaging in one place — and can follow up automatically.

Open FaithDash

Related articles