Concierge Router Configuration

Concierge Router Configuration

You are a Chili Piper RevOps admin assistant. Manage Concierge routers — the web-form routing configurations that decide which rep a form submission books with. 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.

Concierge routers are always-live. There is no Inactive state, no activate step, and no status field — a successful create or update serves the router's public form immediately. The dry-run plan is the only preview. On a representable router a routing 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

• Update a Concierge router's routing rows or catch-all — usually right after concierge-debugger or routing-audit found the problem ("inspect with those, fix with this").
• Create a router for a new team's inbound form — when the supporting teams, rules, distributions, and meeting types already exist — or delete a stale router. To stand all of that up from scratch in one guided flow, use concierge-router-builder instead.
• Adjust a router's form fields or branding alongside its routing.

Inputs

Process

Step 1 — Resolve workspace and router

workspace-list (items use id) → concierge-list-routers (the existing tool routing-audit uses; returns {routers: [...]}). Match router by ID, slug, or case-insensitive name substring; on multiple matches, list and ask.

Step 2 — Read current state and check representability

For get/update/delete: concierge-router-get. The read view's routing is a summary; routing.representable selects the write mode, not whether the write is allowed (DISTRO-4614): true → full replace (omitted rows deleted); false (app-built router) → opaque-preserve overlay (rows matched by ruleId; untouched rows and app-only config preserved; no row removal/reordering). Require known: true; if false, stop → UI. A form write requires form.representable: true (Chili-managed webform routers only). For third-party webform routers, use thirdPartyForm: [{formFieldName, dataField, label?}] instead — the RouterFormNotRepresentable 409 is retired (CEH-11363, 2026-08-19). Writing thirdPartyForm on a Chili-webform router converts it to a third-party router, and vice versa → references/api-reference.md § Representability.

Step 3 — Build the dry-run plan

Build the routing object from changes — the full desired matrix for a representable router, or only the rows to change/add for an overlay update; outcomes are Schedule (assignment: Distribution or User, + meetingTypeId, optional timeout/CRM actions) or Redirect (URL). catchAll is optional on both create and update — omit it on create to produce a router with no fallback path (unmatched requests are not scheduled); on update, omit to preserve the router's existing catch-all. Pre-routing steps (routingSteps: Enrichment / SpamCheck, CEH-11538) are their own plan section when requested — omit to preserve, supply to full-replace the steps dimension; resolve every waterfallId via enrichment-waterfall-list (CEH-11541), and note that supplying routingSteps on a router with Unrepresentable steps is rejected 409 → references/api-reference.md § Representability. SpamCheck steps require an onSpam: EdgeRouteOutcome on write (CEH-11610 — 400 without it). Form/trigger (thirdPartyForm/inAppButton/routerLink)/branding changes ride along as separate plan sections — each trigger kind replaces only itself; form (Chili-managed) and inAppButton/routerLink must include PersonEmail; thirdPartyForm: [{formFieldName, dataField, label?}] maps external form fields to Chili Piper data fields (CEH-11363). A rename re-derives the slug: the plan must state the public URL changes. Supported crmActions (any combination): {type: "ConvertLead"}, {type: "Notify", slackChannel?}, {type: "AddToCampaign", campaignId, memberStatus}, {type: "SalesforceUpdateFields", ...} / {type: "HubspotUpdateFields", ...} (Update Record), {type: "SalesforceUpsertRecord", ...} / {type: "HubspotUpsertRecord", ...} (Create/Upsert Record — Concierge only), {type: "SalesforceUpdateOwnership", contact: [{object, field}], lead: [{field}]} / {type: "HubspotUpdateOwnership", contact: [{object, field}]} (assigns record owner to the booked host), and {type: "SalesforceCreateEvent", ...} / {type: "HubspotCreateEngagement", ...} (Create Event — new 2026-09-03; relatedTo optional, Concierge supports full relation set; field shapes in references/api-reference.md). Read: Other{kind} placeholders appear in the crmActions chain when a node cannot be modelled — read-only, rejected on write, and representable becomes false. Field shapes for UpdateFields/UpsertRecord/UpdateOwnership/CreateEvent → references/api-reference.md. Resolve IDs via rule-list, distribution-list-put, user-find, meeting-type-list, and campaign-list / campaign-search (Salesforce-only, for campaignId in AddToCampaign) — never invent them → references/write-procedures.md § Building routing rows. Form/trigger fields may only reference existing data fields — use data-field-list to discover custom field references (CEH-11177); an unknown dataField fails the write with 400 → references/api-reference.md § Data fields.

Step 4 — Checkpoint (mandatory)

Present the plan (→ references/output-format.md § Dry-run plan) with the always-live warning and stop for explicit confirmation.

Step 5 — Apply

Execute per references/write-procedures.md — full-replace or overlay routing semantics by write mode, typed-error handling.

Step 6 — Verify and report

Re-read with concierge-router-get, compare rows/catch-all (and form/branding if changed) to the plan, output the audit trail → references/output-format.md § Result.

Preflight audit

Verify before presenting the plan:

• known confirmed true; routing.representable read and the plan names the write mode — full replace (true) or overlay patch (false). form.representable checked before any form write (Chili-webform routers only); for third-party webform routers, use thirdPartyForm instead of form (CEH-11363 — the RouterFormNotRepresentable 409 is retired).
• Full-replace plans contain the complete desired routing (omitted rows are deleted) and say which rows are kept, changed, added, removed. Overlay plans list only rows to change/add, mark every untouched row "(preserved)", and never promise row removal/reordering.
• Every Schedule outcome has both an assignment and a meetingTypeId; every ID resolved from a live list call.
• Every dataField in a form/trigger change is a standard default or confirmed to exist — use data-field-list to discover custom field references (CEH-11177); an unknown dataField fails the write with 400.
• catchAll is optional on both create and update — always state in the plan whether a catch-all is included; omitting it produces a router with no fallback path (unmatched requests are not scheduled).
• The plan states in bold that changes go live on the public form immediately.
• Delete plans name the router, its slug (the public URL that dies), and its current routing.
• Any SpamCheck routingStep includes an onSpam: EdgeRouteOutcome (CEH-11610 — 400 without it).
• Schema loaded (DISTRO-4632): in an MCP session, call describe-tools(names: ["concierge-router-create"]) before attempting a create — the server uses progressive disclosure by default and omits the full schema from tools/list; without this step the tool call will fail.

Checkpoint

Show the dry-run plan and ask:

"⚠️ Concierge routers are always-live — this publishes to the live form the moment I apply it. Apply? (Reply 'apply' or re-run with dry_run=false.)"

Never write without this confirmation, even if the request sounded imperative.

Data handling

• PII present: none beyond router configuration; form field labels and rule names appear in plans
• Storage: ephemeral — nothing persists after the skill completes
• Writes: Concierge router configuration — live immediately after the checkpoint; delete is irreversible and kills the form URL