Skip to main content
Routing determines how your notification is delivered across channels. In Design Studio, you can create named routing configurations that are reusable across templates.
This feature is available in Design Studio (Beta). In Classic Designer, routing is configured separately for each template.

​
Selecting a routing configuration

Click the routing dropdown in the template editor toolbar to select or create routing configurations.
Routing selector dropdown showing saved configurations
From this dropdown you can:
  • Select an existing routing configuration
  • Click the pencil icon to edit a configuration
  • Click + Add new routing to create a new configuration

​
Routing schemes

Each routing configuration has a name and a scheme. The scheme determines how channels are prioritized.

​
Basic scheme

The Basic scheme sends notifications to all enabled channels simultaneously.
Basic routing scheme with all channels enabled
Toggle channels on or off to control which channels receive the notification. The flowchart on the right shows that all enabled channels receive the notification at the same time.

​
Advanced scheme

The Advanced scheme provides cascading fallback logic. Notifications are sent to a required channel first, then fall back to other channels if delivery fails.
Advanced routing scheme with fallback chain
The Advanced scheme has two sections:
SectionBehavior
Always send toRequired channel(s) that always receive the notification
If the last above fails, send toFallback channels tried in order until one succeeds
Drag channels to reorder priority. The flowchart visualizes the fallback chain.

​
Reusing routing configurations

Unlike the classic designer where routing is configured per-template, v2 routing configurations are saved and reusable:
  1. Create a routing configuration once (e.g., “Primary” with email + SMS fallback)
  2. Apply it to multiple templates from the routing dropdown
  3. Edit the configuration to update all templates using it
This makes it easier to maintain consistent delivery logic across your notification templates.

Content Blocks

Building notification content

Send API

Sending notifications with routing