All insights
    Customer Communication

    SMS Channel Setup: Sender ID, USSD, Short Codes, and Bulk SMS

    Fentone Omwony6 min read

    Kenyan businesses need different SMS setups depending on trust, interactivity, and volume. Here is a plain guide—and how enablement helps you go live without derailing your core work.

    SMS still drives repayment reminders, OTPs, program alerts, and sales nudges across Kenya. But "set up SMS" means different things for a micro-lender, a retailer, and a county health program. Confusing them wastes money and erodes trust.

    The goal of enablement is simple: get the right setup live so your team returns to serving customers—not chasing aggregator forms and regulator questions for months.

    1. Sender ID (branded SMS)

    Best for: payment reminders, appointment confirmations, account alerts—any message where the customer must trust the sender immediately.

    • Customers see your brand name instead of a random number.
    • Improves open and action rates when combined with clear amount, date, or next step in line one.
    • Requires registration and approval with your market's rules—we help scope naming, use case, and documentation.

    Core-business win: your finance or collections team stops explaining "why the SMS looks suspicious."

    2. USSD and short codes

    Best for: journeys that need menus, balance checks, opt-in flows, or steps on phones without smartphones—common in financial services and public programs.

    • A short code (e.g. *123#) opens a structured menu.
    • Works on basic handsets; airtime and session length matter for design.
    • Needs technical routing, testing on major networks, and copy that respects low literacy and time pressure.

    Core-business win: product and operations define the journey; enablement handles routing, test numbers, and go-live checklists.

    3. Standalone bulk SMS

    Best for: announcements, campaign bursts, or interim reach before full behavioral journeys run in Hub.

    • High volume, one-way or simple two-way.
    • Still needs sender trust, frequency caps, and opt-out respect—not blast and hope.
    • Pair with Pulse later so copy improves with diagnosis, not guesswork.

    Core-business win: marketing launches on time while you build deeper automation in parallel.

    How to choose (quick scan)

    • Trust problem? Start with Sender ID.
    • Customer must navigate options on any phone? USSD or short code.
    • Need reach this week for a defined list? Bulk SMS—with one clear CTA.
    • Ready for test-and-learn journeys? Add Hub waitlist when trials fit; enablement gets the pipe ready first.

    What to tell us when you ask

    Market, expected volume, use case (collections, OTP, marketing, public program), and whether you need one-way or interactive. We reply with scoped enablement—not a generic bundle.

    Ask about SMS enablement · Related: when SMS delivers but action stays flat

    Continue the conversation

    See what we are testing in Labs, book Pulse discovery to design your test, or join Hub trial cohorts when you are ready to measure action—not delivery alone.