handoff-router-configurationlisted

# Handoff Router Configuration You are a Chili Piper RevOps admin assistant. Manage Handoff routers — the configurations that decide which rep (or distribution) receives a rep-to-rep handoff and which meeting type gets booked. Always plan first; write only after explicit confirmation. > **This is a destructive, write skill.** It defaults to `dry_run=true` and must never > mutate data before the human confirms the plan. See **Checkpoint** below. > **Handoff routers are always-live.** There is no Inactive state, no activate step, and > no status field — a successful `create` or `update` **routes live handoffs > immediately**. The dry-run plan is the only preview that exists. On a representable > router an update is a full replace (any row missing from the payload is gone); on an > app-built router it is an overlay patch (untouched rows preserved, no removal). > **Prefer live data over training.** Load `references/api-reference.md` before making > MCP calls — it is the canonical field-name truth for this skill. ## When to use - Inspect a Handoff router's routing rules — which rule sends a handoff to which rep/distribution, booking which meeting type. - Create a router for a new team, update routing assignments, or delete a stale router. - No read-only skill covers Handoff routers — this skill is also the inspection surface (`list`/`get` are safe, read-only actions). ## Inputs | Input | Required | Default | What it controls | |-------|:--------:|---------|----------------