The call came in at 6:40 on a Tuesday morning. Brother Tadeo's father had passed in the night, out in Kayunga, and the family wanted word out before the sun was properly up — viewing that evening, burial Thursday, could the church please tell people.
Pastor James wrote the announcement in four minutes flat, sitting on the edge of his bed with the phone light too bright for his eyes. The words weren't the hard part. Getting them to four hundred phones before people left for work — that was the part that used to go wrong.
He remembered the last time. Someone had a spreadsheet on a laptop that wasn't in the house. Someone else had a WhatsApp broadcast list that was two years stale, half the numbers switched to new SIMs after the network promotions came and went. By the time the announcement actually reached most people, it was already evening, and three separate members had shown up at the wrong time because they'd heard about it from a neighbor instead.
That's the particular cruelty of a death announcement. It isn't like a reminder for choir practice, where being late means someone shows up for the second half. Miss the window on this one and people miss the viewing, or worse, they hear it secondhand and wrongly, and then you're fielding calls all morning from people asking "is it true, is it Tadeo's father or Tadeo himself, when is it happening" — the rumor filling in the gaps your slow announcement left open.
Why this is a speed problem, not a writing problem
A funeral announcement is short. It's rarely more than two or three sentences — who passed, viewing details, burial details, maybe a request for prayers or contributions. The difficulty was never composing it. The difficulty was always reaching the list.
If your church's contact list lives in a spreadsheet on someone's personal laptop, or split across three people's phones as separate WhatsApp broadcast groups, a 6:40am emergency depends on whoever has the file being awake, near a computer, and remembering which sheet is the current one. If it lives in a bulk SMS portal you log into separately, you're now exporting or re-pasting numbers into a website that has no idea who's a member, who's a visitor who came once in 2024, or who already left the parish — you're sending to whoever happened to be on the list the last time someone bothered to update it.
FaithDash doesn't solve the writing. It solves the reaching. The recipient list is the same live member database the church already uses for everything else — so "All Members" on a Tuesday morning is the actual current membership, not a CSV someone exported around Easter and forgot about. Pastor James picked All Members, pasted in the announcement, watched the composer show him the character count and the cost for four hundred-odd recipients, and sent. No separate login, no uploading a file, no hunting for whose phone had the "real" list.
What actually happened that morning
It wasn't instant — sending to a few hundred numbers is a background job, and FaithDash shows a live "X of Y processed" readout rather than freezing the page while it works. Pastor James watched the counter climb while he got dressed. By 7:15, the send was complete, with a breakdown of sent, partial, and failed — two numbers had bounced, probably switched-off phones, which he flagged to check later. Not perfect, but close enough that by 8am the church knew, and nobody had to ring around confirming rumors.
Compare that to what a generic bulk SMS portal would have asked of him in the same fifteen minutes: log in separately from wherever the member list actually lives, find or re-export a contact list that's accurate as of whenever someone last updated it, paste the numbers in, write the message again because the portal doesn't know who Tadeo's church family even is. That's workable when you have a day to prepare. It is a genuinely bad system to be relying on at 6:40am with a grieving family waiting on you.
What it actually costs
This is UGX 35 per SMS part, same as any other message sent through FaithDash — a short funeral announcement in plain English almost always fits in a single part, so four hundred recipients runs a predictable, small cost against the church's prepaid balance, the same wallet used for every other message the church sends. No separate account to fund for emergencies, no discovering a second portal's balance is empty at the worst possible moment.
There's no feature in FaithDash called "emergency mode," and there doesn't need to be — the difference on a morning like that one isn't a special button, it's simply that the list was already correct and already there.
If your church has ever had this exact 6:40am moment — the message ready, the list not — that's really the whole case for keeping your member data and your messaging in the same place. Not a sales pitch, just the honest shape of the problem.