Deacon Wasswa had a rule for himself, learned the hard way: never send a bulk message and then close the laptop. He used to sit there, on a rickety office chair, staring at a spinning wheel on a bulk SMS portal, afraid that if he switched tabs to check his email, or god forbid closed the browser to save battery, the whole send would just... stop. Halfway through. No way to know how far it had gotten, no way to know who'd received it and who hadn't, just a spinner that might or might not still be doing something twenty minutes later.
The 800-name Christmas Eve service announcement was the worst of these. He sat through the entire send in real time because he didn't trust it not to fail silently, missed his own family's Christmas Eve dinner prep by forty-five minutes, and still wasn't entirely sure at the end whether all 800 had actually gone out or whether some had quietly failed somewhere in the middle.
What "background job" actually means here
The next December, sending the same kind of announcement — 800-plus names this time, All Members plus a handful of visitors from the last month — he hit send on the Messages page and the page didn't freeze, didn't demand he sit and watch it, didn't even really ask anything of him at all. A progress readout appeared: "312 of 847 processed," ticking upward. He watched it for maybe thirty seconds out of curiosity, then closed the laptop and went to actually help with dinner.
The send kept running. It's a background job — the system processes it independently of whether the browser tab is open, whether the admin is watching, whether anyone's even in the building. When it finished, he got a completion notification: sent, partial, and failed counts broken out plainly, so if three numbers had bounced for being disconnected, he'd know exactly which three, not just a vague sense that "something didn't go right."
The moment that actually mattered
Here's the part he still brings up when people ask about it: nothing happened. That's the whole story. Christmas Eve, 847 people, and the only thing Deacon Wasswa did was hit send once and check his phone forty minutes later to see "847 of 847 processed — 845 sent, 2 failed" waiting for him. No hovering, no spinner anxiety, no missed dinner prep. The two failures were numbers that had changed carriers without updating their record — a known, explainable thing, not a mystery.
There's a genuine, specific relief in a notification like that landing on your phone while you're doing something else entirely — peeling matooke, helping a niece find her Christmas dress, whatever the actual evening is made of — and realising the church's biggest send of the year just handled itself.
Why this is different from a spinner and a prayer
A generic bulk SMS portal, in most cases, is built for a single web session doing a single blast: you're in the browser, the send happens, you watch it happen. That's fine for smaller volumes or occasional use, and plenty of churches manage that way without incident most of the time. But the moment the number of recipients climbs — a whole-church Christmas or Easter announcement, a funeral notice needing to reach everyone fast — sitting through a live send with no real visibility into partial progress, and no separation between "the page is open" and "the message is actually still sending," turns a five-minute task into an anxious half hour glued to a screen, the way Deacon Wasswa's Christmas Eve dinner discovered the hard way.
FaithDash treats the send itself as a job that runs independently of the page — you get the live "X of Y processed" readout while you're watching, and a completion notification with the sent/partial/failed breakdown whether you're watching or not. The difference isn't the SMS delivery itself, which runs over the same kind of gateway infrastructure either way. It's whether you have to personally babysit the send to trust that it happened.
What this actually costs
No extra charge for sending in the background — it's simply how sends work on the Messages page, same UGX 35 per part whether the job runs while you watch or while you're elsewhere. For 847 recipients on a one-part message, that's a little under UGX 29,650 total, same number either way. The only thing that changed between the two Christmases was whether Deacon Wasswa had to give up his evening to find out if it worked.
He still checks the progress readout out of habit, if he's honest — old anxieties don't disappear just because the system's proven itself a few times. But he checks it while doing something else now, which is really the whole point.