Skip to main content
← All capabilities
Available now

Platform capability · Notifications

Reach users in your app, by email and in Slack

One API for in-app, email and Slack messages

A notification service that delivers by email, in the app and to Slack. It includes templates, layouts, user preferences, delivery logs, open and click tracking, unsubscribe handling, a choice of providers, batch sends with a rate limit, and a notification bell you can embed in your app.

Built in

What you get

  • In-app inbox with read and unread state, updated live
  • Email through your transactional email provider (for example Amazon SES, SendGrid or Postmark)
  • Emails for the whole billing lifecycle: payment received, payment succeeded or failed, subscription created, changed or cancelled, trial ending, and invoices
  • Operators can edit every template and layout. Layouts carry each customer’s branding and reuse shared parts
  • DKIM signing for each sending domain, SPF and DMARC checks, and suppression of addresses that bounced or complained
  • Preferences for each user and channel, with controls for each category
  • Open and click tracking on email
  • Unsubscribe built in, with one-click List-Unsubscribe headers
  • Delivery logs with status, retries and the provider’s response
  • Slack delivery through an incoming webhook or a Slack bot
  • Batch sends, with a limit on how many messages go to each provider at the same time
  • SMS through Twilio or Telnyx, in the countries those providers serve and once a sender is registered
Under the hood

How it works

In-app notifications are a full channel

Many notification products add in-app messages late and with few features. Here in-app is a full channel, with unread state, live delivery and preferences for each category. Email and Slack work alongside it, and SMS through Twilio or Telnyx where those providers serve the destination country. Mobile push is a planned integration.

Edit every template and layout

Operators can change the wording, branding and structure of any template or layout without a new deployment. Templates sit inside layouts (header, footer, branding), and layouts carry each customer’s theme. Template variables have types, so a missing variable produces an error when the message is built, before it reaches the recipient.

Billing emails that you can edit

Billing events trigger emails for payments, subscription changes, trial endings and invoices. Templates and layouts carry each customer’s theme and can be edited. The notification service handles sending through the provider and one-click unsubscribe.

Provider choice and sending controls

Email and Slack can each have several provider configurations, stored encrypted. A customer’s own provider is used first when one is set, and sends can be split between providers by weight. Each provider has its own limit on simultaneous sends. The result of each send is logged and can be retried.

Further additions

Additions that extend the capability described above.

  • Mobile push notifications (APNs / FCM)

Want a deeper walkthrough of Notifications?

A solution architect will demo the live service against your domain model.

Get a deployment assessment