FEATURES

Every message, from one place.

Pluggable channels, operator-configured routing with automatic fallback, an in-app inbox, and scheduled reminders that withdraw themselves when their reason disappears.

Book a demo See the commerce features

1 of 27 catalogue features live on this page

Notifications

What it solves

Notification code starts as one line in a controller and ends as sixty scattered send calls nobody can inventory. Then the SMTP provider goes down on a Friday, and there's no fallback because nobody thought to build one.

What's in it

5 capabilities, in the order people ask about them.

Channels and routing

Channels are pluggable: email, SMS, and an in-app inbox.
For each event type — “order confirmed”, say — an operator chooses which channels send it, and from several configured providers, which is primary and which are fallbacks.
If a provider fails, the system switches to the next automatically, then retries the first after a cooling-off period. Nobody has to notice at 2am.

Notifying people without accounts

Guest orders, guest form submissions, waiting lists — all can receive notifications. Transactional messages only; anything marketing requires explicit consent.

In-app inbox

Every user has a notification inbox — order updates, return outcomes, security alerts — with an unread count and read state.

Scheduled reminders

An expiring reservation, an unpaid order, an abandoned cart — each sends an automatic message at the right moment.
And each cancels itself the moment its reason disappears. Payment completes, or the reservation converts to an order, and the reminder is withdrawn — so nobody receives a message telling them to do something they've already done.

Language at send time

Every user's language preference is stored once and read whenever anything is sent, so a notification arrives in the language that user actually reads.

Contents