Nakato had the laptop balanced on a stack of offering envelope boxes, because the desk in the church office was still covered in last week's attendance registers. She was writing the reminder for Sunday's baptism class, and she was doing something she'd never done at her old church: watching a number change in real time as she typed.
Character count: 41. Then 68. Then 103. Encoding: GSM-7. Parts: 1. Cost per message: UGX 35. Total for 340 members: UGX 11,900.
She kept typing — added the venue, added the time, added "please arrive 15 minutes early" — and watched the total climb, one keystroke at a time, like a taxi meter she could actually see before the trip started.
The old way was finding out afterward
At her previous church, "sending a text" meant exporting a member list into a spreadsheet, logging into a separate bulk SMS site, pasting a block of numbers into a box, typing the message into a different box, and clicking send with no real sense of what it would cost until the balance dropped afterward. Not because the site was dishonest — most pay-as-you-go bulk SMS platforms in Uganda work exactly this way, priced per SMS unit, same as FaithDash's own UGX 35 per part. The gap wasn't the price. It was that nobody showed her the number until it was already spent.
She remembered one specific afternoon: a message she thought was short enough to fit in one part turned out to run two, because of a line break she didn't know counted as a character. Fine on 40 members. Less fine when she did the same thing for a 900-name Easter announcement and the office asked why the SMS budget for the month had a hole in it.
What changes when the meter runs while you type
On the Messages page, the composer doesn't wait for you to hit send to tell you what something costs. As you type, it's already tracking:
- Character count — updating live, the way any text box does, but tied to something that actually matters here.
- Encoding — GSM-7 or Unicode, flagged plainly, because that's the difference between 160 characters fitting in one part and only 70.
- Parts — how many SMS segments this message will actually split into, given the encoding.
- Cost per message and total cost for the selected recipient group — whichever segment you've picked, whether that's all 340 members, just the 22 people tagged "Baptism Class," or the visitors from the last four Sundays.
Nakato picked the "Baptism Class" tag instead of all members — 22 people, not 340 — and the total dropped from twelve thousand shillings to under a thousand. That's not a discovery FaithDash made for her. Segmenting recipients by tag instead of blasting the whole database is something a live member database lets you do that a spreadsheet upload doesn't really encourage, because on a generic portal, a contact list is a contact list — it doesn't know who's in baptism class and who isn't unless someone built and maintained that list by hand, separately, every time.
The moment it actually helped
She wasn't trying to game the system. She just wanted the message to fit in one part instead of two, because the difference across 22 recipients was small, but the habit mattered. She trimmed "please arrive 15 minutes early" down to "please come 15 min early," watched the character count drop under the GSM-7 threshold, watched Parts flip from 2 back to 1, watched the total halve.
There was a genuine flicker of frustration first — she'd written a perfectly polite sentence and the counter was telling her, essentially, "that politeness costs you double." But the annoyance passed fast, replaced by something closer to satisfaction: she wasn't guessing anymore. She hit send knowing exactly what the church was paying, for exactly who was going to receive it, before it happened rather than after.
What this actually costs, plainly
UGX 35 per SMS part, same rate the church pays whether the message is one part or five, whether it's going to 22 people or 900. The composer doesn't change that number — nothing does, it's the market rate the underlying gateway charges, and FaithDash isn't in the business of pretending otherwise. What the composer changes is whether you know the number before you've spent it. That's a small thing until the one afternoon it isn't — the Easter Sunday send, the funeral announcement going to the whole church, the month the treasurer starts asking pointed questions about the SMS line in the budget.
Nakato closed the laptop, boxes of offering envelopes still stacked under it, and went to find out whether the baptism candidates had signed the register yet. The message was already queued, the cost already known, no surprises waiting for her on Monday. Some Sundays, that's the whole win.