As routing configurations grow, admin lists become cluttered and hard to navigate. There's no way to group related assets into folders, filter by active or inactive status, search by name, or hide unreleased configurations from view. Routers, distribution queues, routing rules, and teams all live in flat, unorganized lists, which makes routine maintenance, audits, and go-live staging slower than they need to be.
Requested behavior: Let admins organize routing assets into folders or categories across routers, distribution queues, routing rules, and teams. Within each asset list, support search by name or keyword, filtering by active/inactive status, and the ability to archive inactive configurations without deleting them. Assets staged for a future go-live should be hideable from the default view until they're ready to launch.
Why it matters: Organizations that have been on Chili Piper for multiple years accumulate dozens or hundreds of routing assets. Without organizational structure, admins waste time scrolling through noise to find what's active, can't safely retire old assets without losing them, and have no clean way to manage staged configurations during go-lives or quarterly audits. Teams managing rules across multiple use cases, regions, or products especially feel this, since routine maintenance becomes error-prone when you can't quickly scope down the view.