System Alerts & Transactional Routing
Receive real-time alerts for system events, and trust that password resets and receipts deliver instantly via isolated transactional relays.
Sending is asynchronous and largely invisible - a campaign runs for hours in the background, and problems surface long after the moment they occur. This module exists so that failures reach you while you can still act on them, rather than being discovered from a disappointing report.
Why real-time alerts matter for sending specifically
A campaign that fails silently keeps failing. If a sending account is throttled at the start of a four-hour run, the difference between learning about it immediately and learning about it afterwards is the difference between a brief pause and a campaign that half-delivered. Alerts arrive over a WebSocket connection as events occur: an account entering cool-down, a campaign pausing because every account went offline, a quota being reached.
Transactional mail runs on separate infrastructure
Platform messages - password resets, alerts, account notifications - go through a dedicated gateway entirely separate from your marketing sending accounts. This is deliberate, and it protects two things. Your sending quota is not consumed by system mail, and more importantly, a deliverability problem in your marketing campaigns cannot prevent a password reset from arriving. Keeping transactional and marketing streams apart is standard practice for good reason: they have different urgency, different engagement profiles, and should never share a reputation.
What you are actually notified about
The alerts that matter for sending are operational rather than promotional. An account entering a sixty-minute cool-down after a provider returned a rate-limit response. A campaign pausing because every connected account is simultaneously unavailable. A sending account failing authentication because a password changed or an app-specific credential was revoked at the provider. A daily quota being reached before the campaign finished. Each of these is a condition where a decision is available to you - switch accounts, pause and investigate, reconnect a mailbox - but only while the campaign is still running.
Why in-app rather than email alerts
There is an obvious circularity in notifying someone by email that their email infrastructure has a problem. Alerts are delivered over a persistent WebSocket connection to the dashboard, so they arrive without depending on the thing that may be failing. Transactional email remains available as a channel for account-level events such as password resets, but operational sending alerts are surfaced where you are already working.
Keeping platform mail off your sending accounts
Every message the platform sends on its own behalf - resets, alerts, billing notices - leaves through a dedicated gateway rather than through any mailbox you have connected. Two consequences follow. Your daily sending quota is spent entirely on your campaigns rather than partly on system mail. And your domain reputation reflects only the campaigns you chose to send, rather than being mixed with automated platform traffic that your recipients never asked for and would never engage with.
Feature Breakdown
WebSocket In-App Alerts
Keeps you updated on campaign events and account issues with real-time browser notifications.
Technical Capabilities:
Dedicated Transactional Email Gateways
Ensures system notifications (verification links, password resets) are sent via isolated transactional SMTP channels.
Technical Capabilities:
Spec Sheet
Need a Deep Dive?
See exactly how this module manages background queues, encryption, and delivery logic in our sequence flowchart.
View technical guideReady to Connect Your Nodes?
Scale your deliverability with our intelligent sharding relay. Add your domains and start landing in the inbox.
System Alerts & Transactional Routing questions.
The specifics people ask about before relying on this part of the platform.
How am I told when something goes wrong with a campaign?
In-app alerts arrive over a WebSocket connection as events happen - an account entering cool-down, a campaign pausing because every account went offline, or a quota being reached - so you find out while you can still act on it.
Are system emails sent through my own sending accounts?
No. Transactional messages such as password resets and alerts go through a dedicated gateway kept entirely separate from your marketing sending accounts, so platform mail never consumes your sending quota or affects your domain reputation.