SK Notifications · Features

Messages that arrive.
Provably.

One sending engine for the whole suite — email, SMS, WhatsApp and push — with provider fallbacks, circuit breakers, per-tenant quotas and a per-send audit trail. When a provider fails, the message reroutes. Delivery is the contract.

01

Four channels behind one honest API

Email, SMS, WhatsApp and push from one call, with a per-message channel strategy. The whole suite sends through here, so behavior is consistent everywhere.

One place, consistent behaviour

CRM sequences, calendar reminders, ticket updates and invoice chasers don't each ship their own SMS vendor — they all send through SK Notifications. One API, four channels, one set of rules. Add a channel and every product that sends gains it at once.

In most suites, every module reinvents sending — five products, five vendors, five ways to fail. SK Notifications is one spine they all ride, so delivery, fallbacks and audit work the same everywhere.

Email

Transactional and branded email through managed, reputable infrastructure.

SMS

DLT-compliant Indian SMS plus international, through one consistent interface.

WhatsApp

Business-API WhatsApp with approved templates — the channel India reads.

Push

App and web push for the moments that belong in-app.

Per-message strategy

Choose channels and order per message — WhatsApp first, SMS if it fails.

One API for all

The suite sends through one call — behaviour identical across every product.

02

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.

An outage is a reroute, not a lost message

Providers fail. SK Notifications expects it: health is watched, breakers trip on degradation, and traffic reroutes to a healthy backup on the same channel — or falls through to your next preferred channel. The customer gets the message; you get a log entry instead of a support ticket.

Circuit breakers

A failing provider is detected and bypassed automatically — before it costs you delivery.

Automatic reroute

Traffic moves to a healthy backup on the same channel, in real time.

Channel fallthrough

WhatsApp down? Fall to SMS. The message gets there one way or another.

Nothing silently dropped

A message that can't go now is queued and retried, never quietly lost.

Health monitoring

Provider performance watched continuously — problems caught early.

Retry with backoff

Transient failures retried on a sane schedule, not hammered or abandoned.

03

Quotas and cost gates contain the blast radius

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

The gate trips before the damage

A misfiring loop that tries to send fifty thousand messages doesn't get to. Per-tenant quotas and rate limits hold the excess, raise an alert, and let you decide — so a bug stays a bug instead of becoming an invoice you have to explain. Cost safety is built into the spine, not bolted on after the first scare.

Per-tenant quotas

Hard ceilings per account — one tenant's runaway can't drain the system.

Rate limits

Sends paced so a burst doesn't trip provider abuse limits or your budget.

Cost gates

Bulk sends checked against limits before they fire — not regretted after.

Alerts, not surprises

Approach a limit and you hear about it — before the bill, not with it.

A bug stays a bug

The blast radius of a mistake is contained by design, not by luck.

Spend visibility

See what's being sent and what it costs, per product, in real time.

04

Templates, versioned and approved

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

One template, every product, always current

The appointment reminder, the invoice chaser, the ticket update — each is a managed, versioned template. WhatsApp templates are kept in their approved state; email layouts stay on-brand. Update one and every product using it updates too, so your customer communications never drift out of sync or out of compliance.

Managed WhatsApp templates

Kept in their Meta-approved state — compliant sends, no last-minute rejections.

Branded email layouts

On-brand, responsive, reused — not rebuilt per product.

Versioned

Change with history; roll back if needed. Templates evolve safely.

Variables & personalization

Name, booking time, amount — merged in cleanly and safely.

Reused suite-wide

One reminder template, every product that reminds. Update once.

Preview & test

See exactly what the customer will get before a single real send.

05

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.

Every send has a receipt

Every message writes an audit record: the recipient, the template, the channel, the provider that carried it, and the delivery outcome. Disputes that used to take an afternoon of 'I think we sent it' become a thirty-second lookup. The spine doesn't just send — it remembers, precisely.

Per-send audit

Actor, channel, provider, outcome — recorded for every single message.

Delivery receipts

Where the channel supports it, you see delivered, not just sent.

Searchable history

Find any message to any customer in seconds — disputes end fast.

Failure reasons

When something fails, you see why — bad number, opted out, provider error.

Compliance-ready logs

Proof of delivery for the records that need it — KYC, consent, more.

Analytics

Delivery rates by channel, template and time — tune what actually lands.

One product of a suite that shares a brain.

SK Notifications lives on the same customer record, the same events and the same rails as the rest of the suite.

Start free  See the developer surface →