There is no way to export a summary of routing rules from Chili Piper. Admins who need to audit their rule library, track which rules are active or inactive, identify stale configurations, or share a snapshot of their routing setup with stakeholders have no way to get this information out of the product in a structured format.

Admins should be able to export a CSV report of their routing rules that includes at minimum the rule name, active/inactive status, last published date, and last modified date.

Routing rule libraries grow quickly and become difficult to manage without an external view. A simple metadata export gives ops teams the ability to audit their configuration, identify rules that haven't been updated in a long time, and maintain documentation of their routing setup without manual data entry. This is a basic governance capability that's standard in any tool managing complex configuration at scale.