The Routing Matrix Architecture
Effective communication requires a reliable and flexible routing system to ensure messages reach their intended recipients without delays or failures. Fyno’s Routing feature empowers you to optimize message delivery across multiple providers and channels with ease. This section explores two powerful routing capabilities: Single Channel Route and Omnichannel Route.
Single Channel Route helps you manage multiple providers within a specific channel, enabling traffic distribution, failover setups, and conditional routing.
Omnichannel Route takes it a step further by allowing seamless transitions between different communication channels—SMS, WhatsApp, Email, Push, and more—to ensure message delivery across multiple touchpoints.
By leveraging Fyno’s routing capabilities, you can build redundancy, improve reliability, and maximize engagement with your audience. Let’s dive into the details!
Single channel and omni-channel routes can be copied from your workspace to other workspaces you own. The copy process is only available in workspaces where you have the Owner role.
Steps to copy routes to another workspace
1. Prepare your destination workspace
It is important to note that when copying routes, only the route-related data will be copied to the destination workspace. Any dependencies must be created or copied manually in the destination workspace.
2. Copy your route(s) to another workspace
3. Post copy to-do
Once the routes are copied to the destination workspaces, open each route, re-select the integration (where applicable), and save the route to ensure that it works correctly.
How versioning works
Let’s say we are copying a route from Workspace A to Workspace B. There are two versioning scenarios to keep in mind.
If the route does not exist in Workspace B, then the version created by the copy process will always be v1 (Test).
If the route already exists in Workspace B, then the copy process will create a new standalone version (neither test nor live). For example, if the version in Workspace B is v1 (Test), then the process will create a new version called v2. You can select this version from the version dropdown beside the route name and click “Save” to change the version to v2 (Test), or click the “Go Live” button to promote it to v2 (Live). This ensures that changes to existing versions in the destination workspace are not overwritten and gives you control over when to save or promote the copied route.
