Skip to navigation

Configuring a Single-Channel Route

Click Routes in the left navigation and select the Single Channel tab. This tab lists your existing single channel routes, with when each was last edited. At the top of the page, you can:

  • Search for a route by name.
  • Filter routes by Channel.
  • Filter routes by Version, for example to see only live routes.
  • Switch between a card grid and a list view, using the icon next to + Create.

Create a route

1Click + Create at the top right of the page.
2

In the Create Single Channel Route dialog, select the channel from the dropdown. You can create a route for SMS, RCS, WhatsApp, Email, Viber, Slack, Discord, Teams, Push, Voice and InApp.

3

Enter a Name for the route. The name starts with the channel you selected, for example sms-. Optionally, add a Description, then click Submit.

Flow builder

Creating a route opens the flow builder, where you design how notifications are routed for the channel, including redundancy and failover.

A route has three parts.

Start

Every route begins at Start. Below it, Pick a component to start lets you add your first component.

Components

Components decide what happens to a notification. There are two, and you can click either on the canvas to open its settings:

  • Condition: Controls the flow of notifications, so that specific actions run depending on whether the condition is met. Each condition has a True and a False outcome.
  • Action: Decides how the notification is sent through your providers, using Simply Send, Round Robin, Distribute Between or Do Nothing. Actions also have a Failover section, where you add backup providers in case sending fails, helping you keep your “no downtime” promise to your customers.

Stop

Stop is added after an Action, and marks where that branch of the route ends.

Example

In the route below, a Condition checks whether the variable type equals ivr. On True, the notification is sent with Simply Send through one provider. On False, it is sent with Simply Send through another. Each branch then ends at Stop.

Test and live versions

Every route you create is saved as a Test version, so you can try out different variations and combinations to suit your needs. Saving a Test version does not affect the Live version, which may be plugged into your application and active.

1Make your final changes to the route and test it to make sure you get the results you want.
2Check the version dropdown next to the route name to see which version you are working on.
3To keep the version as a test, click Save. The draft is saved in Test and is not visible in Live.
4

To make the version live, click Go Live, then click Confirm in the Go Live Confirmation dialog. The current version becomes the live version of the route.

If approvals are turned on for your workspace, clicking Go Live asks you to request approval instead. See Approval Requests for how this works.

Once a Single Channel Route is live, every notification event it is plugged into automatically uses the live version.