Category: Inbound | Node Type: Voice |Version: 1.0 | Last Updated: Nov 2025
Overview
The Route Node is one of the most powerful and flexible components in Logixx Studio. It allows you to direct calls to different destinations based on:
The routing type you select
Time of day, day of week, or date
Caller’s area code or state
CRM data (e.g., application stage, workflow status, days in status, app date)
Data retrieved from external sources via GET request
Custom conditions built from multiple logic groups (ANY/ALL)
The Route Node is used to build advanced, dynamic call flows where routing decisions change automatically depending on live conditions.
⚙️ Routing Types
When configuring the Route Node, users select one of the following routing methods:
1. Direct Dial
Routes the caller to one single destination:
A phone number
A user extension
An AI Agent
A Queue and more..
This is the simplest routing type.
2. Multi Dial (Up to 10 Destinations)
Allows you to configure up to 10 target destinations that ring simultaneously.
The first destination to answer receives the call
All other ringing targets are cancelled automatically
Ideal for:
Agent groups
Shared lines
Sales or support teams
Warm-transfer alternatives
3. Conditional Routing
Select this when you want routing decisions to be made based on rules and conditions.
This supports:
✓ Time-based routing
Specific days
Time windows
Business hours
Holidays or date ranges
✓ Geographic routing
Route by state
Route by area code
Route by caller location patterns
✓ CRM integration routing
Leverage CRM parameters such as:
Application Date
Workflow stage
Workflow status
Days in status
Last status
Assignment or ownership
CRM organization metadata
✓ Custom Conditions
Use external data by supplying a source, commonly:
A GET request to another system
Data from your external sources
Parameters included in your inbound metadata
✓ Advanced Logic
Create multiple condition groups using:
ALL conditions must be true (similar to AND logic)
ANY condition may be true (similar to OR logic)
Each rule can contain:
Multiple conditions
Multiple groups
A unique outcome destination
You can add as many rules as needed, and the system evaluates them in order.
⚙️ How Conditional Evaluation Works
When a call reaches the Route Node with Conditional Routing selected:
The system gathers the available data (timestamp, caller location, CRM data, custom parameters).
Each rule is evaluated using the condition logic you configured.
Conditions support comparisons such as:
Equals
Contains
Starts with
Greater/Less than
In/Not In
If ALL conditions in a rule match (using ALL logic) or if ANY condition matches (using ANY logic), the rule is considered a match.
The call is routed to the destination assigned to the first matching rule.
If no rules match, the flow follows your fallback route (if configured).
No technical implementation details, rule engines, or code are required—the UI handles all logic with simple condition blocks.
Node Settings
Setting | Type | Description |
Routing Type | Dropdown | Choose Direct Dial, Multi Dial, or Conditional. |
Destinations | Single or Multiple | Phone numbers, extensions, teams, agents, or AI routing destinations. |
Rules (Conditional only) | Builder UI | Add groups and conditions using ANY/ALL logic. |
Default Destination | Required | Where to route the call if no conditions match. |
Troubleshooting & Tips
Ensure conditions are ordered correctly—rules are evaluated top to bottom.
Use ANY logic for “match if any of these conditions are true.”
Use ALL logic for “match only when every condition is true.”
For multi-dial groups, choose destinations with good variety of availability.
If a call is not routing as expected, check:
Inbound Routing Logs
Call Events
Conditional Rule matches
For complex CRM routing, verify the field values your CRM is supplying.