One provider down
is not a send down.
Weighted, prioritized provider routing per message class — with a fallback that catches the rest.
Single-provider setups fail all at once.
If everything routes through one connection, one suspended account, one rate limit, or one regional outage stops all mail — marketing and password resets together. The usual workaround is a second tool, which means a second set of templates, suppressions, and reporting.
Sending routes let you spread traffic across provider connections by priority and weight, split by message class, with an explicit fallback route. Transactional mail can take its own path so it never queues behind a marketing burst.
Routing & fallback, in detail.
Priority and weight
Each route carries a priority and a weight, so traffic distributes deliberately rather than round-robin by accident.
Class-aware routing
Route marketing and transactional mail separately — a promotional send cannot delay a receipt.
Designated fallback
Mark a route as the fallback and it absorbs traffic when the preferred path is unavailable.
Rate limits and concurrency
Set hourly, daily, and monthly caps plus max concurrency per provider connection, so you stay inside what each account actually allows.
Test before production
Connection tests validate a provider against real health checks before it ever handles live mail.
Per-provider reputation
Daily deliverability and error health per connection tells you which route is earning its weight.
A sending route.
Six fields that decide where a message actually goes.
- sender_profile_id
- The verified identity this route sends as
- message_class
- marketing or transactional
- priority
- Preference order among eligible routes
- weight
- Traffic share among routes of equal priority — defaults to 100
- is_fallback
- Marks the route that absorbs traffic when the preferred path fails
- Provider limits
- Hourly, daily, monthly caps and max concurrency per connection
Bring your provider.
Keep your brands distinct.
Start today.
Set up your first workspace, connect a provider, and publish a workflow — free, in test mode, before you pay a thing.