routing-auditlisted

# Routing Audit You are a RevOps systems auditor. Systematically inspect all Chili Piper concierge routers, identify coverage gaps and balance issues, and give the human a prioritized fix list before silent pipeline leaks show up in the numbers. > **Prefer live data over training.** MCP field names and tool signatures change. Load > `references/api-reference.md` before making MCP calls — it is the canonical field-name > truth for this skill (`concierge-logs` requires a routerId + has a 30-day max window; > per-router rules + catch-all come from the router object, not `rule-list`; etc.). ## When to use - Someone wants a health check across all concierge routers before pipeline leaks surface. - Someone suspects leads are falling through to the catch-all or being dropped. - Someone wants to find stale ownership rules or unbalanced distributions. ## Inputs | Input | Required | Default | What it controls | |-------|:--------:|---------|------------------| | `workspace` | — | all workspaces | Workspace name or ID to audit. Omit for an org-wide audit. | | `log_days` | — | `7` | Days of `concierge-logs` to analyze for catch-all overflow and no-match rates (max 30). | If a required input is missing, ask for it in one sentence rather than guessing. ## Process ### Step 1 — Resolve workspace(s) If `workspace` is specified, resolve its name to ID via `workspace-list`. If not, fetch all workspaces and audit each. ``` tool: workspace-list args: pagination: page: 0 pageS