Overview
Channel Settings provide granular control over how each notification channel behaves. You can configure delivery rules, set conditions for when channels should send, and manage provider integrations—all from a centralized interface within each template.Key Configuration Areas
Channel Settings are organized into three main sections:- General: Basic channel behavior, naming, and send logic
- Conditions: Rules that determine when a channel should or shouldn’t send
- Integrations: Provider configuration and send priority settings
Opening the Channel Settings
To view the Channel Settings, open the Template in the designer list, then click the settings icon next to the channel’s name.
General Settings

Always Send To
This setting controls how the channel behaves in relation to other channels:- “Best Of”: The channel only sends if higher-priority channels fail. This is ideal for fallback scenarios (e.g., SMS as backup when email fails).
- “Always”: The channel sends to every recipient regardless of other channels’ success. Use this when you want guaranteed delivery through multiple channels (e.g., both email and push for important notifications).
The “Best Of” setting works with the channel priority hierarchy to create configurable fallback logic. Higher-priority channels attempt delivery first.
Disable
- When set to Disabled, the Channel will not send under any conditions and will be skipped in the “Best of” Channel send hierarchy.
Email-Specific Settings
Email channels include additional configuration options for sender information and recipients:- From address: Set the sender email address and display name using the format
"FirstName LastName <email@domain.com>" - Reply-To address: Specify where replies should be directed
- CC/BCC addresses: Add additional recipients using replacement variables for dynamic values
For full email address configuration guidance (provider defaults, override hierarchy, and formatting), see Customizing Email Address Fields.

Conditions
Channel conditions allow you to prevent a specific channel from sending based on data or profile properties, while other channels in the same notification can still deliver successfully.How Channel Conditions Work
Unlike template-level conditions that disable entire notifications, channel conditions only affect the specific channel where they’re configured:- Template conditions: Stop the entire notification from sending
- Channel conditions: Skip only this channel, other channels continue normally
Setting Channel Conditions
For step-by-step setup instructions, operators, and UI guidance, see Using Send Conditions.
- Open the channel settings and navigate to the Conditions tab
- Select the source (data or profile) for your condition
- Set the property name, operator, and value
- Add multiple conditions if needed (choose from or / and operators)

When you set multiple AND conditions, all conditions must be met to disable the channel.
User preferences take precedence over channel conditions. If a user has
custom_routing configured, only selected channels are considered. Channel conditions still run for those selected channels, but cannot override the user’s selection.Channel Conditions in JSON
Channel conditions can be configured in the Send API withmessage.channels.<channel>.if, where each value is a JavaScript expression evaluated against data and profile.
Keep this page focused on channel behavior. For JSON examples, custom routing edge cases, and detailed condition patterns, use Using Send Conditions.
Integrations
Each channel can use multiple provider integrations for redundancy and performance. The integrations section lets you:- View existing integrations that are already configured for this channel
- Add new providers to expand your delivery options
- Set send priority to determine which provider to use first
- Configure provider-specific settings like API keys and delivery parameters


What’s Next
Send Conditions
Configure template and channel conditions with UI and JSON examples.
Email Address Fields
Configure
From, Reply-To, CC, and BCC with override behavior.Channel Priority
Set fallback order for channels in
Best Of routing.Variable Not Found
Guard channels against unresolved variables at render time.