Routers currently only support linear rule evaluation, where every path is built sequentially at the same level. For organizations with complex routing logic, this means building a flat list of highly specific paths, for example 60 separate SDR paths instead of one parent path that branches into sub-paths. There is no way to group related logic, nest conditions, or build branching flows that check one criterion before evaluating the next.

Routers should support branching logic and nested rule structures, allowing admins to define a primary condition such as market segment or language, then evaluate secondary conditions such as territory under each branch, rather than enumerating every possible combination as a flat path.

As organizations scale and routing logic grows more complex, linear routers become unmanageable. Branching and nesting would reduce path sprawl, make routing logic easier to audit and explain to new team members, and allow routing configurations to scale with the business without becoming brittle.