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

Fallbacks and breakers — delivery is the contract

When a provider degrades, a circuit breaker trips and traffic reroutes to a backup — the message isn't lost, it's delivered another way. Outages become a routing decision, not a failed customer promise.

Circuit breakers on flaky providers
Automatic reroute to backups
No message silently dropped

Quotas and cost gates contain the blast radius

Per-tenant quotas and rate limits mean a runaway automation can't turn into a five-figure messaging bill or a spam incident. The gate trips before the damage, not after the invoice.

Per-tenant quotas and rate limits
Cost gates on bulk sends
A bug stays a bug, not a bill

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.