Grace was proud of that message. "Youth service moves to 4pm today because of the rain 🙏🏽 See you there!" Short, warm, one small hand-of-prayer emoji at the end because the youth WhatsApp group liked that kind of thing. She had 214 names under the Youth tag. She typed it, glanced at the total, and nearly closed the tab without checking twice.
Good thing she checked twice.
That message, with the emoji sitting in it, was going to cost three times what it looked like it should. Not because FaithDash was charging her extra for having fun — because of a rule about text messages that has nothing to do with churches, WhatsApp, or Uganda at all, and everything to do with how a phone network decides to chop your sentence into pieces.
Why one small icon does so much damage
Here is the part nobody explains until it costs them money. A plain SMS made only of standard Latin letters, numbers, and common punctuation is encoded in something called GSM-7. In GSM-7, a single SMS part holds up to 160 characters. Cross that limit and the message splits into more parts — but you still get 160-character chunks per part, roughly.
The moment your message contains a character GSM-7 doesn't recognise — an emoji, certain accented letters, some curly quotes that Word or WhatsApp autocorrect likes to insert, or non-Latin script — the whole message switches to Unicode encoding. And Unicode doesn't give you 160 characters per part. It gives you 70. Cross that and you're down to 67 per part after that, because a little space gets reserved for stitching the parts back together on the receiving phone.
So Grace's message — comfortably under 160 characters, would have sailed through as one part in plain text — became three Unicode parts the instant that one emoji landed in it. One part became three. And three parts times 214 recipients times UGX 35 per part is a very different number from one part times 214 recipients times UGX 35.
This is not a FaithDash quirk. It's how SMS segmentation works everywhere, on every gateway, for every platform that sends text messages over the actual telecom network — including the one FaithDash itself sends through. A generic bulk SMS portal charging per SMS unit runs into exactly the same wall if you paste in a message with a stray emoji or a smart-quote from a pasted Word document. The physics of the SMS protocol doesn't care whose logo is on the composer.
What's different is whether you find out before or after
This is where the live counter on the Messages page earns its keep. As Grace typed, the composer was already showing her the character count, whether the message was reading as GSM-7 or Unicode, how many parts it had split into, the cost per message, and the total cost for the 214 people under the Youth tag — updating with every keystroke, before she touched send.
She saw it. Total jumped the moment the emoji went in. She deleted it, watched the encoding flip back to GSM-7, watched the part count drop back to one, watched the total shrink to a third of what it had been a second earlier. Same message, same warmth, same "see you there" — she just said it with a full stop instead of a prayer-hands emoji, and the church saved real money on a Tuesday afternoon rain delay.
That's the small relief in this story. Not that FaithDash is cheaper — it isn't, and it doesn't pretend to be. UGX 35 a part is UGX 35 a part, whether you send it from FaithDash, from the gateway underneath it, or from any other bulk SMS platform in the market. The relief is smaller and more useful than a discount: she got to see the cost of her own habit before she paid for it, not after, in a message history entry she'd have to explain to the treasurer later.
The habits worth building
A few things worth knowing if you're the one typing these messages:
- Emojis, most accented letters (the kind that show up if you paste from a document with "smart" formatting), and non-Latin characters all trigger Unicode.
- Straight apostrophes and quotation marks (
'and") are usually fine in GSM-7. Curly ones ('") that autocorrect loves to insert are often not. - If a message feels borderline, delete the fancy punctuation and retype it plainly — the composer will tell you instantly whether that fixed it.
- For a recipient group in the hundreds, one avoidable emoji is not a rounding error. It's real shillings, three times over.
Grace still uses emojis sometimes — birthdays, harvest Sunday, the odd celebratory 🎉 when attendance is good. She just watches the number now instead of guessing. That's really all the composer is for: not stopping you from being human in a text message, just making sure you know what being human costs before the message is already gone.