SK Notifications — Messages that arrive.Provably.

Why it's different

Built to do the work, not just store it.

Five capabilities that make SK Notifications feel less like software you maintain and more like a teammate that already did the task.

Four channels behind one honest API

Email, SMS, WhatsApp and push from one call, with a per-message channel strategy. The rest of the suite — CRM sequences, calendar reminders, ticket updates, invoice chasers — all send through here, so behavior is consistent everywhere.

One API, four channels
Per-message channel strategy
Every product sends through one spine

Shared Redis circuit breaker & failover routing

Outbound delivery health is monitored in real-time. If a primary provider (like Twilio) fails five consecutive times, a shared Redis-backed circuit breaker trips. Traffic instantly failovers to secondary providers (like Meta Cloud or AWS SES) and alerts ops, avoiding any dropped customer notifications.

Real-time Redis-backed state tracking
Automatic provider failover on threshold breach
Instant operations alerts on circuit trip

Idempotency gates and quota enforcement

A Redis-backed idempotency gate blocks duplicate messages at ingress using unique reference keys before consuming any limits. If valid, the quota gate evaluates daily and monthly tenant limits. Should limits exceed, excess calls are blocked or held prior to entering BullMQ sending queues.

Redis SET NX idempotency checks at ingress
Daily and monthly per-tenant quota gates
Dumb-pipe validation before queuing

Templates, versioned and approved

Approved WhatsApp templates and branded email layouts are managed and versioned — reused across every product, updated in one place, compliant with channel rules.

Managed WhatsApp templates
Versioned, branded email layouts
Channel-compliant by design

A receipt for every single send

Who, what, when, which provider, what outcome — logged per message. "Did the customer get it?" stops being a shrug and becomes a lookup. Disputes die in seconds.

Per-send audit: actor, channel, outcome
Delivery receipts where channels support them
"Did it send?" is a lookup, not a guess

That's five of many.

The full capability list — every feature illustrated — is on the features page.

Explore all features →

Fair questions, straight answers.

Do I use this directly, or does the suite use it for me?

Both. Most of the time it's invisible — CRM sequences, calendar reminders and ticket updates ride it automatically. But it's also a first-class product you can send through directly via API for your own notifications, inheriting the same fallbacks, quotas and audit trail.

What happens when a provider goes down?

A circuit breaker detects the failures and reroutes traffic to a backup provider on the same channel, or falls through to your next preferred channel. The message gets delivered another way rather than lost, and the whole thing is logged.

How does it stop a runaway bill?

Per-tenant quotas, rate limits and cost gates. If an automation misfires and tries to send 50,000 messages, the gate trips and holds the excess — you get an alert, not an invoice. The blast radius is contained by design.

Messages that arrive.
Provably.