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.
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.
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.
Transactional and branded email through managed, reputable infrastructure.
DLT-compliant Indian SMS plus international, through one consistent interface.
Business-API WhatsApp with approved templates — the channel India reads.
App and web push for the moments that belong in-app.
Choose channels and order per message — WhatsApp first, SMS if it fails.
The suite sends through one call — behaviour identical across every product.
Delivery health is monitored in real-time. If primary providers degrade, Redis-backed circuit breakers failover to secondary routes to protect delivery.
Softknack Notifications keeps state in a shared Redis hash cb:{channel} across all API servers. If five consecutive sends on Twilio or SendGrid fail, the breaker trips to OPEN, instantly rerouting traffic to fallback channels (Meta / SES) and triggering alerts.
Duplicate messages are blocked at ingress. Quota limits are evaluated atomically before notifications enter active BullMQ dispatch queues.
Before executing any template or calling API networks, Softknack checks the Redis idempotency gate using unique correlation identifiers (SET NX). A separate quota gateway handles daily and monthly tenant limits, preventing billing overruns.
Approved WhatsApp templates and branded email layouts are managed and versioned — reused across every product, updated in one place.
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.
Kept in their Meta-approved state — compliant sends, no last-minute rejections.
On-brand, responsive, reused — not rebuilt per product.
Change with history; roll back if needed. Templates evolve safely.
Name, booking time, amount — merged in cleanly and safely.
One reminder template, every product that reminds. Update once.
See exactly what the customer will get before a single real 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 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.
Actor, channel, provider, outcome — recorded for every single message.
Where the channel supports it, you see delivered, not just sent.
Find any message to any customer in seconds — disputes end fast.
When something fails, you see why — bad number, opted out, provider error.
Proof of delivery for the records that need it — KYC, consent, more.
Delivery rates by channel, template and time — tune what actually lands.
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 →