+254 722 117 850 Support Login
Solutions Alerts & notifications
Use case · Transactional alerts

The 60 seconds after something happens — nailed.

Orders placed, payments cleared, deliveries dispatched, balances changed, outages reported. Sozuri puts the right SMS on the right phone within a minute — branded, idempotent, audit-logged.

Branded sender ID Delivery webhooks Idempotent on messageId
NOTIFICATIONS Customer Alice · today
Bidii Bank: KSh 12,500 received from JOHN K. Your balance: KSh 84,200.09:14
Galaxion: Order #4821 out for delivery. Driver Peter, ETA 10:45.10:24
KPLC Alert: Outage in Karen reported, ETA 14:00. We'll text on restore.11:08
Afya Plus: Lab results for visit 18 May ready. View securely: afya.co.ke/r/X9K714:14
For ops teams, dev teams, customer teams

The notification you send in the first minute is worth more than the call you'll have to make later.

Most "where's my X?" support tickets exist because the customer didn't know X had happened. A branded SMS at the moment of the event — payment cleared, item shipped, account changed — pre-empts the ticket and earns the trust.

< 60sMedian delivery
99.999%API success rate
All 4Kenyan carriers
The journey

Event → SMS → webhook — idempotent end-to-end

1 Something happens

Your system fires an event. Sozuri turns it into a branded SMS.

Order placed, payment cleared, account changed, outage reported — whatever it is, your backend calls /v1/messaging with the customer's number and the message. Branded sender ID, transactional priority, sub-3-second delivery on Safaricom.

  • Transactional sender ID for instant brand recognition
  • Priority routing on the carrier-native SMS rail
  • Idempotent on your own messageId
BIDII BANK Transaction alert
Bidii Bank: KSh 12,500.00 received from JOHN K. Your available balance: KSh 84,200.00. Ref BDS-9X4K.09:14:02
2 Customer sees it — or doesn't

Delivery callback fires the moment the phone rings.

You don't have to poll, you don't have to guess. Sozuri pushes a webhook to your callback URL the second Safaricom (or Airtel / Telkom) confirms delivery, with full messageId, status and network.

  • Webhook within seconds of carrier confirmation
  • Optional auth-key header for source verification
  • Permanent failures surfaced with explicit error codes
YOUR APP Webhook in
POST /your/webhook { "messageId": "MSG-9X4K",
  "status":    "success",
  "network":  "safaricom",
  "timestamp": 1718260920 }
3 Escalate to a richer channel

Some notifications deserve a button, a media file, or a thread.

For higher-stakes events — large payments, account changes, suspicious logins — switch to WhatsApp with an interactive button so the customer can confirm or dispute in one tap. Same project, same auth, different channel.

  • Switch channel to whatsapp for richer formats
  • Interactive buttons capture confirm / dispute responses
  • Per-channel delivery webhooks keep records aligned
What's behind it

The notification stack — SMS first, WhatsApp when it matters

What changes

The first minute, finally automated

−55%

"Where's my X?" tickets

Proactive alerts pre-empt the most common support questions across retail, banking and logistics.

< 3s

Safaricom delivery median

Transactional sends are queued on priority routes. Your customer sees the alert before they put the phone down.

100%

Audit-trail coverage

Every alert is logged with sender, recipient, message ID, delivery state. Exportable for compliance.

“Pre-Sozuri, half our day was answering "did you receive my payment?" Now the customer's phone says yes before they think to ask.”

A Kenyan fintech operations lead
EVENT SMS PHONE in < 60 seconds · idempotent
Your move

Tell the customer before they ask.

The cheapest support ticket is the one that never opens. A 12-cent SMS at the right moment beats a 12-minute call later, every time.

Chat on WhatsApp
Your first SMS in the time it takes to brew coffee. Start building in minutes