Pastor Kizza's nephew was doing an internship in IT, and like most nephews doing an internship in IT, he had Opinions. He'd been poking around the church's FaithDash account, checking the Messages page out of curiosity, and he asked the question that every technically-minded church volunteer eventually asks: "Uncle, when we send SMS from here — whose network is this actually going through?"
It's a fair question, and the honest answer is less dramatic than he was hoping for.
No, FaithDash doesn't have its own private line to MTN and Airtel
FaithDash sends its SMS through the BulkSMS Uganda gateway — app.bulksmsug.com under the hood — the same class of telco-connected SMS infrastructure that independent bulk SMS platforms operating in Uganda also run on. There's no secret backchannel, no proprietary wire straight into the telecom towers that only FaithDash has access to. The message leaves the FaithDash Messages page, goes to the gateway, and the gateway does what SMS gateways do: hands it to the networks for delivery.
The nephew looked a little disappointed, honestly. He'd half-expected some clever piece of infrastructure nobody else had.
Why that's not actually the interesting part
Here's the thing worth sitting with for a second: it was never going to work any other way. Building and maintaining a direct telecom connection — the licensing, the aggregator relationships, the compliance — is its own specialised business, and it's not the business a church management platform should be trying to reinvent. The same is true, structurally, for every bulk SMS platform in this market. RedSMS, Oracom, FamITech, SMSOne, Trust SMS Uganda — none of them are magically bypassing the telecoms either. Everyone in this category is ultimately a customer of a gateway layer that connects to MTN, Airtel, and the rest.
Which means the SMS itself — the actual delivery, the UGX 35-a-part cost, the reliability of the message physically arriving on someone's phone — is the same commodity everywhere. FaithDash doesn't sell you a cheaper SMS, because there isn't a cheaper SMS to sell. Anyone claiming their delivery is dramatically cheaper than the market rate is either eating a loss somewhere or not being fully straight about it.
So what is FaithDash actually doing, then?
This is where the nephew's disappointment turned into something more like understanding. What FaithDash built isn't a better wire to the telecoms — it's everything sitting on top of that wire. The part a generic gateway or portal was never going to build, because it isn't in the SMS-delivery business, it's in the church-database business that happens to be able to send SMS.
That's the live character and cost counter on the Messages page, showing GSM-7 versus Unicode encoding and the running total before you send. That's the recipient list being the church's actual member and visitor database — All members, Visitors only, Leaders only, or a custom tag like "Choir" — instead of a spreadsheet you upload fresh every time. That's the automation layer: visitor follow-ups triggered the day someone registers, event reminders that fire a set number of hours or days before a service without anyone touching a phone, attendee follow-ups sent automatically after an event ends. A generic bulk SMS portal, connected to the exact same kind of gateway, has no concept of "visitor" or "event" or "attendee" — it only knows phone numbers somebody uploaded.
The honest version, for anyone who asks
If someone in your church — a nephew doing an IT internship, a treasurer who reads the fine print, a pastor who wants to know exactly what he's signing the church up for — asks whether FaithDash has some special, cheaper pipeline to send text messages, the honest answer is no. It sends through the same kind of gateway infrastructure as everyone else in this market, at the same UGX 35 per part the whole category charges, because that's what delivering an SMS through Uganda's telecom networks actually costs.
What FaithDash is betting on instead is that a church doesn't actually want a cheaper wire. It wants to stop exporting a spreadsheet every Sunday, stop maintaining a separate contact list nobody trusts, and stop manually remembering to text every visitor the day after they show up. The gateway underneath is unglamorous and shared with the rest of the industry, on purpose. The workflow on top of it is the part actually built for a church.
Pastor Kizza's nephew ended up more interested in the automation rules than the gateway question — he set up an event reminder for the next youth conference, watched it queue itself to fire two days out, and came back the following week mostly to report, a little sheepishly, that it had worked without him doing anything. That's usually how the conversation ends. Not with a clever discovery about the wiring, but with someone realising the wiring was never the point.