For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
LoginTalk to us
DocumentationSDKsConnectAPI Reference
DocumentationSDKsConnectAPI Reference
    • Home
    • Release Notes
  • Getting Started
    • Quickstart
    • Dashboard
    • Alarms
    • Versioning
  • Core Features
    • Integrations
    • Templates
    • Routes
      • Single Channel Route
        • Creating a Single Channel Route
        • "Action" Operator
        • "Condition" Operator
        • Integrating a Single Channel Route
      • Omnichannel Route
      • Copying Routes
    • Notification Events
    • Requests/Go Live
    • Logs
  • Advanced Features
    • Workflows
    • Campaigns
    • User Profiles
    • Approval Request
  • Settings
    • Profile Settings
    • Workspaces
    • Workspace Settings
LogoLogo
LoginTalk to us
Core FeaturesRoutesSingle Channel Route

Plugging Single-Channel Routes into Notification Events

Integrating a Single Channel Route into a notification event allows it to be used effectively.

This is done by simply adding the Single Channel Route instead of Providers.

The understanding here is that adding providers gives you the basic set-up of a single Provider for a specific notification type (SMS, WhatsApp, etc.).

On the other hand, Single Channel Route allows you to create redundancies and other conditions, with multiple Providers, effectively making a complex structure in minutes.

To use a Single Channel Route, select the one you want while setting up the Configuration, in Notification Events.

Was this page helpful?
Previous

Introduction to Omnichannel Orchestration

Next
Built with